[Desktop-packages] [Bug 1949200] Re: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init
** Tags added: impish -- 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/1949200 Title: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/45d4ce4e8f26828ab6993261e8a20208ecf261b0 https://errors.ubuntu.com/problem/e60359af65f32c18a4a6ccc93fd3469b0e675844 https://errors.ubuntu.com/problem/73a93ba578f68516e680373ae324db01336e8bad . ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 29 15:11:43 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2021-10-27 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211023) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=nb_NO.UTF-8 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 40.5-1ubuntu2 Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_writer_default() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200/+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 1949200] Re: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init
The instruction addresses (modulo 16 at least) seem to match up too well to be a coincidence so I believe this is: https://errors.ubuntu.com/problem/45d4ce4e8f26828ab6993261e8a20208ecf261b0 https://errors.ubuntu.com/problem/e60359af65f32c18a4a6ccc93fd3469b0e675844 https://errors.ubuntu.com/problem/73a93ba578f68516e680373ae324db01336e8bad which cumulatively make this the top gnome-shell crasher in impish. ** Description changed: + https://errors.ubuntu.com/problem/45d4ce4e8f26828ab6993261e8a20208ecf261b0 + https://errors.ubuntu.com/problem/e60359af65f32c18a4a6ccc93fd3469b0e675844 + https://errors.ubuntu.com/problem/73a93ba578f68516e680373ae324db01336e8bad . ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 29 15:11:43 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2021-10-27 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211023) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: - LANG=nb_NO.UTF-8 - LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en - PATH=(custom, no user) - SHELL=/bin/bash - XDG_RUNTIME_DIR= + LANG=nb_NO.UTF-8 + LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en + PATH=(custom, no user) + SHELL=/bin/bash + XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 40.5-1ubuntu2 Signal: 5 SourcePackage: gnome-shell StacktraceTop: - g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 - g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 - ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 - g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 + g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 + g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 + ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 + g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_writer_default() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: ** Changed in: gnome-shell (Ubuntu) Importance: Medium => High ** Changed in: gnome-shell (Ubuntu) Status: Incomplete => 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/1949200 Title: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/45d4ce4e8f26828ab6993261e8a20208ecf261b0 https://errors.ubuntu.com/problem/e60359af65f32c18a4a6ccc93fd3469b0e675844 https://errors.ubuntu.com/problem/73a93ba578f68516e680373ae324db01336e8bad . ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 29 15:11:43 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2021-10-27 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211023) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=nb_NO.UTF-8 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 40.5-1ubuntu2 Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_writer_default() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200/+subscriptions -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe :
[Desktop-packages] [Bug 1949200] Re: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init
** Summary changed: - gnome-shell crashed with signal 5 error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init + gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init -- 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/1949200 Title: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init Status in gnome-shell package in Ubuntu: Confirmed Bug description: https://errors.ubuntu.com/problem/45d4ce4e8f26828ab6993261e8a20208ecf261b0 https://errors.ubuntu.com/problem/e60359af65f32c18a4a6ccc93fd3469b0e675844 https://errors.ubuntu.com/problem/73a93ba578f68516e680373ae324db01336e8bad . ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 29 15:11:43 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2021-10-27 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211023) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=nb_NO.UTF-8 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 40.5-1ubuntu2 Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_writer_default() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200/+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 1948617] Re: gnome-shell crashed with SIGTRAP in /usr/lib/x86_64-linux-gnu/libc.so.6+1a476
*** This bug is a duplicate of bug 1949200 *** https://bugs.launchpad.net/bugs/1949200 ** This bug has been marked a duplicate of bug 1949200 gnome-shell crashed with signal 5 error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init -- 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/1948617 Title: gnome-shell crashed with SIGTRAP in /usr/lib/x86_64-linux- gnu/libc.so.6+1a476 Status in gnome-shell package in Ubuntu: Incomplete Bug description: This is an attempt to track a common crash that is affecting impish only: https://errors.ubuntu.com/problem/e60359af65f32c18a4a6ccc93fd3469b0e675844 gnome-shell (5) /usr/lib/x86_64-linux-gnu/libc.so.6+1a476 → /usr/bin/gnome-shell+15ba → /usr/lib/x86_64-linux- gnu/libglib-2.0.so.0.6800.4+4392f → /usr/lib/x86_64-linux- gnu/libglib-2.0.so.0.6800.4+3f633 → /usr/lib/x86_64-linux- gnu/libglib-2.0.so.0.6800.4+3f833 → /usr/lib/x86_64-linux- gnu/libgtk-3.so.0.2404.26+27949f → /usr/lib/x86_64-linux- gnu/libgobject-2.0.so.0.6800.4+2d24a → /usr/lib/x86_64-linux- gnu/libgobject-2.0.so.0.6800.4+14b7d → /usr/lib/x86_64-linux- gnu/libgobject-2.0.so.0.6800.4+15b4d → /usr/lib/x86_64-linux- gnu/libgobject-2.0.so.0.6800.4+16651 → /usr/lib/x86_64-linux- gnu/libgtk-3.so.0.2404.26+58fa0 → /usr/lib/x86_64-linux- gnu/libgtk-3.so.0.2404.26+59213 → /usr/lib/x86_64-linux- gnu/libgtk-3.so.0.2404.26+5db91 → /usr/lib/x86_64-linux- gnu/libgtk-3.so.0.2404.26+32373e → /usr/lib/x86_64-linux- gnu/libmutter-8.so.0.0.0+9b0a7 Looking up the addresses by hand yields something that barely makes sense: __xpg_sigpause + 70 in section .text of /lib/x86_64-linux-gnu/libc.so.6 dump_gjs_stack_on_signal_handler + 202 in section .text of /usr/bin/gnome-shell g_option_context_get_help + 63 in section .text of /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_set_fatal_mask + 179 in section .text of /lib/x86_64-linux-gnu/libglib-2.0.so.0 msort_r + 467 in section .text of /lib/x86_64-linux-gnu/libglib-2.0.so.0 gtk_text_buffer_real_delete_range + 1263 in section .text of /lib/x86_64-linux-gnu/libgtk-3.so.0 g_value_transform + 26 in section .text of /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_with_properties + 285 in section .text of /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_set_valist + 413 in section .text of /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_get_property + 161 in section .text of /lib/x86_64-linux-gnu/libgobject-2.0.so.0 update_node + 4016 in section .text of /lib/x86_64-linux-gnu/libgtk-3.so.0 update_node + 4643 in section .text of /lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_inspector_gestures_class_intern_init + 81 in section .text of /lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_window_move + 46 in section .text of /lib/x86_64-linux-gnu/libgtk-3.so.0 meta_x11_display_new + 5399 in section .text of /lib/x86_64-linux-gnu/libmutter-8.so.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948617/+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 1942378] Re: Some programs don't display properly on Raspberry Pi 4 Model B
[Expired for mutter (Ubuntu) because there has been no activity for 60 days.] ** Changed in: mutter (Ubuntu) Status: Incomplete => Expired -- 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/1942378 Title: Some programs don't display properly on Raspberry Pi 4 Model B Status in mutter package in Ubuntu: Expired Bug description: even my activity to change the time ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: xorg 1:7.7+22ubuntu1 ProcVersionSignature: Ubuntu 5.11.0-1007.7-raspi 5.11.12 Uname: Linux 5.11.0-1007-raspi aarch64 ApportVersion: 2.20.11-0ubuntu65 Architecture: arm64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: unknown CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Wed Sep 1 16:48:36 2021 DistUpgraded: Fresh install DistroCodename: hirsute DistroVariant: ubuntu DpkgLog: ExtraDebuggingInterest: Yes, including running git bisection searches GraphicsCard: ImageMediaBuild: 20210421 Lspci-vt: -[:00]---00.0-[01]00.0 VIA Technologies, Inc. VL805 USB 3.0 Host Controller ProcEnviron: PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: coherent_pool=1M 8250.nr_uarts=0 snd_bcm2835.enable_compat_alsa=0 snd_bcm2835.enable_hdmi=1 video=HDMI-A-1:1280x1024M@60 smsc95xx.macaddr=DC:A6:32:E9:1C:96 vc_mem.mem_base=0x3eb0 vc_mem.mem_size=0x3ff0 dwc_otg.lpm_enable=0 console=tty1 root=LABEL=writable rootfstype=ext4 elevator=deadline rootwait fixrtc quiet splash SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) acpidump: version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.104-1build1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.0.1-2 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.11-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2 version.xserver-xorg-video-intel: xserver-xorg-video-intel N/A version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1942378/+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 1949413] Re: Gnome shell crashes back to login screen randomly
Thanks for the bug report. The first thing to check is whether the crash occurs without all the extensions you have installed. Please uninstall these: 'places-m...@gnome-shell-extensions.gcampax.github.com', 'coverflowalt...@palatis.blogspot.com', 'remove-dropdown- arr...@mpdeimos.com', 'user-theme@gnome-shell- extensions.gcampax.github.com', 'openweather-extens...@jenslody.de', 'cpupo...@mko-sl.de', 'apt-update-indica...@franglais125.gmail.com', 'gnome-shell-screens...@ttll.de', 'extensi...@abteil.org', 'desktop- icons@csoriano' If the crash keeps happening after that then please follow these instructions: https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment ** 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/1949413 Title: Gnome shell crashes back to login screen randomly Status in gnome-shell package in Ubuntu: Incomplete Bug description: Gnome shell crashes randomly to login screen, no error is presented in the GUI. No apparent cause that I can identify. Attached section of syslog for latest crash. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-38.42-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Nov 1 19:11:13 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-11 (1025 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949413/+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 1949352] Re: Removable drives are not handled after screen lock/unlock
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 1949352 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. ** Changed in: gnome-shell (Ubuntu) Status: New => Incomplete ** Summary changed: - Removable drives are not handled after screen lock/unlock + Removable drives are not auto-mounted after screen lock/unlock -- 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/1949352 Title: Removable drives are not auto-mounted after screen lock/unlock Status in gnome-shell package in Ubuntu: Incomplete Bug description: If I lock and then unlock the screen, and then connect a removable drive, it is not recognized by the GNOME shell. The kernel logs show the drive, I can mount it manually, but it is not mounted automatically. The logged errors are attached. I could fix the issue by modifying the source code as given in the attached patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949352/+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 1949200] Re: gnome-shell crashed with signal 5 error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init
Interesting the above attachments show the problem originating from: #29 0x7f2746b35bfe in free_sound_event (d=0x7f273808bf20) at /build/libcanberra-NELJAC/libcanberra-0.30/src/canberra-gtk-module.c:184 which is kind of similar to https://gitlab.gnome.org/GNOME/mutter/-/issues/1475 where GTK is the problem. What gnome-shell extensions are you using? ** Information type changed from Private to Public -- 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/1949200 Title: gnome-shell crashed with signal 5 error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init Status in gnome-shell package in Ubuntu: Incomplete Bug description: . ProblemType: Crash DistroRelease: Ubuntu 22.04 Package: gnome-shell 40.5-1ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-19.19-generic 5.13.14 Uname: Linux 5.13.0-19-generic x86_64 ApportVersion: 2.20.11-0ubuntu72 Architecture: amd64 CasperMD5CheckResult: pass CrashCounter: 1 CurrentDesktop: ubuntu:GNOME Date: Fri Oct 29 15:11:43 2021 DisplayManager: gdm3 ExecutablePath: /usr/bin/gnome-shell InstallationDate: Installed on 2021-10-27 (2 days ago) InstallationMedia: Ubuntu 22.04 LTS "Jammy Jellyfish" - Alpha amd64 (20211023) ProcCmdline: /usr/bin/gnome-shell ProcEnviron: LANG=nb_NO.UTF-8 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en PATH=(custom, no user) SHELL=/bin/bash XDG_RUNTIME_DIR= RelatedPackageVersions: mutter-common 40.5-1ubuntu2 Signal: 5 SourcePackage: gnome-shell StacktraceTop: g_log_writer_default () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_array () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_structured_standard () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 ?? () from /lib/x86_64-linux-gnu/libgtk-3.so.0 g_type_create_instance () from /lib/x86_64-linux-gnu/libgobject-2.0.so.0 Title: gnome-shell crashed with signal 5 in g_log_writer_default() UpgradeStatus: No upgrade log present (probably fresh install) UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo separator: To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200/+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 1949262] Re: Power Savings doesn't turn monitor off in Wayland on NUC8i5INH
If the bug is the same for Xorg and Wayland then that suggests you need a kernel fix (the 'linux' source package). Can you please try some slightly older kernels and see which was the last working version for you? https://kernel.ubuntu.com/~kernel-ppa/mainline/?C=M;O=D ** This bug is no longer a duplicate of bug 1929650 Screen doesn't turn off when using Wayland on some devices -- 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/1949262 Title: Power Savings doesn't turn monitor off in Wayland on NUC8i5INH Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: On previous versions of Ubuntu, after 5 minutes, my monitor would turn off as per settings. Since I reinstalled fresh 21.10, this is not happening. Screen becomes black and stays powered on. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 30 08:11:02 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Lexa [Radeon 540X/550X/630 / RX 640 / E9171 MCM] [1002:6987] (rev c3) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Lexa [Radeon 540X/550X/630 / RX 640 / E9171 MCM] [8086:2079] InstallationDate: Installed on 2021-10-14 (15 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 3: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Intel(R) Client Systems NUC8i5INH ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=1e81e0c8-99b9-447b-b8a2-2ebe4bf0eb88 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2021 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: INWHL357.0043.2021.0817.1957 dmi.board.name: NUC8i5INB dmi.board.vendor: Intel Corporation dmi.board.version: K29935-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrINWHL357.0043.2021.0817.1957:bd08/17/2021:br5.13:svnIntel(R)ClientSystems:pnNUC8i5INH:pvrK47340-403:skuBXNUC8i5INHPA:rvnIntelCorporation:rnNUC8i5INB:rvrK29935-402:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: IN dmi.product.name: NUC8i5INH dmi.product.sku: BXNUC8i5INHPA dmi.product.version: K47340-403 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949262/+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 1949413] [NEW] Gnome shell crashes back to login screen randomly
Public bug reported: Gnome shell crashes randomly to login screen, no error is presented in the GUI. No apparent cause that I can identify. Attached section of syslog for latest crash. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-38.42-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Nov 1 19:11:13 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-11 (1025 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug hirsute wayland-session ** Attachment added: "syslog-gnome-crash.txt" https://bugs.launchpad.net/bugs/1949413/+attachment/5537512/+files/syslog-gnome-crash.txt -- 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/1949413 Title: Gnome shell crashes back to login screen randomly Status in gnome-shell package in Ubuntu: New Bug description: Gnome shell crashes randomly to login screen, no error is presented in the GUI. No apparent cause that I can identify. Attached section of syslog for latest crash. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-shell 3.38.4-1ubuntu3~21.04.1 ProcVersionSignature: Ubuntu 5.11.0-38.42-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Mon Nov 1 19:11:13 2021 DisplayManager: gdm3 InstallationDate: Installed on 2019-01-11 (1025 days ago) InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3) ProcEnviron: TERM=xterm-256color PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_US.UTF-8 SHELL=/bin/bash RelatedPackageVersions: mutter-common 3.38.4-1ubuntu2 SourcePackage: gnome-shell UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949413/+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 1949411] Re: GJS using lots of CPU resources non stop
Right now I have in reality more files on the Desktop created either by SimpleScreenRecording or Kdenlive and if I look at the Desktop, only a previous list of files that existed on the Desktop can be seen. I cannot interact with the Desktop in any way. See the screenshot with this, too. ** Attachment added: "reality desktop files not not match the files shown on the desktop" https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1949411/+attachment/5537511/+files/2021-11-02-00%3A00%3A02_001-Workspace1.jpg -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1949411 Title: GJS using lots of CPU resources non stop Status in gjs package in Ubuntu: New Bug description: In my laptop, gjs is using lots of CPU resources (about 13% in my case) and I cannot stop it. Keeping the mouse over it, it seems to be related to the Desktop extension. I also attached a screeshot showing that. I tried Alt+F2 & r, nothing changes in this regard; I tried disabling the extension and Alt+F2 & r, nothing changes. Restart works. When this happens, the mouse cannot interact with the desktop icons. For instance, when I moved one file, it was still shown on the Desktop, although I have already moved it with Nautilus/Files. I have a theory: I use the desktop to temporary store files, also my screen recording software creates the files on the Desktop. One time, when I moved in Nautilus the file from the Desktop to my working folders, this bug was triggered. Maybe it was a coincidence, but it sure looked like that. My idea is that the extension does not properly work with other programs interacting with the desktop and it somehow crashes instead or re-scanning the files over there and paint them correctly. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gjs 1.68.4-1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Nov 1 23:50:11 2021 InstallationDate: Installed on 2021-10-14 (18 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gjs UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1949411/+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 1949411] [NEW] GJS using lots of CPU resources non stop
Public bug reported: In my laptop, gjs is using lots of CPU resources (about 13% in my case) and I cannot stop it. Keeping the mouse over it, it seems to be related to the Desktop extension. I also attached a screeshot showing that. I tried Alt+F2 & r, nothing changes in this regard; I tried disabling the extension and Alt+F2 & r, nothing changes. Restart works. When this happens, the mouse cannot interact with the desktop icons. For instance, when I moved one file, it was still shown on the Desktop, although I have already moved it with Nautilus/Files. I have a theory: I use the desktop to temporary store files, also my screen recording software creates the files on the Desktop. One time, when I moved in Nautilus the file from the Desktop to my working folders, this bug was triggered. Maybe it was a coincidence, but it sure looked like that. My idea is that the extension does not properly work with other programs interacting with the desktop and it somehow crashes instead or re-scanning the files over there and paint them correctly. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gjs 1.68.4-1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Nov 1 23:50:11 2021 InstallationDate: Installed on 2021-10-14 (18 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gjs UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: gjs (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish ** Attachment added: "desktop extension crashes and gjs uses lots of cpu" https://bugs.launchpad.net/bugs/1949411/+attachment/5537507/+files/2021-11-01-15%3A59%3A29_001-Workspace1.jpg ** Description changed: In my laptop, gjs is using lots of CPU resources (about 13% in my case) and I cannot stop it. Keeping the mouse over it, it seems to be related to the Desktop extension. I also attached a screeshot showing that. I tried Alt+F2 & r, nothing changes in this regard; I tried disabling the extension and Alt+F2 & r, nothing changes. Restart works. - When this happens, usually the mouse cannot interact with the desktop icons. For instance, when I moved one file, it was still shown on the Desktop, although I have already moved it with Nautilus/Files. + When this happens, the mouse cannot interact with the desktop icons. For instance, when I moved one file, it was still shown on the Desktop, although I have already moved it with Nautilus/Files. I have a theory: I use the desktop to temporary store files, also my screen recording software creates the files on the Desktop. One time, when I moved in Nautilus the file from the Desktop to my working folders, this bug was triggered. Maybe it was a coincidence, but it sure looked like that. My idea is that the extension does not properly work with other programs interacting with the desktop and it somehow crashes instead or re-scanning the files over there and paint them correctly. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gjs 1.68.4-1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Mon Nov 1 23:50:11 2021 InstallationDate: Installed on 2021-10-14 (18 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) SourcePackage: gjs 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 gjs in Ubuntu. https://bugs.launchpad.net/bugs/1949411 Title: GJS using lots of CPU resources non stop Status in gjs package in Ubuntu: New Bug description: In my laptop, gjs is using lots of CPU resources (about 13% in my case) and I cannot stop it. Keeping the mouse over it, it seems to be related to the Desktop extension. I also attached a screeshot showing that. I tried Alt+F2 & r, nothing changes in this regard; I tried disabling the extension and Alt+F2 & r, nothing changes. Restart works. When this happens, the mouse cannot interact with the desktop icons. For instance, when I moved one file, it was still shown on the Desktop, although I have already moved it with Nautilus/Files. I have a theory: I use the desktop to temporary store files, also my screen recording software creates the files on the Desktop. One time, when I moved in Nautilus the file from the Desktop to my working folders, this bug was triggered. Maybe it was a coincidence, but it sure looked like that. My idea is that the extension does not properly work with other
[Desktop-packages] [Bug 1929650] Re: Screen doesn't turn off when using Wayland on some devices
I added : MUTTER_DEBUG_ENABLE_ATOMIC_KMS=0 in /etc/environment and rebooted. It didn't fix the problem... -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-settings-daemon in Ubuntu. https://bugs.launchpad.net/bugs/1929650 Title: Screen doesn't turn off when using Wayland on some devices Status in Mutter: Unknown Status in gnome-settings-daemon package in Ubuntu: Confirmed Status in mutter package in Ubuntu: Confirmed Bug description: When the screen of my laptop (Thinkpad E480) is supposed to turn off (because of inactivity or when actively locking screen), the screen dims, turns off for a second and then turns back on while remaining dimmed. I can see the backlight of the screen and the cursor. This bug is only present when using a wayland-session regardless of my settings. It also happens with a fresh user account. Additionally, I tested with the 5.8 and 5.12 kernels with the same result. ProblemType: Bug DistroRelease: Ubuntu 21.04 Package: gnome-power-manager 3.32.0-2 ProcVersionSignature: Ubuntu 5.11.0-17.18-generic 5.11.12 Uname: Linux 5.11.0-17-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.1 Architecture: amd64 CasperMD5CheckResult: pass CurrentDesktop: ubuntu:GNOME Date: Wed May 26 08:13:27 2021 InstallationDate: Installed on 2021-05-24 (1 days ago) InstallationMedia: Ubuntu 21.04 "Hirsute Hippo" - Release amd64 (20210420) SourcePackage: gnome-power-manager UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1929650/+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 1949262] Re: Power Savings doesn't turn monitor off in Wayland on NUC8i5INH
*** This bug is a duplicate of bug 1929650 *** https://bugs.launchpad.net/bugs/1929650 Same thing with Ubuntu on Xorg -- 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/1949262 Title: Power Savings doesn't turn monitor off in Wayland on NUC8i5INH Status in linux package in Ubuntu: Incomplete Status in mutter package in Ubuntu: Incomplete Bug description: On previous versions of Ubuntu, after 5 minutes, my monitor would turn off as per settings. Since I reinstalled fresh 21.10, this is not happening. Screen becomes black and stays powered on. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: xorg 1:7.7+22ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 BootLog: Error: [Errno 13] Permission denied: '/var/log/boot.log' CasperMD5CheckResult: pass CompositorRunning: None CurrentDesktop: ubuntu:GNOME Date: Sat Oct 30 08:11:02 2021 DistUpgraded: Fresh install DistroCodename: impish DistroVariant: ubuntu ExtraDebuggingInterest: Yes GraphicsCard: Advanced Micro Devices, Inc. [AMD/ATI] Lexa [Radeon 540X/550X/630 / RX 640 / E9171 MCM] [1002:6987] (rev c3) (prog-if 00 [VGA controller]) Subsystem: Intel Corporation Lexa [Radeon 540X/550X/630 / RX 640 / E9171 MCM] [8086:2079] InstallationDate: Installed on 2021-10-14 (15 days ago) InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012) Lsusb: Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub Bus 001 Device 002: ID 046d:c534 Logitech, Inc. Unifying Receiver Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub Lsusb-t: /: Bus 02.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/6p, 1M /: Bus 01.Port 1: Dev 1, Class=root_hub, Driver=xhci_hcd/12p, 480M |__ Port 3: Dev 2, If 0, Class=Human Interface Device, Driver=usbhid, 12M |__ Port 3: Dev 2, If 1, Class=Human Interface Device, Driver=usbhid, 12M MachineType: Intel(R) Client Systems NUC8i5INH ProcEnviron: LANGUAGE=en_CA:en PATH=(custom, no user) XDG_RUNTIME_DIR= LANG=en_CA.UTF-8 SHELL=/bin/bash ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.13.0-20-generic root=UUID=1e81e0c8-99b9-447b-b8a2-2ebe4bf0eb88 ro quiet splash vt.handoff=7 SourcePackage: xorg Symptom: display UpgradeStatus: No upgrade log present (probably fresh install) dmi.bios.date: 08/17/2021 dmi.bios.release: 5.13 dmi.bios.vendor: Intel Corp. dmi.bios.version: INWHL357.0043.2021.0817.1957 dmi.board.name: NUC8i5INB dmi.board.vendor: Intel Corporation dmi.board.version: K29935-402 dmi.chassis.type: 35 dmi.chassis.vendor: Intel Corporation dmi.chassis.version: 2.0 dmi.modalias: dmi:bvnIntelCorp.:bvrINWHL357.0043.2021.0817.1957:bd08/17/2021:br5.13:svnIntel(R)ClientSystems:pnNUC8i5INH:pvrK47340-403:skuBXNUC8i5INHPA:rvnIntelCorporation:rnNUC8i5INB:rvrK29935-402:cvnIntelCorporation:ct35:cvr2.0: dmi.product.family: IN dmi.product.name: NUC8i5INH dmi.product.sku: BXNUC8i5INHPA dmi.product.version: K47340-403 dmi.sys.vendor: Intel(R) Client Systems version.compiz: compiz N/A version.libdrm2: libdrm2 2.4.107-8ubuntu1 version.libgl1-mesa-dri: libgl1-mesa-dri 21.2.2-1ubuntu1 version.libgl1-mesa-glx: libgl1-mesa-glx N/A version.xserver-xorg-core: xserver-xorg-core 2:1.20.13-1ubuntu1 version.xserver-xorg-input-evdev: xserver-xorg-input-evdev N/A version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:19.1.0-2build1 version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.99.917+git20200714-1ubuntu2 version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.17-1build1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949262/+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 1843588] Update Released
The verification of the Stable Release Update for nautilus has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1843588 Title: Nautilus doesn't copy filenames for paste to other programs anymore Status in Nautilus: New Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Focal: Fix Released Bug description: [Impact] * One of the upstream changes changed behavior of clipboard copying files/directories from nautilus to applications accepting text only (e.g. gnome-terminal). In such case the pasted input is prefixed with: x-special/nautilus-clipboard copy file:// This was not the case in earlier releases and this change has been reverted in later upstream releases. Reverting the problematic commit will fix the usecase reported in this bug (and all applications where copying from Nautilus and pasting the data into a text-based input makes sense), but will break copying to/from Desktop Icons extension. I recommend reporting the Desktop Icons extension issue (present already in every later Ubuntu release) in a separate bug and track the fix there. [Test Plan] 1. Open nautilus. 2. Right-click on any file or directory and select 'Copy' from the context menu. 3. Open gnome-terminal and right-click paste the contents of the clipboard. Expected result: path of the file/directory is pasted in the terminal. Actual result: pasted input is prefixed with "x-special/nautilus-clipboard copy file://" [Where problems could occur] * There are some workarounds listed in the upstream bug so fixing the root cause may break environments with those workarounds in place. * Reverting this change also limits functionality of the desktop icons extension shipped with Ubuntu. Namely: before the new clipboard API is used in desktop-icons (merge requests [1] and [2]) copying and pasting to/from the desktop extension to a nautilus will not be possible via keyboard shortcuts or context menu (dragging and dropping will remain to work). [1] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/186 [2] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/195 [Other Info] Original bug description: Until Ubuntu 18.10 Nautilus does copy all selected filenames in simple Text format and this way you cold paste the selected files as a list to other programs: for example into the texteditor gedit. This was a very useful function if you have, for example, to upload a file to webmail or other web-service. You cold copy the file within nautilus and paste it directliy to the selection dialog or webfield to upload the file. Or if you wanted a simple List of all your files in a folder you where able to select all files with nautilus, copy and paste into gedit. This is not possible anymore. The output of natilus looks now like this: x-special/nautilus-clipboard copy file:///home//Schreibtisch/new%20document.txt Until Ubuntu 18.10 this looks like this: /home//Schreibtisch/new document.txt Steps to reproduce: 1. Select files with nautilus 2. Press Ctrl+C 3. open gedit 4. press Ctrl+V ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.1-0ubuntu0.19.04.0 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 15:06:14 2019 ExecutablePath: /usr/bin/nautilus SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1843588/+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 1843588] Re: Nautilus doesn't copy filenames for paste to other programs anymore
This bug was fixed in the package nautilus - 1:3.36.3-0ubuntu1.20.04.1 --- nautilus (1:3.36.3-0ubuntu1.20.04.1) focal; urgency=medium * d/p/lp1843588-Revert-clipboard-Use-text-based-clipboard-only.patch: - restore copying filenames functionality (LP: #1843588) -- Dariusz Gadomski Tue, 19 Oct 2021 17:02:02 +0200 ** Changed in: nautilus (Ubuntu Focal) Status: Fix Committed => Fix Released -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1843588 Title: Nautilus doesn't copy filenames for paste to other programs anymore Status in Nautilus: New Status in nautilus package in Ubuntu: Fix Released Status in nautilus source package in Focal: Fix Released Bug description: [Impact] * One of the upstream changes changed behavior of clipboard copying files/directories from nautilus to applications accepting text only (e.g. gnome-terminal). In such case the pasted input is prefixed with: x-special/nautilus-clipboard copy file:// This was not the case in earlier releases and this change has been reverted in later upstream releases. Reverting the problematic commit will fix the usecase reported in this bug (and all applications where copying from Nautilus and pasting the data into a text-based input makes sense), but will break copying to/from Desktop Icons extension. I recommend reporting the Desktop Icons extension issue (present already in every later Ubuntu release) in a separate bug and track the fix there. [Test Plan] 1. Open nautilus. 2. Right-click on any file or directory and select 'Copy' from the context menu. 3. Open gnome-terminal and right-click paste the contents of the clipboard. Expected result: path of the file/directory is pasted in the terminal. Actual result: pasted input is prefixed with "x-special/nautilus-clipboard copy file://" [Where problems could occur] * There are some workarounds listed in the upstream bug so fixing the root cause may break environments with those workarounds in place. * Reverting this change also limits functionality of the desktop icons extension shipped with Ubuntu. Namely: before the new clipboard API is used in desktop-icons (merge requests [1] and [2]) copying and pasting to/from the desktop extension to a nautilus will not be possible via keyboard shortcuts or context menu (dragging and dropping will remain to work). [1] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/186 [2] https://gitlab.gnome.org/World/ShellExtensions/desktop-icons/-/merge_requests/195 [Other Info] Original bug description: Until Ubuntu 18.10 Nautilus does copy all selected filenames in simple Text format and this way you cold paste the selected files as a list to other programs: for example into the texteditor gedit. This was a very useful function if you have, for example, to upload a file to webmail or other web-service. You cold copy the file within nautilus and paste it directliy to the selection dialog or webfield to upload the file. Or if you wanted a simple List of all your files in a folder you where able to select all files with nautilus, copy and paste into gedit. This is not possible anymore. The output of natilus looks now like this: x-special/nautilus-clipboard copy file:///home//Schreibtisch/new%20document.txt Until Ubuntu 18.10 this looks like this: /home//Schreibtisch/new document.txt Steps to reproduce: 1. Select files with nautilus 2. Press Ctrl+C 3. open gedit 4. press Ctrl+V ProblemType: Bug DistroRelease: Ubuntu 19.04 Package: nautilus 1:3.32.1-0ubuntu0.19.04.0 ProcVersionSignature: Ubuntu 5.0.0-27.28-generic 5.0.21 Uname: Linux 5.0.0-27-generic x86_64 ApportVersion: 2.20.10-0ubuntu27.1 Architecture: amd64 CurrentDesktop: ubuntu:GNOME Date: Wed Sep 11 15:06:14 2019 ExecutablePath: /usr/bin/nautilus SourcePackage: nautilus UpgradeStatus: No upgrade log present (probably fresh install) usr_lib_nautilus: To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1843588/+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 1949105] Re: executable text activation does not work
For example, I want to run the idea.sh file with a double click. I change it to an executable file but when I double click it, the Gedit opens this file as a text file. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1949105 Title: executable text activation does not work Status in nautilus package in Ubuntu: Incomplete Bug description: I upgraded my Ubuntu from 21.04 to 21.10. The executable text activation does not work in 21.10. ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: nautilus 1:40.2-1ubuntu1 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown CurrentDesktop: ubuntu:GNOME Date: Thu Oct 28 20:23:12 2021 InstallationDate: Installed on 2020-10-07 (385 days ago) InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423) SourcePackage: nautilus UpgradeStatus: Upgraded to impish on 2021-10-14 (13 days ago) usr_lib_nautilus: evince40.4-2 file-roller 3.40.0-2 nautilus-extension-gnome-terminal 3.38.1-1ubuntu2 nautilus-share0.7.3-2ubuntu4 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1949105/+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 1949352] Re: Removable drives are not handled after screen lock/unlock
** Description changed: If I lock and then unlock the screen, and then connect a removable drive, it is not recognized by the GNOME shell. The kernel logs show the drive, I can mount it manually, but it is not mounted automatically. The logged errors are attached. - I could fix the issue by modify the source code as given in the attached - patch. + I could fix the issue by modifying the source code as given in the + attached patch. -- 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/1949352 Title: Removable drives are not handled after screen lock/unlock Status in gnome-shell package in Ubuntu: New Bug description: If I lock and then unlock the screen, and then connect a removable drive, it is not recognized by the GNOME shell. The kernel logs show the drive, I can mount it manually, but it is not mounted automatically. The logged errors are attached. I could fix the issue by modifying the source code as given in the attached patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949352/+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 1949291] Re: LibreOffice has started displaying a donation nag
** Tags added: rls-jj-incoming -- 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/1949291 Title: LibreOffice has started displaying a donation nag Status in LibreOffice: Confirmed Status in libreoffice package in Ubuntu: New Bug description: I just opened up a spreadsheet (technically a CSV file, but who's counting), to discover LibreOffice displaying an eye-catching blue "Your donations support our worldwide community." banner just below the toolbars and about a toolbar and a half tall. This irritating nag is apparently supposed to display every 90 to 180 days with no in-application means to disable it permanently, and there's apparently also a "Help us make LibreOffice even better!" banner that can appear too. According to this blog post... https://www.remembertheusers.com/2019/11/0580-libreoffice-nag- notices.html ...it is not responsive to configuration overrides within the user profile and the only apparent solution that doesn't require patching the source and rebuilding is to create a file containing the following markup in `$BASEDIR/share/registry` (`/usr/lib/libreoffice/share/registry` as installed by the Ubuntu package): http://www.w3.org/2001/XMLSchema; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance; xmlns:oor="http://openoffice.org/2001/registry;> http://openoffice.org/2004/installation; oor:name="Setup" oor:package="org.openoffice"> 0 0 Regardless of how it's achieved, I think it's tasteless, irritating, and probably doesn't give a very good image to any office customers Ubuntu may have downstream for random employees to be receiving nag banners like that in IT-installed software. Please consider patching it out or otherwise ensuring it never triggers in distro-provided builds of LibreOffice. ProblemType: Bug DistroRelease: Ubuntu 20.04 Package: libreoffice 1:6.4.7-0ubuntu0.20.04.1 ProcVersionSignature: Ubuntu 5.11.0-37.41~20.04.2-generic 5.11.22 Uname: Linux 5.11.0-37-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu27.21 Architecture: amd64 CasperMD5CheckResult: skip CurrentDesktop: KDE Date: Sun Oct 31 04:32:03 2021 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/1949291/+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 1949373] Re: Unable to select with which user to authenticate in gnome-authentication-agent-1
** Package changed: ubuntu => policykit-1-gnome (Ubuntu)
** Tags added: bionic
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to policykit-1-gnome in Ubuntu.
https://bugs.launchpad.net/bugs/1949373
Title:
Unable to select with which user to authenticate in gnome-
authentication-agent-1
Status in policykit-1-gnome package in Ubuntu:
New
Bug description:
Hello,
Linking from the question I originally opened.
https://answers.launchpad.net/ubuntu/+question/698856
Apparently in the GUI it will only show a single sudo user to authenticate
with, while pkexec will list all available sudoers.
This is for 18.04.
--QUOTE--
There are multiple users in the sudo group.
One user is bob and another user is tom. Both bob and tom are admins. Both
are in the sudo group.
User kate is not an admin.
When kate tries to change the IP address, via the UI, she gets a prompt
saying "System policy prevents modification of network settings for all users"
and asks for bob's password in order to authenticate.
The problem is that kate does not have bob's password, she only has tom's
password. However, in the ui, the gnome-authentication-agent-1, provides no way
of changing bob to tom.
If kate tries to run a command via pkexec, say whoami, she does get to
choose whether to authenticate as bob or tom :
AUTHENTICATION FOR org.freedesktop.policykit.exec ===
Authentication is needed to run `/usr/bin/whoami` as the super user
Multiple identities can be used for authentication:
1. bob
2. tom
Choose identity to authenticate as (1-2):
--UNQUOTE--
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/policykit-1-gnome/+bug/1949373/+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 1949373] [NEW] Unable to select with which user to authenticate in gnome-authentication-agent-1
You have been subscribed to a public bug: Hello, Linking from the question I originally opened. https://answers.launchpad.net/ubuntu/+question/698856 Apparently in the GUI it will only show a single sudo user to authenticate with, while pkexec will list all available sudoers. This is for 18.04. --QUOTE-- There are multiple users in the sudo group. One user is bob and another user is tom. Both bob and tom are admins. Both are in the sudo group. User kate is not an admin. When kate tries to change the IP address, via the UI, she gets a prompt saying "System policy prevents modification of network settings for all users" and asks for bob's password in order to authenticate. The problem is that kate does not have bob's password, she only has tom's password. However, in the ui, the gnome-authentication-agent-1, provides no way of changing bob to tom. If kate tries to run a command via pkexec, say whoami, she does get to choose whether to authenticate as bob or tom : AUTHENTICATION FOR org.freedesktop.policykit.exec === Authentication is needed to run `/usr/bin/whoami` as the super user Multiple identities can be used for authentication: 1. bob 2. tom Choose identity to authenticate as (1-2): --UNQUOTE-- ** Affects: policykit-1-gnome (Ubuntu) Importance: Undecided Status: New -- Unable to select with which user to authenticate in gnome-authentication-agent-1 https://bugs.launchpad.net/bugs/1949373 You received this bug notification because you are a member of Desktop Packages, which is subscribed to policykit-1-gnome in Ubuntu. -- Mailing list: https://launchpad.net/~desktop-packages Post to : desktop-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~desktop-packages More help : https://help.launchpad.net/ListHelp
[Desktop-packages] [Bug 1938442] Re: Wrong permissions on ~/.hplip/.gnupg
** Changed in: hplip (Ubuntu) Milestone: None => impish-updates ** Changed in: hplip (Ubuntu) Milestone: impish-updates => focal-updates ** Also affects: hplip (Ubuntu Jammy) Importance: Undecided Assignee: Till Kamppeter (till-kamppeter) Status: New ** Also affects: hplip (Ubuntu Hirsute) Importance: Undecided Status: New ** Also affects: hplip (Ubuntu Bionic) Importance: Undecided Status: New ** Also affects: hplip (Ubuntu Impish) Importance: Undecided Status: New ** Also affects: hplip (Ubuntu Focal) Importance: Undecided Status: New ** Changed in: hplip (Ubuntu Jammy) Milestone: focal-updates => None -- 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/1938442 Title: Wrong permissions on ~/.hplip/.gnupg Status in HPLIP: New Status in hplip package in Ubuntu: New Status in hplip source package in Bionic: New Status in hplip source package in Focal: New Status in hplip source package in Hirsute: New Status in hplip source package in Impish: New Status in hplip source package in Jammy: New Status in Fedora: Unknown Bug description: [Impact] * The directory ~/.hplip/.gnupg is readable by non-root users * This directory contains only public keys, but should still have the permissions changed to 700 for privacy reasons [Test Case] * Install hplip and run `hp-plugin -i` * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwxr-xr-x * rm -rf ~/.hplip and install hplip from -proposed * run `hp-plugin -i` again * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwx-- [Regression Potential] * Because of file permissions becoming more restrictive, it is possible that some other hplip binaries would fail to read the .gnupg directory * To ensure this isn't the case, testing should be done on different hplip use-cases to ensure they still function properly [Original Description] Hi, we have a report in Fedora - https://bugzilla.redhat.com/show_bug.cgi?id=1985251 - where Sergey found out that ~/.hplip/.gnupg directory has permissions 755 instead of 700. Perms 700 prevent accessing the dir by other users, because the dir can contain private keys. However, .gnupg dir contains only a public key used in GPG verification of HP plugin, so the matter isn't that critical, but it is good to have it fixed. The patch is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1938442/+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 1938442] Re: Wrong permissions on ~/.hplip/.gnupg
Reupload to fix s/hplib/hplip/ typo in changelog ** Patch added: "Bionic debdiff" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1938442/+attachment/5537488/+files/lp1938442_bionic.debdiff -- 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/1938442 Title: Wrong permissions on ~/.hplip/.gnupg Status in HPLIP: New Status in hplip package in Ubuntu: New Status in hplip source package in Bionic: New Status in hplip source package in Focal: New Status in hplip source package in Hirsute: New Status in hplip source package in Impish: New Status in hplip source package in Jammy: New Status in Fedora: Unknown Bug description: [Impact] * The directory ~/.hplip/.gnupg is readable by non-root users * This directory contains only public keys, but should still have the permissions changed to 700 for privacy reasons [Test Case] * Install hplip and run `hp-plugin -i` * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwxr-xr-x * rm -rf ~/.hplip and install hplip from -proposed * run `hp-plugin -i` again * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwx-- [Regression Potential] * Because of file permissions becoming more restrictive, it is possible that some other hplip binaries would fail to read the .gnupg directory * To ensure this isn't the case, testing should be done on different hplip use-cases to ensure they still function properly [Original Description] Hi, we have a report in Fedora - https://bugzilla.redhat.com/show_bug.cgi?id=1985251 - where Sergey found out that ~/.hplip/.gnupg directory has permissions 755 instead of 700. Perms 700 prevent accessing the dir by other users, because the dir can contain private keys. However, .gnupg dir contains only a public key used in GPG verification of HP plugin, so the matter isn't that critical, but it is good to have it fixed. The patch is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1938442/+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 1938442] Re: Wrong permissions on ~/.hplip/.gnupg
Reupload to fix s/hplib/hplip/ typo in changelog ** Patch added: "Impish debdiff" https://bugs.launchpad.net/ubuntu/+source/hplip/+bug/1938442/+attachment/5537487/+files/lp1938442_impish.debdiff -- 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/1938442 Title: Wrong permissions on ~/.hplip/.gnupg Status in HPLIP: New Status in hplip package in Ubuntu: New Status in hplip source package in Bionic: New Status in hplip source package in Focal: New Status in hplip source package in Hirsute: New Status in hplip source package in Impish: New Status in hplip source package in Jammy: New Status in Fedora: Unknown Bug description: [Impact] * The directory ~/.hplip/.gnupg is readable by non-root users * This directory contains only public keys, but should still have the permissions changed to 700 for privacy reasons [Test Case] * Install hplip and run `hp-plugin -i` * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwxr-xr-x * rm -rf ~/.hplip and install hplip from -proposed * run `hp-plugin -i` again * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwx-- [Regression Potential] * Because of file permissions becoming more restrictive, it is possible that some other hplip binaries would fail to read the .gnupg directory * To ensure this isn't the case, testing should be done on different hplip use-cases to ensure they still function properly [Original Description] Hi, we have a report in Fedora - https://bugzilla.redhat.com/show_bug.cgi?id=1985251 - where Sergey found out that ~/.hplip/.gnupg directory has permissions 755 instead of 700. Perms 700 prevent accessing the dir by other users, because the dir can contain private keys. However, .gnupg dir contains only a public key used in GPG verification of HP plugin, so the matter isn't that critical, but it is good to have it fixed. The patch is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1938442/+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 1949364] [NEW] package ubuntu-drivers-common 1:0.9.0~0.21.04.1 failed to install/upgrade: installed ubuntu-drivers-common package post-installation script subprocess returned e
Public bug reported: I was just updating ubuntu via terminal ProblemType: Package DistroRelease: Ubuntu 21.04 Package: ubuntu-drivers-common 1:0.9.0~0.21.04.1 ProcVersionSignature: Ubuntu 5.11.0-38.42-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Nov 1 16:00:39 2021 DpkgHistoryLog: Start-Date: 2021-11-01 15:59:43 Commandline: apt --fix-broken install Requested-By: red (1000) Upgrade: libjson-glib-1.0-0:amd64 (1.4.4-2ubuntu2, 1.6.2-1) ErrorMessage: installed ubuntu-drivers-common package post-installation script subprocess returned error exit status 139 InstallationDate: Installed on 2021-10-26 (5 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.4ubuntu0.1 SourcePackage: ubuntu-drivers-common Title: package ubuntu-drivers-common 1:0.9.0~0.21.04.1 failed to install/upgrade: installed ubuntu-drivers-common package post-installation script subprocess returned error exit status 139 UpgradeStatus: Upgraded to hirsute on 2021-11-01 (0 days ago) ** Affects: ubuntu-drivers-common (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package hirsute -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to ubuntu-drivers-common in Ubuntu. https://bugs.launchpad.net/bugs/1949364 Title: package ubuntu-drivers-common 1:0.9.0~0.21.04.1 failed to install/upgrade: installed ubuntu-drivers-common package post- installation script subprocess returned error exit status 139 Status in ubuntu-drivers-common package in Ubuntu: New Bug description: I was just updating ubuntu via terminal ProblemType: Package DistroRelease: Ubuntu 21.04 Package: ubuntu-drivers-common 1:0.9.0~0.21.04.1 ProcVersionSignature: Ubuntu 5.11.0-38.42-generic 5.11.22 Uname: Linux 5.11.0-38-generic x86_64 ApportVersion: 2.20.11-0ubuntu65.4 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Nov 1 16:00:39 2021 DpkgHistoryLog: Start-Date: 2021-11-01 15:59:43 Commandline: apt --fix-broken install Requested-By: red (1000) Upgrade: libjson-glib-1.0-0:amd64 (1.4.4-2ubuntu2, 1.6.2-1) ErrorMessage: installed ubuntu-drivers-common package post-installation script subprocess returned error exit status 139 InstallationDate: Installed on 2021-10-26 (5 days ago) InstallationMedia: Ubuntu 20.04.3 LTS "Focal Fossa" - Release amd64 (20210819) Python3Details: /usr/bin/python3.9, Python 3.9.5, python3-minimal, 3.9.4-1 PythonDetails: N/A RebootRequiredPkgs: Error: path contained symlinks. RelatedPackageVersions: dpkg 1.20.9ubuntu1 apt 2.2.4ubuntu0.1 SourcePackage: ubuntu-drivers-common Title: package ubuntu-drivers-common 1:0.9.0~0.21.04.1 failed to install/upgrade: installed ubuntu-drivers-common package post-installation script subprocess returned error exit status 139 UpgradeStatus: Upgraded to hirsute on 2021-11-01 (0 days ago) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/ubuntu-drivers-common/+bug/1949364/+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 1949363] [NEW] gdm segfault when changing session between users
Public bug reported: Can't switch user session without crashing the hole system. Forced to reboot as gdm crash with segfault ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gdm3 41~rc-0ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Nov 1 14:09:49 2021 InstallationDate: Installed on 2018-01-01 (1399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221) SourcePackage: gdm3 UpgradeStatus: Upgraded to impish on 2019-10-19 (743 days ago) mtime.conffile..etc.gdm3.custom.conf: 2018-11-01T14:01:52.647430 ** Affects: gdm3 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-bug impish -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1949363 Title: gdm segfault when changing session between users Status in gdm3 package in Ubuntu: New Bug description: Can't switch user session without crashing the hole system. Forced to reboot as gdm crash with segfault ProblemType: Bug DistroRelease: Ubuntu 21.10 Package: gdm3 41~rc-0ubuntu2 ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14 Uname: Linux 5.13.0-20-generic x86_64 NonfreeKernelModules: nvidia_modeset nvidia ApportVersion: 2.20.11-0ubuntu71 Architecture: amd64 CasperMD5CheckResult: unknown Date: Mon Nov 1 14:09:49 2021 InstallationDate: Installed on 2018-01-01 (1399 days ago) InstallationMedia: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20171221) SourcePackage: gdm3 UpgradeStatus: Upgraded to impish on 2019-10-19 (743 days ago) mtime.conffile..etc.gdm3.custom.conf: 2018-11-01T14:01:52.647430 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1949363/+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 1949352] Re: Removable drives are not handled after screen lock/unlock
The attachment "The patch with my changes" seems to be a patch. If it isn't, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are a member of the ~ubuntu-reviewers, unsubscribe the team. [This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issues please contact him.] ** Tags added: patch -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1949352 Title: Removable drives are not handled after screen lock/unlock Status in gnome-shell package in Ubuntu: New Bug description: If I lock and then unlock the screen, and then connect a removable drive, it is not recognized by the GNOME shell. The kernel logs show the drive, I can mount it manually, but it is not mounted automatically. The logged errors are attached. I could fix the issue by modify the source code as given in the attached patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949352/+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 1949355] Re: unity-tweak-tool
** Package changed: evince (Ubuntu) => unity-tweak-tool (Ubuntu)
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1949355
Title:
unity-tweak-tool
Status in unity-tweak-tool package in Ubuntu:
New
Bug description:
Hello
it seems to me that the installation of unity-tweak-tool is going wrong
Paramétrage de unity-tweak-tool (0.0.7+-0ubuntu9) ...
/usr/lib/python3/dist-packages/UnityTweakTool/__init__.py:136: SyntaxWarning:
"is not" with a literal. Did you mean "!="?
assert id is not -1
/usr/lib/python3/dist-packages/UnityTweakTool/section/spaghetti/theme.py:155:
SyntaxWarning: "is" with a literal. Did you mean "=="?
self.ui['check_cursor_size'].set_active(True if
gsettings.interface.get_int('cursor-size') is 48 else False)
a@a:~$
thank you
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: evince 40.4-2
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 1 12:33:30 2021
InstallationDate: Installed on 2021-10-24 (8 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
KernLog:
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: evince
UpgradeStatus: Upgraded to jammy on 2021-10-29 (2 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-tweak-tool/+bug/1949355/+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 1949355] [NEW] unity-tweak-tool
Public bug reported:
Hello
it seems to me that the installation of unity-tweak-tool is going wrong
Paramétrage de unity-tweak-tool (0.0.7+-0ubuntu9) ...
/usr/lib/python3/dist-packages/UnityTweakTool/__init__.py:136: SyntaxWarning:
"is not" with a literal. Did you mean "!="?
assert id is not -1
/usr/lib/python3/dist-packages/UnityTweakTool/section/spaghetti/theme.py:155:
SyntaxWarning: "is" with a literal. Did you mean "=="?
self.ui['check_cursor_size'].set_active(True if
gsettings.interface.get_int('cursor-size') is 48 else False)
a@a:~$
thank you
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: evince 40.4-2
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 1 12:33:30 2021
InstallationDate: Installed on 2021-10-24 (8 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
KernLog:
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: evince
UpgradeStatus: Upgraded to jammy on 2021-10-29 (2 days ago)
** Affects: unity-tweak-tool (Ubuntu)
Importance: Undecided
Status: New
** Tags: amd64 apport-bug jammy wayland-session
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1949355
Title:
unity-tweak-tool
Status in unity-tweak-tool package in Ubuntu:
New
Bug description:
Hello
it seems to me that the installation of unity-tweak-tool is going wrong
Paramétrage de unity-tweak-tool (0.0.7+-0ubuntu9) ...
/usr/lib/python3/dist-packages/UnityTweakTool/__init__.py:136: SyntaxWarning:
"is not" with a literal. Did you mean "!="?
assert id is not -1
/usr/lib/python3/dist-packages/UnityTweakTool/section/spaghetti/theme.py:155:
SyntaxWarning: "is" with a literal. Did you mean "=="?
self.ui['check_cursor_size'].set_active(True if
gsettings.interface.get_int('cursor-size') is 48 else False)
a@a:~$
thank you
ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: evince 40.4-2
ProcVersionSignature: Ubuntu 5.13.0-20.20-generic 5.13.14
Uname: Linux 5.13.0-20-generic x86_64
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: ubuntu:GNOME
Date: Mon Nov 1 12:33:30 2021
InstallationDate: Installed on 2021-10-24 (8 days ago)
InstallationMedia: Ubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
KernLog:
ProcEnviron:
TERM=xterm-256color
PATH=(custom, no user)
XDG_RUNTIME_DIR=
LANG=fr_FR.UTF-8
SHELL=/bin/bash
SourcePackage: evince
UpgradeStatus: Upgraded to jammy on 2021-10-29 (2 days ago)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-tweak-tool/+bug/1949355/+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 1949352] Re: Removable drives are not handled after screen lock/unlock
** Patch added: "The patch with my changes" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949352/+attachment/5537456/+files/automount.patch -- 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/1949352 Title: Removable drives are not handled after screen lock/unlock Status in gnome-shell package in Ubuntu: New Bug description: If I lock and then unlock the screen, and then connect a removable drive, it is not recognized by the GNOME shell. The kernel logs show the drive, I can mount it manually, but it is not mounted automatically. The logged errors are attached. I could fix the issue by modify the source code as given in the attached patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949352/+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 1949352] [NEW] Removable drives are not handled after screen lock/unlock
Public bug reported: If I lock and then unlock the screen, and then connect a removable drive, it is not recognized by the GNOME shell. The kernel logs show the drive, I can mount it manually, but it is not mounted automatically. The logged errors are attached. I could fix the issue by modify the source code as given in the attached patch. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Attachment added: "Error log" https://bugs.launchpad.net/bugs/1949352/+attachment/5537455/+files/errorlog.txt -- 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/1949352 Title: Removable drives are not handled after screen lock/unlock Status in gnome-shell package in Ubuntu: New Bug description: If I lock and then unlock the screen, and then connect a removable drive, it is not recognized by the GNOME shell. The kernel logs show the drive, I can mount it manually, but it is not mounted automatically. The logged errors are attached. I could fix the issue by modify the source code as given in the attached patch. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949352/+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 1938442] Re: Wrong permissions on ~/.hplip/.gnupg
The public GPG keys here are only to check the integrity of a downloaded proprietary plugin, to prevent that someone could make HPLIP download and install a fake, malware plugin. HPLIP does not load such a key as long as the user does not try to download the plugin and HPLIP dos also not do any other downloads from the internet. The keys are actually only HP's public keys. No keys of the user are stored under ~/.hplip. So wrong permissions should be harmless here. So what you should do for testing is whether you can still download the proprietary plugin with the stricter permissions (with your patch). If it still works, the stricter permissions could be generally used, but as the keys are only public keys from HP, the stricter permissions are not actually needed. If my assumptions are correct, I do not see a security issue here. Can someone from HP tell whether I am right? -- 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/1938442 Title: Wrong permissions on ~/.hplip/.gnupg Status in HPLIP: New Status in hplip package in Ubuntu: New Status in Fedora: Unknown Bug description: [Impact] * The directory ~/.hplip/.gnupg is readable by non-root users * This directory contains only public keys, but should still have the permissions changed to 700 for privacy reasons [Test Case] * Install hplip and run `hp-plugin -i` * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwxr-xr-x * rm -rf ~/.hplip and install hplip from -proposed * run `hp-plugin -i` again * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwx-- [Regression Potential] * Because of file permissions becoming more restrictive, it is possible that some other hplip binaries would fail to read the .gnupg directory * To ensure this isn't the case, testing should be done on different hplip use-cases to ensure they still function properly [Original Description] Hi, we have a report in Fedora - https://bugzilla.redhat.com/show_bug.cgi?id=1985251 - where Sergey found out that ~/.hplip/.gnupg directory has permissions 755 instead of 700. Perms 700 prevent accessing the dir by other users, because the dir can contain private keys. However, .gnupg dir contains only a public key used in GPG verification of HP plugin, so the matter isn't that critical, but it is good to have it fixed. The patch is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1938442/+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 1938442] Re: Wrong permissions on ~/.hplip/.gnupg
Hey Till, could you review the sponsoring request? ** Changed in: hplip (Ubuntu) Assignee: (unassigned) => Till Kamppeter (till-kamppeter) -- 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/1938442 Title: Wrong permissions on ~/.hplip/.gnupg Status in HPLIP: New Status in hplip package in Ubuntu: New Status in Fedora: Unknown Bug description: [Impact] * The directory ~/.hplip/.gnupg is readable by non-root users * This directory contains only public keys, but should still have the permissions changed to 700 for privacy reasons [Test Case] * Install hplip and run `hp-plugin -i` * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwxr-xr-x * rm -rf ~/.hplip and install hplip from -proposed * run `hp-plugin -i` again * ls -al ~/.hplip and observe that ~/.hplip/.gnupg has perms drwx-- [Regression Potential] * Because of file permissions becoming more restrictive, it is possible that some other hplip binaries would fail to read the .gnupg directory * To ensure this isn't the case, testing should be done on different hplip use-cases to ensure they still function properly [Original Description] Hi, we have a report in Fedora - https://bugzilla.redhat.com/show_bug.cgi?id=1985251 - where Sergey found out that ~/.hplip/.gnupg directory has permissions 755 instead of 700. Perms 700 prevent accessing the dir by other users, because the dir can contain private keys. However, .gnupg dir contains only a public key used in GPG verification of HP plugin, so the matter isn't that critical, but it is good to have it fixed. The patch is attached. To manage notifications about this bug go to: https://bugs.launchpad.net/hplip/+bug/1938442/+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 1949299] Re: gtk4-broadwayd missing in libgtk-4-bin 4.4 (impish and jammy)
Thanks, the package is coming directly from Debian so it needs to be sorted out on that side probably ** Changed in: gtk4 (Ubuntu) Importance: Undecided => Low ** Changed in: gtk4 (Ubuntu) Status: New => Triaged -- 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/1949299 Title: gtk4-broadwayd missing in libgtk-4-bin 4.4 (impish and jammy) Status in gtk4 package in Ubuntu: Triaged Status in gtk4 package in Debian: New Bug description: The binary (gtk4-broadwayd) and also the devel files for gtk4 broadway are missing in the 4.4 packages for impish and jammy. They are in the hirsute package (4.0) though. For example this would be needed for Cambalache: WARNING:cambalache.cmb_view gtk4-broadwayd not found, Gtk 4 workspace wont work. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gtk4/+bug/1949299/+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 1949312] Re: Transmission icon Ubuntu MATE doesn´t fit overall icontheme
** Changed in: transmission (Ubuntu) Importance: Undecided => Low -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1949312 Title: Transmission icon Ubuntu MATE doesn´t fit overall icontheme Status in Ubuntu MATE: New Status in transmission package in Ubuntu: New Status in ubuntu-mate-artwork package in Ubuntu: New Bug description: When using the Yaru icon theme in Ubuntu MATE and adding Transmission to the indicator applet, the Transmission icons does not fit the other icons in the indicator. (The Transmission icon has color, while the others have not) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1949312/+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 1949340] Re: Saving downloads or pages is difficult because of unfocused file chooser dialog
Upstream bug-report is at https://bugs.chromium.org/p/chromium/issues/detail?id=1265366 . -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: Saving downloads or pages is difficult because of unfocused file chooser dialog Status in chromium-browser package in Ubuntu: New Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1949340/+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 1949341] [NEW] Fails to boot recent versions - nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build
Public bug reported: Fails to boot recent versions. Boots only the oldest available (Ubuntu 20.04.2??) on boot menu. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-37-generic Date: Mon Nov 1 21:51:50 2021 PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) ** Affects: nvidia-graphics-drivers-340 (Ubuntu) Importance: Undecided Status: New ** Tags: amd64 apport-package focal -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to nvidia-graphics-drivers-340 in Ubuntu. https://bugs.launchpad.net/bugs/1949341 Title: Fails to boot recent versions - nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build Status in nvidia-graphics-drivers-340 package in Ubuntu: New Bug description: Fails to boot recent versions. Boots only the oldest available (Ubuntu 20.04.2??) on boot menu. ProblemType: Package DistroRelease: Ubuntu 20.04 Package: nvidia-340 340.108-0ubuntu5.20.04.2 ProcVersionSignature: Ubuntu 5.4.0-26.30-generic 5.4.30 Uname: Linux 5.4.0-26-generic x86_64 NonfreeKernelModules: nvidia ApportVersion: 2.20.11-0ubuntu27 Architecture: amd64 CasperMD5CheckResult: skip DKMSKernelVersion: 5.11.0-37-generic Date: Mon Nov 1 21:51:50 2021 PackageVersion: 340.108-0ubuntu5.20.04.2 Python3Details: /usr/bin/python3.8, Python 3.8.2, python3-minimal, 3.8.2-0ubuntu2 PythonDetails: N/A RelatedPackageVersions: dpkg 1.19.7ubuntu3 apt 2.0.2 SourcePackage: nvidia-graphics-drivers-340 Title: nvidia-340 340.108-0ubuntu5.20.04.2: nvidia-340 kernel module failed to build UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nvidia-graphics-drivers-340/+bug/1949341/+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 1949340] Re: Saving downloads or pages is difficult because of unfocused file chooser dialog
** Description changed: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) - 2a. Press + + 2a. Navigate to some page, press + 2b. With "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. ** Description changed: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + - 2b. With "Ask where to save each file before downloading" enabled try to download some file + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: Saving downloads or pages is difficult because of unfocused file chooser dialog Status in chromium-browser package in Ubuntu: New Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1949340/+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 1949340] [NEW] Saving downloads or pages is difficult because of unfocused file chooser dialog
Public bug reported: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. ** Affects: chromium-browser (Ubuntu) Importance: Undecided Status: New ** Tags: bionic focal hirsute impish jammy -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to chromium-browser in Ubuntu. https://bugs.launchpad.net/bugs/1949340 Title: Saving downloads or pages is difficult because of unfocused file chooser dialog Status in chromium-browser package in Ubuntu: New Bug description: Steps to reproduce: 1. Open Chromium (release does not matter, here deb-packaged version from 18.04 LTS is used) 2a. Navigate to some page, press + 2b. Navigate to some page, with "Ask where to save each file before downloading" enabled try to download some file Actual result: * file chooser dialog is unfocused, user should select the window by mouse and then hit for specified location Expected result: * file chooser dialog is focused, user can simply hit to save in previously selected location. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1949340/+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 1949312] Re: Transmission icon Ubuntu MATE doesn´t fit overall icontheme
** Tags added: focal hirsute impish ** Also affects: transmission (Ubuntu) Importance: Undecided Status: New ** Also affects: ubuntu-mate-artwork (Ubuntu) Importance: Undecided Status: New -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to transmission in Ubuntu. https://bugs.launchpad.net/bugs/1949312 Title: Transmission icon Ubuntu MATE doesn´t fit overall icontheme Status in Ubuntu MATE: New Status in transmission package in Ubuntu: New Status in ubuntu-mate-artwork package in Ubuntu: New Bug description: When using the Yaru icon theme in Ubuntu MATE and adding Transmission to the indicator applet, the Transmission icons does not fit the other icons in the indicator. (The Transmission icon has color, while the others have not) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu-mate/+bug/1949312/+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 1949336] Re: /usr/bin/gnome-shell:gnome-shell: ../nouveau/pushbuf.c:728: nouveau_pushbuf_data: Zusicherung \302\273kref\302\253 nicht erf\303\274llt.
*** This bug is a duplicate of bug 1497593 *** https://bugs.launchpad.net/bugs/1497593 ** This bug has been marked a duplicate of bug 1497593 [nouveau] Programs crash with SIGABRT in nouveau_pushbuf_data: Assertion `kref' failed. -- 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/1949336 Title: /usr/bin/gnome-shell:gnome-shell: ../nouveau/pushbuf.c:728: nouveau_pushbuf_data: Zusicherung \302\273kref\302\253 nicht erf\303\274llt. Status in gnome-shell package in Ubuntu: New 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 40.5-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/3999b3d8790aa087484a9a9d0ab0705c35d363e5 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/gnome-shell/+bug/1949336/+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 1949336] [NEW] /usr/bin/gnome-shell:gnome-shell: ../nouveau/pushbuf.c:728: nouveau_pushbuf_data: Zusicherung \302\273kref\302\253 nicht erf\303\274llt.
*** This bug is a duplicate of bug 1497593 *** https://bugs.launchpad.net/bugs/1497593 Public bug reported: The Ubuntu Error Tracker has been receiving reports about a problem regarding gnome-shell. This problem was most recently seen with package version 40.5-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/3999b3d8790aa087484a9a9d0ab0705c35d363e5 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/. ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New ** Tags: impish -- 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/1949336 Title: /usr/bin/gnome-shell:gnome-shell: ../nouveau/pushbuf.c:728: nouveau_pushbuf_data: Zusicherung \302\273kref\302\253 nicht erf\303\274llt. Status in gnome-shell package in Ubuntu: New 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 40.5-1ubuntu2, the problem page at https://errors.ubuntu.com/problem/3999b3d8790aa087484a9a9d0ab0705c35d363e5 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/gnome-shell/+bug/1949336/+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 1948617] Re: gnome-shell crashed with SIGTRAP in /usr/lib/x86_64-linux-gnu/libc.so.6+1a476
It looks like bug 1949200 might be the same issue, maybe. -- 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/1948617 Title: gnome-shell crashed with SIGTRAP in /usr/lib/x86_64-linux- gnu/libc.so.6+1a476 Status in gnome-shell package in Ubuntu: Incomplete Bug description: This is an attempt to track a common crash that is affecting impish only: https://errors.ubuntu.com/problem/e60359af65f32c18a4a6ccc93fd3469b0e675844 gnome-shell (5) /usr/lib/x86_64-linux-gnu/libc.so.6+1a476 → /usr/bin/gnome-shell+15ba → /usr/lib/x86_64-linux- gnu/libglib-2.0.so.0.6800.4+4392f → /usr/lib/x86_64-linux- gnu/libglib-2.0.so.0.6800.4+3f633 → /usr/lib/x86_64-linux- gnu/libglib-2.0.so.0.6800.4+3f833 → /usr/lib/x86_64-linux- gnu/libgtk-3.so.0.2404.26+27949f → /usr/lib/x86_64-linux- gnu/libgobject-2.0.so.0.6800.4+2d24a → /usr/lib/x86_64-linux- gnu/libgobject-2.0.so.0.6800.4+14b7d → /usr/lib/x86_64-linux- gnu/libgobject-2.0.so.0.6800.4+15b4d → /usr/lib/x86_64-linux- gnu/libgobject-2.0.so.0.6800.4+16651 → /usr/lib/x86_64-linux- gnu/libgtk-3.so.0.2404.26+58fa0 → /usr/lib/x86_64-linux- gnu/libgtk-3.so.0.2404.26+59213 → /usr/lib/x86_64-linux- gnu/libgtk-3.so.0.2404.26+5db91 → /usr/lib/x86_64-linux- gnu/libgtk-3.so.0.2404.26+32373e → /usr/lib/x86_64-linux- gnu/libmutter-8.so.0.0.0+9b0a7 Looking up the addresses by hand yields something that barely makes sense: __xpg_sigpause + 70 in section .text of /lib/x86_64-linux-gnu/libc.so.6 dump_gjs_stack_on_signal_handler + 202 in section .text of /usr/bin/gnome-shell g_option_context_get_help + 63 in section .text of /lib/x86_64-linux-gnu/libglib-2.0.so.0 g_log_set_fatal_mask + 179 in section .text of /lib/x86_64-linux-gnu/libglib-2.0.so.0 msort_r + 467 in section .text of /lib/x86_64-linux-gnu/libglib-2.0.so.0 gtk_text_buffer_real_delete_range + 1263 in section .text of /lib/x86_64-linux-gnu/libgtk-3.so.0 g_value_transform + 26 in section .text of /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_new_with_properties + 285 in section .text of /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_set_valist + 413 in section .text of /lib/x86_64-linux-gnu/libgobject-2.0.so.0 g_object_get_property + 161 in section .text of /lib/x86_64-linux-gnu/libgobject-2.0.so.0 update_node + 4016 in section .text of /lib/x86_64-linux-gnu/libgtk-3.so.0 update_node + 4643 in section .text of /lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_inspector_gestures_class_intern_init + 81 in section .text of /lib/x86_64-linux-gnu/libgtk-3.so.0 gtk_window_move + 46 in section .text of /lib/x86_64-linux-gnu/libgtk-3.so.0 meta_x11_display_new + 5399 in section .text of /lib/x86_64-linux-gnu/libmutter-8.so.0 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948617/+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 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
debdiff for focal. Note I back-port a chunk from the patch as hirsute. ** Patch added: "mutter_3.36.9-0ubuntu0.20.04.2.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1948894/+attachment/5537413/+files/mutter_3.36.9-0ubuntu0.20.04.2.debdiff -- 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/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. Status in Mutter: Unknown Status in OEM Priority Project: In Progress Status in X.Org X server: Unknown Status in mutter package in Ubuntu: In Progress Status in mutter package in Fedora: Unknown Bug description: This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. (also observed that the touchscreen USB device drop of a USB bus on the target machine) Note: this bug seems to be timing sensitive. I got an OEM project machine that can reproduce this issue (reproducible on several machines with the same HW design). The machine is using ADL CPU, which needs a patched 5.14 kernel. So I can't reproduce this on impish. With the backported mutter, I verified an upstream patch seems to fix this issue. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872 #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at ../../../../os/log.c:1010 #5 0x56437429c8b0 in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:1312 #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 #7 0x7f447c3cb78b in display_handle_error (data=, display=0x56437639f000, object=0x56437639f000, code=0, message=) at ../src/wayland-client.c:911 #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #10 0x7f447c3cf3a8 in wl_closure_invoke (closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=, target@entry=0x56437639f000, opcode=opcode@entry=0, data=) at ../src/connection.c:1018 #11 0x7f447c3cbc48 in dispatch_event (display=display@entry=0x56437639f000, queue=) at ../src/wayland-client.c:1445 #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, display=0x56437639f000) at ../src/wayland-client.c:1584 #13 wl_display_dispatch_queue_pending (display=0x56437639f000, queue=0x56437639f0d0) at ../src/wayland-client.c:1833 #14 0x7f447c3cd280 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896 #15 0x56437429c9bb in xwl_read_events (xwl_screen=0x564376399dd0) at ../../../../../hw/xwayland/xwayland.c:957 #16 0x564374401c61 in ospoll_wait (ospoll=0x56437638f4a0, timeout=) at ../../../../os/ospoll.c:657 #17 0x5643743faa23 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:208 #18 0x5643743ca4a7 in Dispatch () at ../../../../include/list.h:220 #19 0x5643743ce794 in dix_main (argc=16, argv=0x7ffc44d49298, envp=) at ../../../../dix/main.c:276 #20 0x7f447b8c90b3 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #21 0x56437429c60e in _start ()``` To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948894/+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 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
debdiff for impish ** Patch added: "mutter_40.5-1ubuntu3~21.10.1_impish.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1948894/+attachment/5537406/+files/mutter_40.5-1ubuntu3~21.10.1_impish.debdiff -- 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/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. Status in Mutter: Unknown Status in OEM Priority Project: In Progress Status in X.Org X server: Unknown Status in mutter package in Ubuntu: In Progress Status in mutter package in Fedora: Unknown Bug description: This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. (also observed that the touchscreen USB device drop of a USB bus on the target machine) Note: this bug seems to be timing sensitive. I got an OEM project machine that can reproduce this issue (reproducible on several machines with the same HW design). The machine is using ADL CPU, which needs a patched 5.14 kernel. So I can't reproduce this on impish. With the backported mutter, I verified an upstream patch seems to fix this issue. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872 #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at ../../../../os/log.c:1010 #5 0x56437429c8b0 in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:1312 #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 #7 0x7f447c3cb78b in display_handle_error (data=, display=0x56437639f000, object=0x56437639f000, code=0, message=) at ../src/wayland-client.c:911 #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #10 0x7f447c3cf3a8 in wl_closure_invoke (closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=, target@entry=0x56437639f000, opcode=opcode@entry=0, data=) at ../src/connection.c:1018 #11 0x7f447c3cbc48 in dispatch_event (display=display@entry=0x56437639f000, queue=) at ../src/wayland-client.c:1445 #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, display=0x56437639f000) at ../src/wayland-client.c:1584 #13 wl_display_dispatch_queue_pending (display=0x56437639f000, queue=0x56437639f0d0) at ../src/wayland-client.c:1833 #14 0x7f447c3cd280 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896 #15 0x56437429c9bb in xwl_read_events (xwl_screen=0x564376399dd0) at ../../../../../hw/xwayland/xwayland.c:957 #16 0x564374401c61 in ospoll_wait (ospoll=0x56437638f4a0, timeout=) at ../../../../os/ospoll.c:657 #17 0x5643743faa23 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:208 #18 0x5643743ca4a7 in Dispatch () at ../../../../include/list.h:220 #19 0x5643743ce794 in dix_main (argc=16, argv=0x7ffc44d49298, envp=) at ../../../../dix/main.c:276 #20 0x7f447b8c90b3 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #21 0x56437429c60e in _start ()``` To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948894/+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 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
add Bug-Ubuntu in salsa git, and re-upload jammy debdiff. ** Patch removed: "mutter_40.5-1ubuntu3.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1948894/+attachment/5537386/+files/mutter_40.5-1ubuntu3.debdiff ** Patch added: "mutter_40.5-1ubuntu3.debdiff" https://bugs.launchpad.net/oem-priority/+bug/1948894/+attachment/5537405/+files/mutter_40.5-1ubuntu3.debdiff -- 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/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. Status in Mutter: Unknown Status in OEM Priority Project: In Progress Status in X.Org X server: Unknown Status in mutter package in Ubuntu: In Progress Status in mutter package in Fedora: Unknown Bug description: This is a reproducible issue. Step to reproduce 1. cold boot into gdm login screen. 2. wait for 5 mins, and the screen will be turned off. (also observed that the touchscreen USB device drop of a USB bus on the target machine) Note: this bug seems to be timing sensitive. I got an OEM project machine that can reproduce this issue (reproducible on several machines with the same HW design). The machine is using ADL CPU, which needs a patched 5.14 kernel. So I can't reproduce this on impish. With the backported mutter, I verified an upstream patch seems to fix this issue. Expected result: The screen just turns black. Actual result: Saw Vendor boot logo on the monitor (previous draw by plymouth during booting) Analysis as it happens: 1. Saw "LGDisplay Incell Touch" drop off the USB bus. Kernel message like: "usb 1-9: USB disconnect, device number 6" as the screen turned black. 2. There is no switch on virtual tty. 3. journal log from Xwayland "wl_display@1: error 0: invalid object 24" 4. Xwayland and gnome-shell process both die as this happens. 5. Try to add sleep(30) to OsVendorFatalError(), then both Xwayland and gnome-shell stop there for 30 more seconds. 6. backtrace as Xwayland crashed: ``` #0 0x7f447b8e818b in raise () from /lib/x86_64-linux-gnu/libc.so.6 #1 0x7f447b8c7859 in abort () from /lib/x86_64-linux-gnu/libc.so.6 #2 0x564374403f30 in OsAbort () at ../../../../os/utils.c:1351 #3 0x564374409369 in AbortServer () at ../../../../os/log.c:872 #4 0x56437440a1ca in FatalError (f=f@entry=0x564374416266 "%s") at ../../../../os/log.c:1010 #5 0x56437429c8b0 in xwl_log_handler (format=, args=) at ../../../../../hw/xwayland/xwayland.c:1312 #6 0x7f447c3d027e in wl_log (fmt=fmt@entry=0x7f447c3d121a "%s@%u: error %d: %s\n") at ../src/wayland-util.c:404 #7 0x7f447c3cb78b in display_handle_error (data=, display=0x56437639f000, object=0x56437639f000, code=0, message=) at ../src/wayland-client.c:911 #8 0x7f447b7c0ff5 in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #9 0x7f447b7c040a in ?? () from /lib/x86_64-linux-gnu/libffi.so.7 #10 0x7f447c3cf3a8 in wl_closure_invoke (closure=closure@entry=0x564376e57350, flags=flags@entry=1, target=, target@entry=0x56437639f000, opcode=opcode@entry=0, data=) at ../src/connection.c:1018 #11 0x7f447c3cbc48 in dispatch_event (display=display@entry=0x56437639f000, queue=) at ../src/wayland-client.c:1445 #12 0x7f447c3cd1ef in dispatch_queue (queue=0x56437639f0d0, display=0x56437639f000) at ../src/wayland-client.c:1584 #13 wl_display_dispatch_queue_pending (display=0x56437639f000, queue=0x56437639f0d0) at ../src/wayland-client.c:1833 #14 0x7f447c3cd280 in wl_display_dispatch_pending (display=) at ../src/wayland-client.c:1896 #15 0x56437429c9bb in xwl_read_events (xwl_screen=0x564376399dd0) at ../../../../../hw/xwayland/xwayland.c:957 #16 0x564374401c61 in ospoll_wait (ospoll=0x56437638f4a0, timeout=) at ../../../../os/ospoll.c:657 #17 0x5643743faa23 in WaitForSomething (are_ready=0) at ../../../../os/WaitFor.c:208 #18 0x5643743ca4a7 in Dispatch () at ../../../../include/list.h:220 #19 0x5643743ce794 in dix_main (argc=16, argv=0x7ffc44d49298, envp=) at ../../../../dix/main.c:276 #20 0x7f447b8c90b3 in __libc_start_main () from /lib/x86_64-linux-gnu/libc.so.6 #21 0x56437429c60e in _start ()``` To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948894/+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
