[Desktop-packages] [Bug 1973802] Re: Gnome Shell crashes when disconnecting external monitor
*** This bug is a duplicate of bug 1933186 *** https://bugs.launchpad.net/bugs/1933186 đź‘Ť Thanks for your patience! -- 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/1973802 Title: Gnome Shell crashes when disconnecting external monitor Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 22.04, gnome-shell 42.0-2ubuntu1 When unplugging an external monitor connected via USB-C to my Thinkpad P14s, the entire UI session crashes. While the external monitor is plugged in, it is configured as the primary display. Here are the gnome-shell logs of the latest incident, I suppose the relevant part is `assertion 'window->stack_position >= 0' failed`. May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212959: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212959 does not exist. May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212963: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212963 does not exist. May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212964: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212964 does not exist. May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212965: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212965 does not exist. May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212966: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212966 does not exist. May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212967: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212967 does not exist. May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). May 17 09:56:51 snaut gnome-shell[2048]: Could not create transient scope fo
[Desktop-packages] [Bug 1973802] Re: Gnome Shell crashes when disconnecting external monitor
It just happened again and this time it seems a report has been uploaded: https://errors.ubuntu.com/oops/f18abe5a-d79a-11ec-9ae6-fa163e55efd0 Disconnected the external monitor, the desktop is visible on the laptop screen, and two seconds later, the UI session crashes. The timestamp shown on https://errors.ubuntu.com/user/YOUR_ID is a bit off, however, there weren't any other incidents so this must be the one. -- 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/1973802 Title: Gnome Shell crashes when disconnecting external monitor Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 22.04, gnome-shell 42.0-2ubuntu1 When unplugging an external monitor connected via USB-C to my Thinkpad P14s, the entire UI session crashes. While the external monitor is plugged in, it is configured as the primary display. Here are the gnome-shell logs of the latest incident, I suppose the relevant part is `assertion 'window->stack_position >= 0' failed`. May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212959: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212959 does not exist. May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212963: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212963 does not exist. May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212964: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212964 does not exist. May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212965: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212965 does not exist. May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212966: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212966 does not exist. May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212967: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212967 does not exist. May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). May 17 09:56:49 snaut gnome-shell[2048]: Window manager war
[Desktop-packages] [Bug 1973802] Re: Gnome Shell crashes when disconnecting external monitor
Right. Now I call `apport-cli` with the crash file as parameter. As soon as I press "S", the program terminates immediately. No browser window is being opened. $ apport-cli _usr_bin_gnome-shell.1000.crash *** Send problem report to the developers? After the problem report has been sent, please fill out the form in the automatically opened web browser. What would you like to do? Your options are: S: Send report (79.5 MB) V: View report K: Keep report file for sending later or copying to somewhere else I: Cancel and ignore future crashes of this program version C: Cancel Please choose (S/V/K/I/C): S $ -- 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/1973802 Title: Gnome Shell crashes when disconnecting external monitor Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 22.04, gnome-shell 42.0-2ubuntu1 When unplugging an external monitor connected via USB-C to my Thinkpad P14s, the entire UI session crashes. While the external monitor is plugged in, it is configured as the primary display. Here are the gnome-shell logs of the latest incident, I suppose the relevant part is `assertion 'window->stack_position >= 0' failed`. May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212959: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212959 does not exist. May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212963: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212963 does not exist. May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212964: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212964 does not exist. May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212965: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212965 does not exist. May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212966: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212966 does not exist. May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212967: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212967 does not exist. May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycod
[Desktop-packages] [Bug 1973802] Re: Gnome Shell crashes when disconnecting external monitor
So `ubuntu-bug ` fails and an error UI pops up, asking to send an error report (which I did). After that, `apport-cli` tells me that there are no pending crash reports. Strangely, there are no recent items on https://errors.ubuntu.com/user/, only some that are several days, some several months old. Trying to attach the crash log here failed again. I've opened https://bugs.launchpad.net/launchpad/+bug/1974066 for that. Seems I'm running out of options, sorry. -- 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/1973802 Title: Gnome Shell crashes when disconnecting external monitor Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 22.04, gnome-shell 42.0-2ubuntu1 When unplugging an external monitor connected via USB-C to my Thinkpad P14s, the entire UI session crashes. While the external monitor is plugged in, it is configured as the primary display. Here are the gnome-shell logs of the latest incident, I suppose the relevant part is `assertion 'window->stack_position >= 0' failed`. May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212959: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212959 does not exist. May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212963: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212963 does not exist. May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212964: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212964 does not exist. May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212965: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212965 does not exist. May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212966: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212966 does not exist. May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212967: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212967 does not exist. May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). May 17 0
[Desktop-packages] [Bug 1973802] Re: Gnome Shell crashes when disconnecting external monitor
Thanks. I've found the corresponding crash log and tried to attach it here, but the upload fails (always end up on a site saying "Uh oh :(". Might be the file size (76M), even a gzipped version (55M) did not succeed. Using `ubuntu_bug` as recommended in https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment did not seem to do anything (perhaps running into that same problem). Any ideas? -- 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/1973802 Title: Gnome Shell crashes when disconnecting external monitor Status in gnome-shell package in Ubuntu: Incomplete Bug description: Ubuntu 22.04, gnome-shell 42.0-2ubuntu1 When unplugging an external monitor connected via USB-C to my Thinkpad P14s, the entire UI session crashes. While the external monitor is plugged in, it is configured as the primary display. Here are the gnome-shell logs of the latest incident, I suppose the relevant part is `assertion 'window->stack_position >= 0' failed`. May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212959: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212959 does not exist. May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212963: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212963 does not exist. May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212964: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212964 does not exist. May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212965: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212965 does not exist. May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212966: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212966 does not exist. May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212967: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212967 does not exist. May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). May 17 09:56:49 snaut gnome-shell[2048]: Wind
[Desktop-packages] [Bug 1973802] [NEW] Gnome Shell crashes when disconnecting external monitor
Public bug reported: Ubuntu 22.04, gnome-shell 42.0-2ubuntu1 When unplugging an external monitor connected via USB-C to my Thinkpad P14s, the entire UI session crashes. While the external monitor is plugged in, it is configured as the primary display. Here are the gnome- shell logs of the latest incident, I suppose the relevant part is `assertion 'window->stack_position >= 0' failed`. May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212959: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212959 does not exist. May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2524]: XWAYLAND: mode -1x-1 is not available May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212963: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212963 does not exist. May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212964: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212964 does not exist. May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212965: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212965 does not exist. May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212966: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212966 does not exist. May 17 09:56:49 snaut gnome-shell[2048]: Could not create transient scope for PID 212967: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 212967 does not exist. May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 31 with keysym 31 (keycode a). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 32 with keysym 32 (keycode b). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 33 with keysym 33 (keycode c). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 34 with keysym 34 (keycode d). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 35 with keysym 35 (keycode e). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 36 with keysym 36 (keycode f). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 37 with keysym 37 (keycode 10). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 38 with keysym 38 (keycode 11). May 17 09:56:49 snaut gnome-shell[2048]: Window manager warning: Overwriting existing binding of keysym 39 with keysym 39 (keycode 12). May 17 09:56:51 snaut gnome-shell[2048]: Could not create transient scope for PID 213085: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 213085 does not exist. May 17 09:56:51 snaut gnome-shell[2048]: Could not create transient scope for PID 213089: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 213089 does not exist. May 17 09:56:51 snaut gnome-shell[2048]: Could not create transient scope for PID 213090: GDBus.Error:org.freedesktop.DBus.Error.UnixProcessIdUnknown: Process with ID 213090 does not e
[Desktop-packages] [Bug 1753131] Re: gnome-shell crashes occasionally (libmutter)
I just noticed that the crash leaves a $HOME/core file: $ file core core: ELF 64-bit LSB core file x86-64, version 1 (SYSV), SVR4-style, from '/usr/bin/Xwayland :0 -rootless -terminate -core -listen 4 -listen 5 -displayfd', real uid: 1000, effective uid: 1000, real gid: 1000, effective gid: 1000, execfn: '/usr/bin/Xwayland', platform: 'x86_64' Could this be helpful? -- 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/1753131 Title: gnome-shell crashes occasionally (libmutter) Status in gnome-shell package in Ubuntu: Incomplete Bug description: I see occasional crashes of gnome-shell that get me back to the login screen. After these crashes I find something like the following line in dmesg: gnome-shell[8428]: segfault at b0 ip 7fddec8387d1 sp 7ffdf2061a80 error 4 in libmutter-1.so.0.0.0[7fddec763000+142000] Ubuntu: 17.10 gnome-shell: 3.26.2-0ubuntu0.1 mutter: 3.26.2-0ubuntu0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1753131/+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 1753131] Re: gnome-shell crashes occasionally (libmutter)
It just happened again. There is no file in /var/crash, just the aforementioned line in dmesg and also in /var/log/syslog. It seems that everytime this crash happens I'm working with the Eclipse IDE. I also find those lines in syslog which might be related: java[30229]: Allocating size to GtkScrolledWindow 0x7fee4ab40de0 without calling gtk_widget_get_preferred_width/height(). How does the code know the size to allocate? Anything else I could do to track it down? -- 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/1753131 Title: gnome-shell crashes occasionally (libmutter) Status in gnome-shell package in Ubuntu: Incomplete Bug description: I see occasional crashes of gnome-shell that get me back to the login screen. After these crashes I find something like the following line in dmesg: gnome-shell[8428]: segfault at b0 ip 7fddec8387d1 sp 7ffdf2061a80 error 4 in libmutter-1.so.0.0.0[7fddec763000+142000] Ubuntu: 17.10 gnome-shell: 3.26.2-0ubuntu0.1 mutter: 3.26.2-0ubuntu0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1753131/+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 1753131] Re: gnome-shell crashes occasionally (libmutter)
Thanks, I've applied the workaround. My /var/crash is currently empty, I'll follow your advice when the crash occurs again. -- 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/1753131 Title: gnome-shell crashes occasionally (libmutter) Status in gnome-shell package in Ubuntu: Incomplete Bug description: I see occasional crashes of gnome-shell that get me back to the login screen. After these crashes I find something like the following line in dmesg: gnome-shell[8428]: segfault at b0 ip 7fddec8387d1 sp 7ffdf2061a80 error 4 in libmutter-1.so.0.0.0[7fddec763000+142000] Ubuntu: 17.10 gnome-shell: 3.26.2-0ubuntu0.1 mutter: 3.26.2-0ubuntu0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1753131/+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 1753131] [NEW] gnome-shell crashes occasionally (libmutter)
Public bug reported: I see occasional crashes of gnome-shell that get me back to the login screen. After these crashes I find something like the following line in dmesg: gnome-shell[8428]: segfault at b0 ip 7fddec8387d1 sp 7ffdf2061a80 error 4 in libmutter-1.so.0.0.0[7fddec763000+142000] Ubuntu: 17.10 gnome-shell: 3.26.2-0ubuntu0.1 mutter: 3.26.2-0ubuntu0.1 ** Affects: gnome-shell (Ubuntu) Importance: Undecided Status: New -- 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/1753131 Title: gnome-shell crashes occasionally (libmutter) Status in gnome-shell package in Ubuntu: New Bug description: I see occasional crashes of gnome-shell that get me back to the login screen. After these crashes I find something like the following line in dmesg: gnome-shell[8428]: segfault at b0 ip 7fddec8387d1 sp 7ffdf2061a80 error 4 in libmutter-1.so.0.0.0[7fddec763000+142000] Ubuntu: 17.10 gnome-shell: 3.26.2-0ubuntu0.1 mutter: 3.26.2-0ubuntu0.1 To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1753131/+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 959505] Re: gedit wants to save in "recently used" by default
This is one of the most annoying "features" for me as well, it constantly gets in my way. The current directory is almost always what I want, while the recently used list is always out of context. I believe that a good UI should support the user without "getting in the way". There may be good intentions, but this solution sucks. Please change it or make it configurable! -- You received this bug notification because you are a member of Desktop Packages, which is subscribed to gedit in Ubuntu. https://bugs.launchpad.net/bugs/959505 Title: gedit wants to save in "recently used" by default Status in “gedit” package in Ubuntu: Confirmed Bug description: Clean install of 12.04, open gedit from the dash, type into a new document then File -> Save. By default the save dialog is positioned on "Recently used" which cannot be saved into. Seems a bit strange to default there. Would ~/Documents not make more sense? ProblemType: Bug DistroRelease: Ubuntu 12.04 Package: gedit 3.3.7-0ubuntu2 ProcVersionSignature: Ubuntu 3.2.0-19.30-generic-pae 3.2.11 Uname: Linux 3.2.0-19-generic-pae i686 ApportVersion: 1.94.1-0ubuntu2 Architecture: i386 Date: Mon Mar 19 17:12:23 2012 EcryptfsInUse: Yes InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120211) ProcEnviron: LANGUAGE=en_GB:en TERM=xterm PATH=(custom, no user) LANG=en_GB.UTF-8 SHELL=/bin/bash SourcePackage: gedit UpgradeStatus: No upgrade log present (probably fresh install) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gedit/+bug/959505/+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