[Bug 1949200] Re: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init
** Description changed: GNOME Shell isn't meant to use GTK at all, but it's repeatedly crashing - in GTK. + in GTK since the introduction of GNOME 40. 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: -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gnome-shell-extension-appindicator 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1948894] Re: Xwayland crash in gdm as screen off and touchscreen detach.
** Changed in: mutter (Ubuntu) Importance: Undecided => High ** Package changed: mutter (Fedora) => ubuntu ** Changed in: ubuntu Importance: Unknown => Undecided ** Changed in: ubuntu Status: Unknown => New ** Changed in: ubuntu Remote watch: Red Hat Bugzilla #1516859 => None ** No longer affects: ubuntu ** Bug watch removed: Red Hat Bugzilla #1516859 https://bugzilla.redhat.com/show_bug.cgi?id=1516859 ** Project changed: xorg-server => ubuntu ** Changed in: ubuntu Importance: Unknown => Undecided ** Changed in: ubuntu Status: Unknown => New ** Changed in: ubuntu Remote watch: gitlab.freedesktop.org/xorg/xserver/-/issues #1239 => None ** No longer affects: ubuntu ** Bug watch removed: gitlab.freedesktop.org/xorg/xserver/-/issues #1239 https://gitlab.freedesktop.org/xorg/xserver/-/issues/1239 -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948894/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1949200] Re: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init
If we could then it would be nice to mitigate this by simply ensuring GTK in the gnome-shell process can find the Wayland server automatically instead of X11. Because if we don't find a blanket solution like that then we'll keep getting similar gnome-shell crash reports. ** Also affects: gtk+3.0 (Ubuntu) Importance: Undecided Status: New ** Also affects: gnome-shell-extension-appindicator (Ubuntu) Importance: Undecided Status: New ** Changed in: gtk+3.0 (Ubuntu) Status: New => Confirmed ** Changed in: gtk+3.0 (Ubuntu) Importance: Undecided => High ** Description changed: + GNOME Shell isn't meant to use GTK at all, but it's repeatedly crashing + in GTK. + 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: -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1949200] Re: gnome-shell crashed with SIGTRAP from error "Can't create a GtkStyleContext without a display connection" in gtk_style_context_init
Like the similar upstream bug https://gitlab.gnome.org/GNOME/mutter/-/issues/1475, this appears to be caused by the intersection of: (a) GTK being used in the gnome-shell process (usually by extensions); and (b) The absence of an Xserver for GTK to connect to (Xwayland is only started on-demand now). It looks like one possible offender using GTK is gnome-shell-extension- appindicator. I'm not sure about the other extensions, and it's hard to tell with desktop-icons-ng which in theory uses GTK in a safe way (in a separate client process). -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948617/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/mutter/+bug/1942378/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1949413 Title: Gnome shell crashes back to login screen randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949413/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1949363] Re: gdm segfault when changing session between users
Thank you for taking the time to report this bug and helping to make Ubuntu better. It sounds like some part of the system has crashed. To help us find the cause of the crash please follow these steps: 1. Look in /var/crash for crash files and if found run: ubuntu-bug YOURFILE.crash Then tell us the ID of the newly-created bug. 2. If step 1 failed then look at https://errors.ubuntu.com/user/ID where ID is the content of file /var/lib/whoopsie/whoopsie-id on the machine. Do you find any links to recent problems on that page? If so then please send the links to us. 3. If step 2 also failed then apply the workaround from bug 994921, reboot, reproduce the crash, and retry step 1. Please take care to avoid attaching .crash files to bugs as we are unable to process them as file attachments. It would also be a security risk for yourself. ** Changed in: gdm3 (Ubuntu) Status: New => Incomplete -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1949363 Title: gdm segfault when changing session between users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1949363/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949352/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949200/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949262/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1949413 Title: Gnome shell crashes back to login screen randomly To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949413/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1949411 Title: GJS using lots of CPU resources non stop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1949411/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gjs in Ubuntu. https://bugs.launchpad.net/bugs/1949411 Title: GJS using lots of CPU resources non stop To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gjs/+bug/1949411/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1929650 Title: Screen doesn't turn off when using Wayland on some devices To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1929650/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1949262/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1843588/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/nautilus/+bug/1843588/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to nautilus in Ubuntu. https://bugs.launchpad.net/bugs/1949105 Title: executable text activation does not work To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/nautilus/+bug/1949105/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1949352 Title: Removable drives are not handled after screen lock/unlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949352/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1299604] Re: evolution keeps asking for password
I still have the same issue on Ubuntu 20.04.3 LTS with the XFCE Desktop. Removing the ~/.gnome2/keyrings/ helps but the problem comes again after a few days. -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to evolution in Ubuntu. https://bugs.launchpad.net/bugs/1299604 Title: evolution keeps asking for password To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/evolution/+bug/1299604/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[Bug 1949363] Re: gdm segfault when changing session between users
** Attachment added: "partial syslog" https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1949363/+attachment/5537481/+files/partial_syslog -- You received this bug notification because you are a member of Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1949363 Title: gdm segfault when changing session between users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1949363/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gdm3 in Ubuntu. https://bugs.launchpad.net/bugs/1949363 Title: gdm segfault when changing session between users To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1949363/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1949352 Title: Removable drives are not handled after screen lock/unlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949352/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to evince in Ubuntu. https://bugs.launchpad.net/bugs/1949355 Title: unity-tweak-tool To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/unity-tweak-tool/+bug/1949355/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu
Desktop Bugs, which is subscribed to evince in Ubuntu.
https://bugs.launchpad.net/bugs/1949355
Title:
unity-tweak-tool
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/unity-tweak-tool/+bug/1949355/+subscriptions
--
desktop-bugs mailing list
desktop-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1949352 Title: Removable drives are not handled after screen lock/unlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949352/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to gnome-shell in Ubuntu. https://bugs.launchpad.net/bugs/1949352 Title: Removable drives are not handled after screen lock/unlock To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949352/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949336/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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. To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1949336/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, 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 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1948617/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
[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 Ubuntu Desktop Bugs, which is subscribed to mutter in Ubuntu. https://bugs.launchpad.net/bugs/1948894 Title: Xwayland crash in gdm as screen off and touchscreen detach. To manage notifications about this bug go to: https://bugs.launchpad.net/mutter/+bug/1948894/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
