** No longer affects: gnome-session (Ubuntu Bionic)
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
https://bugs.launchpad.net/bugs/1715365
Title:
gnome-session-check-accelerated crashed with SIGSEGV in
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
**
Yeah, we seem to only be getting crash reports from 3.28 (bionic) now...
https://errors.ubuntu.com/problem/32ef08d11dc442f40fddf95eb9a987d2dd02425a
** Also affects: gnome-session (Ubuntu Cosmic)
Importance: Undecided
Status: New
** Also affects: gnome-session (Ubuntu Eoan)
This crash seems to be fixed in this commit, included in gnome-session 3.30.0:
https://github.com/GNOME/gnome-session/commit/3aafcf0f0129e28b5c52f32284f1164a93867ea3
--
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in
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
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 a member of Ubuntu
Desktop Bugs, which is subscribed to gnome-session in Ubuntu.
** Summary changed:
- gnome-session-check-accelerated crashed with SIGSEGV in
g_hash_table_lookup_node()
+ 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()
** Tags
