gnome-shell lost connection to Xwayland

[Heather Ellsworth]

On an up2date Jammy, running gnome-shell from proposed, and gnome-shell randomly lost my connection to wayland. There was no crash logged in /var/crash.

Journalctl shows that after many of these internal errors, gnome-shell experienced a loss of connection with wayland:

Mar 28 10:25:02 fenrir gnome-shell[15578]: > Internal error: Could not resolve keysym XF86MacroPreset3
Mar 28 10:25:02 fenrir gnome-shell[15578]: > Internal error: Could not resolve keysym XF86KbdLcdMenu1
Mar 28 10:25:02 fenrir gnome-shell[15578]: > Internal error: Could not resolve keysym XF86KbdLcdMenu2
Mar 28 10:25:02 fenrir gnome-shell[15578]: > Internal error: Could not resolve keysym XF86KbdLcdMenu3
Mar 28 10:25:02 fenrir gnome-shell[15578]: > Internal error: Could not resolve keysym XF86KbdLcdMenu4
Mar 28 10:25:02 fenrir gnome-shell[15578]: > Internal error: Could not resolve keysym XF86KbdLcdMenu5
Mar 28 10:25:02 fenrir gnome-shell[15578]: Errors from xkbcomp are not fatal to the X server
Mar 28 10:25:04 fenrir NetworkManager[1433]: <warn> [1648484704.0244] platform-linux: do-add-ip6-address[3: fe80::468f:31f7:6319:46d7]: failure 13 (Permission denied)
Mar 28 10:25:04 fenrir gnome-shell[2974]: Object 0x7fdd044211a0 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management.
Mar 28 10:25:04 fenrir gnome-shell[2974]: Object 0x7fdd056dcd40 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management.
Mar 28 10:25:04 fenrir gnome-shell[2974]: Object 0x55ee75f13920 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management.
Mar 28 10:25:04 fenrir gnome-shell[2974]: Object 0x7fdd0570ec30 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management.
Mar 28 10:25:04 fenrir gnome-shell[2974]: Object 0x55ee6fecfa70 of type IBusText has been finalized while it was still owned by gjs, this is due to invalid memory management.
Mar 28 10:25:06 fenrir NetworkManager[1433]: <warn> [1648484706.0251] platform-linux: do-add-ip6-address[3: fe80::5e83:5ee2:b24c:71b7]: failure 13 (Permission denied)
Mar 28 10:25:08 fenrir NetworkManager[1433]: <warn> [1648484708.0256] ipv6ll[d24c39fb7105ee85,ifindex=3]: changed: no IPv6 link local address to retry after Duplicate Address Detection failures (back off)
Mar 28 10:25:12 fenrir gnome-shell[15153]: Connection to xwayland lost
Mar 28 10:25:12 fenrir gnome-session[15139]: gnome-session-binary[15139]: CRITICAL: gsm_client_peek_id: assertion 'GSM_IS_CLIENT (client)' failed
Mar 28 10:25:12 fenrir gnome-session[15139]: gnome-session-binary[15139]: GLib-CRITICAL: g_hash_table_find: assertion 'version == hash_table->version' failed
Mar 28 10:25:12 fenrir gnome-session[15139]: gnome-session-binary[15139]: WARNING: Lost name on bus: org.gnome.SessionManager

Not sure if there's enough info without a crash file to debug, but putting it here just in case.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu79
Architecture: amd64
CasperMD5CheckResult: unknown
CurrentDesktop: ubuntu:GNOME
DisplayManager: gdm3
DistroRelease: Ubuntu 22.04
InstallationDate: Installed on 2020-06-29 (636 days ago)
InstallationMedia: Ubuntu 20.04 LTS "Focal Fossa" - Release amd64 (20200423)
Package: gnome-shell 42~beta-1ubuntu3
PackageArchitecture: amd64
ProcEnviron:
 TERM=screen
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 5.15.0-23.23-generic 5.15.27
RelatedPackageVersions: mutter-common 42~beta-1ubuntu2
Tags: jammy wayland-session
Uname: Linux 5.15.0-23-generic x86_64
UpgradeStatus: Upgraded to jammy on 2022-01-04 (82 days ago)
UserGroups: adm cdrom dip kvm libvirt lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True

[Heather Ellsworth (hellsworth)]

apport information

[Heather Ellsworth (hellsworth)]

apport information

[Heather Ellsworth (hellsworth)]

apport information

[Heather Ellsworth (hellsworth)]

apport information

[Heather Ellsworth (hellsworth)]

apport information

[Daniel van Vugt (vanvugt)]

If the main issue is:

  gnome-shell[15153]: Connection to xwayland lost

then that suggests the problem was Xwayland crashing so please follow:

  https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment

The "invalid memory" messages are unrelated (bug 1965673).

[Heather Ellsworth (hellsworth)]

Ok it wasn't clear to me if the fault was gnome-shell or xwayland.
Following the instructional link, I do see https://errors.ubuntu.com/user/ID items, but none around this time. The workaround in bug 994921 is outdated and the line it says to comment is no longer in the file... so I'll just see if it happens again.

[Daniel van Vugt (vanvugt)]

I really thought gnome-shell surviving Xwayland crashes was something that was fixed (or scheduled to be fixed) upstream some time ago. But occasionally there are hints in bug reports that it still doesn't recover. Also I just tried it and killing Xwayland does kill gnome-shell too :(

[Daniel van Vugt (vanvugt)]

Turns out both statements are true: gnome-shell is designed to survive Xwayland crashing, and gnome-shell might crash when Xwayland crashes.

In my case:

Mar 29 11:44:48 nine gnome-shell[3392]: Connection to xwayland lost
Mar 29 11:44:48 nine gnome-shell[3392]: Xwayland just died, attempting to recover
...
Mar 29 11:44:48 nine gnome-shell[3392]: Can't create a GtkStyleContext without a display connection
Mar 29 11:44:48 nine gnome-shell[3392]: GNOME Shell crashed with signal 5

So on my system at least, the problem is bug 1949200.

[Heather Ellsworth (hellsworth)]

Thanks for the clarification on their tight coupling! I really hope the crash i saw was some sort of corner case that rarely appears. If I do see it again, I'll let you know.

[Daniel van Vugt (vanvugt)]

Let's assume this was bug 1949200 since I've got to the bottom of that now.