[Desktop-packages] [Bug 1964795] Re: gnome-keyring-daemon crashed with signal 7
** Changed in: gnome-keyring Status: Unknown => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1964795 Title: gnome-keyring-daemon crashed with signal 7 Status in GNOME Keyring: Fix Released Status in gnome-keyring package in Ubuntu: Fix Committed Bug description: Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 gnome-keyring: Installed: 40.0-3ubuntu1 Candidate: 40.0-3ubuntu1 Version table: *** 40.0-3ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages 100 /var/lib/dpkg/status Background process crashes unexpectedly a few moments after login. I'm running the dev release of Jammy on a Raspberry Pi 400 with all updates applied. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-keyring 40.0-3ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-1003.3-raspi 5.15.19 Uname: Linux 5.15.0-1003-raspi aarch64 ApportVersion: 2.20.11-0ubuntu79 Architecture: arm64 CasperMD5CheckResult: unknown Date: Mon Mar 14 15:26:41 2022 Disassembly: => 0x: Cannot access memory at address 0x ExecutablePath: /usr/bin/gnome-keyring-daemon ImageMediaBuild: 20201022 ProcCmdline: /usr/bin/gnome-keyring-daemon --daemonize --login ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_GB.UTF-8 LANGUAGE=en_GB:en XDG_RUNTIME_DIR= Signal: 7 SourcePackage: gnome-keyring StacktraceTop: () () () at /lib/aarch64-linux-gnu/libgio-2.0.so.0 g_signal_emit_valist () at /lib/aarch64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () at /lib/aarch64-linux-gnu/libgobject-2.0.so.0 Title: gnome-keyring-daemon crashed with signal 7 UpgradeStatus: Upgraded to jammy on 2022-03-07 (6 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/1964795/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969460] Re: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings
** Also affects: software-properties (Ubuntu Jammy) Importance: Undecided Status: New ** Changed in: software-properties (Ubuntu Jammy) Milestone: None => ubuntu-22.04.1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1969460 Title: software-properties-gtk crashed with TypeError in on_driver_selection_changed(): Expected a string or a pair of strings Status in OEM Priority Project: New Status in software-properties package in Ubuntu: Fix Committed Status in software-properties source package in Jammy: New Bug description: 1) The release of Ubuntu you are using, via 'lsb_release -rd' or System -> About Ubuntu Ubuntu 22.04 2) The version of the package you are using, via 'apt-cache policy pkgname' or by checking in Software Center software-properties-gtk 0.99.22 3) What you expected to happen No crash when using Additional Drivers with ppa:oem-solutions-group/intel-ipu6 on Dell XPS 13 9320 It can install libcamhal-ipu6ep0 from Additional Drivers without any problem. 4) What happened instead It crashed when selecting libcamhal-ipu6ep0 in Additional Drivers To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/1969460/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1976249] Re: `xvfb-run` doesn't support `--auto-servernum`
Hi, thanks for the response! I'm also not sure how this package works, where is its source, where is the upstream, etc. However, as I said, on Arch Linux `auto-servernum` is marked as deprecated. Googling `auto- display` leads to some information (also on other distros): https://bugs.archlinux.org/task/65039 https://bugzilla.redhat.com/show_bug.cgi?id=1787684 ** Bug watch added: Red Hat Bugzilla #1787684 https://bugzilla.redhat.com/show_bug.cgi?id=1787684 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1976249 Title: `xvfb-run` doesn't support `--auto-servernum` Status in xorg-server package in Ubuntu: New Bug description: `xvfb` is at version `2:21.1.3-2ubuntu2` which is the latest one. However, `xvfb-run -h` doesn't show the `--auto-display` argument and running `xvfb-run --auto-display ls` leads to `xvfb-run: unrecognized option '--auto-display'`. This is strange because in Arch Linux, the same `xvfb-run` version does support `--auto-display`. On Ubuntu one must use `--auto-servernum` because of that but that has been deprecated for quite a while now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1976249/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 874181] Re: brltty daemon prevents creation of ttyUSB0 device link
I just run into this issue after upgrading from 20.04. This is breaking a lot of things for me. It seems that "apt remove brltty" resolved the issue for now, but it should work out of the box as it used to. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/874181 Title: brltty daemon prevents creation of ttyUSB0 device link Status in brltty package in Ubuntu: Confirmed Status in brltty source package in Oneiric: Fix Released Bug description: Impact: This bug is somewhat hardware specific, affecting all users of the USB serial controller, device 10c4:ea60. Test case: With the current version of brltty in Oneiric, brltty takes over any device using the above mentioned USB serial controller, whether it is a Braille display or not. This is because one of Brltty's supported displays uses this USB serial control internally for ocmmunication. The brltty package in oneiric-proposed has the udev rule for this controller commented out, allowing other users of devices based on this controller to work properly. Regression potential: All users of the supported Seika will have to load Brltty manually, as the udev rule for their device is commented out, to allow other USB serial controller users to use their device as a proper serial device. Original description follows: After upgrading from Ubuntu 11.04 to 11.10, I no longer found a '/dev/ttyUSB0' for my serial-to-USB converter. The device is part of a Xilinx FPGA board and is a "10c4:ea60 Cygnal Integrated Products, Inc. CP210x Composite Device". Every time I plugged in the device, dmesg showed the device coming up and 'brltty' did *something* to it. At this point, no device was present in '/dev'. [ 5181.130942] cp210x 1-1.4:1.0: cp210x converter detected [ 5181.203658] usb 1-1.4: reset full speed USB device number 5 using ehci_hcd [ 5181.296637] usb 1-1.4: cp210x converter now attached to ttyUSB0 [ 5181.623749] usb 1-1.4: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 After removing 'brltty', the '/dev/ttyUSB0' device appears again like it used to. ProblemType: Bug DistroRelease: Ubuntu 11.10 Package: brltty (not installed) ProcVersionSignature: Ubuntu 3.0.0-12.20-generic 3.0.4 Uname: Linux 3.0.0-12-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 1.23-0ubuntu3 Architecture: amd64 Date: Fri Oct 14 14:39:29 2011 InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007) ProcEnviron: LANGUAGE= LC_TIME=C LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: brltty UpgradeStatus: Upgraded to oneiric on 2011-10-13 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/874181/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956438] Re: confusing UI -- expected a LAN file share, not DLNA, and '+' button is not apparent
** Changed in: gnome-control-center Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1956438 Title: confusing UI -- expected a LAN file share, not DLNA, and '+' button is not apparent Status in gnome-control-center: New Status in gnome-control-center package in Ubuntu: Triaged Bug description: is this the right package for the media sharing UI in settings on ubuntu 21.10? i was just trying to set up a local network share and the UI for "media sharing" made me think ubuntu thought "people want to share music, video, and pictures folders, so we'll just have those preselected as shareable directories on the network." i know what DLNA is, but it never entered my mind that's what this was for. it should just say something like "via DLNA to things like smart tv's" or something. also, the box that music, videos, and pictures is in is exactly filled up by those 3 buttons, and the "+" button below them is not visible, so it is not apparent you can scroll down and it is there. put the '+' button outside the box so it can't be scrolled away, and show the directories just like normal directories in the file viewer, not as buttons. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1956438/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956438] Re: confusing UI -- expected a LAN file share, not DLNA, and '+' button is not apparent
Thanks. It's a bit tricky, reporting on launchpad is a right starting point but upstream are the ones deciding of design choices so more suitable for such cases ** Changed in: gnome-control-center (Ubuntu) Status: New => Triaged ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1880 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1956438 Title: confusing UI -- expected a LAN file share, not DLNA, and '+' button is not apparent Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Bug description: is this the right package for the media sharing UI in settings on ubuntu 21.10? i was just trying to set up a local network share and the UI for "media sharing" made me think ubuntu thought "people want to share music, video, and pictures folders, so we'll just have those preselected as shareable directories on the network." i know what DLNA is, but it never entered my mind that's what this was for. it should just say something like "via DLNA to things like smart tv's" or something. also, the box that music, videos, and pictures is in is exactly filled up by those 3 buttons, and the "+" button below them is not visible, so it is not apparent you can scroll down and it is there. put the '+' button outside the box so it can't be scrolled away, and show the directories just like normal directories in the file viewer, not as buttons. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1956438/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1976161] Re: Session restarts when opening Pluma or GitHub link in browser
Time that I opened Firefox through the GUI. mai 30 16:40:37 fernando-Latitude-E5500 systemd[1562]: Started snap.firefox.firefox.b2449455-56d8-4537-8f78-5f51a04cd9a5.scope. First logs after I entered the link at Firefox. mai 30 16:41:43 fernando-Latitude-E5500 rtkit-daemon[1259]: Supervising 7 threads of 4 processes of 1 users. mai 30 16:41:43 fernando-Latitude-E5500 rtkit-daemon[1259]: Supervising 7 threads of 4 processes of 1 users. mai 30 16:41:43 fernando-Latitude-E5500 pulseaudio[1575]: X11 I/O error handler called mai 30 16:41:43 fernando-Latitude-E5500 at-spi-bus-launcher[1921]: X connection to :0 broken (explicit kill or server shutdown). 16:41:43 is the exact time the session crashed. ** Attachment added: "Logs reproducing the issue." https://bugs.launchpad.net/ubuntu-mate/+bug/1976161/+attachment/5593923/+files/journalctl-after-issue.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1976161 Title: Session restarts when opening Pluma or GitHub link in browser Status in Ubuntu MATE: New Status in firefox package in Ubuntu: Incomplete Status in snapd package in Ubuntu: Incomplete Bug description: From a fresh install with Ubuntu Mate 22.04, do: 1. Login into your user with password. 2. Open Firefox. 3. Enter "https://github.com/pimlie/ubuntu-mainline-kernel.sh; at URL address. 4. GUI will reset and go back to login screen like started a new session. This also happens when I tried with opening a '.log' with Pluma. I've tried a lot of things at other installation to tackle this problem, but I couldn't solve the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-27 (1 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Snap: snapd 2.55.5 (latest/stable) Snap.Changes: ID Status Spawn Ready Summary 3Done2022-05-28T10:43:02-03:00 2022-05-28T10:46:00-03:00 Auto-refresh snaps "core20", "firefox", "snapd" Tags: jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1976161/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964601] Re: I have no processor!
I'm attaching the full outputs as a tarball (just in case they're useful) but here's the pertinent bits too: $ tail -n 13 /proc/cpuinfo processor : 3 BogoMIPS: 108.00 Features: fp asimd evtstrm crc32 cpuid CPU implementer : 0x41 CPU architecture: 8 CPU variant : 0x0 CPU part: 0xd08 CPU revision: 3 Hardware: BCM2835 Revision: c03131 Serial : 1000acbea889 Model : Raspberry Pi 400 Rev 1.1 It looks like "Model" would be the most appropriate field to report here. Looking at the upstream bug it's querying a "Model name" field (which appears per-CPU on my PC) but not a "Model" field in the final section (though on my PC there is no final section, just the per-CPU sections). On glxinfo: $ glxinfo | grep 'OpenGL renderer' OpenGL renderer string: V3D 4.2 I'm attaching two cases of the udisksctl output. The first (udisk_sd.log) is from a "typical" installation of Ubuntu Desktop for Pi on an SD card. The second (udisk_usb.log) is from the same Pi booting from a USB-attached SSD (which is a fairly common configuration for booting the desktop). Should I post these bits upstream too? ** Attachment added: "1964601.tar.gz" https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1964601/+attachment/5593907/+files/1964601.tar.gz -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1964601 Title: I have no processor! Status in gnome-control-center package in Ubuntu: Incomplete Bug description: At least according to gnome-control-center anyway. Running the Ubuntu Desktop for Raspberry Pi image on a Pi 400 (or a Pi 4B), selecting Settings, then the "About" page shows that gnome- control-center thinks the processor is "", the graphics are "unknown", and apparently so is the disk capacity! I admit it's a trivial thing, but it's been this way since at least hirsute, and it'd be nice to see something vaguely sane in there at some point :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1964601/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1976161] Re: Session restarts when opening Pluma or GitHub link in browser
** Attachment removed: "journalctl-after-issue.log" https://bugs.launchpad.net/ubuntu-mate/+bug/1976161/+attachment/5593896/+files/journalctl-after-issue.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1976161 Title: Session restarts when opening Pluma or GitHub link in browser Status in Ubuntu MATE: New Status in firefox package in Ubuntu: Incomplete Status in snapd package in Ubuntu: Incomplete Bug description: From a fresh install with Ubuntu Mate 22.04, do: 1. Login into your user with password. 2. Open Firefox. 3. Enter "https://github.com/pimlie/ubuntu-mainline-kernel.sh; at URL address. 4. GUI will reset and go back to login screen like started a new session. This also happens when I tried with opening a '.log' with Pluma. I've tried a lot of things at other installation to tackle this problem, but I couldn't solve the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-27 (1 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Snap: snapd 2.55.5 (latest/stable) Snap.Changes: ID Status Spawn Ready Summary 3Done2022-05-28T10:43:02-03:00 2022-05-28T10:46:00-03:00 Auto-refresh snaps "core20", "firefox", "snapd" Tags: jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1976161/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1976161] Re: Session restarts when opening Pluma or GitHub link in browser
I don't recall which time exactly, sorry! I will delete the previous log and send a new one with the time it crashed. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1976161 Title: Session restarts when opening Pluma or GitHub link in browser Status in Ubuntu MATE: New Status in firefox package in Ubuntu: Incomplete Status in snapd package in Ubuntu: Incomplete Bug description: From a fresh install with Ubuntu Mate 22.04, do: 1. Login into your user with password. 2. Open Firefox. 3. Enter "https://github.com/pimlie/ubuntu-mainline-kernel.sh; at URL address. 4. GUI will reset and go back to login screen like started a new session. This also happens when I tried with opening a '.log' with Pluma. I've tried a lot of things at other installation to tackle this problem, but I couldn't solve the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-27 (1 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Snap: snapd 2.55.5 (latest/stable) Snap.Changes: ID Status Spawn Ready Summary 3Done2022-05-28T10:43:02-03:00 2022-05-28T10:46:00-03:00 Auto-refresh snaps "core20", "firefox", "snapd" Tags: jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1976161/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1976302] [NEW] software-properties Additional Drivers tab informational text enhancement
Public bug reported: The Kubuntu installation process offers this check-box on the second screen: "Install third-party software for graphics and Wi-Fi hardware, Flash, MP3 and other media" box while installing Kubuntu as another form of manual installation." If you check that box, your video drivers are handled for you by a collaboration between Ubuntu and NVIDIA. The "Additional Drivers" tab in Software Sources then displays these messages when you open it: * "This device is using a manually-installed driver." * "Continue using a manually installed driver" * "No proprietary drivers are in use." It wasn't obvious to me that "manually-installed" included those of us who checked the little check-box during the installation of the operating system to have our video drivers automatically installed and managed by Ubuntu and NVIDIA. I would like to suggest that the first two messages in the "Additional Drivers" tab get changed to something like this to make it obvious that they include us: * "This device is using a manually-installed or third-party driver." * "Continue using a manually-installed or third-party driver" Or if you'd like to word it differently: * "This device is using a manually-installed or automatically-installed driver." * "Continue using a manually-installed or automatically-installed driver" ** Affects: software-properties (Ubuntu) Importance: Undecided Status: New ** Attachment added: "The two places in which the text appears in the "Additional "Drivers" tab are marked here with arrows." https://bugs.launchpad.net/bugs/1976302/+attachment/5593898/+files/AdditionalDriversTab.png -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to software-properties in Ubuntu. https://bugs.launchpad.net/bugs/1976302 Title: software-properties Additional Drivers tab informational text enhancement Status in software-properties package in Ubuntu: New Bug description: The Kubuntu installation process offers this check-box on the second screen: "Install third-party software for graphics and Wi-Fi hardware, Flash, MP3 and other media" box while installing Kubuntu as another form of manual installation." If you check that box, your video drivers are handled for you by a collaboration between Ubuntu and NVIDIA. The "Additional Drivers" tab in Software Sources then displays these messages when you open it: * "This device is using a manually-installed driver." * "Continue using a manually installed driver" * "No proprietary drivers are in use." It wasn't obvious to me that "manually-installed" included those of us who checked the little check-box during the installation of the operating system to have our video drivers automatically installed and managed by Ubuntu and NVIDIA. I would like to suggest that the first two messages in the "Additional Drivers" tab get changed to something like this to make it obvious that they include us: * "This device is using a manually-installed or third-party driver." * "Continue using a manually-installed or third-party driver" Or if you'd like to word it differently: * "This device is using a manually-installed or automatically-installed driver." * "Continue using a manually-installed or automatically-installed driver" To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/software-properties/+bug/1976302/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] Re: Wifi hotspot not configured correctly on restart
I have also reported the issue upstream: https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1016 ** Bug watch added: gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues #1016 https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues/1016 ** Description changed: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). - The expectation is that the hotpot to be fully functional on startup + The expectation is that the hotspot is fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. - Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) - --- + --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: - default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 - 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 - 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 - 169.254.0.0/16 dev enp2s0 scope link metric 1000 - 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 + default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 + 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 + 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 + 169.254.0.0/16 dev enp2s0 scope link metric 1000 + 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: - RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN - running 1.36.4 connected started full enabled enabled enabled enabled enabled + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: New Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotspot is fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64
[Desktop-packages] [Bug 1956438] Re: confusing UI -- expected a LAN file share, not DLNA, and '+' button is not apparent
ok, submitted here: https://gitlab.gnome.org/GNOME/gnome-control- center/-/issues/1880 this issue tracker needs some indicator to the unsophisticates telling us when to use one vs the other? ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1880 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1880 -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1956438 Title: confusing UI -- expected a LAN file share, not DLNA, and '+' button is not apparent Status in gnome-control-center package in Ubuntu: New Bug description: is this the right package for the media sharing UI in settings on ubuntu 21.10? i was just trying to set up a local network share and the UI for "media sharing" made me think ubuntu thought "people want to share music, video, and pictures folders, so we'll just have those preselected as shareable directories on the network." i know what DLNA is, but it never entered my mind that's what this was for. it should just say something like "via DLNA to things like smart tv's" or something. also, the box that music, videos, and pictures is in is exactly filled up by those 3 buttons, and the "+" button below them is not visible, so it is not apparent you can scroll down and it is there. put the '+' button outside the box so it can't be scrolled away, and show the directories just like normal directories in the file viewer, not as buttons. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956438/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973387] Re: Application hangs when select "Document Properties" in an empty document
Ah, great, thanks for figuring out the details! ** Changed in: gnome-text-editor (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-text-editor in Ubuntu. https://bugs.launchpad.net/bugs/1973387 Title: Application hangs when select "Document Properties" in an empty document Status in gnome-text-editor package in Ubuntu: Fix Released Bug description: Problem summary: When you select "Document Properties" in an empty document the application hangs sending dozens of messages like this (can be seen with journalctl): gtk_widget_measure: assertion 'for_size >= -1' failed Steps to reproduce: --- - Open gnome-text-editor (a new document, so empty) - Select "Document Properties" in menu - Application hangs with these repeated messages: gtk_widget_measure: assertion 'for_size >= -1' failed Tested in amd64 and arm64. Aditional info: --- No apport info because it doesn't crash, just hangs. # lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 # apt-cache policy gnome-text-editor gnome-text-editor: Instalados: 42.1-0ubuntu1 Candidato: 42.1-0ubuntu1 Tabla de versión: *** 42.1-0ubuntu1 500 500 http://archive.ubuntu.com/ubuntu jammy-updates/universe amd64 Packages 100 /var/lib/dpkg/status 42.0-2 500 500 http://archive.ubuntu.com/ubuntu jammy/universe amd64 Packages To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-text-editor/+bug/1973387/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] Re: Wifi hotspot not configured correctly on restart
thanks ** Changed in: network-manager (Ubuntu) Status: Incomplete => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: New Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1976179] Re: evince does not print
And do you have any error in /var/log/cups/error_log ? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1976179 Title: evince does not print Status in evince package in Ubuntu: Incomplete Bug description: Since Update from 20.04 -> 22.04, I am not able to print via evince, ocular is working. $ cat /etc/lsb-release DISTRIB_ID=Ubuntu DISTRIB_RELEASE=22.04 DISTRIB_CODENAME=jammy DISTRIB_DESCRIPTION="Ubuntu 22.04 LTS" When starting evince in terminal, it produces the following output: $ evince ./reise_scheng_formular.pdf\;jsessionid\=581D11B486915D0476F672CBA29B8143.pdf (evince:48073): dbind-WARNING **: 11:51:05.921: Couldn't connect to accessibility bus: Failed to connect to socket /run/user/1000/at-spi/bus_1: Permission denied Gtk-Message: 11:51:05.959: Failed to load module "unity-gtk-module" Gtk-Message: 11:51:05.960: Failed to load module "unity-gtk-module" When I print, I see a small blinking of the lcd display of CANON MX PIXMA 920 printer. The printer dialog says: processing stopped. It could not be restarted. Printing from OCULAR or LibreOffice works still fine. Assumed some rights problems?? To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1976179/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1957779] Re: Regression: GNOME-specific interfaces not available in main
** Changed in: xdg-desktop-portal-gtk (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1957779 Title: Regression: GNOME-specific interfaces not available in main Status in xdg-desktop-portal-gtk package in Ubuntu: Fix Released Bug description: Historically, xdg-desktop-portal-gtk had two roles: * Generic GTK implementations of various interfaces, suitable for all GTK desktops (GNOME, XFCE, etc.) and also as a fallback implementation for desktops that do not have something more "native". Interfaces: Access, Account, AppChooser, Email, FileChooser, Inhibit, Lockdown, Notification, Print, Settings. * GNOME-specific implementations of various interfaces, suitable for GNOME Shell only (and mybe Budgie, but not XFCE, MATE or Cinnamon because they do not use gnome-settings-daemon or a libmutter-based compositor). Interfaces: Background, Remote Desktop, Screencast, Screenshot, Wallpaper. In 1.10.0-2, these roles were separated: * Generic GTK stuff is still in x-d-p-gtk * GNOME-specific functionality has moved to x-d-p-gnome, a separate source package, which is installed by the gnome-core metapackage in Debian In Ubuntu, x-d-p-gtk is in main but x-d-p-gnome is in universe (and presumably not installed by default). This means that users of Snap and Flatpak apps will not have access to the affected interfaces via xdg-desktop-portal any more, which is a regression, particularly if using native Wayland rather than X11. There are two possible solutions to this: 1. Move x-d-p-gnome to main, and install it by default (in any installation that has GNOME Shell). GNOME upstream consider it to be part of a complete GNOME desktop. This is the long-term solution. 2. Patch x-d-p-gtk to reinstate the build-dependencies that were disabled in 1.10.0-2, and re-enable them in d/rules. This provides an older version of these interfaces, which is no longer routinely tested by upstream or Debian. This solution will probably stop working in a future release when these interfaces are removed completely. I would recommend the first solution for Ubuntu 22.04 LTS. I am probably going to use the second solution in Debian bullseye- backports, and if Ubuntu people want to maintain a backport of x-d-p- gtk to older suites like focal, it's probably the right thing to do for those too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1957779/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1976161] Re: Session restarts when opening Pluma or GitHub link in browser
could you also tell us at what time exactly the session closed in that log and on what action to try to match the error? -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1976161 Title: Session restarts when opening Pluma or GitHub link in browser Status in Ubuntu MATE: New Status in firefox package in Ubuntu: Incomplete Status in snapd package in Ubuntu: Incomplete Bug description: From a fresh install with Ubuntu Mate 22.04, do: 1. Login into your user with password. 2. Open Firefox. 3. Enter "https://github.com/pimlie/ubuntu-mainline-kernel.sh; at URL address. 4. GUI will reset and go back to login screen like started a new session. This also happens when I tried with opening a '.log' with Pluma. I've tried a lot of things at other installation to tackle this problem, but I couldn't solve the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-27 (1 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Snap: snapd 2.55.5 (latest/stable) Snap.Changes: ID Status Spawn Ready Summary 3Done2022-05-28T10:43:02-03:00 2022-05-28T10:46:00-03:00 Auto-refresh snaps "core20", "firefox", "snapd" Tags: jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1976161/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1957779] Re: Regression: GNOME-specific interfaces not available in main
** Tags added: jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-desktop-portal-gtk in Ubuntu. https://bugs.launchpad.net/bugs/1957779 Title: Regression: GNOME-specific interfaces not available in main Status in xdg-desktop-portal-gtk package in Ubuntu: Fix Committed Bug description: Historically, xdg-desktop-portal-gtk had two roles: * Generic GTK implementations of various interfaces, suitable for all GTK desktops (GNOME, XFCE, etc.) and also as a fallback implementation for desktops that do not have something more "native". Interfaces: Access, Account, AppChooser, Email, FileChooser, Inhibit, Lockdown, Notification, Print, Settings. * GNOME-specific implementations of various interfaces, suitable for GNOME Shell only (and mybe Budgie, but not XFCE, MATE or Cinnamon because they do not use gnome-settings-daemon or a libmutter-based compositor). Interfaces: Background, Remote Desktop, Screencast, Screenshot, Wallpaper. In 1.10.0-2, these roles were separated: * Generic GTK stuff is still in x-d-p-gtk * GNOME-specific functionality has moved to x-d-p-gnome, a separate source package, which is installed by the gnome-core metapackage in Debian In Ubuntu, x-d-p-gtk is in main but x-d-p-gnome is in universe (and presumably not installed by default). This means that users of Snap and Flatpak apps will not have access to the affected interfaces via xdg-desktop-portal any more, which is a regression, particularly if using native Wayland rather than X11. There are two possible solutions to this: 1. Move x-d-p-gnome to main, and install it by default (in any installation that has GNOME Shell). GNOME upstream consider it to be part of a complete GNOME desktop. This is the long-term solution. 2. Patch x-d-p-gtk to reinstate the build-dependencies that were disabled in 1.10.0-2, and re-enable them in d/rules. This provides an older version of these interfaces, which is no longer routinely tested by upstream or Debian. This solution will probably stop working in a future release when these interfaces are removed completely. I would recommend the first solution for Ubuntu 22.04 LTS. I am probably going to use the second solution in Debian bullseye- backports, and if Ubuntu people want to maintain a backport of x-d-p- gtk to older suites like focal, it's probably the right thing to do for those too. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-desktop-portal-gtk/+bug/1957779/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969340] Re: onboard hover click cant be activated
please run apport-collect 1969340 ** Tags added: impish jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to onboard in Ubuntu. https://bugs.launchpad.net/bugs/1969340 Title: onboard hover click cant be activated Status in Onboard: New Status in onboard package in Ubuntu: New Bug description: Hover click cant be activated on ubuntu 21.10 i launch onboard in a terminal and when i try to activate Hover click, i see the following error : (mousetweaks:2139) : CRITICAL ** 11:06:12:270 : Not running in X11 environment. Aborting same problem in ubuntu mate 21.10 (with mousetweaks installed) and ubuntu 22.04 beta I have physical disability ,, the Hover click is very important for me Thanks To manage notifications about this bug go to: https://bugs.launchpad.net/onboard/+bug/1969340/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971984] Re: pcscd 1.9.5-3 do not start automatically, only manual
** Tags added: jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pcsc-lite in Ubuntu. https://bugs.launchpad.net/bugs/1971984 Title: pcscd 1.9.5-3 do not start automatically, only manual Status in pcsc-lite package in Ubuntu: Confirmed Bug description: Ubuntu Mate 22.04 with the latest updates. Problem is present with internal smart-card reader and also external usb smart-card reader. eid-viewer sees no card reader,but When i do: sudo pcscd -f it is working, also following the tips of Ludovic: https://ludovicrousseau.blogspot.com/2011/11/pcscd-auto-start-using-systemd.html sudo systemctl stop pcscd.socket sudo systemctl start pcscd.socket It is working until next restart. libacsccid1 version: 1.1.8-1 libccid version: 1.5.0-2 pcscd version: 1.9.5-3 eid-archive version: 2022.3 eid-mw version: 5.0.28v5.0.28-0u2204-1 eid-viewer version: 5.0.28v5.0.28-0u2204-1 In Firefox, my eid card is then also recognized, but only in the ESR version, but this is a know Mozilla bug. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pcsc-lite/+bug/1971984/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1976161] Re: Session restarts when opening Pluma or GitHub link in browser
Sebastien, here's the log file from the command after the issue. ** Attachment added: "journalctl-after-issue.log" https://bugs.launchpad.net/ubuntu-mate/+bug/1976161/+attachment/5593896/+files/journalctl-after-issue.log -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1976161 Title: Session restarts when opening Pluma or GitHub link in browser Status in Ubuntu MATE: New Status in firefox package in Ubuntu: Incomplete Status in snapd package in Ubuntu: Incomplete Bug description: From a fresh install with Ubuntu Mate 22.04, do: 1. Login into your user with password. 2. Open Firefox. 3. Enter "https://github.com/pimlie/ubuntu-mainline-kernel.sh; at URL address. 4. GUI will reset and go back to login screen like started a new session. This also happens when I tried with opening a '.log' with Pluma. I've tried a lot of things at other installation to tackle this problem, but I couldn't solve the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-27 (1 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Snap: snapd 2.55.5 (latest/stable) Snap.Changes: ID Status Spawn Ready Summary 3Done2022-05-28T10:43:02-03:00 2022-05-28T10:46:00-03:00 Auto-refresh snaps "core20", "firefox", "snapd" Tags: jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1976161/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1976161] Re: Session restarts when opening Pluma or GitHub link in browser
Hi Alberto, I used the "echo $XDG_SESSION_TYPE" to check the display server and it returned "x11", which I assume it's Xorg (don't know anything about this). I will attach the new logs for the commands you've asked. ** Attachment added: "Contains the commands asked by Alberto" https://bugs.launchpad.net/ubuntu-mate/+bug/1976161/+attachment/5593895/+files/xdg-snapdesk.zip -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to firefox in Ubuntu. https://bugs.launchpad.net/bugs/1976161 Title: Session restarts when opening Pluma or GitHub link in browser Status in Ubuntu MATE: New Status in firefox package in Ubuntu: Incomplete Status in snapd package in Ubuntu: Incomplete Bug description: From a fresh install with Ubuntu Mate 22.04, do: 1. Login into your user with password. 2. Open Firefox. 3. Enter "https://github.com/pimlie/ubuntu-mainline-kernel.sh; at URL address. 4. GUI will reset and go back to login screen like started a new session. This also happens when I tried with opening a '.log' with Pluma. I've tried a lot of things at other installation to tackle this problem, but I couldn't solve the problem. --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: MATE DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2022-05-27 (1 days ago) InstallationMedia: Ubuntu-MATE 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Snap: snapd 2.55.5 (latest/stable) Snap.Changes: ID Status Spawn Ready Summary 3Done2022-05-28T10:43:02-03:00 2022-05-28T10:46:00-03:00 Auto-refresh snaps "core20", "firefox", "snapd" Tags: jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo _MarkForUpload: True To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1976161/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958224] Re: brltty claiming cp210x devices on 22.04
** Changed in: brltty (Debian) Status: Unknown => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1958224 Title: brltty claiming cp210x devices on 22.04 Status in brltty package in Ubuntu: Fix Committed Status in brltty source package in Jammy: Confirmed Status in brltty package in Debian: Confirmed Bug description: * Impact The brltty udev rules are claiming generic devices IDs which makes some other devices like Arduino cards not able to interact with the serial port anymore * Test Case Try to use an Arduino over a cp210x or FTDI serial port, it should be able to talk to the computer * Regression potential There are some braille devices on the market using generic IDs which are going to stop working out of the box. Those devices are uncommon and it's arguably an hardware bugs they are using those IDs. --- Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy brltty: Installed: 6.4-2ubuntu1 brltty appears once again to be claiming cp210x devices with the vendor/product ID of: idVendor=10c4, idProduct=ea60 Example dmesg output: 999.215968] usb 3-6.3: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00 [ 999.215973] usb 3-6.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 999.215975] usb 3-6.3: Product: CP2103 USB to UART Bridge [ 999.215977] usb 3-6.3: Manufacturer: Silicon Labs [ 999.215978] usb 3-6.3: SerialNumber: 0005 [ 999.234070] usbcore: registered new interface driver usbserial_generic [ 999.234081] usbserial: USB Serial support registered for generic [ 999.235262] usbcore: registered new interface driver cp210x [ 999.235272] usbserial: USB Serial support registered for cp210x [ 999.235298] cp210x 3-6.3:1.0: cp210x converter detected [ 999.237039] usb 3-6.3: cp210x converter now attached to ttyUSB0 [ 999.300049] input: PC Speaker as /devices/platform/pcspkr/input/input41 [ 999.807223] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input42 [ 999.991926] usb 3-6.3: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 [ 999.995045] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [ 999.995066] cp210x 3-6.3:1.0: device disconnected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958224] Re: brltty claiming cp210x devices on 22.04
1. This is Debian bug report #667616. 2. *brltty* was installed when doing `do-release-upgrade` from 21.10 to 22.04 [2]. [1]: https://bugs.debian.org/667616 [2]: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/1976293 ** Bug watch added: Debian Bug tracker #667616 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667616 ** Also affects: brltty (Debian) via https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=667616 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to brltty in Ubuntu. https://bugs.launchpad.net/bugs/1958224 Title: brltty claiming cp210x devices on 22.04 Status in brltty package in Ubuntu: Fix Committed Status in brltty source package in Jammy: Confirmed Status in brltty package in Debian: Unknown Bug description: * Impact The brltty udev rules are claiming generic devices IDs which makes some other devices like Arduino cards not able to interact with the serial port anymore * Test Case Try to use an Arduino over a cp210x or FTDI serial port, it should be able to talk to the computer * Regression potential There are some braille devices on the market using generic IDs which are going to stop working out of the box. Those devices are uncommon and it's arguably an hardware bugs they are using those IDs. --- Distributor ID: Ubuntu Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 Codename: jammy brltty: Installed: 6.4-2ubuntu1 brltty appears once again to be claiming cp210x devices with the vendor/product ID of: idVendor=10c4, idProduct=ea60 Example dmesg output: 999.215968] usb 3-6.3: New USB device found, idVendor=10c4, idProduct=ea60, bcdDevice= 1.00 [ 999.215973] usb 3-6.3: New USB device strings: Mfr=1, Product=2, SerialNumber=3 [ 999.215975] usb 3-6.3: Product: CP2103 USB to UART Bridge [ 999.215977] usb 3-6.3: Manufacturer: Silicon Labs [ 999.215978] usb 3-6.3: SerialNumber: 0005 [ 999.234070] usbcore: registered new interface driver usbserial_generic [ 999.234081] usbserial: USB Serial support registered for generic [ 999.235262] usbcore: registered new interface driver cp210x [ 999.235272] usbserial: USB Serial support registered for cp210x [ 999.235298] cp210x 3-6.3:1.0: cp210x converter detected [ 999.237039] usb 3-6.3: cp210x converter now attached to ttyUSB0 [ 999.300049] input: PC Speaker as /devices/platform/pcspkr/input/input41 [ 999.807223] input: BRLTTY 6.4 Linux Screen Driver Keyboard as /devices/virtual/input/input42 [ 999.991926] usb 3-6.3: usbfs: interface 0 claimed by cp210x while 'brltty' sets config #1 [ 999.995045] cp210x ttyUSB0: cp210x converter now disconnected from ttyUSB0 [ 999.995066] cp210x 3-6.3:1.0: device disconnected To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brltty/+bug/1958224/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched
I upgraded from 21.10 to 22.04. This bug happens to me both in Wayland and Xorg (in Wayland this was fixed installing the Evince flatpak alongside the .deb. In Xorg, this doesn't work). I don't use any special directory. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched Status in evince package in Ubuntu: Confirmed Bug description: Just switched from Ubuntu 20.04 to 22.04 and realized that Document Viewer no longer open on the last viewed page and doesn't remember the side pane preference even after using the "Save Current Settings as Default" option. Kindly advise ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.1-3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:58:50 2022 InstallationDate: Installed on 2022-03-19 (34 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1969896/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970139] Re: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS
As a temporary (or final) solution just use another VNC or RDP Server. You can do that only if you use X11 because apart from gnome-remote- desktop there are no working desktop sharing utilities for Wayland. You've more info here: https://help.ubuntu.com/community/VNC/Servers For instance, I'm using vino VNC server, the old-but-gold sharing server for Ubuntu. I'm not only using it to remotely access an started user session. I also use it to access gdm remotely so I can start users sessions remotely directly from the greeter. This is something that I haven't managed to do with genome-remote-session because of it's way of store/access credentials. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1970139 Title: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS Status in gnome-remote-desktop package in Ubuntu: In Progress Bug description: # lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 # apt-cache policy gnome-remote-desktop gnome-remote-desktop: Instalados: 42.0-4ubuntu1 Candidato: 42.0-4ubuntu1 Tabla de versión: *** 42.0-4ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages 100 /var/lib/dpkg/status # uname -a Linux fpgrpi 5.15.0-1005-raspi #5-Ubuntu SMP PREEMPT Mon Apr 4 12:21:48 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux Summary of the bug: --- When I try to connect to gnome-remote-desktop using VNC to a Raspberry Pi 4 Model B Rev 1.4 (8Gb) under Ubuntu 22.04 LTS the VNC client can't connect (connection is refused). The connection passes the Password check validation but don't connect (sometimes shows screen garbage before disconnecting). I've used several VNC clients (Remmina in Ubuntu and Real VNC in Android) getting the same problem failing either in X11 or Wayland. Notes: - VNC connection does work in in previous Ubuntu 21.10 version with the same architecture (arm64) and same Raspberry Pi. - VNC connection also does work in amd64 machines with Ubuntu 22.04 LTS and gnome-remote-desktop 42.0-4ubuntu1, exactly the same software version that doesn't work on arm64 (Raspberry Pi). There is no apport info at all. Also there is almost no info in the journal regarding this problem. When I try to connect to VNC server it show this: On Wayland: --- abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 1884160 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 4169728 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8130560 bytes), total 32768 (slots), used 83 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Main process exited, code=killed, status=11/SEGV abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Failed with result 'signal'. abr 25 00:21:43 fpgrpi gnome-shell[1497]: D-Bus client with active sessions vanished abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 1. abr 25 00:21:43 fpgrpi systemd[1381]: Stopped GNOME Remote Desktop. abr 25 00:21:43 fpgrpi systemd[1381]: Starting GNOME Remote Desktop... abr 25 00:21:43 fpgrpi systemd[1381]: Started GNOME Remote Desktop. abr 25 00:21:43 fpgrpi gnome-remote-desktop-daemon[2125]: Cannot load libcuda.so.1 abr 25 00:21:43 fpgrpi gnome-remote-desktop-daemon[2125]: Cannot load libnvidia-encode.so.1 abr 25 00:21:43 fpgrpi gnome-remote-de[2125]: RDP server started abr 25 00:21:43 fpgrpi gnome-remote-de[2125]: VNC server started On X11: --- abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Main process exited, code=killed, status=11/SEGV abr 25 00:12:18 fpgrpi gnome-shell[3044]: D-Bus client with active sessions vanished abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Failed with result 'signal'. abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 19. abr 25 00:12:18 fpgrpi systemd[2859]: Stopped GNOME Remote Desktop. abr 25 00:12:18 fpgrpi systemd[2859]: Starting GNOME Remote Desktop... abr 25 00:12:18 fpgrpi systemd[2859]: Started
[Desktop-packages] [Bug 1973629] nmcli-dev.txt
apport information ** Attachment added: "nmcli-dev.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593893/+files/nmcli-dev.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] nmcli-con.txt
apport information ** Attachment added: "nmcli-con.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593892/+files/nmcli-con.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] WifiSyslog.txt
apport information ** Attachment added: "WifiSyslog.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593891/+files/WifiSyslog.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] RfKill.txt
apport information ** Attachment added: "RfKill.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593890/+files/RfKill.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] NetDevice.veth2665f1e.txt
apport information ** Attachment added: "NetDevice.veth2665f1e.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593882/+files/NetDevice.veth2665f1e.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] NetDevice.lo.txt
apport information ** Attachment added: "NetDevice.lo.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593881/+files/NetDevice.lo.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] NetworkManager.conf.txt
apport information ** Attachment added: "NetworkManager.conf.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593886/+files/NetworkManager.conf.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] NetDevice.veth3b712b0.txt
apport information ** Attachment added: "NetDevice.veth3b712b0.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593883/+files/NetDevice.veth3b712b0.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] NetDevice.wlp3s0.txt
apport information ** Attachment added: "NetDevice.wlp3s0.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593885/+files/NetDevice.wlp3s0.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] NetDevice.enp2s0.txt
apport information ** Attachment added: "NetDevice.enp2s0.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593880/+files/NetDevice.enp2s0.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] NetDevice.docker0.txt
apport information ** Attachment added: "NetDevice.docker0.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593879/+files/NetDevice.docker0.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] ProcEnviron.txt
apport information ** Attachment added: "ProcEnviron.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593889/+files/ProcEnviron.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] PciNetwork.txt
apport information ** Attachment added: "PciNetwork.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593887/+files/PciNetwork.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] ProcCpuinfoMinimal.txt
apport information ** Attachment added: "ProcCpuinfoMinimal.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593888/+files/ProcCpuinfoMinimal.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] NetDevice.veth542edda.txt
apport information ** Attachment added: "NetDevice.veth542edda.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593884/+files/NetDevice.veth542edda.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] IpAddr.txt
apport information ** Attachment added: "IpAddr.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593877/+files/IpAddr.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] IwConfig.txt
apport information ** Attachment added: "IwConfig.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593878/+files/IwConfig.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] Dependencies.txt
apport information ** Attachment added: "Dependencies.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593876/+files/Dependencies.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) IpRoute: default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 169.254.0.0/16 dev enp2s0 scope link metric 1000 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 NonfreeKernelModules: nvidia_modeset nvidia Package: network-manager 1.36.4-2ubuntu1 PackageArchitecture: amd64 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Tags: wayland-session jammy Uname: Linux 5.15.0-33-generic x86_64 UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers _MarkForUpload: True nmcli-nm: RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN running 1.36.4 connected started full enabled enabled enabled enabled enabled no_proxy: localhost,127.0.0.0/8,::1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] Re: Wifi hotspot not configured correctly on restart
apport information ** Tags added: apport-collected wayland-session ** Description changed: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) + --- + ProblemType: Bug + ApportVersion: 2.20.11-0ubuntu82.1 + Architecture: amd64 + CasperMD5CheckResult: pass + CurrentDesktop: ubuntu:GNOME + DistroRelease: Ubuntu 22.04 + InstallationDate: Installed on 2021-12-08 (173 days ago) + InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) + IpRoute: + default via 10.0.0.138 dev enp2s0 proto dhcp metric 100 + 10.0.0.0/24 dev enp2s0 proto kernel scope link src 10.0.0.15 metric 100 + 10.42.0.0/24 dev wlp3s0 proto kernel scope link src 10.42.0.1 metric 600 + 169.254.0.0/16 dev enp2s0 scope link metric 1000 + 172.17.0.0/16 dev docker0 proto kernel scope link src 172.17.0.1 + NonfreeKernelModules: nvidia_modeset nvidia + Package: network-manager 1.36.4-2ubuntu1 + PackageArchitecture: amd64 + ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 + Tags: wayland-session jammy + Uname: Linux 5.15.0-33-generic x86_64 + UpgradeStatus: Upgraded to jammy on 2022-04-24 (36 days ago) + UserGroups: adm cdrom dip lpadmin lxd nordvpn plugdev sambashare sudo vboxusers + _MarkForUpload: True + nmcli-nm: + RUNNING VERSION STATE STARTUP CONNECTIVITY NETWORKING WIFI-HW WIFI WWAN-HW WWAN + running 1.36.4 connected started full enabled enabled enabled enabled enabled + no_proxy: localhost,127.0.0.0/8,::1 ** Attachment added: "CRDA.txt" https://bugs.launchpad.net/bugs/1973629/+attachment/5593875/+files/CRDA.txt -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) --- ProblemType: Bug ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME DistroRelease: Ubuntu 22.04 InstallationDate: Installed on 2021-12-08 (173 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release
[Desktop-packages] [Bug 1970139] Re: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS
hello guys, This issue is really making ubuntu 22.04 useless on raspberry pi 4, DOES ANYONE HAVE ANY ALTERNATE OR TEMPORARY SOLUTION TO IT? we need to use raspberry pi remotely as it is mounted on our robot without connecting any screen. :) It would help us a lot -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-remote-desktop in Ubuntu. https://bugs.launchpad.net/bugs/1970139 Title: VNC Connection doesn't work on arm64 (Raspberry Pi 4 8Gb) in Ubuntu 22.04 LTS Status in gnome-remote-desktop package in Ubuntu: In Progress Bug description: # lsb_release -rd Description: Ubuntu 22.04 LTS Release: 22.04 # apt-cache policy gnome-remote-desktop gnome-remote-desktop: Instalados: 42.0-4ubuntu1 Candidato: 42.0-4ubuntu1 Tabla de versión: *** 42.0-4ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages 100 /var/lib/dpkg/status # uname -a Linux fpgrpi 5.15.0-1005-raspi #5-Ubuntu SMP PREEMPT Mon Apr 4 12:21:48 UTC 2022 aarch64 aarch64 aarch64 GNU/Linux Summary of the bug: --- When I try to connect to gnome-remote-desktop using VNC to a Raspberry Pi 4 Model B Rev 1.4 (8Gb) under Ubuntu 22.04 LTS the VNC client can't connect (connection is refused). The connection passes the Password check validation but don't connect (sometimes shows screen garbage before disconnecting). I've used several VNC clients (Remmina in Ubuntu and Real VNC in Android) getting the same problem failing either in X11 or Wayland. Notes: - VNC connection does work in in previous Ubuntu 21.10 version with the same architecture (arm64) and same Raspberry Pi. - VNC connection also does work in amd64 machines with Ubuntu 22.04 LTS and gnome-remote-desktop 42.0-4ubuntu1, exactly the same software version that doesn't work on arm64 (Raspberry Pi). There is no apport info at all. Also there is almost no info in the journal regarding this problem. When I try to connect to VNC server it show this: On Wayland: --- abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 1884160 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 4169728 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8130560 bytes), total 32768 (slots), used 83 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:42 fpgrpi kernel: vc4-drm gpu: swiotlb buffer is full (sz: 8294400 bytes), total 32768 (slots), used 3 (slots) abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Main process exited, code=killed, status=11/SEGV abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Failed with result 'signal'. abr 25 00:21:43 fpgrpi gnome-shell[1497]: D-Bus client with active sessions vanished abr 25 00:21:43 fpgrpi systemd[1381]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 1. abr 25 00:21:43 fpgrpi systemd[1381]: Stopped GNOME Remote Desktop. abr 25 00:21:43 fpgrpi systemd[1381]: Starting GNOME Remote Desktop... abr 25 00:21:43 fpgrpi systemd[1381]: Started GNOME Remote Desktop. abr 25 00:21:43 fpgrpi gnome-remote-desktop-daemon[2125]: Cannot load libcuda.so.1 abr 25 00:21:43 fpgrpi gnome-remote-desktop-daemon[2125]: Cannot load libnvidia-encode.so.1 abr 25 00:21:43 fpgrpi gnome-remote-de[2125]: RDP server started abr 25 00:21:43 fpgrpi gnome-remote-de[2125]: VNC server started On X11: --- abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Main process exited, code=killed, status=11/SEGV abr 25 00:12:18 fpgrpi gnome-shell[3044]: D-Bus client with active sessions vanished abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Failed with result 'signal'. abr 25 00:12:18 fpgrpi systemd[2859]: gnome-remote-desktop.service: Scheduled restart job, restart counter is at 19. abr 25 00:12:18 fpgrpi systemd[2859]: Stopped GNOME Remote Desktop. abr 25 00:12:18 fpgrpi systemd[2859]: Starting GNOME Remote Desktop... abr 25 00:12:18 fpgrpi systemd[2859]: Started GNOME Remote Desktop. abr 25 00:12:19 fpgrpi gnome-remote-desktop-daemon[23876]: Cannot load libcuda.so.1 abr 25 00:12:19 fpgrpi gnome-remote-desktop-daemon[23876]: Cannot load libnvidia-encode.so.1 abr 25 00:12:19 fpgrpi gnome-remote-de[23876]: RDP server started abr 25 00:12:19 fpgrpi gnome-remote-de[23876]: VNC server started To manage notifications about this bug go to:
[Desktop-packages] [Bug 1976179] Re: evince does not print
Hi Sebastian, nothing was thrown during run of journalctl: $ journalctl -f Mai 30 17:04:16 laptoppete-G752VSK dbus-daemon[1263]: [system] Successfully activated service 'org.freedesktop.timedate1' Mai 30 17:04:16 laptoppete-G752VSK systemd[1]: Started Time & Date Service. Mai 30 17:04:17 laptoppete-G752VSK snapd[1290]: storehelpers.go:722: cannot refresh: snap has no updates available: "bare", "canonical-livepatch", "core", "core18", "core20", "firefox", "gnome-3-28-1804", "gnome-3-34-1804", "gnome-3-38-2004", "gtk-common-themes", "notepad-plus-plus", "pycharm-community", "snap-store", "snapd", "spotify", "vlc", "wine-platform-5-stable", "wine-platform-6-stable", "wine-platform-runtime", "xmind" Mai 30 17:04:17 laptoppete-G752VSK snapd[1290]: snapstate.go:1567: cannot refresh snap "skype": snap "skype" has running apps (skype) Mai 30 17:04:17 laptoppete-G752VSK systemd[2778]: Starting snapd user session agent... Mai 30 17:04:17 laptoppete-G752VSK systemd[2778]: Started snapd user session agent. Mai 30 17:04:25 laptoppete-G752VSK /usr/libexec/gdm-x-session[2878]: (EE) event12 - ELAN1203:00 04F3:304E Touchpad: kernel bug: Touch jump detected and discarded. Mai 30 17:04:25 laptoppete-G752VSK /usr/libexec/gdm-x-session[2878]: See https://wayland.freedesktop.org/libinput/doc/1.20.0/touchpad-jumping-cursors.html for details Mai 30 17:04:46 laptoppete-G752VSK systemd[1]: systemd-timedated.service: Deactivated successfully. Mai 30 17:04:47 laptoppete-G752VSK snap[6845]: session_agent.go:329: read unix @->/run/user/1000/bus: use of closed network connection Mai 30 17:06:03 laptoppete-G752VSK wpa_supplicant[1301]: wlp4s0: WPA: Group rekeying completed with 2c:3a:fd:82:47:8b [GTK=CCMP] Mai 30 17:06:13 laptoppete-G752VSK audit[7013]: AVC apparmor="DENIED" operation="connect" profile="/usr/bin/evince" name="/run/user/1000/at-spi/bus_1" pid=7013 comm="evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000 Mai 30 17:06:13 laptoppete-G752VSK kernel: audit: type=1400 audit(1653923173.800:122): apparmor="DENIED" operation="connect" profile="/usr/bin/evince" name="/run/user/1000/at-spi/bus_1" pid=7013 comm="evince" requested_mask="wr" denied_mask="wr" fsuid=1000 ouid=1000 Mai 30 17:06:13 laptoppete-G752VSK dbus-daemon[2807]: [session uid=1000 pid=2807] Activating service name='org.gnome.evince.Daemon' requested by ':1.123' (uid=1000 pid=7013 comm="evince ./reise_scheng_formular.pdf;jsessionid=581D" label="/usr/bin/evince (enforce)") Mai 30 17:06:13 laptoppete-G752VSK dbus-daemon[2807]: [session uid=1000 pid=2807] Successfully activated service 'org.gnome.evince.Daemon' Mai 30 17:06:38 laptoppete-G752VSK systemd[1]: Starting Ubuntu Advantage Timer for running repeated jobs... Mai 30 17:06:38 laptoppete-G752VSK systemd[1]: ua-timer.service: Deactivated successfully. Mai 30 17:06:38 laptoppete-G752VSK systemd[1]: Finished Ubuntu Advantage Timer for running repeated jobs. Mai 30 17:06:56 laptoppete-G752VSK gnome-shell[3113]: Object .Gjs_ui_messageTray_Notification (0x55b4a29a1c20), has been already disposed — impossible to emit any signal on it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Mai 30 17:06:56 laptoppete-G752VSK gnome-shell[3113]: == Stack trace for context 0x55b4a242c190 == Mai 30 17:06:56 laptoppete-G752VSK gnome-shell[3113]: #0 7ffc87104b50 b resource:///org/gnome/shell/ui/messageTray.js:493 (3c83bc156ba0 @ 69) Mai 30 17:06:56 laptoppete-G752VSK gnome-shell[3113]: #1 55b4a4eaf420 i resource:///org/gnome/shell/ui/messageTray.js:489 (3c83bc156b50 @ 56) Mai 30 17:06:56 laptoppete-G752VSK gnome-shell[3113]: #2 55b4a4eaf398 i resource:///org/gnome/shell/ui/calendar.js:784 (3c83bc15cce0 @ 22) Mai 30 17:06:56 laptoppete-G752VSK gnome-shell[3113]: == Stack trace for context 0x55b4a242c190 == Mai 30 17:06:56 laptoppete-G752VSK gnome-shell[3113]: #0 7ffc87104b50 b resource:///org/gnome/shell/ui/messageTray.js:494 (3c83bc156ba0 @ 84) Mai 30 17:06:56 laptoppete-G752VSK gnome-shell[3113]: #1 55b4a4eaf420 i resource:///org/gnome/shell/ui/messageTray.js:489 (3c83bc156b50 @ 56) Mai 30 17:06:56 laptoppete-G752VSK gnome-shell[3113]: #2 55b4a4eaf398 i resource:///org/gnome/shell/ui/calendar.js:784 (3c83bc15cce0 @ 22) Mai 30 17:06:56 laptoppete-G752VSK gnome-shell[3113]: Object .Gjs_ui_messageTray_Notification (0x55b4a29a1c20), has been already disposed — impossible to access it. This might be caused by the object having been destroyed from C code using something such as destroy(), dispose(), or remove() vfuncs. Mai 30 17:06:56 laptoppete-G752VSK systemd[2778]: Started Application launched by gnome-shell. Mai 30 17:06:56 laptoppete-G752VSK gnome-control-c[7054]: Failed to load module "unity-gtk-module" Mai 30 17:06:56 laptoppete-G752VSK gnome-control-c[7054]: Failed to load module "unity-gtk-module" Mai 30 17:06:56 laptoppete-G752VSK
[Desktop-packages] [Bug 1958722] Re: improve the sound -> over-amplification row
** Changed in: gnome-control-center (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1958722 Title: improve the sound -> over-amplification row Status in gnome-control-center package in Ubuntu: Fix Released Bug description: Issue: - The Over-Amplification setting present under Sound-panel in ubuntu-22.04 is a bit outdated because all the other settings-options in the sound-panel make use of round-listboxes in GNOME-41. - I also noticed Over-Amplification's description GtkLabel is not aligned. Proposal: - make use of GtkListbox, HdyPreferencesRow and HdyActionRow for Over-Amplification. - MR for the same: https://gitlab.gnome.org/Community/Ubuntu/gnome-control-center/-/merge_requests/6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1958722/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1812506] Re: Ubuntu 18.04 gnome-control-center > Devices > Removable_media > Ask_what_to_do - does not ask
in Ubuntu 22.10 for ALL Removable Media I have 'ask what to do' inserting a blank CD i see TWO icons in the dock with 'Blank CD-R Disk' but no questions and nothing in the notification area inserting a data disk ONE icon with 'Data disk (25 Dec 08)' and the same in notification area inserting another data disk ONE icon with 'Disk' and the same in notification area inserting an audio disk ONE icon with 'Audio disk' and the same in notification area inserting an USB key I see his name in the dock and in notification area inserting an USB key with the ISO of Ubuntu 22.04 TWO icons with 'Writable' and 'Ubuntu 22.04 LTS' in the dock and 2 notes in in notification area for ALL these Media i see also the info in the left nautilus sidebar but NO QUESTIONS and NO icons on Desktop. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1812506 Title: Ubuntu 18.04 gnome-control-center > Devices > Removable_media > Ask_what_to_do - does not ask Status in gnome-control-center package in Ubuntu: Incomplete Bug description: On Ubuntu 18.04.1 when I insert a CD or DVD I don't see the window asking_what_to_do also if I specified this option in gnome-control- center > Devices > Removable_media I see only a new icon on the desktop. CD audio: 'Rhytmbox' and 'open-folder' works fine. 'Ask_what_to_do' does nothing Blank CD disk: 'Open_folder' and 'Ask_what_to_do' does nothing, also call K3b or call CD/DVD creator (brasero) does nothing Blank DVD disk: like Blank CD On same hardware different partitions with Artful, Cosmic and Disco I see the same problem. On same hardware different partition with Ubuntu Xenial inserting any CD/DVD I see a window saying: 'You have just inserted ... Chose what application to launch' ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: gnome-control-center 1:3.28.2-0ubuntu0.18.04.2 ProcVersionSignature: Ubuntu 4.15.0-43.46-generic 4.15.18 Uname: Linux 4.15.0-43-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Sat Jan 19 18:49:21 2019 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2018-05-01 (263 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Release amd64 (20180426) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1812506/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1974428] Re: Update to the current 1.36 stable version
1.36.6-0ubuntu1 is working as expected testing wifi, VPN, hotspot and standard desktop options. The autopkgtests showed no problem and we didn't get report of new problems. ** Tags removed: verification-needed verification-needed-jammy ** Tags added: verification-done verification-done-jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager in Ubuntu. https://bugs.launchpad.net/bugs/1974428 Title: Update to the current 1.36 stable version Status in network-manager package in Ubuntu: Fix Released Status in network-manager source package in Jammy: Fix Committed Bug description: * Impact It's a stable update from upstream, the changes are listed in the NEWS https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/blob/nm-1-36/NEWS * Test Case Since it's an update with several fixes the testing should focus on a specific point but rather by validating that the testplan is green, https://wiki.ubuntu.com/NetworkManager/DistroTesting * Regression potential There are fixes around IPv6 handling, VPN connections and the hotspot feature, verify that those configurations are still working as expected. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1974428/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1973629] Re: Wifi hotspot not configured correctly on restart
Thank you for your bug report. If the status is wrong at system start then the problem is probably due to network-manager itself. Could you trigger the bug and then when the system is in the buggy state do $ apport-collect 1973629 The issue is probably also worth reporting upstream on https://gitlab.freedesktop.org/NetworkManager/NetworkManager/-/issues ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Package changed: gnome-control-center (Ubuntu) => network-manager (Ubuntu) ** Changed in: network-manager (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1973629 Title: Wifi hotspot not configured correctly on restart Status in network-manager package in Ubuntu: Incomplete Bug description: I have configured the hotspot to automatically start at startup. The hotspot correctly starts on startup, but it appears to be configured incorrectly. No device connected to it can reach the internet. When opening the settings, Wifi is indicated to be disabled, even though the hotspot is running (see screenshot). The expectation is that the hotpot to be fully functional on startup meaning every device connected to it can reach the internet. Currently the issue can be fixed by activating Wifi and then starting a hotspot, even though the hotspot is already running. The hotspot started at startup does not have to be shut down before starting a hotspot in the settings. All this leads me to believe that somewhere the configuration of Wifi goes wrong on startup. Running Ubuntu 22.04 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: dconf-service 0.40.0-3 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon May 16 19:59:02 2022 InstallationDate: Installed on 2021-12-08 (159 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: dconf UpgradeStatus: Upgraded to jammy on 2022-04-24 (22 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1973629/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1926218] Re: Disable or Remove FLoC features and the provider service
The test plan in the linked resource (https://github.com/brave/brave- core/pull/8468) is: 1. Open chrome://components and make sure that there is no Federated Learning of Cohorts component. 2. Open the devtools (F12) console, type document.interestCohort() and confirm that you get an error: VM119:1 Uncaught TypeError: document.interestCohort is not a function at :1:10 The Chromium snap passes both tests. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1926218 Title: Disable or Remove FLoC features and the provider service Status in chromium-browser package in Ubuntu: Triaged Bug description: Disable or remove entire FLoc, - FLoC component - Any other FLoC functionalities shipped in Chromium - FLoC client-side determinations of cohorts - Any reporting of FLoC cohort determinations to Google (or otherwise) servers (i.e., the reporting used for k-anonymity cohort protections) - FLoC JS methods (i.e. document.interestCohort) Brave, Vivaldi, Bromite have addressed FLoC issue and edge browser has disabled it Resources: https://github.com/brave/brave-core/pull/8468 https://answers.launchpad.net/ubuntu/+source/chromium-browser/+question/696632 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1926218/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1974435] Re: wacom tablet button selection interface doesn't allow picking from dropdown
** Changed in: gnome-control-center Status: Unknown => New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1974435 Title: wacom tablet button selection interface doesn't allow picking from dropdown Status in gnome-control-center: New Status in gnome-control-center package in Ubuntu: Triaged Bug description: I have a graphics table (Wacom Co., Ltd CTL-4100WL [Intuos BT (S)]), and gnome sees it happily. It provides me an interface to bind the buttons on the tablet to other functions, for example keyboard shortcuts. However it's not possible to select options in the dropdown for doing this, the mouse clicks are simply ignored on the dropdown. I also can't send a screenshot of the interface because prt scr doesn't work there, and when I use a different method I just get a black screenshot - so attached is a photo of the screen, sorry. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu13.2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 20 13:42:02 2022 InstallationDate: Installed on 2022-03-23 (57 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1974435/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1974435] Re: wacom tablet button selection interface doesn't allow picking from dropdown
Thanks, it also has been reported upstream on https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1805 ** Changed in: gnome-control-center (Ubuntu) Status: New => Triaged ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Bug watch added: gitlab.gnome.org/GNOME/gnome-control-center/-/issues #1805 https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1805 ** Also affects: gnome-control-center via https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues/1805 Importance: Unknown Status: Unknown -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1974435 Title: wacom tablet button selection interface doesn't allow picking from dropdown Status in gnome-control-center: Unknown Status in gnome-control-center package in Ubuntu: Triaged Bug description: I have a graphics table (Wacom Co., Ltd CTL-4100WL [Intuos BT (S)]), and gnome sees it happily. It provides me an interface to bind the buttons on the tablet to other functions, for example keyboard shortcuts. However it's not possible to select options in the dropdown for doing this, the mouse clicks are simply ignored on the dropdown. I also can't send a screenshot of the interface because prt scr doesn't work there, and when I use a different method I just get a black screenshot - so attached is a photo of the screen, sorry. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu13.2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri May 20 13:42:02 2022 InstallationDate: Installed on 2022-03-23 (57 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220313) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1974435/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956969] Re: When I restrt or shut down my ubuntu budgie just hangs there and freezes
thanks for the reply, let's close ** Changed in: gnome-control-center (Ubuntu) Status: Incomplete => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1956969 Title: When I restrt or shut down my ubuntu budgie just hangs there and freezes Status in gnome-control-center package in Ubuntu: Fix Released Bug description: When I do the restart or the shutdown ubuntu freezes. I used to restart to get into my other distr (have dualinstallation in my laptop) via grub selection. Now, it never gets there (to grub) and I am forced to shut down using the power button. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-control-center 1:40.0-1ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Mon Jan 10 08:59:21 2022 InstallationDate: Installed on 2021-04-24 (261 days ago) InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to impish on 2021-10-21 (80 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-04-24T17:04:23.204166 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956969/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964795] Re: gnome-keyring-daemon crashed with signal 7
The issue should be fixed with https://launchpad.net/ubuntu/+source/gnome-keyring/42.1-1 according to the gitlab ticket, it might be worth SRUing to the LTS if we have a testcase describing how to trigger the issue ** Changed in: gnome-keyring (Ubuntu) Importance: Undecided => High ** Also affects: gnome-keyring via https://gitlab.gnome.org/GNOME/gnome-keyring/-/issues/105 Importance: Unknown Status: Unknown ** Changed in: gnome-keyring (Ubuntu) Status: Confirmed => In Progress ** Changed in: gnome-keyring (Ubuntu) Status: In Progress => Fix Committed ** Changed in: gnome-keyring (Ubuntu) Assignee: (unassigned) => Jeremy Bicha (jbicha) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-keyring in Ubuntu. https://bugs.launchpad.net/bugs/1964795 Title: gnome-keyring-daemon crashed with signal 7 Status in GNOME Keyring: Unknown Status in gnome-keyring package in Ubuntu: Fix Committed Bug description: Description: Ubuntu Jammy Jellyfish (development branch) Release: 22.04 gnome-keyring: Installed: 40.0-3ubuntu1 Candidate: 40.0-3ubuntu1 Version table: *** 40.0-3ubuntu1 500 500 http://ports.ubuntu.com/ubuntu-ports jammy/main arm64 Packages 100 /var/lib/dpkg/status Background process crashes unexpectedly a few moments after login. I'm running the dev release of Jammy on a Raspberry Pi 400 with all updates applied. ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-keyring 40.0-3ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-1003.3-raspi 5.15.19 Uname: Linux 5.15.0-1003-raspi aarch64 ApportVersion: 2.20.11-0ubuntu79 Architecture: arm64 CasperMD5CheckResult: unknown Date: Mon Mar 14 15:26:41 2022 Disassembly: => 0x: Cannot access memory at address 0x ExecutablePath: /usr/bin/gnome-keyring-daemon ImageMediaBuild: 20201022 ProcCmdline: /usr/bin/gnome-keyring-daemon --daemonize --login ProcEnviron: SHELL=/bin/bash PATH=(custom, no user) LANG=en_GB.UTF-8 LANGUAGE=en_GB:en XDG_RUNTIME_DIR= Signal: 7 SourcePackage: gnome-keyring StacktraceTop: () () () at /lib/aarch64-linux-gnu/libgio-2.0.so.0 g_signal_emit_valist () at /lib/aarch64-linux-gnu/libgobject-2.0.so.0 g_signal_emit () at /lib/aarch64-linux-gnu/libgobject-2.0.so.0 Title: gnome-keyring-daemon crashed with signal 7 UpgradeStatus: Upgraded to jammy on 2022-03-07 (6 days ago) UserGroups: adm cdrom dip libvirt lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-keyring/+bug/1964795/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1971516] Re: Entering fileselector subdir disables the save button until filename is edited
** Changed in: gtk4 (Ubuntu) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk4 in Ubuntu. https://bugs.launchpad.net/bugs/1971516 Title: Entering fileselector subdir disables the save button until filename is edited Status in gtk4 package in Ubuntu: Fix Released Bug description: Affecting Chrome, Chromium, Firefox, Brave, Vivaldi Files can not reliably be downloaded to any folder except ~/downloads and /tmp. Ubuntu 22.04 Chrome installed from .deb, Brave installed from repos. Firefox and Chromium are both sneaky-snaps, but the behaviour is the same. Other reports in the wild: https://forum.vivaldi.net/topic/74989/ubuntu-22-04-save-as-doesn-t-fully-work https://askubuntu.com/questions/1405148/browsers-unable-to-save-downloads-to-network-drive-after-upgrade-to-ubuntu-22-04 Similar Bug(s): https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1970984 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/1971516/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970921] Re: Drag and drop does not work
Thank you for your bug report. Do you use gpaste? The description is a bit similar to https://gitlab.gnome.org/GNOME/nautilus/-/issues/1832 ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #1832 https://gitlab.gnome.org/GNOME/nautilus/-/issues/1832 ** Changed in: nautilus (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1970921 Title: Drag and drop does not work Status in nautilus package in Ubuntu: Incomplete Bug description: After upgrading Ubuntu to 22.04 drag and dropping files from nautilus to web browser (chromium, google chrome / apps like seafile, etc.) do not work. Also drag & drop from nautilus to slack desktop app does not work. If making several attempts, it might suddenly work with nth attempt. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 29 13:32:48 2022 InstallationDate: Installed on 2016-11-22 (1983 days ago) InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Release amd64 (20161012.2) SourcePackage: nautilus UpgradeStatus: Upgraded to jammy on 2022-04-29 (0 days ago) usr_lib_nautilus: evince42.1-3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1970921/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1974026] Re: webdav doesn't work with folder
Thank you for your bug report, could you register it directly upstream on https://gitlab.gnome.org/GNOME/nautilus/-/issues ? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1974026 Title: webdav doesn't work with folder Status in nautilus package in Ubuntu: New Bug description: If I try with ubuntu 22.04 in nautilus "connect to server" with an address like `davs://webdav.foo.de/__test-intern` I'm connected only to: davs://webdav.foo.de/ With Ubuntu 20.04 the connection is established as desired and still works. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-30.31-generic 5.15.30 Uname: Linux 5.15.0-30-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 18 14:00:54 2022 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'large'" b'org.gnome.nautilus.list-view' b'default-column-order' b"['name', 'size', 'type', 'owner', 'group', 'permissions', 'where', 'date_modified', 'date_modified_with_time', 'date_accessed', 'recency', 'starred', 'detailed_type']" b'org.gnome.nautilus.list-view' b'default-visible-columns' b"['name', 'size', 'permissions', 'date_modified', 'starred']" b'org.gnome.nautilus.window-state' b'initial-size' b'(924, 1006)' b'org.gnome.nautilus.window-state' b'sidebar-width' b'223' InstallationDate: Installed on 2022-04-22 (26 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince42.1-3 file-roller 3.42.0-1 nautilus-extension-brasero3.12.3-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1974026/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970274] Re: On Wayland viewing the keyboard layout for an input source opens in XWayland window
** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** Package changed: gnome-control-center (Ubuntu) => libgnomekbd (Ubuntu) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1970274 Title: On Wayland viewing the keyboard layout for an input source opens in XWayland window Status in libgnomekbd package in Ubuntu: New Bug description: Description: Ubuntu 22.04 LTS Release: 22.04 gnome-control-center: Installed: 1:41.4-1ubuntu13 Candidate: 1:41.4-1ubuntu13 Version table: *** 1:41.4-1ubuntu13 500 500 http://gb.archive.ubuntu.com/ubuntu jammy-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu jammy-security/main amd64 Packages 100 /var/lib/dpkg/status 1:41.4-1ubuntu12 500 500 http://gb.archive.ubuntu.com/ubuntu jammy/main amd64 Packages Opening the keyboard layout for an input source on Wayland opens the windows in XWayland. On a high resolution display with fractional scaling enabled, the window's content is blurry making it hard to discern certain characters in the layout. Expected: Keyboard layout to open in a native Wayland window, with characters crisp and legible ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu13 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Apr 25 22:20:32 2022 InstallationDate: Installed on 2022-03-31 (24 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Beta amd64 (20220329.1) RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libgnomekbd/+bug/1970274/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969601] Re: context menu cut, after screen resolution is changed
Thank you for your bug report, could you also report the issue upstream on https://gitlab.gnome.org/GNOME/nautilus/-/issues ? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1969601 Title: context menu cut, after screen resolution is changed Status in nautilus package in Ubuntu: New Bug description: I have a 4K monitor. If I open Nautilus window when display is in 1920x1080 resolution, then change the resolution to 3840x2160 AND change "scaling" to 200% then the context menu appears cut. Changing the resolution and leaving "scaling" at 100% does not trigger the bug. That is the content is scaled by 200% correctly, but the bounds of the context menu window seems not transformed and is twice too small to fit the content. When I open a new window (I do not need to kill already opened window). Then the right-click context menu is fine, in the new window. In the "old" window it remains cut. No LSB modules are available. Distributor ID: Ubuntu Description: Ubuntu 22.04 LTS Release: 22.04 Codename: jammy nautilus: Installed: 1:42.0-1ubuntu2 Candidate: 1:42.0-1ubuntu2 Version table: *** 1:42.0-1ubuntu2 500 500 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages 100 /var/lib/dpkg/status ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: nautilus 1:42.0-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 11:17:59 2022 SourcePackage: nautilus UpgradeStatus: Upgraded to jammy on 2022-03-19 (32 days ago) mtime.conffile..etc.apport.crashdb.conf: 2021-05-03T18:07:38.595923 usr_lib_nautilus: evince42.1-3 file-roller 3.42.0-1 nautilus-extension-gnome-terminal 3.44.0-1ubuntu1 nautilus-share0.7.3-2ubuntu6 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1969601/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969628] Re: Used memory indication is not really useful
Thank you for your bug report, could you also report it upstream on https://gitlab.gnome.org/GNOME/gnome-system-monitor/-/issues ? ** Changed in: gnome-system-monitor (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-system-monitor in Ubuntu. https://bugs.launchpad.net/bugs/1969628 Title: Used memory indication is not really useful Status in gnome-system-monitor package in Ubuntu: New Bug description: The values shown as "memory used" are not really informative. Roughly speaking "used" memory (indicated in the tool) = "really used" memory (NOT indicated in the tool) + "cache" (indicated in the tool) + "available" (NOT indicated in the tool) The tool shows the LHS "used memory" and "cache", but does not show the "available memory". With modern kernels the tendency is to "use" memory as much as possible in various buffers, so the value indicated in that tool has no practical value. For a user I would presume that "memory" should be indication of "really used" memory, because only that tells him how many application will he be able to run. Currently my Machine tells me it is using 61 GB of memory, with 20.5 GB in Cache. While all I have open are some basic simple tools like skype, Gnome-Terminal and a few Google Chrome windows. Thing is I have 33GB in "available" (according to TOP), which tells me that I am "really using" around 7GB of memory, which sounds about right. There is no way to get the 7GB value from gnome-system-monitor. The gnome-system-monitor should show "really used memory" or at the very least show also "available" memory just below "cache". ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-system-monitor 42.0-1 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Apr 20 16:07:09 2022 SourcePackage: gnome-system-monitor UpgradeStatus: Upgraded to jammy on 2022-03-19 (32 days ago) mtime.conffile..etc.apport.crashdb.conf: 2021-05-03T18:07:38.595923 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/1969628/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1975890] Re: mp4 video gets stuck in a frame, like it's paused
No, I can reproduce it with many different video files. Nothing shows up on the cmdline. Firefox plays the videos just fine, by the way. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to totem in Ubuntu. https://bugs.launchpad.net/bugs/1975890 Title: mp4 video gets stuck in a frame, like it's paused Status in totem package in Ubuntu: Incomplete Bug description: The video stops playing at a certain random frame, like it's been paused. You can drag the range control and move forwards and backwards and the frame will change as expected, but toggling play/pause does nothing. I can only reproduce this on Ubuntu 22.04. On Debian 11 it works as expected. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: totem 42.0-1ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-33.34-generic 5.15.30 Uname: Linux 5.15.0-33-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu May 26 23:13:19 2022 InstallationDate: Installed on 2022-05-23 (3 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: totem UpgradeStatus: No upgrade log present (probably fresh install) XorgLog: Error: [Errno 2] Arquivo ou diretório inexistente: '/var/log/Xorg.0.log' To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1975890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1976255] Re: accountsservice ftbfs in the jammy release pocket
This was fixed via accountsservice 22.07.5-2ubuntu1.3 in jammy-updates. ** Changed in: accountsservice (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to accountsservice in Ubuntu. https://bugs.launchpad.net/bugs/1976255 Title: accountsservice ftbfs in the jammy release pocket Status in accountsservice package in Ubuntu: Fix Released Bug description: as seen in a test rebuild, this package fails to build in the jammy release pocket (note the log behind the link might go away): https://launchpadlibrarian.net/604216054/buildlog_ubuntu-jammy- amd64.accountsservice_22.07.5-2ubuntu1_BUILDING.txt.gz Ok: 2 Expected Fail: 0 Fail: 10 Unexpected Pass:0 Skipped:0 Timeout:0 Full log written to /<>/obj-x86_64-linux-gnu/meson-logs/testlog.txt cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/testlog.txt ==> meson-logs/testlog.txt <== Log of Meson test suite run on 2022-05-30T08:33:42.861398 Inherited environment: SCHROOT_GID=2501 DEB_HOST_MULTIARCH=x86_64-linux-gnu LC_ALL=C.UTF-8 DEB_HOST_GNU_SYSTEM=linux-gnu DEB_BUILD_GNU_TYPE=x86_64-linux-gnu DEB_LDFLAGS_MAINT_APPEND=-Wl,--as-needed DEB_TARGET_ARCH_LIBC=gnu DEB_BUILD_ARCH_ENDIAN=little DEB_BUILD_GNU_SYSTEM=linux-gnu DEB_BUILD_ARCH_BITS=64 DEB_BUILD_OPTIONS=parallel=4 DEB_HOST_ARCH=amd64 DEB_TARGET_ARCH_ENDIAN=little DEB_BUILD_PROFILES=noudeb SOURCE_DATE_EPOCH=1645543676 V=1 DEB_HOST_ARCH_BITS=64 LANG=C.UTF-8 MAKEFLAGS='' SCHROOT_GROUP=buildd DEB_TARGET_ARCH=amd64 DEB_HOST_GNU_CPU=x86_64 DEB_BUILD_ARCH_LIBC=gnu MFLAGS='' DEB_TARGET_ARCH_BITS=64 DEB_BUILD_ARCH_CPU=amd64 SCHROOT_ALIAS_NAME=build-PACKAGEBUILD-23614463 DEB_HOST_ARCH_OS=linux SHELL=/bin/sh DEB_HOST_ARCH_CPU=amd64 SCHROOT_USER=buildd PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games DEB_BUILD_ARCH_ABI=base DEB_BUILD_ARCH=amd64 DEB_HOST_ARCH_LIBC=gnu SCHROOT_SESSION_ID=build-PACKAGEBUILD-23614463 DEB_TARGET_ARCH_CPU=amd64 DEB_HOST_GNU_TYPE=x86_64-linux-gnu DEB_BUILD_ARCH_OS=linux LOGNAME=buildd DEB_TARGET_MULTIARCH=x86_64-linux-gnu DEB_BUILD_GNU_CPU=x86_64 DEB_TARGET_ARCH_OS=linux USER=buildd DEB_HOST_ARCH_ABI=base DEB_BUILD_MULTIARCH=x86_64-linux-gnu DEB_TARGET_GNU_TYPE=x86_64-linux- gnu DEB_TARGET_ARCH_ABI=base SCHROOT_UID=2001 SCHROOT_COMMAND='dpkg- buildpackage -us -uc -mLaunchpad Build Daemon -b -rfakeroot' DEB_TARGET_GNU_CPU=x86_64 APT_CONFIG=/var/lib/sbuild/apt.conf HOME=/<>/debian/.debhelper/generated/_source/home DEB_RULES_REQUIRES_ROOT=binary-targets DEB_TARGET_GNU_SYSTEM=linux-gnu DEB_HOST_ARCH_ENDIAN=little TERM=unknown SCHROOT_CHROOT_NAME=build- PACKAGEBUILD-23614463 MAKELEVEL=1 DH_INTERNAL_BUILDFLAGS=1 ASFLAGS='' CFLAGS='-g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat- lto-objects -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security' CPPFLAGS='-Wdate-time -D_FORTIFY_SOURCE=2' CXXFLAGS='-g -O2 -ffile-prefix- map=/<>=. -flto=auto -ffat-lto-objects -flto=auto -ffat- lto-objects -fstack-protector-strong -Wformat -Werror=format-security' DFLAGS=-frelease FCFLAGS='-g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack- protector-strong' FFLAGS='-g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack- protector-strong' GCJFLAGS='-g -O2 -ffile-prefix- map=/<>=. -flto=auto -ffat-lto-objects -fstack-protector- strong' LDFLAGS='-Wl,-Bsymbolic-functions -flto=auto -ffat-lto-objects -flto=auto -Wl,-z,relro -Wl,--as-needed' OBJCFLAGS='-g -O2 -ffile- prefix-map=/<>=. -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format- security' OBJCXXFLAGS='-g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack- protector-strong -Wformat -Werror=format-security' XDG_RUNTIME_DIR=/tmp/dh-xdg-rundir-JPi9I5rR MESON_TESTTHREADS=4 1/12 accountsservice:accounts-service+libaccountsservice+TestAccountsService / TestAccountsService.test_cache_user FAIL0.33s exit status 1 08:33:42 LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/src/libaccountsservice GI_TYPELIB_PATH=/<>/obj-x86_64-linux-gnu/src/libaccountsservice G_DEBUG=fatal-criticals G_MESSAGES_DEBUG=all MALLOC_PERTURB_=58 /usr/bin/python3 /<>/obj-x86_64-linux-gnu/../tests/test-libaccountsservice.py TestAccountsService.test_cache_user --- output --- test_cache_user (__main__.TestAccountsService) ... (process:11790): accountsservice-DEBUG: 08:33:43.062: Finding a graphical session for user 2001 (process:11790): accountsservice-DEBUG: 08:33:43.062: Failed to identify the current session (process:11790):
[Desktop-packages] [Bug 1965642] Re: appearance selection will break the UI
Thank you for your bug report. Is that still an issue with the newer Ubuntu? If so could you attach a screenshot showing the problem? ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1965642 Title: appearance selection will break the UI Status in gnome-control-center package in Ubuntu: Incomplete Bug description: as soon as you click the appearance option, the sidebar will disappear (forever) and you cannot, after closing settings (gnome control center), re-open it in any way. only solution i found is to reset all options via terminal: dconf reset -f / ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-control-center 1:40.0-1ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-35.40-generic 5.13.19 Uname: Linux 5.13.0-35-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Mar 19 22:29:12 2022 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2022-03-19 (0 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1965642/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1967235] Re: Can not trash files in other partitions
Thank you for your bug report. It does sound similar to https://gitlab.gnome.org/GNOME/nautilus/-/issues/1071, is that still an issue in the current Ubuntu serie? ** Bug watch added: gitlab.gnome.org/GNOME/nautilus/-/issues #1071 https://gitlab.gnome.org/GNOME/nautilus/-/issues/1071 ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1967235 Title: Can not trash files in other partitions Status in nautilus package in Ubuntu: Incomplete Bug description: I know this is an old one, but this is still present, either it is a regression or not. Files in another partition than home can only be deleted but not moved to Trash, even if the whole partition has writing allowed for the current user. How to reproduce: USER=th mkdir /home/th/shim sudo mkdir /mnt/shim sudo mount -o bind /home/th/shim cd /mnt/shim touch ttt nautilus /mnt/shim Now trashing ttt fails. However trashing when in /home/th/shim it works. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1.20.04.1 ProcVersionSignature: Ubuntu 5.8.0-55.62~20.04.1-lowlatency 5.8.18 Uname: Linux 5.8.0-55-lowlatency x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: XFCE Date: Thu Mar 31 09:27:36 2022 InstallationDate: Installed on 2019-12-19 (832 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1967235/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1964601] Re: I have no processor!
Thank you for your bug report. The CPU missing has been reported upstream on https://gitlab.gnome.org/GNOME/libgtop/-/issues/60 Could you provide the content of /proc/cpuinfo on the raspi? And what is the output of $ glxinfo | grep 'OpenGL renderer string' And could you add the log generated by $ udiskctl dump > udisk.log ** Bug watch added: gitlab.gnome.org/GNOME/libgtop/-/issues #60 https://gitlab.gnome.org/GNOME/libgtop/-/issues/60 ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1964601 Title: I have no processor! Status in gnome-control-center package in Ubuntu: Incomplete Bug description: At least according to gnome-control-center anyway. Running the Ubuntu Desktop for Raspberry Pi image on a Pi 400 (or a Pi 4B), selecting Settings, then the "About" page shows that gnome- control-center thinks the processor is "", the graphics are "unknown", and apparently so is the disk capacity! I admit it's a trivial thing, but it's been this way since at least hirsute, and it'd be nice to see something vaguely sane in there at some point :) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1964601/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1965624] Re: gnome-control-center changes to light theme after selecting options
** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1965624 Title: gnome-control-center changes to light theme after selecting options Status in gnome-control-center package in Ubuntu: New Bug description: After going into Appearance, then selecting Notifications, then Appearance again, the app turns to light theme for some reason. And when you do it again, it goes back to dark. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.4-1ubuntu8 ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27 Uname: Linux 5.15.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu79 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sat Mar 19 09:13:36 2022 InstallationDate: Installed on 2022-03-09 (10 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: Upgraded to jammy on 2022-03-17 (2 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1965624/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1976260] [NEW] mozjs91 ftbfs in the jammy release pocket
Public bug reported: as seen in a test rebuild, this package fails to build in the jammy release pocket (note the log behind the link might go away): https://launchpadlibrarian.net/604217092/buildlog_ubuntu-jammy- amd64.mozjs91_91.7.0-2_BUILDING.txt.gz [...] ## non262/Intl/DateTimeFormat/timeZone_version.js: rc = 3, run time = 0.014026 /<>/js/src/tests/non262/Intl/DateTimeFormat/timeZone_version.js:16:9 Error: Asserti on failed: got "2022a", expected "2021a3" Stack: @/<>/js/src/tests/non262/Intl/DateTimeFormat/timeZone_version.js:16:9 TEST-UNEXPECTED-FAIL | non262/Intl/DateTimeFormat/timeZone_version.js | (args: "") [0.0 s] make[3]: *** [Makefile:63: check-jstests] Error 1 ** Affects: mozjs91 (Ubuntu) Importance: Undecided Status: New ** Tags: ftbfs rls-jj-incoming ** Tags added: ftbfs rls-jj-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mozjs91 in Ubuntu. https://bugs.launchpad.net/bugs/1976260 Title: mozjs91 ftbfs in the jammy release pocket Status in mozjs91 package in Ubuntu: New Bug description: as seen in a test rebuild, this package fails to build in the jammy release pocket (note the log behind the link might go away): https://launchpadlibrarian.net/604217092/buildlog_ubuntu-jammy- amd64.mozjs91_91.7.0-2_BUILDING.txt.gz [...] ## non262/Intl/DateTimeFormat/timeZone_version.js: rc = 3, run time = 0.014026 /<>/js/src/tests/non262/Intl/DateTimeFormat/timeZone_version.js:16:9 Error: Asserti on failed: got "2022a", expected "2021a3" Stack: @/<>/js/src/tests/non262/Intl/DateTimeFormat/timeZone_version.js:16:9 TEST-UNEXPECTED-FAIL | non262/Intl/DateTimeFormat/timeZone_version.js | (args: "") [0.0 s] make[3]: *** [Makefile:63: check-jstests] Error 1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mozjs91/+bug/1976260/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
Re: [Desktop-packages] [Bug 1956969] Re: When I restrt or shut down my ubuntu budgie just hangs there and freezes
No, it doesn't. On Mon, 30 May 2022, 06:15 Sebastien Bacher, <1956...@bugs.launchpad.net> wrote: > The issue isn't due to the settings interface. Is that still a problem > in the newer serie? > > ** Changed in: gnome-control-center (Ubuntu) >Status: New => Incomplete > > -- > You received this bug notification because you are subscribed to the bug > report. > https://bugs.launchpad.net/bugs/1956969 > > Title: > When I restrt or shut down my ubuntu budgie just hangs there and > freezes > > Status in gnome-control-center package in Ubuntu: > Incomplete > > Bug description: > When I do the restart or the shutdown ubuntu freezes. I used to > restart to get into my other distr (have dualinstallation in my > laptop) via grub selection. Now, it never gets there (to grub) and I > am forced to shut down using the power button. > > ProblemType: Bug > DistroRelease: Ubuntu 21.10 > Package: gnome-control-center 1:40.0-1ubuntu5 > ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 > Uname: Linux 5.13.0-23-generic x86_64 > ApportVersion: 2.20.11-0ubuntu71 > Architecture: amd64 > CasperMD5CheckResult: pass > CurrentDesktop: Budgie:GNOME > Date: Mon Jan 10 08:59:21 2022 > InstallationDate: Installed on 2021-04-24 (261 days ago) > InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Release amd64 > (20210420) > SourcePackage: gnome-control-center > UpgradeStatus: Upgraded to impish on 2021-10-21 (80 days ago) > modified.conffile..etc.default.apport: ># set this to 0 to disable apport, or to 1 to enable it ># you can temporarily override this with ># sudo service apport start force_start=1 >enabled=0 > mtime.conffile..etc.default.apport: 2021-04-24T17:04:23.204166 > > To manage notifications about this bug go to: > > https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956969/+subscriptions > > -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1956969 Title: When I restrt or shut down my ubuntu budgie just hangs there and freezes Status in gnome-control-center package in Ubuntu: Incomplete Bug description: When I do the restart or the shutdown ubuntu freezes. I used to restart to get into my other distr (have dualinstallation in my laptop) via grub selection. Now, it never gets there (to grub) and I am forced to shut down using the power button. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-control-center 1:40.0-1ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Mon Jan 10 08:59:21 2022 InstallationDate: Installed on 2021-04-24 (261 days ago) InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to impish on 2021-10-21 (80 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-04-24T17:04:23.204166 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956969/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1933890] Re: No wacom tablet or stylus discovered, Fujitsu T935
The change is in this update, https://bugs.launchpad.net/ubuntu/+source/libwacom/2.2.0-1 ** Changed in: libwacom (Ubuntu) Status: In Progress => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libwacom in Ubuntu. https://bugs.launchpad.net/bugs/1933890 Title: No wacom tablet or stylus discovered, Fujitsu T935 Status in libwacom package in Ubuntu: Fix Released Bug description: I installed Ubuntu 21.04 on my Fujitsu T935, which has a Wacom stylus and screen. The command line seems to find it, and it works fine, but I cannot calibrate it without the gnome-control-center. $ xsetwacom --list devices Wacom MultiTouch Sensor Finger touch id: 10 type: TOUCH Wacom MultiTouch Sensor Pen stylusid: 11 type: STYLUS Wacom MultiTouch Sensor Pen eraserid: 15 type: ERASER Any ideas what to do? Thanks, Rob ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-control-center 1:3.38.5-1ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-22.23-generic 5.11.21 Uname: Linux 5.11.0-22-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Jun 28 17:45:08 2021 InstallationDate: Installed on 2021-05-25 (34 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libwacom/+bug/1933890/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958334] Re: Nautilus says "preparing" yet never shows the actual operation of emptying the trash, even when finished; the program just says "Preparing"
** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1958334 Title: Nautilus says "preparing" yet never shows the actual operation of emptying the trash, even when finished; the program just says "Preparing" Status in nautilus package in Ubuntu: New Bug description: I should know what operations are going on, and the operation should not be stuck being listed as "preparing" perpetually, even when said task finished. This happens whenever I empty the Trash in Ubuntu. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1.20.04.1 ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jan 19 00:18:15 2022 GsettingsChanges: b'org.gnome.nautilus.compression' b'default-compression-format' b"'tar.xz'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1038, 552)' b'org.gnome.nautilus.preferences' b'fts-enabled' b'false' InstallationDate: Installed on 2021-10-03 (108 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1958334/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1976259] [NEW] librsvg ftbfs in the jammy release pocket
Public bug reported: as seen in a test rebuild, this package fails to build in the jammy release pocket (note the log behind the link might go away): https://launchpadlibrarian.net/604216345/buildlog_ubuntu- jammy-i386.librsvg_2.52.5+dfsg-3_BUILDING.txt.gz test url_resolver::tests::allows_relative ... ok failures: transform::tests::parses_transform_list stdout thread 'transform::tests::parses_transform_list' panicked at 'assertion failed: t1.y0.approx_eq(t2.y0, (epsilon, 1))', src/transform.rs:716:9 transform::tests::parses_valid_transform stdout thread 'transform::tests::parses_valid_transform' panicked at 'assertion failed: t1.y0.approx_eq(t2.y0, (epsilon, 1))', src/transform.rs:716:9 failures: transform::tests::parses_transform_list transform::tests::parses_valid_transform test result: FAILED. 254 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.02s error: test failed, to rerun pass '--lib' make[5]: *** [Makefile:1537: check-local] Error 101 ** Affects: librsvg (Ubuntu) Importance: Undecided Status: New ** Tags: ftbfs rls-jj-incoming ** Tags added: ftbfs rls-jj-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to librsvg in Ubuntu. https://bugs.launchpad.net/bugs/1976259 Title: librsvg ftbfs in the jammy release pocket Status in librsvg package in Ubuntu: New Bug description: as seen in a test rebuild, this package fails to build in the jammy release pocket (note the log behind the link might go away): https://launchpadlibrarian.net/604216345/buildlog_ubuntu- jammy-i386.librsvg_2.52.5+dfsg-3_BUILDING.txt.gz test url_resolver::tests::allows_relative ... ok failures: transform::tests::parses_transform_list stdout thread 'transform::tests::parses_transform_list' panicked at 'assertion failed: t1.y0.approx_eq(t2.y0, (epsilon, 1))', src/transform.rs:716:9 transform::tests::parses_valid_transform stdout thread 'transform::tests::parses_valid_transform' panicked at 'assertion failed: t1.y0.approx_eq(t2.y0, (epsilon, 1))', src/transform.rs:716:9 failures: transform::tests::parses_transform_list transform::tests::parses_valid_transform test result: FAILED. 254 passed; 2 failed; 0 ignored; 0 measured; 0 filtered out; finished in 0.02s error: test failed, to rerun pass '--lib' make[5]: *** [Makefile:1537: check-local] Error 101 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/librsvg/+bug/1976259/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1846554] Re: 'Files' icon should not be listed twice in the Cinnamon start menu
** Changed in: nautilus (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1846554 Title: 'Files' icon should not be listed twice in the Cinnamon start menu Status in cinnamon package in Ubuntu: New Status in nautilus package in Ubuntu: New Bug description: The Nautilus 'Files' icon gets always listed twice in the Cinnamon start menu (reproduced on Ubuntu 16.04 LTS and unchanged on 18.04 LTS). This small fix to /usr/share/applications/nautilus.desktop seems to work: Change > NotShowIn=Unity;GNOME; into > NotShowIn=Unity;GNOME;X-Cinnamon; (no idea if this is the best solution) ProblemType: Bug DistroRelease: Ubuntu 18.04 Package: nautilus 1:3.26.4-0~ubuntu18.04.4 [modified: usr/share/applications/nautilus.desktop] ProcVersionSignature: Ubuntu 4.15.0-64.73-generic 4.15.18 Uname: Linux 4.15.0-64-generic x86_64 ApportVersion: 2.20.9-0ubuntu7.7 Architecture: amd64 CurrentDesktop: X-Cinnamon Date: Thu Oct 3 20:57:27 2019 EcryptfsInUse: Yes GsettingsChanges: b'org.gnome.nautilus.window-state' b'sidebar-width' b'240' b'org.gnome.nautilus.window-state' b'geometry' b"'1268x778+396+123'" SourcePackage: nautilus UpgradeStatus: Upgraded to bionic on 2019-09-14 (19 days ago) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cinnamon/+bug/1846554/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1958333] Re: Progress Bar should disappear from icon after file operations cease, but it lingers fora few minutes after
Thank you for your bug report, could you try if that's still an issue in the newer Ubuntu series? ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1958333 Title: Progress Bar should disappear from icon after file operations cease, but it lingers fora few minutes after Status in nautilus package in Ubuntu: Incomplete Bug description: This happens after copying files or extracting every time. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: nautilus 1:3.36.3-0ubuntu1.20.04.1 ProcVersionSignature: Ubuntu 5.13.0-25.26~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-25-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Wed Jan 19 00:14:54 2022 GsettingsChanges: b'org.gnome.nautilus.compression' b'default-compression-format' b"'tar.xz'" b'org.gnome.nautilus.window-state' b'initial-size' b'(1038, 552)' b'org.gnome.nautilus.preferences' b'fts-enabled' b'false' InstallationDate: Installed on 2021-10-03 (108 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1958333/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1955697] Re: file-roller fails to extract zip|rar|tar to symlinked directories
Thank you for your bug report. Is that still an issue and if so could you explain exactly what you mean by 'the output folder is or is below a symbolic link'? ** Changed in: file-roller (Ubuntu) Importance: Undecided => Low ** Changed in: file-roller (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to file-roller in Ubuntu. https://bugs.launchpad.net/bugs/1955697 Title: file-roller fails to extract zip|rar|tar to symlinked directories Status in file-roller package in Ubuntu: Incomplete Bug description: File-roller fails to extract rar, zip, xz and tar archives when 1) the output folder is or is below a symbolic link and 2) extraction is run from the context menu (Extract Here) The typical error message is: "There was an error while extracting ". The file is not a directory." Extraction does work when I 1) navigate to the actual location of the output folder or move the archive(s) to a location that is not a symbolic link or 2) open the archive and run "Extract to" from its menu (which is quite cumbersome when there are dozens of archives to process...). I am dual booting 20.04 and 21.10 with a single home directory (which is where the problematic symlink is located). The issue I am reporting occurs only when I am using 21.10. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: file-roller 3.40.0-2 ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19 Uname: Linux 5.13.0-22-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Dec 24 07:29:37 2021 InstallationDate: Installed on 2021-10-12 (73 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Beta amd64 (20210922) SourcePackage: file-roller UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/file-roller/+bug/1955697/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1961642] Re: No password samba share authentication error
Thank you for taking the time to report this issue and helping to make Ubuntu better. Examining the information you have given us, this does not appear to be a bug report so we are closing it and converting it to a question in the support tracker. We understand the difficulties you are facing, but it is better to raise problems you are having in the support tracker at https://answers.launchpad.net/ubuntu if you are uncertain if they are bugs. You can also find help with your problem in the support forum of your local Ubuntu community http://loco.ubuntu.com/ or asking at https://askubuntu.com or https://ubuntuforums.org. For help on reporting bugs, see https://help.ubuntu.com/community/ReportingBugs. ** Changed in: nautilus (Ubuntu) Importance: Undecided => Low ** Changed in: nautilus (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1961642 Title: No password samba share authentication error Status in nautilus package in Ubuntu: Invalid Bug description: When trying to connect to a shared file from a windows pc via samba in nautilus, authentication is prompted. Windows pc has no password set. Nautilus does not understand this problem and keeps requesting authentication. Windows pc is windows 10. Only one account - Administrator with no password. Access to this windows pc is easy via another windows pc, credentials are prompted for and the login is "Administrator" with a blank password. With nautilus, when the password, nautilus will continually ask for login credentials, like they are invalid. Description: Ubuntu 21.10 Release: 21.10 ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-28.31-generic 5.13.19 Uname: Linux 5.13.0-28-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Feb 21 17:14:50 2022 GsettingsChanges: b'org.gnome.nautilus.icon-view' b'default-zoom-level' b"'larger'" b'org.gnome.nautilus.window-state' b'initial-size' b'(2478, 1166)' b'org.gnome.nautilus.preferences' b'default-folder-viewer' b"'list-view'" InstallationDate: Installed on 2022-02-06 (14 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: evince40.4-2 file-roller 3.40.0-2 nautilus-extension-gnome-terminal 3.38.1-1ubuntu2 nautilus-share0.7.3-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1961642/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1960079] Re: Settings should cover cases where the dock is disabled
Thank you for your bug report. It shouldn't be possible to disable the dock in an Ubuntu session since it's part of the Ubuntu session definition, so that would be the issue there. ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1960079 Title: Settings should cover cases where the dock is disabled Status in gnome-control-center package in Ubuntu: New Bug description: Release:22.04 - Ubuntu Jammy Jellyfish (development branch) Description: The Appearance Settings within Gnome Settings contains various configuration items for the dock. However, it is possible to disable the dock fully using the Gnome Extensions application. In the case where it is fully disabled, Gnome Settings still shows dock configuration options. Expectation: It would be great if those options are hidden when you've disabled the dock completely. It would also be great to be able to disable the dock from the settings panel. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1960079/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1959491] Re: Settings Power says performance mode disabled but allows performance mode
** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1959491 Title: Settings Power says performance mode disabled but allows performance mode Status in gnome-control-center package in Ubuntu: New Bug description: Settings Power says performance mode disabled but allows to set performance mode Open 'Settings' select 'Power' the window says: 'Performance mode temporary disabled...' but i I select 'Performance' the option is accepted. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.1-1ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-18.18-generic 5.15.12 Uname: Linux 5.15.0-18-generic x86_64 ApportVersion: 2.20.11-0ubuntu76 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Jan 29 17:52:29 2022 InstallationDate: Installed on 2022-01-03 (26 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20220103) SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1959491/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1962590] Re: Un-checking Make available to other users causes WiFi failure to connect
** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1962590 Title: Un-checking Make available to other users causes WiFi failure to connect Status in gnome-control-center package in Ubuntu: New Bug description: If I un-check the "Make available to other users" box, as soon as the computer is rebooted it will not re-connect to that WiFi network again and acts as if it has never connected to the network. I have to click on the SSID name and set up a new connection (e.g. "SSIDname 1") to reconnect. If I again go into settings and un-check the box on the new connection, the issue repeats (and I end up with "SSIDname 2", etc.). Even if I go back and re-check the box and apply the settings, the system refuses to reconnect using that connection and I have to set up a new one. Any new connection works fine across reboots, etc. until the first reboot after I un-check the box and apply the settings. I only have one user on this system, currently. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-control-center 1:3.36.5-0ubuntu3 ProcVersionSignature: Ubuntu 5.13.0-30.33~20.04.1-generic 5.13.19 Uname: Linux 5.13.0-30-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Tue Mar 1 10:17:15 2022 EcryptfsInUse: Yes ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-10-28 (489 days ago) InstallationMedia: Ubuntu 20.04.1 LTS "Focal Fossa" - Release amd64 (20200731) ProcEnviron: PATH=(custom, user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-control-center UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1962590/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1976255] [NEW] accountsservice ftbfs in the jammy release pocket
Public bug reported: as seen in a test rebuild, this package fails to build in the jammy release pocket (note the log behind the link might go away): https://launchpadlibrarian.net/604216054/buildlog_ubuntu-jammy- amd64.accountsservice_22.07.5-2ubuntu1_BUILDING.txt.gz Ok: 2 Expected Fail: 0 Fail: 10 Unexpected Pass:0 Skipped:0 Timeout:0 Full log written to /<>/obj-x86_64-linux-gnu/meson-logs/testlog.txt cd obj-x86_64-linux-gnu && tail -v -n \+0 meson-logs/testlog.txt ==> meson-logs/testlog.txt <== Log of Meson test suite run on 2022-05-30T08:33:42.861398 Inherited environment: SCHROOT_GID=2501 DEB_HOST_MULTIARCH=x86_64-linux- gnu LC_ALL=C.UTF-8 DEB_HOST_GNU_SYSTEM=linux-gnu DEB_BUILD_GNU_TYPE=x86_64-linux-gnu DEB_LDFLAGS_MAINT_APPEND=-Wl,--as- needed DEB_TARGET_ARCH_LIBC=gnu DEB_BUILD_ARCH_ENDIAN=little DEB_BUILD_GNU_SYSTEM=linux-gnu DEB_BUILD_ARCH_BITS=64 DEB_BUILD_OPTIONS=parallel=4 DEB_HOST_ARCH=amd64 DEB_TARGET_ARCH_ENDIAN=little DEB_BUILD_PROFILES=noudeb SOURCE_DATE_EPOCH=1645543676 V=1 DEB_HOST_ARCH_BITS=64 LANG=C.UTF-8 MAKEFLAGS='' SCHROOT_GROUP=buildd DEB_TARGET_ARCH=amd64 DEB_HOST_GNU_CPU=x86_64 DEB_BUILD_ARCH_LIBC=gnu MFLAGS='' DEB_TARGET_ARCH_BITS=64 DEB_BUILD_ARCH_CPU=amd64 SCHROOT_ALIAS_NAME=build-PACKAGEBUILD-23614463 DEB_HOST_ARCH_OS=linux SHELL=/bin/sh DEB_HOST_ARCH_CPU=amd64 SCHROOT_USER=buildd PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games DEB_BUILD_ARCH_ABI=base DEB_BUILD_ARCH=amd64 DEB_HOST_ARCH_LIBC=gnu SCHROOT_SESSION_ID=build-PACKAGEBUILD-23614463 DEB_TARGET_ARCH_CPU=amd64 DEB_HOST_GNU_TYPE=x86_64-linux-gnu DEB_BUILD_ARCH_OS=linux LOGNAME=buildd DEB_TARGET_MULTIARCH=x86_64-linux-gnu DEB_BUILD_GNU_CPU=x86_64 DEB_TARGET_ARCH_OS=linux USER=buildd DEB_HOST_ARCH_ABI=base DEB_BUILD_MULTIARCH=x86_64-linux-gnu DEB_TARGET_GNU_TYPE=x86_64-linux-gnu DEB_TARGET_ARCH_ABI=base SCHROOT_UID=2001 SCHROOT_COMMAND='dpkg-buildpackage -us -uc -mLaunchpad Build Daemon -b -rfakeroot' DEB_TARGET_GNU_CPU=x86_64 APT_CONFIG=/var/lib/sbuild/apt.conf HOME=/<>/debian/.debhelper/generated/_source/home DEB_RULES_REQUIRES_ROOT=binary-targets DEB_TARGET_GNU_SYSTEM=linux-gnu DEB_HOST_ARCH_ENDIAN=little TERM=unknown SCHROOT_CHROOT_NAME=build- PACKAGEBUILD-23614463 MAKELEVEL=1 DH_INTERNAL_BUILDFLAGS=1 ASFLAGS='' CFLAGS='-g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat- lto-objects -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format-security' CPPFLAGS='-Wdate-time -D_FORTIFY_SOURCE=2' CXXFLAGS='-g -O2 -ffile-prefix- map=/<>=. -flto=auto -ffat-lto-objects -flto=auto -ffat- lto-objects -fstack-protector-strong -Wformat -Werror=format-security' DFLAGS=-frelease FCFLAGS='-g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack- protector-strong' FFLAGS='-g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack- protector-strong' GCJFLAGS='-g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -fstack-protector-strong' LDFLAGS='-Wl,-Bsymbolic-functions -flto=auto -ffat-lto-objects -flto=auto -Wl,-z,relro -Wl,--as-needed' OBJCFLAGS='-g -O2 -ffile- prefix-map=/<>=. -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack-protector-strong -Wformat -Werror=format- security' OBJCXXFLAGS='-g -O2 -ffile-prefix-map=/<>=. -flto=auto -ffat-lto-objects -flto=auto -ffat-lto-objects -fstack- protector-strong -Wformat -Werror=format-security' XDG_RUNTIME_DIR=/tmp/dh-xdg-rundir-JPi9I5rR MESON_TESTTHREADS=4 1/12 accountsservice:accounts-service+libaccountsservice+TestAccountsService / TestAccountsService.test_cache_user FAIL0.33s exit status 1 08:33:42 LD_LIBRARY_PATH=/<>/obj-x86_64-linux-gnu/src/libaccountsservice GI_TYPELIB_PATH=/<>/obj-x86_64-linux-gnu/src/libaccountsservice G_DEBUG=fatal-criticals G_MESSAGES_DEBUG=all MALLOC_PERTURB_=58 /usr/bin/python3 /<>/obj-x86_64-linux-gnu/../tests/test-libaccountsservice.py TestAccountsService.test_cache_user --- output --- test_cache_user (__main__.TestAccountsService) ... (process:11790): accountsservice-DEBUG: 08:33:43.062: Finding a graphical session for user 2001 (process:11790): accountsservice-DEBUG: 08:33:43.062: Failed to identify the current session (process:11790): accountsservice-DEBUG: 08:33:43.062: ActUserManager: seat unloaded, so trying to set loaded property (process:11790): accountsservice-DEBUG: 08:33:43.062: ActUserManager: Seat wouldn't load, so giving up on it and setting loaded property (process:11790): accountsservice-DEBUG: 08:33:43.062: ActUserManager: already loaded, so not setting loaded property (process:11790): accountsservice-DEBUG: 08:33:43.063: ActUserManager: Creating user 'user', 'I am User', 1 (process:11790): accountsservice-DEBUG: 08:33:43.063: ActUserManager: calling 'ListCachedUsers' (process:11790):
[Desktop-packages] [Bug 1976256] [NEW] fprintd ftbfs in the jammy release pocket
Public bug reported:
as seen in a test rebuild, this package fails to build in the jammy
release pocket (note the log behind the link might go away):
https://launchpadlibrarian.net/604216188/buildlog_ubuntu-jammy-
amd64.fprintd_1.94.2-1_BUILDING.txt.gz
[...]
==
ERROR: test_pam_timeout (__main__.TestPamFprintd)
--
Traceback (most recent call last):
File "/<>/tests/pam/test_pam_fprintd.py", line 327, in
test_pam_timeout
self.setup_device()
File "/<>/tests/pam/test_pam_fprintd.py", line 85, in
setup_device
device_path = self.obj_fprintd_mock.AddDevice('FDO Trigger Finger Laser
Reader', 3, 'swipe')
File "/usr/lib/python3/dist-packages/dbus/proxies.py", line 141, in __call__
return self._connection.call_blocking(self._named_service,
File "/usr/lib/python3/dist-packages/dbus/connection.py", line 652, in
call_blocking
reply_message = self.send_message_with_reply_and_block(
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.InvalidArgs: Invalid
arguments: More items found in D-Bus signature than in Python arguments
--
Ran 1 test in 0.251s
FAILED (errors=1)
stderr:
PWRAP_DEBUG[ (19455)] - pwrap_init: Initialize pam_wrapper
PWRAP_DEBUG[ (19455)] - copy_confdir: Copy config files from
/<>/obj-x86_64-linux-gnu/tests/pam/services to /tmp/pam.q
PWRAP_DEBUG[ (19455)] - pwrap_init: Successfully initialized
pam_wrapper
PWRAP_DEBUG[ (19457)] - pwrap_init: Initialize pam_wrapper
PWRAP_DEBUG[ (19457)] - copy_confdir: Copy config files from
/<>/obj-x86_64-linux-gnu/tests/pam/services to /tmp/pam.s
PWRAP_DEBUG[ (19457)] - pwrap_init: Successfully initialized
pam_wrapper
PWRAP_DEBUG[ (19460)] - pwrap_init: Initialize pam_wrapper
PWRAP_DEBUG[ (19460)] - copy_confdir: Copy config files from
/<>/obj-x86_64-linux-gnu/tests/pam/services to /tmp/pam.0
PWRAP_DEBUG[ (19460)] - pwrap_init: Successfully initialized
pam_wrapper
--
531/531 fprintd:dist / check-translations
OK 0.17s
08:35:21 G_SLICE=always-malloc MALLOC_CHECK_=2 MALLOC_PERTURB_=96
/<>/po/check-translations.sh
--- output ---
--
Summary of Failures:
496/531 fprintd:+test_fprintd_utils+TestFprintdUtils /
TestFprintdUtils.test_fprintd_delete
FAIL 0.33s
exit status 1
498/531 fprintd:+test_fprintd_utils+TestFprintdUtils /
TestFprintdUtils.test_fprintd_enroll
FAIL 0.33s
exit status 1
499/531 fprintd:+test_fprintd_utils+TestFprintdUtils /
TestFprintdUtils.test_fprintd_list
FAIL 0.31s
exit status 1
504/531 fprintd:+test_fprintd_utils+TestFprintdUtilsVerify /
TestFprintdUtilsVerify.test_fprintd_list_all_fingers
FAIL 0.31s exit
status 1
505/531 fprintd:+test_fprintd_utils+TestFprintdUtilsVerify /
TestFprintdUtilsVerify.test_fprintd_multiple_verify_fails
FAIL 0.32s exit
status 1
506/531 fprintd:+test_fprintd_utils+TestFprintdUtilsVerify /
TestFprintdUtilsVerify.test_fprintd_verify
FAIL 0.31s exit
status 1
507/531 fprintd:+test_fprintd_utils+TestFprintdUtilsVerify /
TestFprintdUtilsVerify.test_fprintd_verify_any_finger_identification
FAIL 0.31s exit
status 1
508/531 fprintd:+test_fprintd_utils+TestFprintdUtilsVerify /
TestFprintdUtilsVerify.test_fprintd_verify_any_finger_no_identification
FAIL 0.32s exit
status 1
510/531 fprintd:+test_fprintd_utils+TestFprintdUtilsVerify /
TestFprintdUtilsVerify.test_fprintd_verify_enrolled_fingers
FAIL 0.33s exit
status 1
511/531 fprintd:+test_fprintd_utils+TestFprintdUtilsVerify /
TestFprintdUtilsVerify.test_fprintd_verify_no_enrolled_fingers
FAIL 0.32s exit
status 1
512/531
[Desktop-packages] [Bug 1952539] Re: Power Mode keeps switching back to balanced after performance is selected manually
The issue should be fixed in the current version ** Changed in: power-profiles-daemon (Ubuntu) Importance: Undecided => Low ** Changed in: power-profiles-daemon (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to power-profiles-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1952539 Title: Power Mode keeps switching back to balanced after performance is selected manually Status in power-profiles-daemon package in Ubuntu: Fix Released Bug description: I want my computer to keep running in performance mode. This worked well with 21.04, but since the upgrade the gnome shell applet tp switch this has been gone, instead in the setting i can now chose between performance / balanced and power saver. When I chose performance, close the settings app, and start doing what I want (make music with applications for this), I soon start to hear latency crackles. I go back to the settings then, and continue to see Power Mode being switched back to Balanced. What would I expect: I would expect after chosing Performance explicitly, it would stay like this. Especially as long as I dont change the power connection state of the machine or reboot, but ideally even when these things happen. But here, it doesn't even stay as selected even though the system is on a power line, and no reboot. It doesn't even last one minute in the state I chose it to be. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-control-center 1:40.0-1ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-21.21-lowlatency 5.13.18 Uname: Linux 5.13.0-21-lowlatency x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Sun Nov 28 01:54:18 2021 ExecutablePath: /usr/bin/gnome-control-center InstallationDate: Installed on 2020-04-12 (594 days ago) InstallationMedia: Ubuntu 19.10 "Eoan Ermine" - Release amd64 (20191017) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to impish on 2021-11-14 (13 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/power-profiles-daemon/+bug/1952539/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1825299] Re: The onscreen keyboard doesn't hide when touching anywhere out of the onscreen keyboard
** Changed in: gnome-shell (Ubuntu Bionic) Status: Triaged => Won't Fix ** Changed in: gnome-shell (Ubuntu Focal) Status: Triaged => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1825299 Title: The onscreen keyboard doesn't hide when touching anywhere out of the onscreen keyboard Status in GNOME Shell: New Status in OEM Priority Project: Fix Released Status in gnome-shell package in Ubuntu: Fix Released Status in gnome-shell source package in Bionic: Won't Fix Status in gnome-shell source package in Focal: Won't Fix Bug description: I use a XPS 13 9380 laptop with Disco. The onscreen keyboard doesn't hide when touching anywhere out of the onscreen keyboard. To add this, will be a good user experience. To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/1825299/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1876879] Re: gnome-software cannot install classic snaps if a channel is selected
** Changed in: gnome-software (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-software in Ubuntu. https://bugs.launchpad.net/bugs/1876879 Title: gnome-software cannot install classic snaps if a channel is selected Status in snap-store-desktop: Fix Released Status in gnome-software package in Ubuntu: Fix Released Bug description: I tried installing Android Studio from gnome-software. In the top right dropdown, it asks for the source. For Andoid Studio it displays Ubuntu. I was suspicious of it being a deb and not a snap. So I clicked on it and it shown me 3 Snap channel options. I selected latest/stable. The source changed according to my selection. Then I tried installing it but it failed saying: Unable to install "Android Studio": snap "android-studio" requires classic confinement I was puzzled. So I went back to the search menu, I clicked again on Android Studio and the source was now again on Ubuntu (note that this is not an option available in the dropdown). I checked the details and indeed it's the snap package from channel latest/stable, just the source is somehow misleading. Now it installed the software without issues. What doesn't work: - Source dropdown (top-right) shows "Ubuntu" instead of the snap channel - Selecting a channel breaks the install functionality for classic snaps (it seems like it attempts to install them without --classic) Workaround: Do not select any channel, just use what is provided, and it works. If needing to use a different channel, use the command line (or perhaps check if this works in the Snap Store, if it has not the same issue). ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-software 3.36.0-0ubuntu3 ProcVersionSignature: Ubuntu 5.4.0-28.32-generic 5.4.30 Uname: Linux 5.4.0-28-generic x86_64 ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: GNOME Date: Tue May 5 11:09:26 2020 InstallationDate: Installed on 2020-04-03 (31 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Beta amd64 (20200401) InstalledPlugins: gnome-software-plugin-flatpak 3.36.0-0ubuntu3 gnome-software-plugin-snap3.36.0-0ubuntu3 SourcePackage: gnome-software UpgradeStatus: No upgrade log present (probably fresh install) modified.conffile..etc.apport.crashdb.conf: [modified] mtime.conffile..etc.apport.crashdb.conf: 2020-05-04T10:26:46.106768 To manage notifications about this bug go to: https://bugs.launchpad.net/snap-store-desktop/+bug/1876879/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1890924] Re: Location services work with location services off, 20.04
There hasn't been more report about that and there is a new LTS out since, we are not likely to work on changing focal at this point ** Changed in: geoclue-2.0 (Ubuntu Focal) Status: Triaged => Won't Fix ** Changed in: geoclue-2.0 (Ubuntu Focal) Assignee: Sebastien Bacher (seb128) => (unassigned) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to geoclue-2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1890924 Title: Location services work with location services off, 20.04 Status in geoclue-2.0 package in Ubuntu: Fix Released Status in geoclue-2.0 source package in Focal: Won't Fix Status in geoclue-2.0 source package in Groovy: Won't Fix Bug description: * Impact Disabling the location service in settings isn't reflection on traditional deb applications * Test case - Log in an Ubuntu desktop session - install geoclue-2-demo - go to gnome-control-center, privacy, location and ensure the service is disabled - $ /usr/libexec/geoclue-2.0/demos/where-am-i the script should return a permission error and not a location * Regression potential [racb] Users who are currently relying on a working location service despite having a setting disabling it will find that the location service will stop working because the setting will start to be honoured. The change is in the client library, try a few applications, deb and snap or flatpak and make sure the status is correct respected - Not sure if this is the right package, but in the privacy -> location settings, in 18.04 I had to have my application be approved by user to access location with Geoclue. Now it seems this is working without the location services "enabled"?? My application is repeater-START: https://sourceforge.net/projects/repeater-start/ Steps to see issue: 1) install Repeater-START and click the locate me button circle to the left. It goes to your rough location on map. 2) Go to settings, privacy, location, note that location is turned off!? ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: gnome-settings-daemon 3.36.1-0ubuntu1 ProcVersionSignature: Ubuntu 5.4.0-40.44-generic 5.4.44 Uname: Linux 5.4.0-40-generic x86_64 NonfreeKernelModules: wl ApportVersion: 2.20.11-0ubuntu27.3 Architecture: amd64 CasperMD5CheckResult: skip Date: Sat Aug 8 19:38:12 2020 InstallationDate: Installed on 2017-07-29 (1106 days ago) InstallationMedia: Ubuntu 17.04 "Zesty Zapus" - Release amd64 (20170412) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: gnome-settings-daemon UpgradeStatus: Upgraded to focal on 2020-06-22 (47 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/geoclue-2.0/+bug/1890924/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1976249] Re: `xvfb-run` doesn't support `--auto-servernum`
Thank you for your bug report. The script isn't part of upstream xorg- server, where did you see that --auto-servernum has been deprecated? The script for Debian (and such Ubuntu) is on https://salsa.debian.org/xorg-team/xserver/xorg-server/-/blob/debian-unstable/debian/local/xvfb-run it seems fedora also has a copy which they patched some years ago to mark that option as deprecated and add auto-display instead, unsure what was the motivation behind the change though https://src.fedoraproject.org/rpms/xorg-x11-server/c/9e2c5679 ** Changed in: xorg-server (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1976249 Title: `xvfb-run` doesn't support `--auto-servernum` Status in xorg-server package in Ubuntu: New Bug description: `xvfb` is at version `2:21.1.3-2ubuntu2` which is the latest one. However, `xvfb-run -h` doesn't show the `--auto-display` argument and running `xvfb-run --auto-display ls` leads to `xvfb-run: unrecognized option '--auto-display'`. This is strange because in Arch Linux, the same `xvfb-run` version does support `--auto-display`. On Ubuntu one must use `--auto-servernum` because of that but that has been deprecated for quite a while now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1976249/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched
I just opened Evince from the command line ('evince' -> Enter) and am
seeing this error:
Entity: line 41: parser error : Extra content at the end of the document
endstream
It could be totally unrelated to this bug though.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1969896
Title:
Evince Document Viewer(42.0) does not remember last page in 22.04 and
opens in a tiny window when launched
Status in evince package in Ubuntu:
Confirmed
Bug description:
Just switched from Ubuntu 20.04 to 22.04 and realized that Document
Viewer no longer open on the last viewed page and doesn't remember the
side pane preference even after using the "Save Current Settings as
Default" option. Kindly advise
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: evince 42.1-3
ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30
Uname: Linux 5.15.0-25-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
Date: Fri Apr 22 15:58:50 2022
InstallationDate: Installed on 2022-03-19 (34 days ago)
InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223)
ProcEnviron:
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: evince
UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1969896/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1969896] Re: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched
I upgraded from 21.10 to 22.04. The issue happens when using a Wayland session or an Xorg session. My userdir is a local one. There is nothing special about my configuration. One thing that might be noteworthy is that before upgrading I was using the night mode of Evince and now it is stuck in night mode. I can disable night mode but this is not saved, meaning that when I close Evince and open it again it is back to night mode. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1969896 Title: Evince Document Viewer(42.0) does not remember last page in 22.04 and opens in a tiny window when launched Status in evince package in Ubuntu: Confirmed Bug description: Just switched from Ubuntu 20.04 to 22.04 and realized that Document Viewer no longer open on the last viewed page and doesn't remember the side pane preference even after using the "Save Current Settings as Default" option. Kindly advise ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: evince 42.1-3 ProcVersionSignature: Ubuntu 5.15.0-25.25-generic 5.15.30 Uname: Linux 5.15.0-25-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Apr 22 15:58:50 2022 InstallationDate: Installed on 2022-03-19 (34 days ago) InstallationMedia: Ubuntu 20.04.4 LTS "Focal Fossa" - Release amd64 (20220223) ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: evince UpgradeStatus: Upgraded to jammy on 2022-04-21 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evince/+bug/1969896/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1976249] [NEW] `xvfb-run` doesn't support `--auto-servernum`
Public bug reported: `xvfb` is at version `2:21.1.3-2ubuntu2` which is the latest one. However, `xvfb-run -h` doesn't show the `--auto-display` argument and running `xvfb-run --auto-display ls` leads to `xvfb-run: unrecognized option '--auto-display'`. This is strange because in Arch Linux, the same `xvfb-run` version does support `--auto-display`. On Ubuntu one must use `--auto-servernum` because of that but that has been deprecated for quite a while now. ** Affects: xorg-server (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xorg-server in Ubuntu. https://bugs.launchpad.net/bugs/1976249 Title: `xvfb-run` doesn't support `--auto-servernum` Status in xorg-server package in Ubuntu: New Bug description: `xvfb` is at version `2:21.1.3-2ubuntu2` which is the latest one. However, `xvfb-run -h` doesn't show the `--auto-display` argument and running `xvfb-run --auto-display ls` leads to `xvfb-run: unrecognized option '--auto-display'`. This is strange because in Arch Linux, the same `xvfb-run` version does support `--auto-display`. On Ubuntu one must use `--auto-servernum` because of that but that has been deprecated for quite a while now. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/1976249/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1970495] Re: Window manager freezes when plugging in USB-C dock with external monitor ([drm] *ERROR* mstb 00000000f21f0a30 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed)
I can reproduce this issue, too. When plug in the dock(with HDMI 4k monitor), the screen freeze and keyboard/touchpad won't work, but I still can ssh into the machine. Un-plug the dock, everything works again. BTW, I found gnome-shell runs in 100% while the issue happened, and un- plug the dock the CPU usage of gnome-shell comes back to normal. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1970495 Title: Window manager freezes when plugging in USB-C dock with external monitor ([drm] *ERROR* mstb f21f0a30 port 1: DPCD read on addr 0x4b0 for 1 bytes NAKed) Status in linux package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: 1. Problem DOES appear on Lenovo T470s (Intel). 2. Problem DOES appear on Lenovo T14 Gen2 (AMD). 3. Problem does NOT appear on either of the above *when in the Live Installer*. I specifically checked that my dock behaved well under the Live Installer before deciding to move my workstations to Jammy. Upon logging into a fresh Jammy install, I found the following problem behavior: When the dock is plugged in, the built-in display freezes and the dock-attached displays power up but never render anything (ie, they stay black). Unplugging the USB-C cable gets mouse/keyboard response back on the built-in display. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.0-2ubuntu1 ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30 Uname: Linux 5.15.0-27-generic x86_64 ApportVersion: 2.20.11-0ubuntu82 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Tue Apr 26 18:32:35 2022 DisplayManager: gdm3 InstallationDate: Installed on 2022-04-26 (0 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.0-3ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1970495/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956969] Re: When I restrt or shut down my ubuntu budgie just hangs there and freezes
The issue isn't due to the settings interface. Is that still a problem in the newer serie? ** Changed in: gnome-control-center (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1956969 Title: When I restrt or shut down my ubuntu budgie just hangs there and freezes Status in gnome-control-center package in Ubuntu: Incomplete Bug description: When I do the restart or the shutdown ubuntu freezes. I used to restart to get into my other distr (have dualinstallation in my laptop) via grub selection. Now, it never gets there (to grub) and I am forced to shut down using the power button. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gnome-control-center 1:40.0-1ubuntu5 ProcVersionSignature: Ubuntu 5.13.0-23.23-generic 5.13.19 Uname: Linux 5.13.0-23-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: Budgie:GNOME Date: Mon Jan 10 08:59:21 2022 InstallationDate: Installed on 2021-04-24 (261 days ago) InstallationMedia: Ubuntu-Budgie 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to impish on 2021-10-21 (80 days ago) modified.conffile..etc.default.apport: # set this to 0 to disable apport, or to 1 to enable it # you can temporarily override this with # sudo service apport start force_start=1 enabled=0 mtime.conffile..etc.default.apport: 2021-04-24T17:04:23.204166 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956969/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1887270] Re: brisk-menu crashed with SIGSEGV in g_slice_free_chain_with_offset()
Is that still an issue in newer series? ** Changed in: glib2.0 (Ubuntu) Status: New => Incomplete ** Changed in: glib2.0 (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1887270 Title: brisk-menu crashed with SIGSEGV in g_slice_free_chain_with_offset() Status in brisk-menu package in Ubuntu: Invalid Status in glib2.0 package in Ubuntu: Incomplete Bug description: Happened on MATE groovy live. ProblemType: Crash DistroRelease: Ubuntu 20.10 Package: mate-applet-brisk-menu 0.6.0-2 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: zfs zunicode zavl icp zcommon znvpair ApportVersion: 2.20.11-0ubuntu42 Architecture: amd64 CasperMD5CheckResult: pass CasperVersion: 1.452 CurrentDesktop: MATE Date: Sun Jul 12 08:25:47 2020 ExecutablePath: /usr/lib/x86_64-linux-gnu/brisk-menu/brisk-menu LiveMediaBuild: Ubuntu-MATE 20.10 "Groovy Gorilla" - Alpha amd64 (20200712) ProcCmdline: /usr/lib/x86_64-linux-gnu/brisk-menu//brisk-menu ProcEnviron: SHELL=/bin/bash XDG_RUNTIME_DIR= PATH=(custom, no user) LANG=en_US.UTF-8 SegvAnalysis: Segfault happened at: 0x7f07befc5d3e : mov(%r15,%rax,1),%r15 PC (0x7f07befc5d3e) ok source "(%r15,%rax,1)" (0x3ff8) not located in a known VMA region (needed readable region)! destination "%r15" ok SegvReason: reading unknown VMA Signal: 11 SourcePackage: brisk-menu StacktraceTop: g_slice_free_chain_with_offset () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_main_loop_run () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 Title: brisk-menu crashed with SIGSEGV in g_slice_free_chain_with_offset() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/brisk-menu/+bug/1887270/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956059] Re: Backport gspawn fixes to impish
Thank you for the report and the work, sorry that it didn't get triaged and acted on before though. It doesn't make sense to SRU to that serie anymore so closing the bug ** Changed in: glib2.0 (Ubuntu) Importance: Undecided => Low ** Changed in: glib2.0 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to glib2.0 in Ubuntu. https://bugs.launchpad.net/bugs/1956059 Title: Backport gspawn fixes to impish Status in glib2.0 package in Ubuntu: Fix Released Bug description: A few changes for gspawn landed in the 2.67 series that had some bugs which were later fixed and backported to 2.70 as seen in https://gitlab.gnome.org/GNOME/glib/-/merge_requests/2394. These bugs are present in 2.68 as on impish, but that series won't see any more updates upstream. Currently this is causing a bug in the OSTree test suite as seen in https://github.com/ostreedev/ostree/issues/2495 with https://github.com/ostreedev/ostree/issues/2495#issuecomment-1000247260 confirming from glib's maintainer that these bugs are likely the issue. Attached is a debdiff with the 3 patches that were backported to 2.70. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/glib2.0/+bug/1956059/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956388] Re: gtk+3.0: FTBFS: dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below
The issue is fixed in the current version ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => High ** Changed in: gtk+3.0 (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gtk+3.0 in Ubuntu. https://bugs.launchpad.net/bugs/1956388 Title: gtk+3.0: FTBFS: dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below Status in gtk+3.0 package in Ubuntu: Fix Released Status in gtk+3.0 package in Debian: Fix Released Bug description: apt-get source -b libgtk-3-dev Reading package lists... Done Picking 'gtk+3.0' as source package instead of 'libgtk-3-dev' NOTICE: 'gtk+3.0' packaging is maintained in the 'Git' version control system at: https://salsa.debian.org/gnome-team/gtk3.git -b ubuntu/focal Please use: git clone https://salsa.debian.org/gnome-team/gtk3.git -b ubuntu/focal to retrieve the latest (possibly unreleased) updates to the package. Need to get 22.9 MB of source archives. Get:1 http://archive.ubuntu.com/ubuntu focal-updates/main gtk+3.0 3.24.20-0ubuntu1 (dsc) [3,639 B] Get:2 http://archive.ubuntu.com/ubuntu focal-updates/main gtk+3.0 3.24.20-0ubuntu1 (tar) [22.7 MB] Get:3 http://archive.ubuntu.com/ubuntu focal-updates/main gtk+3.0 3.24.20-0ubuntu1 (diff) [171 kB] Fetched 22.9 MB in 28s (815 kB/s) dpkg-source: info: extracting gtk+3.0 in gtk+3.0-3.24.20 dpkg-source: info: unpacking gtk+3.0_3.24.20.orig.tar.xz dpkg-source: info: unpacking gtk+3.0_3.24.20-0ubuntu1.debian.tar.xz dpkg-source: info: using patch list from debian/patches/series ... dwz: debian/libgtk-3-0/usr/lib/x86_64-linux-gnu/libgtk-3.so.0.2404.16: DWARF compression not beneficial - old size 8243658 new size 8376050 dh_strip -O--buildsystem=autoconf debian/rules override_dh_makeshlibs make[1]: Entering directory '/root/gtk+3.0-3.24.20' sed: couldn't write 35 items to stdout: Broken pipe dh_makeshlibs -plibgtk-3-0 --add-udeb=libgtk-3-0-udeb -Xusr/lib/x86_64-linux-gnu/gtk-3.0/3.0.0 -- -c4 dpkg-gensymbols: error: some new symbols appeared in the symbols file: see diff output below dpkg-gensymbols: warning: debian/libgtk-3-0/DEBIAN/symbols doesn't match completely debian/libgtk-3-0.symbols --- debian/libgtk-3-0.symbols (libgtk-3-0_3.24.20-0ubuntu1_amd64) +++ dpkg-gensymbolsrezAkY 2022-01-04 20:54:52.551202248 + @@ -1,5 +1,8 @@ libgdk-3.so.0 libgtk-3-0 #MINVER# * Build-Depends-Package: libgtk-3-dev + _gdk_get_resource@Base 3.24.20-0ubuntu1 + _gdk_register_resource@Base 3.24.20-0ubuntu1 + _gdk_unregister_resource@Base 3.24.20-0ubuntu1 gdk__private__@Base 3.16.2 gdk_add_option_entries_libgtk_only@Base 3.0.0 gdk_anchor_hints_get_type@Base 3.21.5 @@ -758,6 +761,9 @@ gdk_x11_xatom_to_atom@Base 3.0.0 gdk_x11_xatom_to_atom_for_display@Base 3.0.0 libgtk-3.so.0 libgtk-3-0 #MINVER# + _gtk_get_resource@Base 3.24.20-0ubuntu1 + _gtk_register_resource@Base 3.24.20-0ubuntu1 + _gtk_unregister_resource@Base 3.24.20-0ubuntu1 gtk_about_dialog_add_credit_section@Base 3.3.16 gtk_about_dialog_get_artists@Base 3.0.0 gtk_about_dialog_get_authors@Base 3.0.0 dh_makeshlibs: error: failing due to earlier errors make[1]: *** [debian/rules:243: override_dh_makeshlibs] Error 2 make[1]: Leaving directory '/root/gtk+3.0-3.24.20' make: *** [debian/rules:135: binary] Error 2 dpkg-buildpackage: error: debian/rules binary subprocess returned exit status 2 W: Download is performed unsandboxed as root as file 'gtk+3.0_3.24.20-0ubuntu1.dsc' couldn't be accessed by user '_apt'. - pkgAcquire::Run (13: Permission denied) E: Build command 'cd gtk+3.0-3.24.20 && dpkg-buildpackage -b -uc' failed. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libgtk-3-dev (not installed) ProcVersionSignature: Ubuntu 5.4.0-92.103-generic 5.4.157 Uname: Linux 5.4.0-92-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: MATE Date: Wed Jan 5 00:02:06 2022 InstallationDate: Installed on 2020-04-23 (621 days ago) InstallationMedia: Ubuntu-MATE 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: gtk+3.0 UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk+3.0/+bug/1956388/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1956438] Re: confusing UI -- expected a LAN file share, not DLNA, and '+' button is not apparent
The issue would be better reported upstream on https://gitlab.gnome.org/GNOME/gnome-control-center/-/issues ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1956438 Title: confusing UI -- expected a LAN file share, not DLNA, and '+' button is not apparent Status in gnome-control-center package in Ubuntu: New Bug description: is this the right package for the media sharing UI in settings on ubuntu 21.10? i was just trying to set up a local network share and the UI for "media sharing" made me think ubuntu thought "people want to share music, video, and pictures folders, so we'll just have those preselected as shareable directories on the network." i know what DLNA is, but it never entered my mind that's what this was for. it should just say something like "via DLNA to things like smart tv's" or something. also, the box that music, videos, and pictures is in is exactly filled up by those 3 buttons, and the "+" button below them is not visible, so it is not apparent you can scroll down and it is there. put the '+' button outside the box so it can't be scrolled away, and show the directories just like normal directories in the file viewer, not as buttons. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1956438/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1870829] Re: AptX and AptX HD unavailable as Bluetooth audio quality options
** Changed in: pulseaudio (Ubuntu) Status: Confirmed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to pulseaudio in Ubuntu. https://bugs.launchpad.net/bugs/1870829 Title: AptX and AptX HD unavailable as Bluetooth audio quality options Status in pulseaudio package in Ubuntu: Fix Released Status in pulseaudio package in Debian: Fix Released Bug description: Current situation: When one connects a Bluetooth audio device, at best one can choose between "Headset Head Unit (HSP/HFP)" and "High Fidelity Playback (A2DP Sink)". That is sad when the audio device supports AptX or AptX HD. Expected situation: One can select AptX or AptX HD as the Bluetooth audio output profile. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/1870829/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1908358] Re: gnome-control-center crashes on start
Thank you for your bug report. Is that still an issue and if so could you do $ ldd -r $(which gnome-control-center) and provide the output on the bug? those issues are usually due to local installation of libraries ** Changed in: gnome-control-center (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-control-center in Ubuntu. https://bugs.launchpad.net/bugs/1908358 Title: gnome-control-center crashes on start Status in gnome-control-center package in Ubuntu: Incomplete Bug description: Description: Ubuntu 20.04.1 LTS Release: 20.04 gnome-control-center: Installed: 1:3.36.4-0ubuntu2 Candidate: 1:3.36.4-0ubuntu2 Version table: *** 1:3.36.4-0ubuntu2 500 500 http://ru.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 100 /var/lib/dpkg/status 1:3.36.1-1ubuntu5 500 500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages samba-libs: Installed: 2:4.11.6+dfsg-0ubuntu1.6 Candidate: 2:4.11.6+dfsg-0ubuntu1.6 Version table: *** 2:4.11.6+dfsg-0ubuntu1.6 500 500 http://ru.archive.ubuntu.com/ubuntu focal-updates/main amd64 Packages 500 http://security.ubuntu.com/ubuntu focal-security/main amd64 Packages 100 /var/lib/dpkg/status 2:4.11.6+dfsg-0ubuntu1 500 500 http://ru.archive.ubuntu.com/ubuntu focal/main amd64 Packages When I start gnome-control-center it crashes with error: $ gnome-control-center gnome-control-center: symbol lookup error: /usr/lib/x86_64-linux-gnu/samba/libclidns.so.0: undefined symbol: ndr_pull_dns_name_packet, version NDR_NBT_0.0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/1908358/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1769991] Re: [16.04] Unable to import OpenVPN configuration into Network Manager
** Changed in: network-manager-openvpn (Ubuntu Xenial) Status: New => Won't Fix ** Changed in: network-manager-openvpn (Ubuntu Xenial) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to network-manager-openvpn in Ubuntu. https://bugs.launchpad.net/bugs/1769991 Title: [16.04] Unable to import OpenVPN configuration into Network Manager Status in network-manager-openvpn package in Ubuntu: Fix Released Status in network-manager-openvpn source package in Xenial: Won't Fix Bug description: In 16.04, it is currently not possible to import OpenVPN configurations. Specifically, imports fail with the error of: The file 'filename.ovpn' could not be read or does not contain recognized VPN connection information. Error: Key file contains line 'client' which is not a key-value pair, group, or comment. -- An example configuration that fails to import is as follows (with some critical components excluded, like a proper remote address, or a proper x509 name); this is a config that otherwise works with a Sophos XG Firewall-based SSL VPN system client dev tun persist-tun persist-key proto tcp verify-x509-name "" route remote_host 255.255.255.255 net_gateway resolv-retry infinite remote 1.2.3.4 8443 tcp ca ca.crt cert client.crt key client.key auth-user-pass cipher AES-256-CBC auth SHA512 comp-lzo no route-delay 4 verb 3 reneg-sec 0 -- This same exact configuration works with a direct call of `openvpn ./filename.ovpn`. Why Network Manager is unable to parse or import the OpenVPN configuration is beyond my ability to comprehend. Note that the same configuration made by hand in the new VPN window works fine, but the import function fails. (Which is a pretty severe bug) ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager-openvpn 1.1.93-1ubuntu1.1 ProcVersionSignature: Ubuntu 4.13.0-39.44~16.04.1-generic 4.13.16 Uname: Linux 4.13.0-39-generic x86_64 ApportVersion: 2.20.1-0ubuntu2.16 Architecture: amd64 CurrentDesktop: Unity Date: Tue May 8 14:59:54 2018 InstallationDate: Installed on 2016-12-20 (503 days ago) InstallationMedia: Ubuntu 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719) SourcePackage: network-manager-openvpn UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1769991/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
