[Desktop-packages] [Bug 2042740] Re: xdg-screensaver doesn't support xss-lock
...note that using the xss-lock available from apt-get, the man page mentions the freedesktop.org patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/2042740 Title: xdg-screensaver doesn't support xss-lock Status in xdg-utils package in Ubuntu: New Bug description: It appears this was fixed in upstream "from freedesktop.org" https://bugs.freedesktop.org/show_bug.cgi?id=108865 However that patch did not fully work for me, as the '^xss-lock' pattern doesn't find "/usr/bin/xss-lock" which is how "ps" actually lists the process i'm attaching a patch which fixes the issue and is resilient to process paths ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xdg-utils 1.1.3-4.1ubuntu3~22.04.1 [modified: usr/bin/xdg-screensaver] ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sat Nov 4 11:16:36 2023 InstallationDate: Installed on 2020-06-04 (1248 days ago) InstallationMedia: Lubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203) PackageArchitecture: all SourcePackage: xdg-utils UpgradeStatus: Upgraded to jammy on 2022-09-03 (426 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/2042740/+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 2042740] Re: xdg-screensaver doesn't support xss-lock
The attachment "patch to add support for xss-lock" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/2042740 Title: xdg-screensaver doesn't support xss-lock Status in xdg-utils package in Ubuntu: New Bug description: It appears this was fixed in upstream "from freedesktop.org" https://bugs.freedesktop.org/show_bug.cgi?id=108865 However that patch did not fully work for me, as the '^xss-lock' pattern doesn't find "/usr/bin/xss-lock" which is how "ps" actually lists the process i'm attaching a patch which fixes the issue and is resilient to process paths ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xdg-utils 1.1.3-4.1ubuntu3~22.04.1 [modified: usr/bin/xdg-screensaver] ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sat Nov 4 11:16:36 2023 InstallationDate: Installed on 2020-06-04 (1248 days ago) InstallationMedia: Lubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203) PackageArchitecture: all SourcePackage: xdg-utils UpgradeStatus: Upgraded to jammy on 2022-09-03 (426 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/2042740/+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 2042740] [NEW] xdg-screensaver doesn't support xss-lock
Public bug reported: It appears this was fixed in upstream "from freedesktop.org" https://bugs.freedesktop.org/show_bug.cgi?id=108865 However that patch did not fully work for me, as the '^xss-lock' pattern doesn't find "/usr/bin/xss-lock" which is how "ps" actually lists the process i'm attaching a patch which fixes the issue and is resilient to process paths ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xdg-utils 1.1.3-4.1ubuntu3~22.04.1 [modified: usr/bin/xdg-screensaver] ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sat Nov 4 11:16:36 2023 InstallationDate: Installed on 2020-06-04 (1248 days ago) InstallationMedia: Lubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203) PackageArchitecture: all SourcePackage: xdg-utils UpgradeStatus: Upgraded to jammy on 2022-09-03 (426 days ago) ** Affects: xdg-utils (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/2042740 Title: xdg-screensaver doesn't support xss-lock Status in xdg-utils package in Ubuntu: New Bug description: It appears this was fixed in upstream "from freedesktop.org" https://bugs.freedesktop.org/show_bug.cgi?id=108865 However that patch did not fully work for me, as the '^xss-lock' pattern doesn't find "/usr/bin/xss-lock" which is how "ps" actually lists the process i'm attaching a patch which fixes the issue and is resilient to process paths ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xdg-utils 1.1.3-4.1ubuntu3~22.04.1 [modified: usr/bin/xdg-screensaver] ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sat Nov 4 11:16:36 2023 InstallationDate: Installed on 2020-06-04 (1248 days ago) InstallationMedia: Lubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203) PackageArchitecture: all SourcePackage: xdg-utils UpgradeStatus: Upgraded to jammy on 2022-09-03 (426 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/2042740/+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 2042740] Re: xdg-screensaver doesn't support xss-lock
** Attachment added: "patch to add support for xss-lock" https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/2042740/+attachment/5716025/+files/patch.txt ** Description changed: It appears this was fixed in upstream "from freedesktop.org" https://bugs.freedesktop.org/show_bug.cgi?id=108865 However that patch did not fully work for me, as the '^xss-lock' pattern doesn't find "/usr/bin/xss-lock" which is how "ps" actually lists the process - This patch works for me: - -- - --- xdg-screensaver.orig2021-11-19 11:09:46.0 -0800 - +++ xdg-screensaver 2023-11-04 11:01:01.877293873 -0700 - @@ -618,6 +618,14 @@ -xautolock_screensaver "$1" -;; - - +xss-lock_screensaver) - + if [ "$1" = "lock" ]; then - + screensaver_xserver "activate" - + else - + screensaver_xserver "$1" - + fi - + ;; - + - xfce) -[ -n "$DISPLAY" ] && screensaver_xserver "$1" -;; - @@ -1401,6 +1409,8 @@ - dbus-send --print-reply --dest=org.freedesktop.DBus /org/freedesktop/DBus org.freedesktop.DBus.GetNameOwner string:org.cinnamon.ScreenSaver > /dev/null 2>&1 && DE="cinnamon" - # Consider "xautolock" a separate DE - xautolock -enable > /dev/null 2>&1 && DE="xautolock_screensaver" - +# Consider "xss-lock" a separate DE - +xss-lock --version > /dev/null 2>&1 && pgrep xss-lock > /dev/null 2>&1 && DE="xss-lock_screensaver" - - if [ "$action" = "resume" ] ; then - do_resume - [ + i'm attaching a patch which fixes the issue and is resilient to process + paths ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xdg-utils 1.1.3-4.1ubuntu3~22.04.1 [modified: usr/bin/xdg-screensaver] ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sat Nov 4 11:16:36 2023 InstallationDate: Installed on 2020-06-04 (1248 days ago) InstallationMedia: Lubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203) PackageArchitecture: all SourcePackage: xdg-utils UpgradeStatus: Upgraded to jammy on 2022-09-03 (426 days ago) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to xdg-utils in Ubuntu. https://bugs.launchpad.net/bugs/2042740 Title: xdg-screensaver doesn't support xss-lock Status in xdg-utils package in Ubuntu: New Bug description: It appears this was fixed in upstream "from freedesktop.org" https://bugs.freedesktop.org/show_bug.cgi?id=108865 However that patch did not fully work for me, as the '^xss-lock' pattern doesn't find "/usr/bin/xss-lock" which is how "ps" actually lists the process i'm attaching a patch which fixes the issue and is resilient to process paths ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: xdg-utils 1.1.3-4.1ubuntu3~22.04.1 [modified: usr/bin/xdg-screensaver] ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: LXQt Date: Sat Nov 4 11:16:36 2023 InstallationDate: Installed on 2020-06-04 (1248 days ago) InstallationMedia: Lubuntu 18.04.4 LTS "Bionic Beaver" - Release amd64 (20200203) PackageArchitecture: all SourcePackage: xdg-utils UpgradeStatus: Upgraded to jammy on 2022-09-03 (426 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/xdg-utils/+bug/2042740/+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 2034664] Re: Meta.Rectangle is deprecated, use Mtk.Rectangle instead
Thanks Pablo, I must've done something wrong. Installed it now and issue solved for me on mantic. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell-extension-ubuntu-dock in Ubuntu. https://bugs.launchpad.net/bugs/2034664 Title: Meta.Rectangle is deprecated, use Mtk.Rectangle instead Status in gnome-shell-extension-tiling-assistant package in Ubuntu: Fix Released Status in gnome-shell-extension-ubuntu-dock package in Ubuntu: Fix Released Status in gnome-shell-extension-tiling-assistant source package in Mantic: Fix Released Status in gnome-shell-extension-ubuntu-dock source package in Mantic: Fix Committed Bug description: [ Impact ] The gnome-shell 45.rc log fills with: Meta.Rectangle is deprecated, use Mtk.Rectangle instead [ Test case ] Run ubuntu with ubuntu extensions enabled (only). journalctl /usr/bin/gnome-shell should not contain any reference to Meta.Rectangle deprecation [ Regression potential ] Introspected types are not defined and so extensions may try to use undefined code. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-tiling-assistant/+bug/2034664/+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 2032361] Re: /usr/bin/gjs-console -> mem_error -> slab_allocator_free_chunk -> magazine_cache_trim -> magazine_cache_push_magazine -> thread_memory_magazine2_unload
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2032361 Title: /usr/bin/gjs-console -> mem_error -> slab_allocator_free_chunk -> magazine_cache_trim -> magazine_cache_push_magazine -> thread_memory_magazine2_unload Status in gjs package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Confirmed Status in gjs source package in Jammy: Confirmed Status in gnome-shell-extension-desktop-icons-ng source package in Jammy: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gjs. This problem was most recently seen with package version 1.72.4-0ubuntu0.22.04.1, the problem page at https://errors.ubuntu.com/problem/1f9c97abee01a68e89299b0eb72857417359a8f3 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2032361/+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 2032361] Re: /usr/bin/gjs-console -> mem_error -> slab_allocator_free_chunk -> magazine_cache_trim -> magazine_cache_push_magazine -> thread_memory_magazine2_unload
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gjs (Ubuntu Jammy) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2032361 Title: /usr/bin/gjs-console -> mem_error -> slab_allocator_free_chunk -> magazine_cache_trim -> magazine_cache_push_magazine -> thread_memory_magazine2_unload Status in gjs package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Confirmed Status in gjs source package in Jammy: Confirmed Status in gnome-shell-extension-desktop-icons-ng source package in Jammy: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gjs. This problem was most recently seen with package version 1.72.4-0ubuntu0.22.04.1, the problem page at https://errors.ubuntu.com/problem/1f9c97abee01a68e89299b0eb72857417359a8f3 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2032361/+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 2032361] Re: /usr/bin/gjs-console -> mem_error -> slab_allocator_free_chunk -> magazine_cache_trim -> magazine_cache_push_magazine -> thread_memory_magazine2_unload
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell-extension-desktop-icons-ng (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2032361 Title: /usr/bin/gjs-console -> mem_error -> slab_allocator_free_chunk -> magazine_cache_trim -> magazine_cache_push_magazine -> thread_memory_magazine2_unload Status in gjs package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Confirmed Status in gjs source package in Jammy: Confirmed Status in gnome-shell-extension-desktop-icons-ng source package in Jammy: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gjs. This problem was most recently seen with package version 1.72.4-0ubuntu0.22.04.1, the problem page at https://errors.ubuntu.com/problem/1f9c97abee01a68e89299b0eb72857417359a8f3 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2032361/+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 2032361] Re: /usr/bin/gjs-console -> mem_error -> slab_allocator_free_chunk -> magazine_cache_trim -> magazine_cache_push_magazine -> thread_memory_magazine2_unload
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gjs (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/2032361 Title: /usr/bin/gjs-console -> mem_error -> slab_allocator_free_chunk -> magazine_cache_trim -> magazine_cache_push_magazine -> thread_memory_magazine2_unload Status in gjs package in Ubuntu: Confirmed Status in gnome-shell-extension-desktop-icons-ng package in Ubuntu: Confirmed Status in gjs source package in Jammy: Confirmed Status in gnome-shell-extension-desktop-icons-ng source package in Jammy: Confirmed Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gjs. This problem was most recently seen with package version 1.72.4-0ubuntu0.22.04.1, the problem page at https://errors.ubuntu.com/problem/1f9c97abee01a68e89299b0eb72857417359a8f3 contains more details, including versions of packages affected, stacktrace or traceback, and individual crash reports. If you do not have access to the Ubuntu Error Tracker and are a software developer, you can request it at http://forms.canonical.com/reports/. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/2032361/+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 2042705] Re: screen blank randomly fails and system crashes when X is restarted
It sounds like this bug is (at least partly) related to https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2040453 -- 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/2042705 Title: screen blank randomly fails and system crashes when X is restarted Status in gnome-shell package in Ubuntu: New Bug description: My screen randomly stops blanking, ignoring the interval I set under Settings > Power > Power Saving Options > Screen blank (8 minutes). This behaviour behaviour has so far manifested only after I resumed the system from suspend but that connection is not consistent - more often than not, the system resumes without any noticeable impact on screen blanking. However, when screen blanking does break, it appears to go hand in hand with an unstable gnome session. That is, when I try to restart my gnome session (I am using X), it results in a desktop crash and I am forced to log out. (on a side note: I noticed the other day that gnome also broke when I logged out of my second desktop account to return to my main account; the screen went black and I had to reboot). The crash does not appear to generate a log but journald has recorded the following at/around the time that restarting gnome-shell ended in a crash (the messages are reproduced here in reverse order): nov 04 02:41:46 Dapple gsd-media-keys[3125]: g_dbus_proxy_call_internal: assertion 'G_IS_DBUS_PROXY (proxy)' failed nov 04 02:41:45 Dapple systemd[2589]: org.gnome.Shell-disable-extensions.service - Disable GNOME Shell extensions after failure was skipped because of an unmet condition check (ConditionPathExists=/run/user/1002/gnome-shell-disa> nov 04 02:41:45 Dapple systemd[2589]: Reached target gnome-session-failed.target - GNOME Session Failed. nov 04 02:41:45 Dapple systemd[2589]: Started gnome-session-failed.service - GNOME Session Failed lockdown screen (user). nov 04 02:41:45 Dapple systemd[2589]: org.gnome.Shell@x11.service: Triggering OnFailure= dependencies. nov 04 02:41:45 Dapple systemd[2589]: Failed to start org.gnome.Shell@x11.service - GNOME Shell on X11. nov 04 02:41:45 Dapple systemd[2589]: org.gnome.Shell@x11.service: Failed with result 'protocol'. nov 04 02:41:45 Dapple systemd[2589]: org.gnome.Shell@x11.service: Start request repeated too quickly. nov 04 02:41:45 Dapple systemd[2589]: Stopped org.gnome.Shell@x11.service - GNOME Shell on X11. nov 04 02:41:45 Dapple systemd[2589]: org.gnome.Shell@x11.service: Scheduled restart job, restart counter is at 4. nov 04 02:41:45 Dapple systemd[2589]: Failed to start org.gnome.Shell@x11.service - GNOME Shell on X11. nov 04 02:41:45 Dapple systemd[2589]: org.gnome.Shell@x11.service: Failed with result 'protocol'. nov 04 02:41:45 Dapple gnome-shell[73870]: Window manager error: Another compositing manager is already running on screen 0 on display “:1”. nov 04 02:41:45 Dapple gsd-media-keys[3125]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Object does not exist at path “/org/gnome/Shell” nov 04 02:41:44 Dapple gsd-media-keys[3125]: Failed to grab accelerators: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: Object does not exist at path “/org/gnome/Shell” nov 04 02:41:44 Dapple xdg-desktop-por[3867]: Failed to get application states: GDBus.Error:org.freedesktop.portal.Error.Failed: Could not get window list nov 04 02:41:44 Dapple /usr/libexec/gdm-x-session[2762]: (--) NVIDIA(GPU-0): nov 04 02:41:44 Dapple /usr/libexec/gdm-x-session[2762]: (--) NVIDIA(GPU-0): DFP-4: 330.0 MHz maximum pixel clock nov 04 02:41:44 Dapple /usr/libexec/gdm-x-session[2762]: (--) NVIDIA(GPU-0): DFP-4: Internal TMDS nov 04 02:41:44 Dapple /usr/libexec/gdm-x-session[2762]: (--) NVIDIA(GPU-0): DFP-4: disconnected nov 04 02:41:44 Dapple /usr/libexec/gdm-x-session[2762]: (--) NVIDIA(GPU-0): nov 04 02:41:44 Dapple /usr/libexec/gdm-x-session[2762]: (--) NVIDIA(GPU-0): DFP-3: 165.0 MHz maximum pixel clock nov 04 02:41:44 Dapple /usr/libexec/gdm-x-session[2762]: (--) NVIDIA(GPU-0): DFP-3: Internal TMDS nov 04 02:41:44 Dapple /usr/libexec/gdm-x-session[2762]: (--) NVIDIA(GPU-0): DFP-3: disconnected nov 04 02:41:44 Dapple /usr/libexec/gdm-x-session[2762]: (--) NVIDIA(GPU-0): nov 04 02:41:44 Dapple /usr/libexec/gdm-x-session[2762]: (--) NVIDIA(GPU-0): DFP-2: 960.0 MHz maximum pixel clock nov 04 02:41:44 Dapple /usr/libexec/gdm-x-session[2762]: (--) NVIDIA(GPU-0): DFP-2: Internal DisplayPort nov 04 02:41:44 Dapple /usr/libexec/gdm-x-session[2762]: (--) NVIDIA(GPU-0): DFP-2: disconnected nov 04 02:41:44 Dapple /usr/libexec/gdm-x-session[2762]: (--) NVIDIA(GPU-0): nov 04 02:41:44 Dapple /usr/libexec/gdm-x-session[2762]: (--) NVIDIA(GPU-0): BenQ EW3270U (DFP-1): 600.0 MHz maximum pixel clock nov 04 02:41:44 Dapple /usr/libexec/gdm-x-sessi
[Desktop-packages] [Bug 2031096] Re: udisks2 daemon fails to start
Bug no longer present in release version of 23.10. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/2031096 Title: udisks2 daemon fails to start Status in udisks: New Status in udisks2 package in Ubuntu: Incomplete Bug description: udisks2 2.10.0 fails to start in Ubuntu Mantic (23.10) Error status is: Aug 11 10:36:37 nodename systemd[1]: Starting udisks2.service - Disk Manager... Aug 11 10:36:37 nodename udisksd[232247]: udisks daemon version 2.10.0 starting Aug 11 10:36:38 nodename udisksd[232247]: Error getting 'loop28' information: Failed to open device loop28: No such file o> Aug 11 10:36:38 nodename udisksd[232247]: Error getting 'loop28' information: Failed to open device loop28: No such file o> Aug 11 10:36:38 nodename udisksd[232247]: *** stack smashing detected ***: terminated Aug 11 10:36:38 nodename systemd[1]: udisks2.service: Main process exited, code=dumped, status=6/ABRT Aug 11 10:36:38 nodename systemd[1]: udisks2.service: Failed with result 'core-dump'. Aug 11 10:36:38 nodename systemd[1]: Failed to start udisks2.service - Disk Manager. This bug seems to refer: https://github.com/storaged- project/udisks/issues/1139 To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/2031096/+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 2039235] Re: gnome-online-accounts -> when signing into google account, infinite loading after entering password
Can confirm that the workaround worked for me as well. I had a yubikey on my google account and that was what caused the issue. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-online-accounts in Ubuntu. https://bugs.launchpad.net/bugs/2039235 Title: gnome-online-accounts -> when signing into google account, infinite loading after entering password Status in gnome-online-accounts package in Ubuntu: Confirmed Bug description: 1) What you expected to happen - sign in is successful, which will allow google services to populate the appropriate applications (calendar, mail, google drive) 2) What actually happened - sign in hangs infinitely after entering the password - the process is able to detect that the password is correct or incorrect. When entering an incorrect password, it will correctly and quickly complain that the password is incorrect. When entering the correct password, the bug will occur. 3) Steps to reproduce a) start the program b) select online accounts c) select google d) enter email e) enter password f) loads forever ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gnome-online-accounts 3.48.0-2 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Thu Oct 12 22:27:59 2023 InstallationDate: Installed on 2023-10-12 (0 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-online-accounts UpgradeStatus: No upgrade log present (probably fresh install) Hardware info (not sure if relevant): cpu: intel gpu: nvidia (driver version: "Using NVIDIA driver metapackage from nvidia-driver-535(proprietary, tested)") To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-online-accounts/+bug/2039235/+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 2042729] [NEW] Xorg freeze
Public bug reported:
Computer unresponsive after closing laptop screen and reopening. GDM
screen does not appear to login, just see contents of the X session
before i closed the lid. mouse moves and hardware buttons (mute, caps
lock etc) are responsive with LEDs. Have to hard reboot to login and use
computer
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus..01.00.0: Error: path was not a regular file.
.proc.driver.nvidia.registry: Binary: ""
.proc.driver.nvidia.suspend: suspend hibernate resume
.proc.driver.nvidia.suspend_depth: default modeset uvm
.proc.driver.nvidia.version:
NVRM version: NVIDIA UNIX x86_64 Kernel Module 535.129.03 Thu Oct 19
18:56:32 UTC 2023
GCC version:
ApportVersion: 2.27.0-0ubuntu5
Architecture: amd64
BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log'
CasperMD5CheckResult: pass
CompositorRunning: None
CurrentDesktop: ubuntu:GNOME
Date: Sat Nov 4 15:33:14 2023
DistUpgraded: 2023-11-02 15:19:38,871 DEBUG 'libkf5itemviews5' scheduled for
remove but not safe to remove, skipping
DistroCodename: mantic
DistroVariant: ubuntu
ExtraDebuggingInterest: Yes
GpuHangFrequency: Several times a week
GpuHangReproducibility: Yes, I can easily reproduce it
GpuHangStarted: Within the last few days
GraphicsCard:
Intel Corporation CoffeeLake-H GT2 [UHD Graphics 630] [8086:3e9b] (prog-if 00
[VGA controller])
Subsystem: Lenovo CoffeeLake-H GT2 [UHD Graphics 630] [17aa:229f]
NVIDIA Corporation TU117M [GeForce GTX 1650 Mobile / Max-Q] [10de:1f91] (rev
a1) (prog-if 00 [VGA controller])
Subsystem: Lenovo TU117M [GeForce GTX 1650 Mobile / Max-Q] [17aa:229f]
InstallationDate: Installed on 2023-05-24 (164 days ago)
InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230417)
MachineType: {report['dmi.sys.vendor']} {report['dmi.product.name']}
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
SHELL=/bin/bash
XDG_RUNTIME_DIR=
ProcKernelCmdLine: BOOT_IMAGE=/vmlinuz-6.5.0-10-generic
root=UUID=45e4e3f8-045a-4651-bd83-6087eca44175 ro quiet splash vt.handoff=7
SourcePackage: xorg
Symptom: display
Title: Xorg freeze
UpgradeStatus: Upgraded to mantic on 2023-11-02 (2 days ago)
dmi.bios.date: 09/19/2023
dmi.bios.release: 1.48
dmi.bios.vendor: LENOVO
dmi.bios.version: N2OET61W (1.48 )
dmi.board.asset.tag: Not Available
dmi.board.name: 20QV00BRUK
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40697 WIN
dmi.chassis.asset.tag: No Asset Information
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.version: None
dmi.ec.firmware.release: 1.22
dmi.modalias:
dmi:bvnLENOVO:bvrN2OET61W(1.48):bd09/19/2023:br1.48:efr1.22:svnLENOVO:pn20QV00BRUK:pvrThinkPadX1Extreme2nd:rvnLENOVO:rn20QV00BRUK:rvrSDK0J40697WIN:cvnLENOVO:ct10:cvrNone:skuLENOVO_MT_20QV_BU_Think_FM_ThinkPadX1Extreme2nd:
dmi.product.family: ThinkPad X1 Extreme 2nd
dmi.product.name: 20QV00BRUK
dmi.product.sku: LENOVO_MT_20QV_BU_Think_FM_ThinkPad X1 Extreme 2nd
dmi.product.version: ThinkPad X1 Extreme 2nd
dmi.sys.vendor: LENOVO
version.compiz: compiz N/A
version.libdrm2: libdrm2 2.4.115-1
version.libgl1-mesa-dri: libgl1-mesa-dri 23.2.1-1ubuntu3
version.libgl1-mesa-glx: libgl1-mesa-glx 23.0.4-0ubuntu1~23.04.1
version.nvidia-graphics-drivers: nvidia-graphics-drivers-* N/A
version.xserver-xorg-core: xserver-xorg-core 2:21.1.7-3ubuntu2.1
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-3
version.xserver-xorg-video-intel: xserver-xorg-video-intel
2:2.99.917+git20210115-1
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-2build1
** Affects: xorg (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug freeze mantic ubuntu
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to xorg in Ubuntu.
https://bugs.launchpad.net/bugs/2042729
Title:
Xorg freeze
Status in xorg package in Ubuntu:
New
Bug description:
Computer unresponsive after closing laptop screen and reopening. GDM
screen does not appear to login, just see contents of the X session
before i closed the lid. mouse moves and hardware buttons (mute, caps
lock etc) are responsive with LEDs. Have to hard reboot to login and
use computer
ProblemType: Bug
DistroRelease: Ubuntu 23.10
Package: xorg 1:7.7+23ubuntu2
ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3
Uname: Linux 6.5.0-10-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
.proc.driver.nvidia.capabilities.gpu0: Error: path was not a regular file.
.proc.driver.nvidia.capabilities.mig: Error: path was not a regular file.
.proc.driver.nvidia.gpus.0
[Desktop-packages] [Bug 2039328] Please test proposed package
Hello Dimitri, or anyone else affected, Accepted ubuntu-meta into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/ubuntu- meta/1.524.1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users. If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed- mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification- failed-mantic. In either case, without details of your testing we will not be able to proceed. Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping! N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2039328 Title: Update ubuntu-meta with promotions done between last ubuntu-meta build & release Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Mantic: Fix Committed Status in ubuntu-meta source package in Noble: Fix Released Bug description: [ Impact ] * ubuntu-seeds were changed since last meta update * to ensure correct upgrades; regenerate ubuntu-meta with contents / changes done before release [ Test Plan ] * Check that arm64 upgrades of ubuntu-desktop-minimal from lunar to mantic install newly recommended packages. [ Where problems could occur ] * This is automatically generated change based on ubuntu-seeds commit [1]. * Theoretically, regressions would occur if new desktop-minimal-recommends dependencies on arm64 (flash-kernel, protection-domain-mapper, qrtr-tools): - have issues on install during release-upgrade; - have issues on regular system usage (after installed). [ Other Info ] * ubuntu-meta was not uploaded during final freeze, to prevent rebuilding all images as changes affect arm64 only, which is a brand new release image * protection-domain-mapper [2] and qrtr [3] moved from universe to main in Mantic. * flash-kernel is/was already in main. [1] https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=afe820cd49514896e96d02303298ed873d8d7f8a [2] https://launchpad.net/ubuntu/+source/protection-domain-mapper/1.0-4ubuntu2/+publishinghistory [3] https://launchpad.net/ubuntu/+source/qrtr/1.0-2ubuntu1/+publishinghistory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2039328/+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 2039328] Re: Update ubuntu-meta with promotions done between last ubuntu-meta build & release
ubuntu-meta sponsored to noble, but no bug ref in changelog, so marking this fix released for noble. ** Changed in: ubuntu-meta (Ubuntu Noble) Status: Fix Committed => Fix Released ** Changed in: ubuntu-meta (Ubuntu Mantic) Status: Confirmed => Fix Committed ** Tags added: verification-needed verification-needed-mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2039328 Title: Update ubuntu-meta with promotions done between last ubuntu-meta build & release Status in ubuntu-meta package in Ubuntu: Fix Released Status in ubuntu-meta source package in Mantic: Fix Committed Status in ubuntu-meta source package in Noble: Fix Released Bug description: [ Impact ] * ubuntu-seeds were changed since last meta update * to ensure correct upgrades; regenerate ubuntu-meta with contents / changes done before release [ Test Plan ] * Check that arm64 upgrades of ubuntu-desktop-minimal from lunar to mantic install newly recommended packages. [ Where problems could occur ] * This is automatically generated change based on ubuntu-seeds commit [1]. * Theoretically, regressions would occur if new desktop-minimal-recommends dependencies on arm64 (flash-kernel, protection-domain-mapper, qrtr-tools): - have issues on install during release-upgrade; - have issues on regular system usage (after installed). [ Other Info ] * ubuntu-meta was not uploaded during final freeze, to prevent rebuilding all images as changes affect arm64 only, which is a brand new release image * protection-domain-mapper [2] and qrtr [3] moved from universe to main in Mantic. * flash-kernel is/was already in main. [1] https://git.launchpad.net/~ubuntu-core-dev/ubuntu-seeds/+git/ubuntu/commit/?id=afe820cd49514896e96d02303298ed873d8d7f8a [2] https://launchpad.net/ubuntu/+source/protection-domain-mapper/1.0-4ubuntu2/+publishinghistory [3] https://launchpad.net/ubuntu/+source/qrtr/1.0-2ubuntu1/+publishinghistory To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2039328/+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 2042728] [NEW] No sound from speakers. Chip Everest ESSX 8336 (ESSX8336, ES8336).
Public bug reported: Similar to bug #1977685. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joel905 F wireplumber /dev/snd/seq:joel902 F pipewire CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sat Nov 4 15:27:44 2023 InstallationDate: Installed on 2023-11-03 (1 days ago) InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) ProcEnviron: LANG=fr_FR.UTF-8 LANGUAGE=fr_FR PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2021 dmi.bios.release: 0.5 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V0.5.0_P8S4M1E0F0L2B0T0P2G00A0U0D605_ENE dmi.board.asset.tag: Default string dmi.board.name: G8316 dmi.board.vendor: THOMSON dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV0.5.0_P8S4M1E0F0L2B0T0P2G00A0U0D605_ENE:bd04/23/2021:br0.5:efr1.2:svnTHOMSON:pnN14C4WH64:pvrDefaultstring:rvnTHOMSON:rnG8316:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuN14C4WH64: dmi.product.family: N14C4WH64 dmi.product.name: N14C4WH64 dmi.product.sku: N14C4WH64 dmi.product.version: Default string dmi.sys.vendor: THOMSON ** Affects: pulseaudio (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic ** Summary changed: - No soud from speakers. Chip ESSX 8336. + No soud from speakers. Chip Everest ESSX 8336 (ESSX8336, ES8336). ** Summary changed: - No soud from speakers. Chip Everest ESSX 8336 (ESSX8336, ES8336). + No sound from speakers. Chip Everest ESSX 8336 (ESSX8336, ES8336). -- 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/2042728 Title: No sound from speakers. Chip Everest ESSX 8336 (ESSX8336, ES8336). Status in pulseaudio package in Ubuntu: New Bug description: Similar to bug #1977685. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: pulseaudio 1:16.1+dfsg1-2ubuntu4 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: joel905 F wireplumber /dev/snd/seq:joel902 F pipewire CasperMD5CheckResult: pass CurrentDesktop: XFCE Date: Sat Nov 4 15:27:44 2023 InstallationDate: Installed on 2023-11-03 (1 days ago) InstallationMedia: Xubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231010) ProcEnviron: LANG=fr_FR.UTF-8 LANGUAGE=fr_FR PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon. SourcePackage: pulseaudio Symptom: audio UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 04/23/2021 dmi.bios.release: 0.5 dmi.bios.vendor: American Megatrends Inc. dmi.bios.version: V0.5.0_P8S4M1E0F0L2B0T0P2G00A0U0D605_ENE dmi.board.asset.tag: Default string dmi.board.name: G8316 dmi.board.vendor: THOMSON dmi.board.version: Default string dmi.chassis.asset.tag: Default string dmi.chassis.type: 10 dmi.chassis.vendor: Default string dmi.chassis.version: Default string dmi.ec.firmware.release: 1.2 dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvrV0.5.0_P8S4M1E0F0L2B0T0P2G00A0U0D605_ENE:bd04/23/2021:br0.5:efr1.2:svnTHOMSON:pnN14C4WH64:pvrDefaultstring:rvnTHOMSON:rnG8316:rvrDefaultstring:cvnDefaultstring:ct10:cvrDefaultstring:skuN14C4WH64: dmi.product.family: N14C4WH64 dmi.product.name: N14C4WH64 dmi.product.sku: N14C4WH64 dmi.product.version: Default string dmi.sys.vendor: THOMSON To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pulseaudio/+bug/2042728/+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 2031096] Re: udisks2 daemon fails to start
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Run these commands: journalctl -b0 > journal.txt journalctl -b-1 > prevjournal.txt and attach the resulting text files here. 2. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: udisks2 (Ubuntu) Importance: Undecided => High ** Changed in: udisks2 (Ubuntu) Status: Confirmed => Incomplete -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/2031096 Title: udisks2 daemon fails to start Status in udisks: New Status in udisks2 package in Ubuntu: Incomplete Bug description: udisks2 2.10.0 fails to start in Ubuntu Mantic (23.10) Error status is: Aug 11 10:36:37 nodename systemd[1]: Starting udisks2.service - Disk Manager... Aug 11 10:36:37 nodename udisksd[232247]: udisks daemon version 2.10.0 starting Aug 11 10:36:38 nodename udisksd[232247]: Error getting 'loop28' information: Failed to open device loop28: No such file o> Aug 11 10:36:38 nodename udisksd[232247]: Error getting 'loop28' information: Failed to open device loop28: No such file o> Aug 11 10:36:38 nodename udisksd[232247]: *** stack smashing detected ***: terminated Aug 11 10:36:38 nodename systemd[1]: udisks2.service: Main process exited, code=dumped, status=6/ABRT Aug 11 10:36:38 nodename systemd[1]: udisks2.service: Failed with result 'core-dump'. Aug 11 10:36:38 nodename systemd[1]: Failed to start udisks2.service - Disk Manager. This bug seems to refer: https://github.com/storaged- project/udisks/issues/1139 To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/2031096/+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 1977685] Re: Sound card/chip Everest ESSX 8336 (ESSX8336, ES8336) not supported.
This hack (that I have not tested) for Ubuntu 22.04 may be interesting: https://ubuntuhandbook.org/index.php/2022/07/fix-no-sound-issue- ubuntu-22-04-essx8336/ ** Summary changed: - sound card Everest ESSX8336 not supported + Sound card/chip Everest ESSX 8336 (ESSX8336, ES8336) not supported. ** Tags added: mantic -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1977685 Title: Sound card/chip Everest ESSX 8336 (ESSX8336, ES8336) not supported. Status in alsa-driver package in Ubuntu: Confirmed Bug description: I work with Ubuntu 22.04 but the Everest semiconductor Co Ltd ESSX8336\1 sound card is not recognized. On the web a lot of people have the same problem. It's an annoying problem. Could you please help us to solve this problem. I have a Huawei Matebook D15 series Matebook D 15 (2021) i3 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 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.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: francois852 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 5 15:44:25 2022 InstallationDate: Installed on 2022-04-22 (43 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2022 dmi.bios.release: 1.41 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.41 dmi.board.asset.tag: NULL dmi.board.name: BOHB-WAX9-PCB-B2 dmi.board.vendor: HUAWEI dmi.board.version: M1340 dmi.chassis.asset.tag: NULL dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1340 dmi.ec.firmware.release: 1.41 dmi.modalias: dmi:bvnHUAWEI:bvr1.41:bd02/21/2022:br1.41:efr1.41:svnHUAWEI:pnBOHB-WAX9:pvrM1340:rvnHUAWEI:rnBOHB-WAX9-PCB-B2:rvrM1340:cvnHUAWEI:ct10:cvrM1340:skuC100: dmi.product.family: MateBook D dmi.product.name: BOHB-WAX9 dmi.product.sku: C100 dmi.product.version: M1340 dmi.sys.vendor: HUAWEI mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-06-04T20:59:26.778687 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1977685/+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 2042543] Re: Firefox-snap cannot save files or launch apps due to faulty apparmor configuration
the snap will access the filesystem through xdg-desktop-portal-gtk (or the equivalent for your desktop) though if the snapd desktop interfaces is connected it should also be able to directly access user directories -- 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/2042543 Title: Firefox-snap cannot save files or launch apps due to faulty apparmor configuration Status in firefox package in Ubuntu: Incomplete Bug description: Since a recent update, firefox cannot any more save pages, images or download files. It also cannot launch other processes like zoom via meeting links. This seems to be caused by a faulty apparmor configuration and a common problem since the introduction of the snap package, e.g. c.f. https://arstechnica.com/civis/threads/snap-based- firefox-is-a-terrible-experience.1487499 or https://ubuntuforums.org/showthread.php?t=2476758 . However, none of the proposed workarounds works for me, neither editing apparmor configuration files, reinstalling firefox, or refreshing it via Help -> More troubleshoot information -> Refresh firefox. Finally, I found that snap installs two binaries, one in /usr/bin/firefox and one in /snap/firefox/3252/usr/lib/firefox/firefox. If I start firefox from cli with typing firefox, the first one is invoked, which is broken. If I explicitly invoke /snap/firefox/3252/usr/lib/firefox/firefox, saving works fine. So I just aliased the second binary to firefox in the .bashrc. This binary also strangely seems to use its own configuration, i.e. own apps, password storage, etc. I hope this information helps other users with the same problem and the package maintainers with fixing the configuration. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Nov 2 10:03:30 2023 InstallationDate: Installed on 2015-11-05 (2918 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: Upgraded to jammy on 2022-10-30 (367 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2042543/+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 1977685] Re: sound card Everest ESSX8336 not supported
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: alsa-driver (Ubuntu) Status: New => Confirmed -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to alsa-driver in Ubuntu. https://bugs.launchpad.net/bugs/1977685 Title: Sound card/chip Everest ESSX 8336 (ESSX8336, ES8336) not supported. Status in alsa-driver package in Ubuntu: Confirmed Bug description: I work with Ubuntu 22.04 but the Everest semiconductor Co Ltd ESSX8336\1 sound card is not recognized. On the web a lot of people have the same problem. It's an annoying problem. Could you please help us to solve this problem. I have a Huawei Matebook D15 series Matebook D 15 (2021) i3 ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: alsa-base 1.0.25+dfsg-0ubuntu7 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.1 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC0: francois852 F pulseaudio CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jun 5 15:44:25 2022 InstallationDate: Installed on 2022-04-22 (43 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) PackageArchitecture: all ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=fr_FR.UTF-8 SHELL=/bin/bash SourcePackage: alsa-driver UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/21/2022 dmi.bios.release: 1.41 dmi.bios.vendor: HUAWEI dmi.bios.version: 1.41 dmi.board.asset.tag: NULL dmi.board.name: BOHB-WAX9-PCB-B2 dmi.board.vendor: HUAWEI dmi.board.version: M1340 dmi.chassis.asset.tag: NULL dmi.chassis.type: 10 dmi.chassis.vendor: HUAWEI dmi.chassis.version: M1340 dmi.ec.firmware.release: 1.41 dmi.modalias: dmi:bvnHUAWEI:bvr1.41:bd02/21/2022:br1.41:efr1.41:svnHUAWEI:pnBOHB-WAX9:pvrM1340:rvnHUAWEI:rnBOHB-WAX9-PCB-B2:rvrM1340:cvnHUAWEI:ct10:cvrM1340:skuC100: dmi.product.family: MateBook D dmi.product.name: BOHB-WAX9 dmi.product.sku: C100 dmi.product.version: M1340 dmi.sys.vendor: HUAWEI mtime.conffile..etc.modprobe.d.alsa-base.conf: 2022-06-04T20:59:26.778687 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/alsa-driver/+bug/1977685/+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 2027962] Re: Needs packaging: libei
** Package changed: ubuntu => libei (Ubuntu) ** Changed in: libei (Ubuntu) Status: New => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libei in Ubuntu. https://bugs.launchpad.net/bugs/2027962 Title: Needs packaging: libei Status in libei package in Ubuntu: Fix Released Bug description: This new project needs packaging: https://gitlab.freedesktop.org/libinput/libei because it's now a build dependency for mutter 45. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libei/+bug/2027962/+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 2027962] [NEW] Needs packaging: libei
You have been subscribed to a public bug: This new project needs packaging: https://gitlab.freedesktop.org/libinput/libei because it's now a build dependency for mutter 45. ** Affects: libei (Ubuntu) Importance: High Status: Fix Released ** Tags: mantic needs-packaging -- Needs packaging: libei https://bugs.launchpad.net/bugs/2027962 You received this bug notification because you are a member of Desktop Packages, which is subscribed to libei in Ubuntu. -- 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 1574582] Re: HP lt4120 Snapdragon X5 LTE USB modem not recognized by network-manager
In the kernel 5.15.x and up the modem X5 is working in the MBIM mode, so the updated udev script attached. ** Attachment added: "99-hp-lt4120-test.rules" https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574582/+attachment/5715918/+files/99-hp-lt4120-test.rules -- 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/1574582 Title: HP lt4120 Snapdragon X5 LTE USB modem not recognized by network- manager Status in network-manager package in Ubuntu: Confirmed Bug description: USB modem not recognized by network-manager. Modem information in attached ProblemType: Bug DistroRelease: Ubuntu 16.04 Package: network-manager 1.1.93-0ubuntu4 ProcVersionSignature: Ubuntu 4.4.0-21.37-generic 4.4.6 Uname: Linux 4.4.0-21-generic x86_64 ApportVersion: 2.20.1-0ubuntu2 Architecture: amd64 CasperVersion: 1.376 Date: Mon Apr 25 11:14:04 2016 IfupdownConfig: # interfaces(5) file used by ifup(8) and ifdown(8) auto lo iface lo inet loopback IpRoute: default via 10.106.36.1 dev wlp2s0 proto static metric 600 1.1.1.1 via 10.106.36.1 dev wlp2s0 proto dhcp metric 600 10.106.36.0/22 dev wlp2s0 proto kernel scope link src 10.106.39.123 metric 600 169.254.0.0/16 dev wlp2s0 scope link metric 1000 LiveMediaBuild: Ubuntu 16.04 LTS "Xenial Xerus" - Release amd64 (20160420.1) NetworkManager.state: [main] NetworkingEnabled=true WirelessEnabled=true WWANEnabled=true ProcEnviron: TERM=xterm-256color PATH=(custom, no user) LANG=en_US.UTF-8 SHELL=/bin/bash SourcePackage: network-manager UpgradeStatus: No upgrade log present (probably fresh install) nmcli-dev: DEVICE TYPE STATE DBUS-PATH CONNECTION CON-UUID CON-PATH wlp2s0 wifi connected /org/freedesktop/NetworkManager/Devices/1 IQORAMS_REPAIR 3b1e13ff-f9c9-4a49-a576-465bc2713e21 /org/freedesktop/NetworkManager/ActiveConnection/1 enxb2e41f35ffe1 ethernet disconnected /org/freedesktop/NetworkManager/Devices/2 -- -- -- enp0s31f6ethernet unavailable /org/freedesktop/NetworkManager/Devices/3 -- -- -- lo loopback unmanaged /org/freedesktop/NetworkManager/Devices/0 -- -- -- nmcli-nm: Error: command ['nmcli', '-f', 'all', 'nm'] failed with exit code 2: Error: Object 'nm' is unknown, try 'nmcli help'. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1574582/+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 1930387] Re: The system voice doesn't change after disable "Over-Amplification"
** Changed in: gnome-control-center Status: Fix Released => 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/1930387 Title: The system voice doesn't change after disable "Over-Amplification" Status in gnome-control-center: New Status in OEM Priority Project: New Status in gnome-control-center package in Ubuntu: Triaged Bug description: [Summary] The system voice doesn't change after disable "Over-Amplification" [Reproduce] 1. Boot into the system. 2. Launch Settings > Sound 3. Enable "Over-Amplification" 4. Maximize the system Volume 5. Disable "Over-Amplification" [Expected result] The system voice can become lower. [Actual result] The system volume showed as 100 but the voice doesn't become lower. [Fail Rate] 100% [Additional information] Ubuntu Version: 20.04.2 LTS Image: sutton-newell-focal-amd64-20210414-220 gnome-control-center: 1:3.36.5-0ubuntu1 To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-control-center/+bug/1930387/+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 2032852] Re: package libreoffice-common 1:6.0.7-0ubuntu0.18.04.13 failed to install/upgrade: conflicting packages - not installing libreoffice-common
Thanks Mike, after lot of stuff trail and error, your suggestion works like charm!! Cheers!! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to libreoffice in Ubuntu. https://bugs.launchpad.net/bugs/2032852 Title: package libreoffice-common 1:6.0.7-0ubuntu0.18.04.13 failed to install/upgrade: conflicting packages - not installing libreoffice- common Status in libreoffice package in Ubuntu: Confirmed Status in libreoffice source package in Focal: In Progress Bug description: package install error ProblemType: Package DistroRelease: Ubuntu 20.04 Package: libreoffice-common 1:6.0.7-0ubuntu0.18.04.13 ProcVersionSignature: Ubuntu 4.15.0-213.224-generic 4.15.18 Uname: Linux 4.15.0-213-generic x86_64 ApportVersion: 2.20.11-0ubuntu27.27 Architecture: amd64 CasperMD5CheckResult: skip Date: Thu Aug 24 02:36:52 2023 ErrorMessage: conflicting packages - not installing libreoffice-common InstallationDate: Installed on 2023-08-22 (1 days ago) InstallationMedia: Ubuntu 14.04.5 LTS "Trusty Tahr" - Release amd64 (20160803) PackageArchitecture: all Python3Details: /usr/bin/python3.8, Python 3.8.10, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3.2 apt 2.0.9 SourcePackage: libreoffice Title: package libreoffice-common 1:6.0.7-0ubuntu0.18.04.13 failed to install/upgrade: conflicting packages - not installing libreoffice-common UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/2032852/+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 2042724] [NEW] locking screen results in exit of session
Public bug reported: system installed with 22.04, upgraded to 23.04 and then to 23.10 today; whenever I lock the screen or the laptop suspends, I'm presented with the login screen to re-authenticate but my session is not maintained and all apps have been killed. Issue was not present on Lunar. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gdm3 45~beta-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 4 14:13:53 2023 InstallationDate: Installed on 2023-09-12 (53 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) SourcePackage: gdm3 UpgradeStatus: Upgraded to mantic on 2023-11-04 (0 days ago) ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/2042724 Title: locking screen results in exit of session Status in gdm3 package in Ubuntu: New Bug description: system installed with 22.04, upgraded to 23.04 and then to 23.10 today; whenever I lock the screen or the laptop suspends, I'm presented with the login screen to re-authenticate but my session is not maintained and all apps have been killed. Issue was not present on Lunar. ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: gdm3 45~beta-1ubuntu1 ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 NonfreeKernelModules: zfs ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 4 14:13:53 2023 InstallationDate: Installed on 2023-09-12 (53 days ago) InstallationMedia: Ubuntu 22.04.3 LTS "Jammy Jellyfish" - Release amd64 (20230807.2) SourcePackage: gdm3 UpgradeStatus: Upgraded to mantic on 2023-11-04 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2042724/+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 2034619] Re: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland
Another +1 on -proposed mutter. It solves the problem for me too. -- 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/2034619 Title: [amdgpu] gnome-shell gets SIGKILL'd when lock screen or under heavy load in Wayland Status in Linux: New Status in Mutter: Fix Released Status in X.Org X server: Fix Released Status in linux package in Ubuntu: Triaged Status in mutter package in Ubuntu: Fix Released Status in linux source package in Mantic: Triaged Status in mutter source package in Mantic: Fix Committed Bug description: [ Impact ] gnome-shell gets unceremoniously SIGKILLed on some Ryzen systems, sometimes when the screen locks, sometimes when launching particular apps. [ Workaround ] Add this to /etc/environment: MUTTER_DEBUG_KMS_THREAD_TYPE=user and then reboot. [ Test Plan ] Not all Ryzen systems (including one I just purchased) are able to reproduce the bug. We have no choice but to leave final verification to the community. Anyone affected should try locking their screen and verify they are not instantly returned to the login screen. [ Where problems could occur ] Anywhere in frame scheduling and particularly for mouse cursor movement since that's what the real-time thread exists to optimize. [ Original Description ] I have this issue on Ubuntu 23.10. Lock screen works only with an external monitor connected. Otherwise the session is ended and the user is logged out and brought to the gdm screen. All works in xorg. ProblemType: Crash DistroRelease: Ubuntu 23.10 Package: gnome-shell 45~beta.1-0ubuntu2 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.27.0-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Sep 6 22:32:22 2023 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2023-09-03 (3 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230901.1) ProcCmdline: /usr/bin/gnome-shell RelatedPackageVersions: mutter-common 45~beta.1-1ubuntu2 UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin plugdev sudo users separator: To manage notifications about this bug go to: https://bugs.launchpad.net/linux/+bug/2034619/+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 2042543] Re: Firefox-snap cannot save files or launch apps due to faulty apparmor configuration
The journalctl contains essentially the same inforamtion as the dmesg excerpt that I had already uploaded. Though the desktop environment was a good hint. It has plasma and xfce installed, it worked in neither environment. I installed gnome to test it, and it works now. Strangely it also works now in xfce and plasma. I guess that the the firefox package misses one of the dependencies that were installed for gnome. -- 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/2042543 Title: Firefox-snap cannot save files or launch apps due to faulty apparmor configuration Status in firefox package in Ubuntu: Incomplete Bug description: Since a recent update, firefox cannot any more save pages, images or download files. It also cannot launch other processes like zoom via meeting links. This seems to be caused by a faulty apparmor configuration and a common problem since the introduction of the snap package, e.g. c.f. https://arstechnica.com/civis/threads/snap-based- firefox-is-a-terrible-experience.1487499 or https://ubuntuforums.org/showthread.php?t=2476758 . However, none of the proposed workarounds works for me, neither editing apparmor configuration files, reinstalling firefox, or refreshing it via Help -> More troubleshoot information -> Refresh firefox. Finally, I found that snap installs two binaries, one in /usr/bin/firefox and one in /snap/firefox/3252/usr/lib/firefox/firefox. If I start firefox from cli with typing firefox, the first one is invoked, which is broken. If I explicitly invoke /snap/firefox/3252/usr/lib/firefox/firefox, saving works fine. So I just aliased the second binary to firefox in the .bashrc. This binary also strangely seems to use its own configuration, i.e. own apps, password storage, etc. I hope this information helps other users with the same problem and the package maintainers with fixing the configuration. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Nov 2 10:03:30 2023 InstallationDate: Installed on 2015-11-05 (2918 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: Upgraded to jammy on 2022-10-30 (367 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2042543/+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 2042543] Re: Firefox-snap cannot save files or launch apps due to faulty apparmor configuration
** Attachment added: "journalctl.txt" https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2042543/+attachment/5715902/+files/journalctl.txt -- 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/2042543 Title: Firefox-snap cannot save files or launch apps due to faulty apparmor configuration Status in firefox package in Ubuntu: Incomplete Bug description: Since a recent update, firefox cannot any more save pages, images or download files. It also cannot launch other processes like zoom via meeting links. This seems to be caused by a faulty apparmor configuration and a common problem since the introduction of the snap package, e.g. c.f. https://arstechnica.com/civis/threads/snap-based- firefox-is-a-terrible-experience.1487499 or https://ubuntuforums.org/showthread.php?t=2476758 . However, none of the proposed workarounds works for me, neither editing apparmor configuration files, reinstalling firefox, or refreshing it via Help -> More troubleshoot information -> Refresh firefox. Finally, I found that snap installs two binaries, one in /usr/bin/firefox and one in /snap/firefox/3252/usr/lib/firefox/firefox. If I start firefox from cli with typing firefox, the first one is invoked, which is broken. If I explicitly invoke /snap/firefox/3252/usr/lib/firefox/firefox, saving works fine. So I just aliased the second binary to firefox in the .bashrc. This binary also strangely seems to use its own configuration, i.e. own apps, password storage, etc. I hope this information helps other users with the same problem and the package maintainers with fixing the configuration. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: firefox 1:1snap1-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Thu Nov 2 10:03:30 2023 InstallationDate: Installed on 2015-11-05 (2918 days ago) InstallationMedia: Ubuntu 14.04.3 LTS "Trusty Tahr" - Beta amd64 (20150805) Snap.Changes: no changes found SourcePackage: firefox UpgradeStatus: Upgraded to jammy on 2022-10-30 (367 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/firefox/+bug/2042543/+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 2042695] Re: gnome-control-center crashes
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Run these commands: journalctl -b0 > journal.txt journalctl -b-1 > prevjournal.txt and attach the resulting text files here. 2. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 3. If step 2 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** 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/2042695 Title: gnome-control-center crashes Status in gnome-control-center package in Ubuntu: Incomplete Bug description: This sums it up. I don't know what has changed recently to cause this. $ gnome-control-center (gnome-control-center:30888): GLib-CRITICAL **: 12:03:40.812: g_strsplit: assertion 'string != NULL' failed Segmentation fault (core dumped) ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-control-center 1:41.7-0ubuntu0.22.04.7 ProcVersionSignature: Ubuntu 5.15.0-88.98-generic 5.15.126 Uname: Linux 5.15.0-88-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Fri Nov 3 12:06:59 2023 InstallationDate: Installed on 2021-03-28 (949 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) 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-04-30 (552 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2042695/+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 2042696] Re: Unknown disk capacity is displayed in "About" dialog
*** This bug is a duplicate of bug 2038761 *** https://bugs.launchpad.net/bugs/2038761 Thank you for your bug report, it seems the same issue than bug #2038761 with udisks and nvme drives ** Changed in: gnome-control-center (Ubuntu) Importance: Undecided => Low ** This bug has been marked a duplicate of bug 2038761 gnome-disk-utility does not give size of nvme disk -- 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/2042696 Title: Unknown disk capacity is displayed in "About" dialog Status in gnome-control-center package in Ubuntu: New Bug description: I upgraded from Ubuntu 23.04 to 23.10 and when I open Settings => About, I can see "Unknown" disk capacity: https://i.imgur.com/KM97Ytm.png This is what "df" shows (it look correctly): $ df Filesystem 1K-blocks Used Available Use% Mounted on tmpfs1571420 6032 1565388 1% /run /dev/nvme0n1p2 490617784 292924832 172697472 63% / tmpfs7857080123348 7733732 2% /dev/shm tmpfs 512016 5104 1% /run/lock efivarfs 1486777 47% /sys/firmware/efi/efivars tmpfs7857080 0 7857080 0% /run/qemu /dev/nvme0n1p1523248 6252516996 2% /boot/efi tmpfs1571416 16768 1554648 2% /run/user/1000 Used SW: # System Details Report --- ## Report details - **Date generated:** 2023-11-03 20:34:31 ## Hardware Information: - **Hardware Model:** Lenovo Yoga Slim 7 14ARE05 - **Memory:** 16.0 GiB - **Processor:** AMD Ryzen™ 7 4700U with Radeon™ Graphics × 8 - **Graphics:**AMD Radeon™ Graphics - **Disk Capacity:** (null) ## Software Information: - **Firmware Version:**DMCN43WW - **OS Name:** Ubuntu 23.10 - **OS Build:**(null) - **OS Type:** 64-bit - **GNOME Version:** 45.0 - **Windowing System:**Wayland - **Kernel Version:** Linux 6.5.0-10-generic To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2042696/+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 2042682] Re: Graphics in Multitasking settings appear blurry
** 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/2042682 Title: Graphics in Multitasking settings appear blurry Status in gnome-control-center package in Ubuntu: New Bug description: The clarification graphics for the following settings appear to be blurry: - Hot Corner - Active Screen Edges - Multi-monitor I think that due to these graphics being low-resolution, these graphics were being scaled, resulting in blurry image. ProblemType: Bug DistroRelease: Ubuntu 24.04 Package: gnome-control-center 1:45.0-1ubuntu3 ProcVersionSignature: Ubuntu 6.5.0-9.9-generic 6.5.3 Uname: Linux 6.5.0-9-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Fri Nov 3 19:29:37 2023 InstallationDate: Installed on 2022-05-12 (540 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Release amd64 (20220419) SourcePackage: gnome-control-center UpgradeStatus: Upgraded to noble on 2023-08-14 (81 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-control-center/+bug/2042682/+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 1884759] Re: [snap] U2f yubikey not recognized until unplugged and plugged back in
As per https://forum.snapcraft.io/t/request-for-auto-connection-of- hardware-observe-for-brave/37604 it sounds like if the chromium snap plugged hardware-observe and had this auto-connected, this should be sufficient to fix this bug. -- 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/1884759 Title: [snap] U2f yubikey not recognized until unplugged and plugged back in Status in chromium-browser package in Ubuntu: Confirmed Bug description: I was previously using u2f from yubikey in chromium snap, but now it doesn't work. No apparmor deny in dmesg (except accessing bluez), u2f slot is conneced. U2f still works in firefox installed as deb. # snap connections chromium | grep u2f u2f-devices chromium:u2f-devices :u2f-devices manual To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1884759/+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 2042715] [NEW] gpu-manager service takes 10 seconds during boot
Public bug reported: There is obviously something not right with the gpu-manager service as it's taking more than 10 seconds to run during boot, and this is happening every time. # systemd-analyze blame 13.254s plymouth-quit-wait.service 10.347s gpu-manager.service 3.843s NetworkManager-wait-online.service 1.313s logrotate.service 1.276s fwupd-refresh.service 1.197s snapd.service 1.134s NetworkManager.service 871ms fwupd.service 772ms udisks2.service ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 4 10:32:53 2023 InstallationDate: Installed on 2023-10-12 (23 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: ubuntu-meta (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug mantic wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-meta in Ubuntu. https://bugs.launchpad.net/bugs/2042715 Title: gpu-manager service takes 10 seconds during boot Status in ubuntu-meta package in Ubuntu: New Bug description: There is obviously something not right with the gpu-manager service as it's taking more than 10 seconds to run during boot, and this is happening every time. # systemd-analyze blame 13.254s plymouth-quit-wait.service 10.347s gpu-manager.service 3.843s NetworkManager-wait-online.service 1.313s logrotate.service 1.276s fwupd-refresh.service 1.197s snapd.service 1.134s NetworkManager.service 871ms fwupd.service 772ms udisks2.service ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-desktop (not installed) ProcVersionSignature: Ubuntu 6.5.0-10.10-generic 6.5.3 Uname: Linux 6.5.0-10-generic x86_64 ApportVersion: 2.27.0-0ubuntu5 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sat Nov 4 10:32:53 2023 InstallationDate: Installed on 2023-10-12 (23 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Release amd64 (20231011) SourcePackage: ubuntu-meta UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-meta/+bug/2042715/+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 2031096] Re: udisks2 daemon fails to start
udisks2 crashes and fails to start udisks2.service after upgrading from 23.04 to 23.10. I did this upgrade twice on the same machine (with a clean install of 23.04) and it fails all the same. Initially udisks2.service was crashing with a differ error: Nov 03 udisksd[6369]: failed to load module swap: /lib/x86_64-linux-gnu/libbd_swap.so.3: invalid ELF header Nov 03 udisksd[6369]: Failed to load the 'swap' libblockdev plugin so I reinstalled udisks2 and now I get the error reported here. Nov 04 udisksd[3130]: udisks daemon version 2.10.1 starting Nov 04 udisksd[3130]: *** stack smashing detected ***: terminated Nov 04 systemd[1]: udisks2.service: Main process exited, code=dumped, status=6/ABRT Nov 04 systemd[1]: udisks2.service: Failed with result 'core-dump'. Nov 04 systemd[1]: Failed to start udisks2.service - Disk Manager. Weird thing is that sometimes it does start properly and will mount external disks but I can't figure out why. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to udisks2 in Ubuntu. https://bugs.launchpad.net/bugs/2031096 Title: udisks2 daemon fails to start Status in udisks: New Status in udisks2 package in Ubuntu: Confirmed Bug description: udisks2 2.10.0 fails to start in Ubuntu Mantic (23.10) Error status is: Aug 11 10:36:37 nodename systemd[1]: Starting udisks2.service - Disk Manager... Aug 11 10:36:37 nodename udisksd[232247]: udisks daemon version 2.10.0 starting Aug 11 10:36:38 nodename udisksd[232247]: Error getting 'loop28' information: Failed to open device loop28: No such file o> Aug 11 10:36:38 nodename udisksd[232247]: Error getting 'loop28' information: Failed to open device loop28: No such file o> Aug 11 10:36:38 nodename udisksd[232247]: *** stack smashing detected ***: terminated Aug 11 10:36:38 nodename systemd[1]: udisks2.service: Main process exited, code=dumped, status=6/ABRT Aug 11 10:36:38 nodename systemd[1]: udisks2.service: Failed with result 'core-dump'. Aug 11 10:36:38 nodename systemd[1]: Failed to start udisks2.service - Disk Manager. This bug seems to refer: https://github.com/storaged- project/udisks/issues/1139 To manage notifications about this bug go to: https://bugs.launchpad.net/udisks/+bug/2031096/+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
