[Desktop-packages] [Bug 2028326] [NEW] cups-browsed uses a CPU thread at 100%
Public bug reported: On my Kubuntu Lunar system, with package cups-browsed (2.0~rc1-0ubuntu1.1), cups-browsed is getting stuck inconsistently and some hours after initial boot in a 100% CPU usage loop (seems to use a single thread at 100%). Looks like https://bugs.launchpad.net/ubuntu/+source/cups- browsed/+bug/2018504 but I am already using the package that appears to contain a fix for that bug, so this may be a different root cause. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups-browsed 2.0~rc1-0ubuntu1.1 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CupsErrorLog: CurrentDesktop: KDE Date: Thu Jul 20 23:00:50 2023 InstallationDate: Installed on 2023-06-10 (40 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Release amd64 (20230414.1) Lpstat: device for Canon_TR4500_series: implicitclass://Canon_TR4500_series/ MachineType: Dell Inc. Inspiron 1520 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Canon_TR4500_series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Canon_TR4500_series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-25-generic root=UUID=db9a1f13-abe0-456b-b50a-f9ee27bea5eb ro quiet splash vt.handoff=7 SourcePackage: cups-browsed UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/03/2008 dmi.bios.release: 0.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 0.7 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd02/03/2008:br0.7:efr0.7:svnDellInc.:pnInspiron1520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:sku: dmi.product.name: Inspiron 1520 dmi.sys.vendor: Dell Inc. ** Affects: cups-browsed (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to cups-browsed in Ubuntu. https://bugs.launchpad.net/bugs/2028326 Title: cups-browsed uses a CPU thread at 100% Status in cups-browsed package in Ubuntu: New Bug description: On my Kubuntu Lunar system, with package cups-browsed (2.0~rc1-0ubuntu1.1), cups-browsed is getting stuck inconsistently and some hours after initial boot in a 100% CPU usage loop (seems to use a single thread at 100%). Looks like https://bugs.launchpad.net/ubuntu/+source/cups- browsed/+bug/2018504 but I am already using the package that appears to contain a fix for that bug, so this may be a different root cause. ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: cups-browsed 2.0~rc1-0ubuntu1.1 ProcVersionSignature: Ubuntu 6.2.0-25.25-generic 6.2.13 Uname: Linux 6.2.0-25-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CupsErrorLog: CurrentDesktop: KDE Date: Thu Jul 20 23:00:50 2023 InstallationDate: Installed on 2023-06-10 (40 days ago) InstallationMedia: Kubuntu 23.04 "Lunar Lobster" - Release amd64 (20230414.1) Lpstat: device for Canon_TR4500_series: implicitclass://Canon_TR4500_series/ MachineType: Dell Inc. Inspiron 1520 Papersize: letter PpdFiles: Error: command ['fgrep', '-H', '*NickName', '/etc/cups/ppd/Canon_TR4500_series.ppd'] failed with exit code 2: grep: /etc/cups/ppd/Canon_TR4500_series.ppd: Permission denied ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-6.2.0-25-generic root=UUID=db9a1f13-abe0-456b-b50a-f9ee27bea5eb ro quiet splash vt.handoff=7 SourcePackage: cups-browsed UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 02/03/2008 dmi.bios.release: 0.7 dmi.bios.vendor: Dell Inc. dmi.bios.version: A07 dmi.board.vendor: Dell Inc. dmi.chassis.type: 8 dmi.chassis.vendor: Dell Inc. dmi.ec.firmware.release: 0.7 dmi.modalias: dmi:bvnDellInc.:bvrA07:bd02/03/2008:br0.7:efr0.7:svnDellInc.:pnInspiron1520:pvr:rvnDellInc.:rn:rvr:cvnDellInc.:ct8:cvr:sku: dmi.product.name: Inspiron 1520 dmi.sys.vendor: Dell Inc. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cups-browsed/+bug/2028326/+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 2028311] Re: 22.04 : Default screenshot utility can be triggered from login-screen but useless.
I can't seem to reproduce this. There is no screenshot feature available in the login screen. Are you sure you don't have any extensions installed? Even if it did work, you should expect screenshots to appear in ~gdm, not ~root ** Tags added: jammy ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete -- 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/2028311 Title: 22.04 : Default screenshot utility can be triggered from login-screen but useless. Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hi, Ubuntu 22.04 ( Gnome, GDM, Wayland ) Hitting « PrintScreen » key in login-screen launches default « new » screenshot utility. It seems to work, at the end it says « picture has been saved in the paperboard ». But how get hands on that paperboard later ? No picture is saved in /root. I suspect the screenshot utility should not be launch-able from login- screen, as it suggests something impossible to do ( get a screenshot of login- screen. ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2028311/+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 2028311] Re: 22.04 : Default screenshot utility can be triggered from login-screen but useless.
Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal: apport-collect 2028311 When reporting bugs in the future please use apport by using 'ubuntu- bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs. -- 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/2028311 Title: 22.04 : Default screenshot utility can be triggered from login-screen but useless. Status in gnome-shell package in Ubuntu: Incomplete Bug description: Hi, Ubuntu 22.04 ( Gnome, GDM, Wayland ) Hitting « PrintScreen » key in login-screen launches default « new » screenshot utility. It seems to work, at the end it says « picture has been saved in the paperboard ». But how get hands on that paperboard later ? No picture is saved in /root. I suspect the screenshot utility should not be launch-able from login- screen, as it suggests something impossible to do ( get a screenshot of login- screen. ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2028311/+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 2020049] Re: gnome-shell crashed with SIGSEGV in clutter_stage_view_get_onscreen() from meta_stage_impl_add_onscreen_frame_info() from add_onscreen_frame_info() from post_finis
Try using 'apport-cli' instead of 'ubuntu-bug'. If crash reports still get rejected then check that all your packages are up to date before reporting another: sudo apt update sudo apt full-upgrade -- 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/2020049 Title: gnome-shell crashed with SIGSEGV in clutter_stage_view_get_onscreen() from meta_stage_impl_add_onscreen_frame_info() from add_onscreen_frame_info() from post_finish_frame() from try_post_latest_swap() Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Committed Status in mutter source package in Mantic: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/c675f1d61cef940571272d7e655162f1b1cddab1 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/mutter/+bug/2020049/+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 2027571] Re: gnome-extensions-app crash, parser_get_compose_table: assertion failed:
** Changed in: gtk4 (Ubuntu) Status: Triaged => Fix Committed ** Tags added: fixed-in-gtk4-4.11.5 fixed-upstream -- 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/2027571 Title: gnome-extensions-app crash, parser_get_compose_table: assertion failed: Status in GNOME Shell: New Status in GTK+: Fix Released Status in gtk4 package in Ubuntu: Fix Committed Bug description: ENV: Ubuntu 22.04.2 LTS on X11, GNOME Shell 42.9 symptom : gnome-extensions-app crash everytime right at start. message: ``` /usr/bin/gnome-extensions-app ** Gtk:ERROR:../../../gtk/gtkcomposetable.c:981:parser_get_compose_table: assertion failed: (data[first_pos + i] <= data[first_pos + i + 1]) Bail out! Gtk:ERROR:../. ``` gdb backtrace: ``` ** Gtk:ERROR:../../../gtk/gtkcomposetable.c:981:parser_get_compose_table: assertion failed: (data[first_pos + i] <= data[first_pos + i + 1]) Bail out! Gtk:ERROR:../../../gtk/gtkcomposetable.c:981:parser_get_compose_table: assertion failed: (data[first_pos + i] <= data[first_pos + i + 1]) Thread 16 "pool-gnome-exte" received signal SIGABRT, Aborted. [Switching to Thread 0x70858640 (LWP 9456)] __pthread_kill_implementation (no_tid=0, signo=6, threadid=140737228670528) at ./nptl/pthread_kill.c:44 44./nptl/pthread_kill.c: No such file or directory. (gdb) bt #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140737228670528) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=140737228670528) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=140737228670528, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #3 0x776bb476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x776a17f3 in __GI_abort () at ./stdlib/abort.c:79 #5 0x77d44b57 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x77d9e70f in g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x711be0e3 in () at /lib/x86_64-linux-gnu/libgtk-4.so.1 #8 0x7123a0b4 in () at /lib/x86_64-linux-gnu/libgtk-4.so.1 #9 0x7123a7b1 in () at /lib/x86_64-linux-gnu/libgtk-4.so.1 #10 0x77b9f194 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #11 0x77dad6b4 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x77daaa51 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7770db43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #14 0x7779fa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 ``` Moreover, I found in my snap logs that there was update recently applied, might be linked ``` $snap changes ID Status SpawnReadySummary 253 Doneyesterday at 21:47 CEST yesterday at 21:47 CEST Remove "gnome-3-34-1804" snap 254 Doneyesterday at 22:23 CEST yesterday at 22:23 CEST Refresh "gnome-3-38-2004" snap ``` Moreover, is seems I have multiple snap version of gnome installed ``` snap list ... gnome-3-28-18043.28.0-19-g98f9e67.98f9e67 198latest/stable canonical✓ - gnome-3-38-20040+git.efb213a 143latest/stable canonical✓ - gnome-42-2204 0+git.ff35a85 120latest/stable canonical✓ - ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome (not installed) ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99 Uname: Linux 5.15.0-76-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jul 12 12:10:10 2023 InstallationDate: Installed on 2021-08-18 (692 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: meta-gnome3 UpgradeStatus: Upgraded to jammy on 2023-07-01 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2027571/+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 2028312] Re: does not support spec 1.5
error when trying trying to validate a desktop file running spec 1.5: $ desktop-file-validate Applications/squashfs-root/org.keepassxc.KeePassXC.desktop Applications/squashfs-root/org.keepassxc.KeePassXC.desktop: error: value "1.5" for key "Version" in group "Desktop Entry" is not a known version Applications/squashfs-root/org.keepassxc.KeePassXC.desktop: hint: value item "Security" in key "Categories" in group "Desktop Entry" can be extended with another category among the following categories: Settings, or System Applications/squashfs-root/org.keepassxc.KeePassXC.desktop: error: file contains key "SingleMainWindow" in group "Desktop Entry", but keys extending the format should start with "X-" -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/2028312 Title: does not support spec 1.5 Status in desktop-file-utils package in Ubuntu: New Bug description: This package's code is a bit behind from the upstream code. In 2022, code was committed to support 1.5: https://gitlab.freedesktop.org/xdg/desktop-file-utils/-/commit/56d220dd679c7c3a8f995a41a27a7d6f3df49dea When trying to validate .desktop files in Ubuntu that are running 1.5, I am getting errors. I am running Ubuntu 23.04 desktop-file-utils 0.26-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/2028312/+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 2028312] [NEW] does not support spec 1.5
Public bug reported: This package's code is a bit behind from the upstream code. In 2022, code was committed to support 1.5: https://gitlab.freedesktop.org/xdg/desktop-file-utils/-/commit/56d220dd679c7c3a8f995a41a27a7d6f3df49dea When trying to validate .desktop files in Ubuntu that are running 1.5, I am getting errors. I am running Ubuntu 23.04 desktop-file-utils 0.26-1ubuntu5 ** Affects: desktop-file-utils (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to desktop-file-utils in Ubuntu. https://bugs.launchpad.net/bugs/2028312 Title: does not support spec 1.5 Status in desktop-file-utils package in Ubuntu: New Bug description: This package's code is a bit behind from the upstream code. In 2022, code was committed to support 1.5: https://gitlab.freedesktop.org/xdg/desktop-file-utils/-/commit/56d220dd679c7c3a8f995a41a27a7d6f3df49dea When trying to validate .desktop files in Ubuntu that are running 1.5, I am getting errors. I am running Ubuntu 23.04 desktop-file-utils 0.26-1ubuntu5 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/desktop-file-utils/+bug/2028312/+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 2028311] Re: 22.04 : Default screenshot utility can be triggered from login-screen but useless.
After that, when you log in into a session you might believe you have some picture to paste, and it seems it's not the case : Gimp will say there's no data to paste from paperboard. So I expect one of these two things : ⋅ make the screenshot available to paste in regular session or ⋅ make screenshot tool NOT available in login-screen. -- 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/2028311 Title: 22.04 : Default screenshot utility can be triggered from login-screen but useless. Status in gnome-shell package in Ubuntu: New Bug description: Hi, Ubuntu 22.04 ( Gnome, GDM, Wayland ) Hitting « PrintScreen » key in login-screen launches default « new » screenshot utility. It seems to work, at the end it says « picture has been saved in the paperboard ». But how get hands on that paperboard later ? No picture is saved in /root. I suspect the screenshot utility should not be launch-able from login- screen, as it suggests something impossible to do ( get a screenshot of login- screen. ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2028311/+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 2028311] [NEW] 22.04 : Default screenshot utility can be triggered from login-screen but useless.
Public bug reported: Hi, Ubuntu 22.04 ( Gnome, GDM, Wayland ) Hitting « PrintScreen » key in login-screen launches default « new » screenshot utility. It seems to work, at the end it says « picture has been saved in the paperboard ». But how get hands on that paperboard later ? No picture is saved in /root. I suspect the screenshot utility should not be launch-able from login- screen, as it suggests something impossible to do ( get a screenshot of login- screen. ) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Description changed: Hi, - Ubuntu 22.04 ( Gnome, GDM ) + Ubuntu 22.04 ( Gnome, GDM, Wayland ) Hitting « PrintScreen » key in login-screen launches default « new » screenshot utility. It seems to work, at the end it says « picture has been saved in the paperboard ». But how get hands on that paperboard later ? No picture is saved in /root. I suspect the screenshot utility should not be launch-able from login- screen, as it suggests something impossible to do ( get a screenshot of login- screen. ) -- 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/2028311 Title: 22.04 : Default screenshot utility can be triggered from login-screen but useless. Status in gnome-shell package in Ubuntu: New Bug description: Hi, Ubuntu 22.04 ( Gnome, GDM, Wayland ) Hitting « PrintScreen » key in login-screen launches default « new » screenshot utility. It seems to work, at the end it says « picture has been saved in the paperboard ». But how get hands on that paperboard later ? No picture is saved in /root. I suspect the screenshot utility should not be launch-able from login- screen, as it suggests something impossible to do ( get a screenshot of login- screen. ) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2028311/+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 2026826] Re: glib2.0 (2.77.0 ) breaks Netplan build
** Changed in: glib 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/2026826 Title: glib2.0 (2.77.0 ) breaks Netplan build Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: Fix Committed Bug description: Netplan FTBFS as of the latest release of glib2.0 (2.77.0-0ubuntu1) in mantic-proposed. See: https://launchpad.net/ubuntu/+source/netplan.io/0.106.1-3 When I downgrade glib in my sbuild environment, everything works as expected: $ apt install libglib2.0-0=2.76.3-1ubuntu1 libglib2.0-bin=2.76.3-1ubuntu1 libglib2.0-dev=2.76.3-1ubuntu1 libglib2.0-dev-bin=2.76.3-1ubuntu1 libglib2.0-data=2.76.3-1ubuntu1 The build also works fine in Debian unstable, which is using glib2.0 2.74.6-2. Netplan is using plenty of GLib's keyfile functions (https://docs.gtk.org/glib/struct.KeyFile.html), which seem to producing a different output with this newer release (some strange line breaks injected in the middle of a keyfile). Example keyfile from the test_wifis.test_wifi_wowlan test, that should be generated by Netplan and the way it fails: Expected output: ``` [connection] id=netplan-wl0-homenet type=wifi interface-name=wl0 [wifi] wake-on-wlan=330 ssid=homenet mode=infrastructure [ipv4] method=link-local [ipv6] method=ignore ``` Failure: ``` E AssertionError: '[con[88 chars]330\n\nssid=homenet\nmode=infrastructure\n[ipv[44 chars]re\n' != '[con[88 chars]330\nssid=homenet\nmode=infrastructure\n\n[ipv[44 chars]re\n' E [connection] E id=netplan-wl0-homenet E type=wifi E interface-name=wl0 E E [wifi] E wake-on-wlan=330 E - E ssid=homenet E mode=infrastructure E + E [ipv4] E method=link-local E E [ipv6] E method=ignore ``` To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/2026826/+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 2027571] Re: gnome-extensions-app crash, parser_get_compose_table: assertion failed:
** Changed in: gtk Status: New => 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/2027571 Title: gnome-extensions-app crash, parser_get_compose_table: assertion failed: Status in GNOME Shell: New Status in GTK+: Fix Released Status in gtk4 package in Ubuntu: Triaged Bug description: ENV: Ubuntu 22.04.2 LTS on X11, GNOME Shell 42.9 symptom : gnome-extensions-app crash everytime right at start. message: ``` /usr/bin/gnome-extensions-app ** Gtk:ERROR:../../../gtk/gtkcomposetable.c:981:parser_get_compose_table: assertion failed: (data[first_pos + i] <= data[first_pos + i + 1]) Bail out! Gtk:ERROR:../. ``` gdb backtrace: ``` ** Gtk:ERROR:../../../gtk/gtkcomposetable.c:981:parser_get_compose_table: assertion failed: (data[first_pos + i] <= data[first_pos + i + 1]) Bail out! Gtk:ERROR:../../../gtk/gtkcomposetable.c:981:parser_get_compose_table: assertion failed: (data[first_pos + i] <= data[first_pos + i + 1]) Thread 16 "pool-gnome-exte" received signal SIGABRT, Aborted. [Switching to Thread 0x70858640 (LWP 9456)] __pthread_kill_implementation (no_tid=0, signo=6, threadid=140737228670528) at ./nptl/pthread_kill.c:44 44./nptl/pthread_kill.c: No such file or directory. (gdb) bt #0 __pthread_kill_implementation (no_tid=0, signo=6, threadid=140737228670528) at ./nptl/pthread_kill.c:44 #1 __pthread_kill_internal (signo=6, threadid=140737228670528) at ./nptl/pthread_kill.c:78 #2 __GI___pthread_kill (threadid=140737228670528, signo=signo@entry=6) at ./nptl/pthread_kill.c:89 #3 0x776bb476 in __GI_raise (sig=sig@entry=6) at ../sysdeps/posix/raise.c:26 #4 0x776a17f3 in __GI_abort () at ./stdlib/abort.c:79 #5 0x77d44b57 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #6 0x77d9e70f in g_assertion_message_expr () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #7 0x711be0e3 in () at /lib/x86_64-linux-gnu/libgtk-4.so.1 #8 0x7123a0b4 in () at /lib/x86_64-linux-gnu/libgtk-4.so.1 #9 0x7123a7b1 in () at /lib/x86_64-linux-gnu/libgtk-4.so.1 #10 0x77b9f194 in () at /lib/x86_64-linux-gnu/libgio-2.0.so.0 #11 0x77dad6b4 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #12 0x77daaa51 in () at /lib/x86_64-linux-gnu/libglib-2.0.so.0 #13 0x7770db43 in start_thread (arg=) at ./nptl/pthread_create.c:442 #14 0x7779fa00 in clone3 () at ../sysdeps/unix/sysv/linux/x86_64/clone3.S:81 ``` Moreover, I found in my snap logs that there was update recently applied, might be linked ``` $snap changes ID Status SpawnReadySummary 253 Doneyesterday at 21:47 CEST yesterday at 21:47 CEST Remove "gnome-3-34-1804" snap 254 Doneyesterday at 22:23 CEST yesterday at 22:23 CEST Refresh "gnome-3-38-2004" snap ``` Moreover, is seems I have multiple snap version of gnome installed ``` snap list ... gnome-3-28-18043.28.0-19-g98f9e67.98f9e67 198latest/stable canonical✓ - gnome-3-38-20040+git.efb213a 143latest/stable canonical✓ - gnome-42-2204 0+git.ff35a85 120latest/stable canonical✓ - ``` ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome (not installed) ProcVersionSignature: Ubuntu 5.15.0-76.83-generic 5.15.99 Uname: Linux 5.15.0-76-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Wed Jul 12 12:10:10 2023 InstallationDate: Installed on 2021-08-18 (692 days ago) InstallationMedia: Ubuntu 20.04.2.0 LTS "Focal Fossa" - Release amd64 (20210209.1) SourcePackage: meta-gnome3 UpgradeStatus: Upgraded to jammy on 2023-07-01 (10 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-shell/+bug/2027571/+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 2028301] Re: Feature request: Use dark text on a bright background
See also this Trisquel issue: mate-terminal: Proposed theme profile for improved ergonomics - https://gitlab.trisquel.org/trisquel/package- helpers/-/issues/95 ** Bug watch added: gitlab.trisquel.org/trisquel/package-helpers/-/issues #95 https://gitlab.trisquel.org/trisquel/package-helpers/-/issues/95 ** Description changed: * The default background color in Ubuntu MATE 22.04 is white. * The default background color in Ubuntu 22.04, and 23.04, is tyrian purple-ish (very dark). A dark background will cause eye-straining on day time use. This will turn off the default theme and use a light-purple background instead: profile_key=$(gsettings get org.gnome.Terminal.ProfilesList default | sed -e "s/'//g" | tr -d "\n") gsettings set org.gnome.Terminal.Legacy.Profile:/org/gnome/terminal/legacy/profiles:/:$profile_key/ use-theme-colors false gsettings set org.gnome.Terminal.Legacy.Profile:/org/gnome/terminal/legacy/profiles:/:$profile_key/ background-color "'rgb(255,224,255)'" + + + See also: + * Trisquel issue: mate-terminal: Proposed theme profile for improved ergonomics - https://gitlab.trisquel.org/trisquel/package-helpers/-/issues/95 + * mate-terminal (unpackaged): [Feature request]: Use bright background #441 - https://github.com/mate-desktop/mate-terminal/issues/441 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-terminal 3.48.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jul 20 17:06:24 2023 InstallationDate: Installed on 2023-04-23 (87 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: - LANG=en_US.UTF-8 - PATH=(custom, no user) - SHELL=/bin/bash - TERM=xterm-256color - XDG_RUNTIME_DIR= + LANG=en_US.UTF-8 + PATH=(custom, no user) + SHELL=/bin/bash + TERM=xterm-256color + XDG_RUNTIME_DIR= SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2028301 Title: Feature request: Use dark text on a bright background Status in gnome-terminal package in Ubuntu: New Bug description: * The default background color in Ubuntu MATE 22.04 is white. * The default background color in Ubuntu 22.04, and 23.04, is tyrian purple-ish (very dark). A dark background will cause eye-straining on day time use. This will turn off the default theme and use a light-purple background instead: profile_key=$(gsettings get org.gnome.Terminal.ProfilesList default | sed -e "s/'//g" | tr -d "\n") gsettings set org.gnome.Terminal.Legacy.Profile:/org/gnome/terminal/legacy/profiles:/:$profile_key/ use-theme-colors false gsettings set org.gnome.Terminal.Legacy.Profile:/org/gnome/terminal/legacy/profiles:/:$profile_key/ background-color "'rgb(255,224,255)'" See also: * Trisquel issue: mate-terminal: Proposed theme profile for improved ergonomics - https://gitlab.trisquel.org/trisquel/package-helpers/-/issues/95 * mate-terminal (unpackaged): [Feature request]: Use bright background #441 - https://github.com/mate-desktop/mate-terminal/issues/441 ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-terminal 3.48.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jul 20 17:06:24 2023 InstallationDate: Installed on 2023-04-23 (87 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2028301/+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 2028301] [NEW] Feature request: Use dark text on a bright background
Public bug reported: * The default background color in Ubuntu MATE 22.04 is white. * The default background color in Ubuntu 22.04, and 23.04, is tyrian purple-ish (very dark). A dark background will cause eye-straining on day time use. This will turn off the default theme and use a light-purple background instead: profile_key=$(gsettings get org.gnome.Terminal.ProfilesList default | sed -e "s/'//g" | tr -d "\n") gsettings set org.gnome.Terminal.Legacy.Profile:/org/gnome/terminal/legacy/profiles:/:$profile_key/ use-theme-colors false gsettings set org.gnome.Terminal.Legacy.Profile:/org/gnome/terminal/legacy/profiles:/:$profile_key/ background-color "'rgb(255,224,255)'" ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-terminal 3.48.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jul 20 17:06:24 2023 InstallationDate: Installed on 2023-04-23 (87 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-terminal (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug lunar wayland-session -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-terminal in Ubuntu. https://bugs.launchpad.net/bugs/2028301 Title: Feature request: Use dark text on a bright background Status in gnome-terminal package in Ubuntu: New Bug description: * The default background color in Ubuntu MATE 22.04 is white. * The default background color in Ubuntu 22.04, and 23.04, is tyrian purple-ish (very dark). A dark background will cause eye-straining on day time use. This will turn off the default theme and use a light-purple background instead: profile_key=$(gsettings get org.gnome.Terminal.ProfilesList default | sed -e "s/'//g" | tr -d "\n") gsettings set org.gnome.Terminal.Legacy.Profile:/org/gnome/terminal/legacy/profiles:/:$profile_key/ use-theme-colors false gsettings set org.gnome.Terminal.Legacy.Profile:/org/gnome/terminal/legacy/profiles:/:$profile_key/ background-color "'rgb(255,224,255)'" ProblemType: Bug DistroRelease: Ubuntu 23.04 Package: gnome-terminal 3.48.0-1ubuntu1 ProcVersionSignature: Ubuntu 6.2.0-20.20-generic 6.2.6 Uname: Linux 6.2.0-20-generic x86_64 ApportVersion: 2.26.1-0ubuntu2 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Jul 20 17:06:24 2023 InstallationDate: Installed on 2023-04-23 (87 days ago) InstallationMedia: Ubuntu 23.04 "Lunar Lobster" - Release amd64 (20230418) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= SourcePackage: gnome-terminal UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/2028301/+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 1697122] Re: Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel scrolling with touchpad and touch gestures
** Tags added: udeng-1089 -- 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/1697122 Title: Package Firefox with MOZ_USE_XINPUT2=1 in environment to enable pixel scrolling with touchpad and touch gestures Status in Mozilla Firefox: Confirmed Status in firefox package in Ubuntu: Triaged Bug description: Ubuntu version: Kubuntu 17.04 Firefox version: 53.0.3+build1-0ubuntu0.17.04.2 In Firefox, two-finger scroll gestures on a touchpad are interpreted as scroll wheel rotations, and the content scrolls three lines at a time. This is inappropriate behavior for touchpad scrolling; it should scroll pixel-by-pixel. Firefox already has the ability to do this, you just need to turn it on by running the program with MOZ_USE_XINPUT2=1 in the environment: for example, by running `MOZ_USE_XINPUT2=1 firefox`, or adding it to /etc/environment or something like that. Turning on this behavior yields a large usability improvement for laptop users. Therefore, I am proposing that MOZ_USE_XINPUT2=1 be permanently added to the packaging such that it's always present when Firefox runs. This is what Fedora does, and it results in a much improved experience for the laptop user. To manage notifications about this bug go to: https://bugs.launchpad.net/firefox/+bug/1697122/+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 1968907] Re: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed
Same issue here, OS 100% up-to-date: Distributor ID: Ubuntu Description:Ubuntu 22.04.2 LTS Release:22.04 Codename: jammy Since today update, the gnome keyring is no more able to login at startup, thus after I enter my user password, the GUI is 100% stuck, not even showing the "The login keyring did not get unlocked when you logged into your computer". I need to switch to another "session", do some actions, and then move back to GUI to be able to keep on. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-session in Ubuntu. https://bugs.launchpad.net/bugs/1968907 Title: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Status in gnome-session: Fix Released Status in gnome-session package in Ubuntu: Fix Released Bug description: Hi, I see the following errors in the system logs: # journalctl | grep gnome-session-binary Apr 13 18:22:54 vougeot gnome-session[3453]: gnome-session-binary[3453]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Apr 13 18:22:54 vougeot gnome-session[3453]: gnome-session-binary[3453]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Apr 13 18:22:54 vougeot gnome-session-binary[3453]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed Apr 13 18:22:54 vougeot gnome-session-binary[3453]: GLib-GIO-CRITICAL: g_bus_get_sync: assertion 'error == NULL || *error == NULL' failed ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-session-bin 42.0-1ubuntu2 Uname: Linux 5.17.2-051702-generic x86_64 ApportVersion: 2.20.11-0ubuntu81 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: KDE Date: Wed Apr 13 19:48:49 2022 RebootRequiredPkgs: Error: path contained symlinks. SourcePackage: gnome-session UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/gnome-session/+bug/1968907/+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 2026637] Re: [mantic] many useful apps are marked for auto removal
** Tags removed: rls-mm-incoming ** Tags added: foundations-todo -- 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/2026637 Title: [mantic] many useful apps are marked for auto removal Status in ubuntu-meta package in Ubuntu: Triaged Status in ubuntu-release-upgrader package in Ubuntu: Triaged Bug description: Today update want remove a lot of apps. This happens on two systems installed from ISO dated 2023-06-07 and 2023-05-21 corrado@corrado-n03-mm-0607:~$ sudo apt update && sudo apt upgrade [sudo] password for corrado: Hit:1 http://archive.ubuntu.com/ubuntu mantic InRelease Hit:2 http://archive.ubuntu.com/ubuntu mantic-updates InRelease Hit:3 http://archive.ubuntu.com/ubuntu mantic-backports InRelease Hit:4 http://archive.ubuntu.com/ubuntu mantic-security InRelease Reading package lists... Done Building dependency tree... Done Reading state information... Done All packages are up to date. Reading package lists... Done Building dependency tree... Done Reading state information... Done Calculating upgrade... Done The following packages were automatically installed and are no longer required: aisleriot baobab branding-ubuntu cheese cheese-common file-roller gir1.2-rb-3.0 gnome-mahjongg gnome-mines gnome-sudoku gnome-video-effects gstreamer1.0-clutter-3.0 guile-3.0-libs libavahi-ui-gtk3-0 libcairomm-1.16-1 libcdr-0.1-1 libchamplain-0.12-0 libchamplain-gtk-0.12-0 libcheese-gtk25 libcheese8 libclutter-gst-3.0-0 libdmapsharing-4.0-3 libevent-2.1-7 libfreehand-0.1-1 libfreerdp-client2-2 libglibmm-2.68-1 libgnome-games-support-1-3 libgnome-games-support-common libgpod-common libgpod4 libgtkmm-4.0-0 libgupnp-igd-1.0-4 libixml10 liblc3-0 libminiupnpc17 libmspub-0.1-1 libmujs2 libnatpmp1 libpagemaker-0.0-0 libpangomm-2.48-1 libqqwing2v5 libreoffice-calc libreoffice-draw libreoffice-gnome libreoffice-gtk3 libreoffice-impress librhythmbox-core10 libsdl-image1.2 libsdl1.2debian libsgutils2-1.46-2 libsigc++-3.0-0 libupnp13 libvisio-0.1-1 lp-solve media-player-info python3-mako python3-renderpm python3-reportlab-accel remmina remmina-common remmina-plugin-rdp remmina-plugin-secret remmina-plugin-vnc rhythmbox rhythmbox-data rhythmbox-plugin-alternative-toolbar rhythmbox-plugins shotwell shotwell-common simple-scan transmission-common transmission-gtk Use 'sudo apt autoremove' to remove them. 0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded. corrado@corrado-n03-mm-0607: ProblemType: Bug DistroRelease: Ubuntu 23.10 Package: ubuntu-desktop 1.505 ProcVersionSignature: Ubuntu 6.3.0-7.7-generic 6.3.5 Uname: Linux 6.3.0-7-generic x86_64 ApportVersion: 2.26.1-0ubuntu3 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Sun Jul 9 08:53:45 2023 InstallationDate: Installed on 2023-06-07 (31 days ago) InstallationMedia: Ubuntu 23.10 "Mantic Minotaur" - Daily amd64 (20230607) ProcEnviron: LANG=en_US.UTF-8 PATH=(custom, no user) SHELL=/bin/bash TERM=xterm-256color XDG_RUNTIME_DIR= 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/2026637/+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 2028054] Re: [MIR] python-rlpycairo
Ok, we're not doing the MIR then and waiting for the desktop team to demote the printing stack. ** Changed in: python-rlpycairo (Ubuntu) Status: Incomplete => Won't Fix -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/2028054 Title: [MIR] python-rlpycairo Status in hplip package in Ubuntu: New Status in python-reportlab package in Ubuntu: New Status in python-rlpycairo package in Ubuntu: Won't Fix Bug description: python-rlpycairo is a new dependency of python-reportlab (currently owned by Foundations). The only consumer of python-reportlab is hplip (owned by Desktop), apparently it needs it for scanning: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=651240 $ reverse-depends src:python-reportlab -c main -r mantic Reverse-Depends === * hplip (for python3-reportlab) Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, ppc64el, s390x src:hplip -> src:python-reportlab -> src:python-rlpycairo -> src:freetype-py & src:ttf-bitstream-vera So from the above, it sounds like this new dependency is actually needed (after the reportlab package dropped its renderpm extension). It should be discussed between Foundations and Desktop who's owning those dependencies and doing the MIRs for python-rlpycairo, freetype- py and ttf-bitstream-vera To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/2028054/+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 2028054] Re: [MIR] python-rlpycairo
** Tags removed: rls-mm-incoming -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to hplip in Ubuntu. https://bugs.launchpad.net/bugs/2028054 Title: [MIR] python-rlpycairo Status in hplip package in Ubuntu: New Status in python-reportlab package in Ubuntu: New Status in python-rlpycairo package in Ubuntu: Won't Fix Bug description: python-rlpycairo is a new dependency of python-reportlab (currently owned by Foundations). The only consumer of python-reportlab is hplip (owned by Desktop), apparently it needs it for scanning: https://bugs.debian.org/cgi- bin/bugreport.cgi?bug=651240 $ reverse-depends src:python-reportlab -c main -r mantic Reverse-Depends === * hplip (for python3-reportlab) Packages without architectures listed are reverse-dependencies in: amd64, arm64, armhf, ppc64el, s390x src:hplip -> src:python-reportlab -> src:python-rlpycairo -> src:freetype-py & src:ttf-bitstream-vera So from the above, it sounds like this new dependency is actually needed (after the reportlab package dropped its renderpm extension). It should be discussed between Foundations and Desktop who's owning those dependencies and doing the MIRs for python-rlpycairo, freetype- py and ttf-bitstream-vera To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/2028054/+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 2028144] Re: libperl-glib gkeyfiles tests failure after libglib2.77 update
** Changed in: glib 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/2028144 Title: libperl-glib gkeyfiles tests failure after libglib2.77 update Status in GLib: Fix Released Status in glib2.0 package in Ubuntu: In Progress Status in libglib-perl package in Ubuntu: Triaged Bug description: Reported upstream as https://gitlab.gnome.org/GNOME/glib/-/issues/3056 now To manage notifications about this bug go to: https://bugs.launchpad.net/glib/+bug/2028144/+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 2026727] Re: Clicking on a notification no longer raises window in LTS 22.04.3
Status changed to 'Confirmed' because the bug affects multiple users. ** Changed in: gnome-shell (Ubuntu) Status: New => Confirmed -- 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/2026727 Title: Clicking on a notification no longer raises window in LTS 22.04.3 Status in gnome-shell package in Ubuntu: Confirmed Bug description: As part of the LTS 22.04.3 release many gnome package updates are available in the 'proposed' repository. When checking these on a test machine I noticed that the window raise behavior when clicking on notifications has regressed for some applications. In 22.04.2 clicking on a notification in gnome shell would raise the application window and focus the inbox or chat channel the message was received in. In the 22.04.3 proposed packages this is still the case for e.g. Thunderbird, but for other applications such as 'slack' and 'signal' clicking on a new message notification no longer raises the application window. Although not a major bug, it's quite annoying as it breaks the workflow and means extra work in finding the application and the channel that the message arrived at. Due to the many package updates it's not clear to me which update broke the behavior (maybe mutter or gnome-shell) but filing it under shell because of the notification area issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-77.84-generic 5.15.108 Uname: Linux 5.15.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jul 10 08:47:24 2023 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-02 (1102 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.9-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-11-19 (232 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026727/+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 2026727] Re: Clicking on a notification no longer raises window in LTS 22.04.3
Same issue here - Distro: Ubuntu 22.04 GNOME Version: 42.9 Architecture: x86 i9 13th Gen -- 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/2026727 Title: Clicking on a notification no longer raises window in LTS 22.04.3 Status in gnome-shell package in Ubuntu: Confirmed Bug description: As part of the LTS 22.04.3 release many gnome package updates are available in the 'proposed' repository. When checking these on a test machine I noticed that the window raise behavior when clicking on notifications has regressed for some applications. In 22.04.2 clicking on a notification in gnome shell would raise the application window and focus the inbox or chat channel the message was received in. In the 22.04.3 proposed packages this is still the case for e.g. Thunderbird, but for other applications such as 'slack' and 'signal' clicking on a new message notification no longer raises the application window. Although not a major bug, it's quite annoying as it breaks the workflow and means extra work in finding the application and the channel that the message arrived at. Due to the many package updates it's not clear to me which update broke the behavior (maybe mutter or gnome-shell) but filing it under shell because of the notification area issue. ProblemType: Bug DistroRelease: Ubuntu 22.04 Package: gnome-shell 42.9-0ubuntu2 ProcVersionSignature: Ubuntu 5.15.0-77.84-generic 5.15.108 Uname: Linux 5.15.0-77-generic x86_64 ApportVersion: 2.20.11-0ubuntu82.5 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Jul 10 08:47:24 2023 DisplayManager: gdm3 InstallationDate: Installed on 2020-07-02 (1102 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 42.9-0ubuntu1 SourcePackage: gnome-shell UpgradeStatus: Upgraded to jammy on 2022-11-19 (232 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/2026727/+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 2020049] Re: gnome-shell crashed with SIGSEGV in clutter_stage_view_get_onscreen() from meta_stage_impl_add_onscreen_frame_info() from add_onscreen_frame_info() from post_finis
I tried reporting my most recent crash but ubuntu-bug just exits immediately when I try to send the report with 'ubuntu-bug ' and pressing S afterwards. I'll continue trying to report it. -- 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/2020049 Title: gnome-shell crashed with SIGSEGV in clutter_stage_view_get_onscreen() from meta_stage_impl_add_onscreen_frame_info() from add_onscreen_frame_info() from post_finish_frame() from try_post_latest_swap() Status in mutter package in Ubuntu: Fix Released Status in mutter source package in Lunar: Fix Committed Status in mutter source package in Mantic: Fix Released Bug description: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 44.0-2ubuntu3, the problem page at https://errors.ubuntu.com/problem/c675f1d61cef940571272d7e655162f1b1cddab1 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/mutter/+bug/2020049/+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 2027671] Re: [SRU] libreoffice 7.5.5 for lunar
** Description changed: [Impact] * LibreOffice 7.5.5 is in its fifth bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.5_release * Version 7.5.4 is currently released in lunar. For a list of fixed bugs compared to 7.5.4 see the list of bugs fixed in the release candidates of 7.5.5 (that's a total of 70 bugs): https://wiki.documentfoundation.org/Releases/7.5.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.5.5/RC2#List_of_fixed_bugs + + 7.5.5 RC2 is identical to the 7.5.5 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1589/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests https://wiki.documentfoundation.org/Development/UITests * Regression tests https://wiki.documentfoundation.org/QA/Testing/Regression_Tests * Feature tests https://wiki.documentfoundation.org/QA/Testing/Feature_Tests * Launchpad testing. The libreoffice packages include autopkgtests that were run and verified as passing. Tested build can be found at https://launchpad.net/~libreoffice/+archive/ubuntu/libreoffice-prereleases/+sourcepub/15016907/+listing-archive-extra * [amd64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/amd64/libr/libreoffice/20230718_033443_f8aa9@/log.gz * [arm64] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/arm64/libr/libreoffice/20230714_103204_cba01@/log.gz * [armhf] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/armhf/libr/libreoffice/20230714_150913_425f2@/log.gz * [ppc64el] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/ppc64el/libr/libreoffice/20230714_061923_700ec@/log.gz * [riscv64] not available * [s390x] https://autopkgtest.ubuntu.com/results/autopkgtest-lunar-libreoffice-libreoffice-prereleases/lunar/s390x/libr/libreoffice/20230715_114537_85189@/log.gz * General smoke testing of all the applications in the office suite were carried out by going through the manual testplan as documented by: https://wiki.ubuntu.com/Process/Merges/TestPlans/libreoffice [Regression Potential] * A minor release with a total of 70 bug fixes always carries the potential for introducing regressions, even though it is a bugfix-only release, meaning that no new features were added, and no existing features were removed. * A combination of autopkgtests and careful smoke testing as described above should provide reasonable confidence that no regressions sneaked in.a -- 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/2027671 Title: [SRU] libreoffice 7.5.5 for lunar Status in libreoffice package in Ubuntu: New Status in libreoffice source package in Lunar: In Progress Bug description: [Impact] * LibreOffice 7.5.5 is in its fifth bugfix release of the 7.5 line: https://wiki.documentfoundation.org/ReleasePlan/7.5#7.5.5_release * Version 7.5.4 is currently released in lunar. For a list of fixed bugs compared to 7.5.4 see the list of bugs fixed in the release candidates of 7.5.5 (that's a total of 70 bugs): https://wiki.documentfoundation.org/Releases/7.5.5/RC1#List_of_fixed_bugs https://wiki.documentfoundation.org/Releases/7.5.5/RC2#List_of_fixed_bugs 7.5.5 RC2 is identical to the 7.5.5 release * Given the nature of the project, the complexity of the codebase and the high level of quality assurance upstream, it is preferable to SRU a minor release rather than cherry-pick selected bug fixes. [Testing] * Upstream testing. Bugs fixed upstream typically include unit/regression tests, and the release itself is extensively exercised (both in an automated manner and manually). * A recent set of upstream's automated jenkins testing can be found here: https://ci.libreoffice.org/job/gerrit_75/1589/ * More information about the upstream QA testing can be found here: * Automated tests https://wiki.documentfoundation.org/QA/Testing/Automated_Tests * Automated UI tests
[Desktop-packages] [Bug 1736176]
(In reply to Karsten from comment #38) Please use some common sense! We are discussing the [Scroll Lock] keyboard key here, not [Kbd Layout] key. This key was *intended* specifically for the purpose of modifying the behavior of arrow keys [1]; it was intended that this key woks as it was introduced in LibreOffice 5.3. So it *definitely* was implementing *the* standard behavior. Standard for all spreadsheet software (so industry best practices compliance); standard for keyboard design; standard for the vast majority of users. The behavior before that was *not* standard (and users imagining that any behavior of their favorite version X is "standard", are just proof of https://xkcd.com/1172/). And unlimited flexibility with every feature being configurable is bad. Bad for users; bad for maintenance. If we tried to do that, we wouldn't be able to improve the program. People wanted that feature since long ago (it was introduced in 2017 to implement tdf#46200 from 2012, which had many watchers, and itself referenced i#7179 from 2002). Those people who wanted the old behavior asked for that, and finally it arrived. Those who wrote things like comment 33 after that, are just ... let me not call things their proper names. [1] https://en.wikipedia.org/wiki/Scroll_Lock -- 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/1736176 Title: [upstream] Can't jump between cells when non-english input layout is active Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Confirmed Bug description: Can't jump between LibreOffice Calc cells by arrow keys when non- english input layout is active. It's because Ubuntu is using Scroll Lock indicator (LED) to show state of layout switch, but in LibreOffice Scroll Lock state is used to switch between page's scrolling and jumping on cells. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libreoffice 1:5.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 4 17:25:29 2017 InstallationDate: Installed on 2017-10-19 (45 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1736176/+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 1736176]
(In reply to Karsten from comment #38) > (In reply to Mike Kaganski from comment #36) > > If no one was affected bad enough to jump in and try to fix it, with > > friendly help of > > mentors here offering their assistance, it indicates not a huge problem... > > Why any problem must be caused by introducing new features? > Why the standard behaviour is changed and new features are not optional, so > that everything keeps fine? Often options are added, but keep in mind that this duplicates the maintenance burden of a feature. The danger is having an ever-growing fractal of test cases to care for. -- 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/1736176 Title: [upstream] Can't jump between cells when non-english input layout is active Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Confirmed Bug description: Can't jump between LibreOffice Calc cells by arrow keys when non- english input layout is active. It's because Ubuntu is using Scroll Lock indicator (LED) to show state of layout switch, but in LibreOffice Scroll Lock state is used to switch between page's scrolling and jumping on cells. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libreoffice 1:5.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 4 17:25:29 2017 InstallationDate: Installed on 2017-10-19 (45 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1736176/+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 1736176]
(In reply to Heiko Tietze from comment #37) > Standard behavior is not clearly defined but you are right, and we do our > best. Standard behaviour can be defined as the working of a software in a stable version. > In this case scroll lock was implemented as a standard. Normally your team is feeling offended when it is measured with MS Office. The nice thing of Libreoffice is to do it better. :-P > More questionable is the second part with everything being optional. Let's > better > decide on every change whether it make sense to bloat the options, even when > it's an advanced setting. It is bad usability if you a) have to change an > option, and b) struggle to find it. Sorry - it is bad usability when you have to find out why the software cannot be used in a accustomed matter any more and it is really pain when you are forced to find out workarounds to compensate new "features" that will make you crazy. > > That's the reason why i am still using Version 7.1.8.1... > You miss a lot of goodies :-). The goodie is to be able to work with Libreoffice without circumnavigate the pain of workarounds. In the most cases only the absolute standard basic features are needed. An Office package is something like a basic tool for writing text or calculating in a spread sheet. Observing most other users they never use any special functionality, because they simply don't understand it. So about what kind of progress we are talking about? > We offer release > candidates and nightly builds that run in parallel so you can test the new > releases. Your input is very much welcome. Thanks - the time will come to test a new stable release. :-) -- 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/1736176 Title: [upstream] Can't jump between cells when non-english input layout is active Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Confirmed Bug description: Can't jump between LibreOffice Calc cells by arrow keys when non- english input layout is active. It's because Ubuntu is using Scroll Lock indicator (LED) to show state of layout switch, but in LibreOffice Scroll Lock state is used to switch between page's scrolling and jumping on cells. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libreoffice 1:5.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 4 17:25:29 2017 InstallationDate: Installed on 2017-10-19 (45 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1736176/+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 1736176]
(In reply to Mike Kaganski from comment #36) > (In reply to Karsten from comment #33) > > Lol. There are hundreds of millions (billions?) Excel users out there; and > each of them enjoys ScrollLock support, working exactly the same way it was > implemented almost 6 years ago in Calc. And there are hundreds of other users that suffer under the non optional implementation of that feature. ;-) In the own case it was not a special keyboard, it was the behaviour of KDE that did not allow to alter the state when I remember correct. > If no one was affected bad enough to jump in and try to fix it, with friendly > help of > mentors here offering their assistance, it indicates not a huge problem... Why any problem must be caused by introducing new features? Why the standard behaviour is changed and new features are not optional, so that everything keeps fine? -- 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/1736176 Title: [upstream] Can't jump between cells when non-english input layout is active Status in LibreOffice: Fix Released Status in libreoffice package in Ubuntu: Confirmed Bug description: Can't jump between LibreOffice Calc cells by arrow keys when non- english input layout is active. It's because Ubuntu is using Scroll Lock indicator (LED) to show state of layout switch, but in LibreOffice Scroll Lock state is used to switch between page's scrolling and jumping on cells. ProblemType: Bug DistroRelease: Ubuntu 17.10 Package: libreoffice 1:5.4.1-0ubuntu1 ProcVersionSignature: Ubuntu 4.13.0-17.20-generic 4.13.8 Uname: Linux 4.13.0-17-generic x86_64 ApportVersion: 2.20.7-0ubuntu3.5 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Mon Dec 4 17:25:29 2017 InstallationDate: Installed on 2017-10-19 (45 days ago) InstallationMedia: Ubuntu 17.10 "Artful Aardvark" - Release amd64 (20171018) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=uk_UA.UTF-8 SHELL=/bin/bash SourcePackage: libreoffice UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/df-libreoffice/+bug/1736176/+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 1958019]
Then sounds like your laptop is supported by my patch: https://bugzilla.kernel.org/show_bug.cgi?id=216194 This patch will never make it into the kernel. But if you are able to apply the patch and build your own kernel... This will get you sound. (In reply to Linghui Ding from comment #775) > Here is the URL: > > > http://alsa-project.org/db/?f=1ea099cf4369c1547b45eec8f9fefdc2f7cfd892 > > > Thanks a lot, and do you think kernel 6.5.0 will include a method that would > solve this sound problem? -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]
Is there any update on the AMD model of the Legion 7 Gen 7? My understanding is it's a different device - but curious if progress has been made there? -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]
(In reply to Cameron Berkenpas from comment #774) > Depends on which laptop you have. It will work if you have the Legion 7i Gen > 7, but not for the Gen 8 (but there is work to get the Gen 8 working that > will be mainlined). > > Share a link to your alsa-info. > > (In reply to Linghui Ding from comment #773) > > > So, this patch can solve the sound problem, right? Enlighten me pls, I > would > > sacrifice everything to hear my laptop. Here is the URL: http://alsa-project.org/db/?f=1ea099cf4369c1547b45eec8f9fefdc2f7cfd892 Thanks a lot, and do you think kernel 6.5.0 will include a method that would solve this sound problem? -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]
Depends on which laptop you have. It will work if you have the Legion 7i Gen 7, but not for the Gen 8 (but there is work to get the Gen 8 working that will be mainlined). Share a link to your alsa-info. (In reply to Linghui Ding from comment #773) > So, this patch can solve the sound problem, right? Enlighten me pls, I would > sacrifice everything to hear my laptop. -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]
(In reply to antidense from comment #769) > I have the Legion S7 16ARHA7 w/ Cirrus amp. I've been patching the kernel > using lenovo-7i-gen7-sound-6.2.0-rc3-0.0.5b-002.patch with working sound. > However, I'm not able to hibernate my laptop successfully. It will hang > after saving to disk but it won't shut off on it's own - just stays on with > a black screen with the fan going. Then it drains the battery until it dies. > If I turn it on again, it will successfully resume from hibernation. I'm not > sure what is causing it. It works find if nothing is open (just > gnome-shell), but as soon as I open firefox or chrome the problem recurs if > it goes to hibernate. Did anyone else have the same issue? So, this patch can solve the sound problem, right? Enlighten me pls, I would sacrifice everything to hear my laptop. -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 1958019]
(In reply to antidense from comment #769) > I have the Legion S7 16ARHA7 w/ Cirrus amp. I've been patching the kernel > using lenovo-7i-gen7-sound-6.2.0-rc3-0.0.5b-002.patch with working sound. > However, I'm not able to hibernate my laptop successfully. It will hang > after saving to disk but it won't shut off on it's own - just stays on with > a black screen with the fan going. Then it drains the battery until it dies. > If I turn it on again, it will successfully resume from hibernation. I'm not > sure what is causing it. It works find if nothing is open (just > gnome-shell), but as soon as I open firefox or chrome the problem recurs if > it goes to hibernate. Did anyone else have the same issue? So, this patch can solve the sound problem, right? Enlighten me pls, I would sacrifice everything to hear my laptop. -- 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/1958019 Title: [Lenovo Legion7 16ACHg6 82N6, Realtek ALC287, Speaker, Internal] No sound at all Status in sound-2.6 (alsa-kernel): Confirmed Status in alsa-driver package in Ubuntu: Confirmed Bug description: On my Lenovo Legion-7-16ACHg6 laptop I can't hear any sound by internal speakers, but it work by headphones connected to standard jack aux. uname -r 5.11.0-44-generic ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: alsa-base 1.0.25+dfsg-0ubuntu5 ProcVersionSignature: Ubuntu 5.11.0-44.48~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-44-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 AudioDevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio CasperMD5CheckResult: skip CurrentDesktop: ubuntu:GNOME Date: Sat Jan 15 15:10:53 2022 InstallationDate: Installed on 2021-10-11 (96 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) PackageArchitecture: all SourcePackage: alsa-driver Symptom: audio Symptom_AlsaPlaybackTest: ALSA playback test through plughw:Generic failed Symptom_Card: Family 17h (Models 10h-1fh) HD Audio Controller - HD-Audio Generic Symptom_DevicesInUse: USERPID ACCESS COMMAND /dev/snd/controlC2: i3draven 1266 F pulseaudio /dev/snd/controlC0: i3draven 1266 F pulseaudio /dev/snd/controlC1: i3draven 1266 F pulseaudio /dev/snd/pcmC1D0p: i3draven 1266 F...m pulseaudio Symptom_Jack: Speaker, Internal Symptom_Type: No sound at all Title: [82N6, Realtek ALC287, Speaker, Internal] No sound at all UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 11/08/2021 dmi.bios.release: 1.49 dmi.bios.vendor: LENOVO dmi.bios.version: GKCN49WW dmi.board.asset.tag: NO Asset Tag dmi.board.name: LNVNB161216 dmi.board.vendor: LENOVO dmi.board.version: SDK0R32862 WIN dmi.chassis.asset.tag: NO Asset Tag dmi.chassis.type: 10 dmi.chassis.vendor: LENOVO dmi.chassis.version: Legion 7 16ACHg6 dmi.ec.firmware.release: 1.49 dmi.modalias: dmi:bvnLENOVO:bvrGKCN49WW:bd11/08/2021:br1.49:efr1.49:svnLENOVO:pn82N6:pvrLegion716ACHg6:skuLENOVO_MT_82N6_BU_idea_FM_Legion716ACHg6:rvnLENOVO:rnLNVNB161216:rvrSDK0R32862WIN:cvnLENOVO:ct10:cvrLegion716ACHg6: dmi.product.family: Legion 7 16ACHg6 dmi.product.name: 82N6 dmi.product.sku: LENOVO_MT_82N6_BU_idea_FM_Legion 7 16ACHg6 dmi.product.version: Legion 7 16ACHg6 dmi.sys.vendor: LENOVO To manage notifications about this bug go to: https://bugs.launchpad.net/sound-2.6/+bug/1958019/+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 2023363] Re: Mouse input latency in GNOME 44.1 Wayland sessions is one frame higher than it was in 44.0 and earlier
Fix proposed to Debian: https://salsa.debian.org/gnome-team/mutter/-/merge_requests/101 -- 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/2023363 Title: Mouse input latency in GNOME 44.1 Wayland sessions is one frame higher than it was in 44.0 and earlier Status in mutter package in Ubuntu: In Progress Status in mutter source package in Lunar: In Progress Status in mutter source package in Mantic: In Progress Bug description: [ Impact ] Mouse input latency in Wayland sessions is slightly higher in 23.10 than 22.04 at the moment. I might be imagining things and it does feel like only one frame higher latency. But experimenting with MUTTER_DEBUG_TRIPLE_BUFFERING seems to confirm my suspicion: BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=auto (the Ubuntu default) BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=always GOOD: MUTTER_DEBUG_TRIPLE_BUFFERING=never [ Workaround ] Add MUTTER_DEBUG_FORCE_KMS_MODE=simple to /etc/environment. Actually that was already a good idea for the best cursor performance even before this bug. [ Test Plan ] 0. Find a machine with an Intel GPU. 1. Add this to /etc/environment: CLUTTER_DEBUG=frame-timings 2. Reboot. 3. Log in to a Wayland session and wait for the desktop to become idle. 4. Also log in via ssh from a remote machine and run: journalctl -f /usr/bin/gnome-shell 5. Over your idle desktop just wiggle the mouse continuously for at least 5 seconds. 6. In your ssh login, verify that the resulting log messages from gnome-shell say "[FRAME_TIMINGS]: Double buffering:" and not "[FRAME_TIMINGS]: Triple buffering:" when only the mouse pointer is moving. [ Where problems could occur ] In the frame rate and latency of the Ubuntu desktop experience. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023363/+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 2021956] Re: crash cups-proxyd
Upon further investigation, I noticed that the cups snap was installed alongside the apt package from the Ubuntu repositories, which is installed by default on ubuntu-desktop and ubuntu-desktop-minimal: # dpkg -l | grep cups ii bluez-cups 5.64-0ubuntu1 amd64Bluetooth printer driver for CUPS ii cups 2.4.1op1-1ubuntu4.4 amd64Common UNIX Printing System(tm) - PPD/driver support, web interface ii cups-browsed 1.28.15-0ubuntu1.2 amd64OpenPrinting CUPS Filters - cups-browsed ii cups-bsd 2.4.1op1-1ubuntu4.4 amd64Common UNIX Printing System(tm) - BSD commands ii cups-client2.4.1op1-1ubuntu4.4 amd64Common UNIX Printing System(tm) - client programs (SysV) ii cups-common2.4.1op1-1ubuntu4.4 all Common UNIX Printing System(tm) - common files ii cups-core-drivers 2.4.1op1-1ubuntu4.4 amd64Common UNIX Printing System(tm) - driverless printing ii cups-daemon2.4.1op1-1ubuntu4.4 amd64Common UNIX Printing System(tm) - daemon ii cups-filters 1.28.15-0ubuntu1.2 amd64OpenPrinting CUPS Filters - Main Package ii cups-filters-core-drivers 1.28.15-0ubuntu1.2 amd64OpenPrinting CUPS Filters - Driverless printing ii cups-ipp-utils 2.4.1op1-1ubuntu4.4 amd64Common UNIX Printing System(tm) - IPP developer/admin utilities ii cups-pk-helper 0.2.6-1ubuntu5 amd64PolicyKit helper to configure cups with fine-grained privileges ii cups-ppdc 2.4.1op1-1ubuntu4.4 amd64Common UNIX Printing System(tm) - PPD manipulation utilities ii cups-server-common 2.4.1op1-1ubuntu4.4 all Common UNIX Printing System(tm) - server common files ii libcups2:amd64 2.4.1op1-1ubuntu4.4 amd64Common UNIX Printing System(tm) - Core library ii libcupsfilters1:amd64 1.28.15-0ubuntu1.2 amd64OpenPrinting CUPS Filters - Shared library ii libcupsimage2:amd642.4.1op1-1ubuntu4.4 amd64Common UNIX Printing System(tm) - Raster image library ii printer-driver-hpcups 3.21.12+dfsg0-1 amd64HP Linux Printing and Imaging - CUPS Raster driver (hpcups) ii python3-cups:amd64 2.0.1-5build1 amd64Python3 bindings for CUPS ii python3-cupshelpers1.5.16-0ubuntu3 all Python utility modules around the CUPS printing system # snap list Name Version Revision Tracking Herausgeber Hinweise bare 1.0 5 latest/stable canonical✓ base chromium 114.0.5735.198 2529 latest/stable canonical✓ - core18 202305302785 latest/stable canonical✓ base core20 202306221974 latest/stable canonical✓ base core22 20230703817 latest/stable canonical✓ base cups 2.4.6-4 980 latest/stable openprinting✓- firefox115.0.2-1 2908 latest/stable mozilla✓ - gnome-3-28-18043.28.0-19-g98f9e67.98f9e67 198 latest/stable canonical✓ - gnome-3-38-20040+git.efb213a 143 latest/stable canonical✓ - gnome-42-2204 0+git.ff35a85 120 latest/stable canonical✓ - gtk-common-themes 0.1-81-g442e511 1535 latest/stable canonical✓ - mqtt-explorer 0.3.5 29latest/stable thomasnordquist - snap-store 41.3-71-g709398e959 latest/stable canonical✓ - snapd 2.59.5 19457 latest/stable canonical✓ snapd snapd-desktop-integration 0.9 83latest/stable canonical✓ - After removing the snap package the segfault did not occur again: # snap remove cups I have yet to
[Desktop-packages] [Bug 2023363] Re: Mouse input latency in GNOME 44.1 Wayland sessions is one frame higher than it was in 44.0 and earlier
** Description changed: [ Impact ] Mouse input latency in Wayland sessions is slightly higher in 23.10 than 22.04 at the moment. I might be imagining things and it does feel like only one frame higher latency. But experimenting with MUTTER_DEBUG_TRIPLE_BUFFERING seems to confirm my suspicion: BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=auto (the Ubuntu default) BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=always GOOD: MUTTER_DEBUG_TRIPLE_BUFFERING=never + + [ Workaround ] + + Add MUTTER_DEBUG_FORCE_KMS_MODE=simple to /etc/environment. Actually + that was already a good idea for the best cursor performance even before + this bug. [ Test Plan ] 0. Find a machine with an Intel GPU. 1. Add this to /etc/environment: CLUTTER_DEBUG=frame-timings 2. Reboot. 3. Log in to a Wayland session and wait for the desktop to become idle. 4. Also log in via ssh from a remote machine and run: journalctl -f /usr/bin/gnome-shell 5. Over your idle desktop just wiggle the mouse continuously for at least 5 seconds. 6. In your ssh login, verify that the resulting log messages from gnome- shell say "[FRAME_TIMINGS]: Double buffering:" and not "[FRAME_TIMINGS]: Triple buffering:" when only the mouse pointer is moving. [ Where problems could occur ] In the frame rate and latency of the Ubuntu desktop experience. -- 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/2023363 Title: Mouse input latency in GNOME 44.1 Wayland sessions is one frame higher than it was in 44.0 and earlier Status in mutter package in Ubuntu: In Progress Status in mutter source package in Lunar: In Progress Status in mutter source package in Mantic: In Progress Bug description: [ Impact ] Mouse input latency in Wayland sessions is slightly higher in 23.10 than 22.04 at the moment. I might be imagining things and it does feel like only one frame higher latency. But experimenting with MUTTER_DEBUG_TRIPLE_BUFFERING seems to confirm my suspicion: BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=auto (the Ubuntu default) BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=always GOOD: MUTTER_DEBUG_TRIPLE_BUFFERING=never [ Workaround ] Add MUTTER_DEBUG_FORCE_KMS_MODE=simple to /etc/environment. Actually that was already a good idea for the best cursor performance even before this bug. [ Test Plan ] 0. Find a machine with an Intel GPU. 1. Add this to /etc/environment: CLUTTER_DEBUG=frame-timings 2. Reboot. 3. Log in to a Wayland session and wait for the desktop to become idle. 4. Also log in via ssh from a remote machine and run: journalctl -f /usr/bin/gnome-shell 5. Over your idle desktop just wiggle the mouse continuously for at least 5 seconds. 6. In your ssh login, verify that the resulting log messages from gnome-shell say "[FRAME_TIMINGS]: Double buffering:" and not "[FRAME_TIMINGS]: Triple buffering:" when only the mouse pointer is moving. [ Where problems could occur ] In the frame rate and latency of the Ubuntu desktop experience. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023363/+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 2023363] Re: Mouse input latency in GNOME 44.1 Wayland sessions is one frame higher than it was in 44.0 and earlier
** Description changed: [ Impact ] Mouse input latency in Wayland sessions is slightly higher in 23.10 than 22.04 at the moment. I might be imagining things and it does feel like only one frame higher latency. But experimenting with MUTTER_DEBUG_TRIPLE_BUFFERING seems to confirm my suspicion: BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=auto (the Ubuntu default) BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=always GOOD: MUTTER_DEBUG_TRIPLE_BUFFERING=never [ Test Plan ] 0. Find a machine with an Intel GPU. 1. Add this to /etc/environment: CLUTTER_DEBUG=frame-timings 2. Reboot. 3. Log in to a Wayland session and wait for the desktop to become idle. 4. Also log in via ssh from a remote machine and run: -journalctl -f /usr/bin/gnome-shell + journalctl -f /usr/bin/gnome-shell - 5. Over your idle desktop just wiggle the mouse continuously. + 5. Over your idle desktop just wiggle the mouse continuously for at + least 5 seconds. 6. In your ssh login, verify that the resulting log messages from gnome- shell say "[FRAME_TIMINGS]: Double buffering:" and not "[FRAME_TIMINGS]: Triple buffering:" when only the mouse pointer is moving. [ Where problems could occur ] In the frame rate and latency of the Ubuntu desktop experience. -- 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/2023363 Title: Mouse input latency in GNOME 44.1 Wayland sessions is one frame higher than it was in 44.0 and earlier Status in mutter package in Ubuntu: In Progress Status in mutter source package in Lunar: In Progress Status in mutter source package in Mantic: In Progress Bug description: [ Impact ] Mouse input latency in Wayland sessions is slightly higher in 23.10 than 22.04 at the moment. I might be imagining things and it does feel like only one frame higher latency. But experimenting with MUTTER_DEBUG_TRIPLE_BUFFERING seems to confirm my suspicion: BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=auto (the Ubuntu default) BAD: MUTTER_DEBUG_TRIPLE_BUFFERING=always GOOD: MUTTER_DEBUG_TRIPLE_BUFFERING=never [ Test Plan ] 0. Find a machine with an Intel GPU. 1. Add this to /etc/environment: CLUTTER_DEBUG=frame-timings 2. Reboot. 3. Log in to a Wayland session and wait for the desktop to become idle. 4. Also log in via ssh from a remote machine and run: journalctl -f /usr/bin/gnome-shell 5. Over your idle desktop just wiggle the mouse continuously for at least 5 seconds. 6. In your ssh login, verify that the resulting log messages from gnome-shell say "[FRAME_TIMINGS]: Double buffering:" and not "[FRAME_TIMINGS]: Triple buffering:" when only the mouse pointer is moving. [ Where problems could occur ] In the frame rate and latency of the Ubuntu desktop experience. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/2023363/+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 2021956] Re: crash cups-proxyd
I also experience this issue on a freshly installed Ubuntu 22.04 Desktop with no printers atteched. First I give an overview of my system and then I'll try to add the missing information. *** Kernel version: *** # uname -a Linux hostname 5.15.0-76-generic #83-Ubuntu SMP Thu Jun 15 19:16:32 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux *** OS information: *** # cat /etc/os-release PRETTY_NAME="Ubuntu 22.04.2 LTS" NAME="Ubuntu" VERSION_ID="22.04" VERSION="22.04.2 LTS (Jammy Jellyfish)" VERSION_CODENAME=jammy ID=ubuntu ID_LIKE=debian HOME_URL="https://www.ubuntu.com/; SUPPORT_URL="https://help.ubuntu.com/; BUG_REPORT_URL="https://bugs.launchpad.net/ubuntu/; PRIVACY_POLICY_URL="https://www.ubuntu.com/legal/terms-and-policies/privacy-policy; UBUNTU_CODENAME=jammy *** List of installed Snaps: *** root@hostname:~# snap list Name Version Revision Tracking Herausgeber Hinweise bare 1.0 5 latest/stable canonical✓ base chromium 114.0.5735.198 2529 latest/stable canonical✓ - core18 202305302785 latest/stable canonical✓ base core20 202306221974 latest/stable canonical✓ base core22 20230703817 latest/stable canonical✓ base cups 2.4.6-4 980 latest/stable openprinting✓- firefox115.0.2-1 2908 latest/stable mozilla✓ - gnome-3-28-18043.28.0-19-g98f9e67.98f9e67 198 latest/stable canonical✓ - gnome-3-38-20040+git.efb213a 143 latest/stable canonical✓ - gnome-42-2204 0+git.ff35a85 120 latest/stable canonical✓ - gtk-common-themes 0.1-81-g442e511 1535 latest/stable canonical✓ - mqtt-explorer 0.3.5 29latest/stable thomasnordquist - snapd 2.59.5 19457 latest/stable canonical✓ snapd *** Segfault in the syslog: *** # less /var/log/syslog: Jul 20 09:48:29 hostname kernel: [ 86.133013] audit: type=1326 audit(1689839309.216:87): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=snap.cups.cupsd pid=8278 comm="cupsd" exe="/snap/cups/980/sbin/cupsd" sig=0 arch=c03e syscall=93 compat=0 ip=0x7fd3108a8c4b code=0x5 Jul 20 09:48:30 hostname kernel: [ 87.194090] audit: type=1326 audit(1689839310.280:88): auid=4294967295 uid=0 gid=0 ses=4294967295 subj=snap.cups.cupsd pid=8280 comm="cups-proxyd" exe="/snap/cups/980/sbin/cups-proxyd" sig=0 arch=c03e syscall=314 compat=0 ip=0x7f652264ca3d code=0x5 Jul 20 09:48:30 hostname kernel: [ 87.861485] cups-proxyd[8280]: segfault at 18 ip 56043483ad75 sp 7f58ad80 error 4 in cups-proxyd[560434837000+7000] Jul 20 09:48:30 hostname kernel: [ 87.861534] Code: 83 3d ee b2 00 00 00 41 54 55 48 89 fd 53 0f 85 f4 00 00 00 48 8d 1d 69 3d 00 00 48 63 45 1c 48 89 df 48 c1 e0 05 48 03 45 08 <48> 8b 50 18 8b 70 14 e8 0f d0 ff ff 44 8b 65 18 48 89 c7 45 85 e4 *** cups-proxyd_log from the time of the system startup: *** # cat /var/snap/cups/current/var/log/cups-proxyd_log Thu Jul 20 09:48:29 2023 main() in THREAD 140072331107008 Thu Jul 20 09:48:29 2023 System CUPS: /run/cups/cups.sock Thu Jul 20 09:48:29 2023 Proxy CUPS: /var/snap/cups/common/run/cups.sock Thu Jul 20 09:48:29 2023 cups-proxyd version 1.0 starting. Thu Jul 20 09:48:29 2023 Check whether both CUPS daemons are running. Thu Jul 20 09:48:29 2023 cups-proxyd: Creating http connection to CUPS daemon via domain socket: /var/snap/cups/common/run/cups.sock Thu Jul 20 09:48:29 2023 cups-proxyd: Failed creating http connection to CUPS daemon via domain socket: /var/snap/cups/common/run/cups.sock Thu Jul 20 09:48:30 2023 cups-proxyd: Creating http connection to CUPS daemon via domain socket: /var/snap/cups/common/run/cups.sock Thu Jul 20 09:48:30 2023 cups-proxyd: Creating http connection to CUPS daemon via domain socket: /run/cups/cups.sock Thu Jul 20 09:48:30 2023 cups-proxyd: Closing connection to proxy CUPS daemon. Thu Jul 20 09:48:30 2023 cups-proxyd: Closing connection to system's CUPS daemon. Thu Jul 20 09:48:30 2023 cups-proxyd (/var/snap/cups/common/run/cups.sock): cupsEnumDests Thu Jul 20 09:48:30 2023 Using signal handler SIGNAL Thu Jul 20 09:48:30 2023 [Avahi Browser] Avahi server connection got available, setting up service browsers. Thu Jul 20 09:48:30 2023 Creating subscription to D-Bus notifications on the system's CUPS daemon. Thu Jul 20 09:48:30 2023 cups-proxyd: Creating http connection to CUPS daemon via domain socket: /run/cups/cups.sock Thu Jul 20 09:48:30 2023 cups-proxyd: Closing connection to system's CUPS daemon. Thu Jul 20 09:48:30 2023 Updating queues on proxy CUPS in 500 msecs Thu Jul 20 09:48:30 2023 browse_callback() in THREAD
