Am 20.11.19 um 19:35 schrieb Yaroslav Halchenko: > > 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
systemd does not tell gdm to restart on suspend/resume. That said, I'm not sure what you mean by "gdm resets prior session completely" -- Why is it that all of the instruments seeking intelligent life in the universe are pointed away from Earth?
signature.asc
Description: OpenPGP digital signature