It just happened, so attached the crash file that was generated. NB: gnome-shell 3.26.1-0ubuntu2 mutter 3.26.1-1 libmutter-1-0 3.26.1-1
NB: I notice there's also a libmutter-0-0 installed, possibly a hangover from the original zesty install. but ldd $(which gnome-shell) indicates it's linked to libmutter-1.so.0 so it's presumably irrelevant. I've now removed it anyway. This was a bit of a messy event. It went something like this: Attempted to wake system (from displaysleep, wasn't suspended) It appeared at first to work! My session was there. But the displays config was wrong. I noticed that my 4K monitor had (again, I think it's *its* problem) woken up thinking it's a 1440p monitor. As this is usually fixed by powercycling it, I did so. The second monitor (actually the first in discovery order), which is *actually* a 1440p monitor, also went to sleep. Power-cycling *it* woke them both up, (I think; things got confusing) but at that point it came back to the gdm login screen. So I'm guessing around then was where the gnome-shell crash happened. Often it's simpler than that. I wake the system up, it comes up logged- out. ** Attachment added: "_usr_bin_gnome-shell.1000.crash" https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+attachment/4967524/+files/_usr_bin_gnome-shell.1000.crash -- 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/1720149 Title: gnome-shell segv on wake from display or system sleep To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1720149/+subscriptions -- desktop-bugs mailing list desktop-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/desktop-bugs
