On Wed, 20 Nov 2019, Michael Biebl wrote: > > Problem statement:
> > if laptop lid is closed after suspend is initiated (via keyboard > > shortcut), but before laptop actually is suspended, then upon resume > > multiple > > things happen > > - (seems to be 100% reproducible): gdm resets prior session completely. > What exactly do you mean by that? If gdm behaves unexpectedly, why is > this a systemd issue? primarily because (I could be wrong) suspend/resume is instrumented via systemd (and systemd-sleep) in particular. And I felt that there is some (incorrect) interaction between all the components (systemd-sleep, systemd-logind) participating in the game. I do not spot any explicit message from gdm in the logs which would hint that it behaves unexpectedly. It feels more like some powers from above (systemd) instruct it to restart or smth like that. but I could be totally wrong... please advise > > - (50%): some fonts get screwed up (sorry - no screenshot) > That's most likely a driver or kernel issue, but not systemd. > > - (33%): some (e.g. Super+Return) custom (gnome keyboard shortcuts > > settings) keyboard shortcuts not in effect, and even though listed among > > Keyboard Shortcuts. > Does not seem to be a systemd issue. Indeed. I mentioned those as just additional symptoms for the main problem with hope they could help to troubleshoot. -- Yaroslav O. Halchenko Center for Open Neuroscience http://centerforopenneuroscience.org Dartmouth College, 419 Moore Hall, Hinman Box 6207, Hanover, NH 03755 Phone: +1 (603) 646-9834 Fax: +1 (603) 646-1419 WWW: http://www.linkedin.com/in/yarik
