gnome-session-check-accelerated crashed with SIGSEGV in g_hash_table_lookup_node() from g_hash_table_lookup() from lookup_cached_xatom() from gdk_x11_atom_to_xatom_for_display()

StacktraceTop:
 ?? ()
 g_hash_table_lookup_node (hash_return=<synthetic pointer>, key=0x47, hash_table=0x55f3e4d41b80) at ../../../../glib/ghash.c:379
 g_hash_table_lookup (hash_table=0x55f3e4d41b80, key=key@entry=0x47) at ../../../../glib/ghash.c:1153
 lookup_cached_xatom (atom=0x47, display=0x55f3e4d3e000) at ././gdk/x11/gdkproperty-x11.c:76
 gdk_x11_atom_to_xatom_for_display (display=0x55f3e4d3e000, atom=0x47) at ././gdk/x11/gdkproperty-x11.c:109

Status changed to 'Confirmed' because the bug affects multiple users.

Happens sometimes when I;m trying to switch users. The worst thing about this bug is that it hangs user switching process and I have to press ctrl+alt+f1 to make gdm appear.
This bug is really critical for users that don't know so much about hotkeys, so, please, fix! it asap!

This bug persists in 18.04.

Just ran into this nasty bug in Ubuntu 18.04. Hope it gets fixed soon because i have some users that are non technical people and telling them to CTRL + DEL + F1 is not a great way

It appears this crash might be one of the two top crashes (which look like they might be the same one crash):

https://errors.ubuntu.com/problem/97011086e8272197873e57cacbf4e75b9723824f
https://errors.ubuntu.com/problem/32ef08d11dc442f40fddf95eb9a987d2dd02425a

Such a basic funcionality as switching users is not working since 1.5 years and there is still nobody assigned to that critical issue?

I partly agree. Users don't bother to report the bugs as it is difficult
and as this is free software and complaining feels unjustified. However I
am simply not able to put enough effort to prove my point (will be too busy
for that now). It is incredible that basic functionality is at such a poor
level. Bug appears to an ordinary user so vaguely that bug reporting fails
to show the cause of the problem. The most serious problems have been
somehow fixed, but it is still a shameful quality (standard ubuntu 18.04
clean install few months ago). Often we need to boot to be able to change
the user (sorry if you feel this is spam ... this message was inspired by
one such occasion again).

ke 23. tammik. 2019 klo 21.00 Johanna Müller (<email address hidden>)
kirjoitti:

> Such a basic funcionality as switching users is not working since 1.5
> years and there is still nobody assigned to that critical issue?
>
> --
> You received this bug notification because you are subscribed to a
> duplicate bug report (1772268).
> https://bugs.launchpad.net/bugs/1715365
>
> Title:
> gnome-session-check-accelerated crashed with SIGSEGV in
> g_hash_table_lookup_node() from g_hash_table_lookup() from
> lookup_cached_xatom() from gdk_x11_atom_to_xatom_for_display()
>
> Status in gnome-session package in Ubuntu:
> Confirmed
>
> Bug description:
> Possibly:
>
> https://errors.ubuntu.com/problem/97011086e8272197873e57cacbf4e75b9723824f
>
> https://errors.ubuntu.com/problem/32ef08d11dc442f40fddf95eb9a987d2dd02425a
>
> ---
>
> bug at login
>
> ProblemType: Crash
> DistroRelease: Ubuntu 17.10
> Package: gnome-session-bin 3.25.90-0ubuntu2
> Uname: Linux 4.12.0-041200-generic x86_64
> ApportVersion: 2.20.7-0ubuntu1
> Architecture: amd64
> CurrentDesktop: GNOME-Greeter:GNOME
> Date: Sun Sep 3 09:34:09 2017
> Disassembly: => 0x0: Cannot access memory at address 0x0
> ExecutablePath: /usr/lib/gnome-session/gnome-session-check-accelerated
> InstallationDate: Installed on 2015-04-16 (874 days ago)
> InstallationMedia: Ubuntu 14.10 "Utopic Unicorn" - Release amd64
> (20141022.1)
> ProcCmdline: /usr/lib/gnome-session/gnome-session-check-accelerated
> SegvAnalysis:
> Segfault happened at: 0x0: Cannot access memory at address 0x0
> PC (0x00000000) not located in a known VMA region (needed executable
> region)!
> SegvReason: executing NULL VMA
> Signal: 11
> SourcePackage: gnome-session
> StacktraceTop:
> ()
> g_hash_table_lookup () at /lib/x86_64-linux-gnu/libglib-2.0.so.0
> gdk_x11_atom_to_xatom_for_display () at
> /usr/lib/x86_64-linux-gnu/libgdk-3.so.0
> ()
> __libc_start_main (main=0x55f3e2ce4200, argc=1, argv=0x7ffcebd38af8,
> init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>,
> stack_end=0x7ffcebd38ae8) at ../csu/libc-start.c:291
> Title: gnome-session-check-accelerated crashed with SIGSEGV
> UpgradeStatus: Upgraded to artful on 2017-08-25 (11 days ago)
> UserGroups:
>
> To manage notifications about this bug go to:
>
> https://bugs.launchpad.net/ubuntu/+source/gnome-session/+bug/1715365/+subscriptions
>

This crash seems to be fixed in this commit, included in gnome-session 3.30.0:
https://github.com/GNOME/gnome-session/commit/3aafcf0f0129e28b5c52f32284f1164a93867ea3

Yeah, we seem to only be getting crash reports from 3.28 (bionic) now...
https://errors.ubuntu.com/problem/32ef08d11dc442f40fddf95eb9a987d2dd02425a

The upstream commit is describing the issue being with "X11 with nested wayland" which doesn't seem like a frequent/important scenario. Untargetting from bionic but it can go through rls-bb-incoming process if someone disagrees and also it doesn't stop a SRU to happen if there is an owner