Bug#945158: if laptop lid is closed during suspend, gdm session is reset upon resume (NVIDIA?)
Hi, I've been seeing the same behavior for the past few weeks (months?), but didn't get around to debugging it. Symptoms match pretty exactly: closing the lid leads to a logout (session crash?); suspending via power button does not. Superficially, this seems considerably more likely to be related to gdm/gnome-screensaver/gnome-session than to systemd. Just installed a new system, restored a few user config files from backup (including ~/.config/dconf) and the issue popped up again. My suggestion would be to reopen and reassign this to a gnome package, so we can keep digging. BTW: my setup is a pretty vanilla wayland gnome session on an intel card. Cheers, Leo
Bug#945158: if laptop lid is closed during suspend, gdm session is reset upon resume (NVIDIA?)
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) Did you spot any message from logind that it behaves wrong? -- 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
Bug#945158: if laptop lid is closed during suspend, gdm session is reset upon resume (NVIDIA?)
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
Bug#945158: if laptop lid is closed during suspend, gdm session is reset upon resume (NVIDIA?)
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
Bug#945158: if laptop lid is closed during suspend, gdm session is reset upon resume (NVIDIA?)
Control: tags -1 + moreinfo Am 20.11.19 um 16:05 schrieb Yaroslav Halchenko: > Package: systemd > Version: 243-7 > Severity: normal > > 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? > - (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. Michael -- 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
