Bug 749962
| Summary: | systemd-logind - session removed after resume from ram (suspend to ram, polkitd) | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Thomas Meyer <thomas.mey> |
| Component: | systemd | Assignee: | systemd-maint |
| Status: | CLOSED NOTABUG | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | medium | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 16 | CC: | johannbg, johannbg, lpoetter, metherid, mschmidt, notting, plautrba, systemd-maint |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i686 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2012-01-29 15:44:36 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Thomas Meyer
2011-10-29 09:16:13 UTC
What makes you think systemd is involved or even responsible here? Right now systemd has no role in suspending the system. correct, systemd has no role in suspending. but after suspending the machine via a ssh connection with "sudo pm-suspend" with the same user as the current X session user, in the resume phase I see this message: "Oct 29 10:31:47 localhost systemd-logind[581]: Removed session 21." and my X session is thrown away and I need to login again. I don't know if this is always the case when suspending via a remote ssh session. I will test this. It hit me twice since the fedora 16 upgrade. and when I remember correctly both times I did a remote suspend via ssh. normal local suspend to ram via works correctly and doesn't kill my X session. Well, the "Removed session 21" messages is probably more symptom than reason of your problem. My guess is that X crashes or something like that, so please check if you find any log messages pointing to something like that. Also, was session 21 in that case an X session, or the ssh session? If it's the SSH session and you suspended from remote, then it's kinda expected that it goes away as soon as you resume. Session 21 was the X session: Oct 27 22:10:08 localhost systemd-logind[581]: New session 21 of user thomas. Oct 27 22:10:08 localhost systemd-logind[581]: Linked /tmp/.X11-unix/X0 to /run/user/thomas/X11/display. and Session 23 was probably the ssh session: Oct 29 00:45:11 localhost systemd-logind[581]: New session 23 of user thomas. Oct 29 00:45:26 localhost kernel: [76410.689259] PM: Syncing filesystems ... done. Oct 29 10:31:41 localhost kernel: [76411.299154] Freezing user space processes ... (elapsed 0.03 seconds) done. I grep'ed for backtraces in the Xorg log, but found nothing . also no crashes captured by abrtd. I just suspended from a ssh session, but resume didn't kill my X session, but I didn't wait many hours, just a few minutes. I will try again with a few hours gap between a ssh remote suspend and resume and see if this happens again. "Xorg.0.old" log file also indicates no crash: startup: [ 44582.231] (==) Log file: "/var/log/Xorg.0.log", Time: Thu Oct 27 22:09:42 2011 ->which matches above login time. closure, i.e. last entry in log file: [ 76424.698] Server terminated successfully (0). Closing log file. Closing this as notabug feel free to reopen this if this a still an issue and is relevant to systemd Thanks |