<html> <head> <base href="https://bugs.freedesktop.org/" /> </head> <body> <div> <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Logging out in VT freezes display + input" href="https://bugs.freedesktop.org/show_bug.cgi?id=88381#c4">Comment # 4</a> on <a class="bz_bug_link bz_status_NEEDINFO " title="NEEDINFO - Logging out in VT freezes display + input" href="https://bugs.freedesktop.org/show_bug.cgi?id=88381">bug 88381</a> from <a class="email" href="mailto:lennart@poettering.net" title="Lennart Poettering <lennart@poettering.net>"> Lennart Poettering</a> <pre>(In reply to amosonn from <a href="show_bug.cgi?id=88381#c3">comment #3</a>) > System does not seem to react to keypresses, at least not as far as display > is concerned; I will check more thoroughly whether keypresses still go > through to the X session, and only display is cut off; however, I think this > is not the case. > > As far as I understand, systemd is, at least in part, responsible for > managing session switches, incl. VT switches. Therefore, since the system > still runs (audio output from online streaming continues normally), I assume > that systemd somehow denies the X session of access to the display and > keyboard, but still intercepts keypresses so a switch to another VT is also > impossible. logind subscribes to VT chnages, and can issue them. But VT change keypress are handled by your display server or by the kernel, logind is not involved. > As I have mentioned, sshd does not completely hang; it does respond to a > connection, but fails to open a new session (at least as far as can be > inferred from the output on the remote host). As journald logs stop after > the fatal logout, I can't tell for sure what happens. This feels like a kernel hang of some kind, as userspace appears to be stuck entirely. Note that pam_systemd on most distros is included in the PAM stack as non-fatal. Thus, whatever happens, if logind is stuck, you can still log in. Given that you cannot login this is likely caused by something else, not logind. > Lastly, this might be related to some issue with getty. However, even in the > case where getty hangs, I'd expect systemd to eventually "forcefully" > rescind access to display and keyboard and transfer it to the requested VT > (that of the X session). Well, if the entire userspace is dead (which appears to be the case), then logind is dead too.</pre> </div> <hr> You are receiving this mail because: <ul> <li>You are the QA Contact for the bug.</li> <li>You are the assignee for the bug.</li> </ul> </body> </html>