On Fri, 27 Nov 2015 00:29:33 +0100 Michael Biebl wrote: > Am 27.11.2015 um 00:16 schrieb Francesco Poli: [...] > > Could you please specify the exact steps needed to obtain the log you > > would like to see? > > A Xorg.0.log and a journalctl -alb log might be helpful.
These two logs are attached. They were taken just after reproducing the bug from a newly created SSH session. I hope these logs may help in understanding what's going on: I see some evdev errors in Xorg.0.log and a backtrace. Moreover I see some unclear (at least to me) messages from systemd-logind. By the way, from within the SSH session I could close the X session by just quitting Fluxbox with: $ killall -TERM fluxbox After that, although my X session was gone, I could regain control of the input devices (keyboard and mouse were back to normal) and I could start a new X session from the console (TTY1). In other words, a reboot was not strictly needed in order for the system to come back to a normal working state. [...] > To me this sounds like an X problem. It's possible, even though I cannot understand how X could be blamed for the automatic switch back from TTY2 to TTY1 (which is occupied by the X session). On the other hand, it's more than plausible that the issue with ignored input devices may be X's fault. > Which Xorg version do you use? The one currently in Debian testing: $ dpkg -l | grep xserver-xorg-core | cut -c 1-60 ii xserver-xorg-core 2:1.17.3-2 -- http://www.inventati.org/frx/ There's not a second to spare! To the laboratory! ..................................................... Francesco Poli . GnuPG key fpr == CA01 1147 9CD2 EFDF FB82 3925 3E1C 27E1 1F69 BFFE
Xorg.0.log.gz
Description: application/gzip
journalctl.log.gz
Description: application/gzip
pgpQYtp8SqGLi.pgp
Description: PGP signature
