Not succeeded in reproducing this again after rebuilding GNOME Shell with ASAN_OPTIONS=detect_leaks=0 CFLAGS="-fsanitize=address -fsanitize=return -fsanitize=bounds -fsanitize=object-size". I do now manage to trigger debian bug 823216 quite reliably now, with the difference that I can log on again immediately. It is usually the user GNOME Shell and XWayland which crash, but at least once the gdm ones crashed.
[1] https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823216 I trigger this by opening a few applications (Firefox with a few windows seems to make it easier to reproduce) and repeatedly opening and closing the laptop lid. It seems that, as per systemd logind settings this should not trigger a suspend when docked, but occasionally it does. The xwayland termination happens just before this (as observed from an ssh session on my other laptop: I can see the results just before the session stops responding due to the suspension). ** Bug watch added: Debian Bug tracker #823216 https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823216 -- 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/1724259 Title: gnome-shell frozen and using 100% CPU after docking and display configuration change To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1724259/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs