Arch Linux

emacsomancer

Member

Registered: 2014-09-20

Posts: 211

odd forced "logout"

This has happened several times over the last few months. (Sometimes) When I come to my computer in the morning (which I leave running at night), I find the login screen (XDM). All, or  most, of the applications that were running are still running, though the graphical ones I am unable to access (but I can see in ps aux that they're still active). I've looked through the journal, and the only things that I find that look potentially related are two coredumps

Jun 11 03:42:55 sindhu rsnapshot[30004]: /var/lib/systemd/coredump/
Jun 12 01:49:11 sindhu systemd[1]: Created slice system-systemd\x2dcoredump.slice.
Jun 12 01:49:13 sindhu systemd-coredump[5106]: Process 28517 (cantata) of user 1000 dumped core.
Jun 12 01:49:15 sindhu systemd-coredump[5108]: Process 943 (emacs) of user 1000 dumped core.
Jun 12 03:43:58 sindhu rsnapshot[6098]: /var/lib/systemd/coredump/

Cantata is a QT graphical frontend for mpd. (Emacs, is, of course, emacs.) And indeed neither of these applications are still running in this scenario.

Is there something else I should be looking for?

I checked the journal around the time of these coredumps and found this:

Jun 12 01:49:11 sindhu [884]: pam_unix(xdm:session): session closed for user myuser
Jun 12 01:49:11 sindhu qbittorrent[1773]: The X11 connection broke (error 1). Did the X11 server die?
Jun 12 01:49:11 sindhu cantata[28517]: The X11 connection broke (error 1). Did the X11 server die?
Jun 12 01:49:11 sindhu cantata[28517]: QSocketNotifier: Socket notifiers cannot be enabled or disabled from another thread
Jun 12 01:49:11 sindhu cantata[28517]: QSocketNotifier: Socket notifiers cannot be enabled or disabled from another thread
Jun 12 01:49:11 sindhu cantata[28517]: QSocketNotifier: Invalid socket 19 and type 'Read', disabling...
Jun 12 01:49:11 sindhu kernel: TagHelperIface[28520]: segfault at 7fb1a0922ea8 ip 00007fb4a0539d3d sp 00007fb4862c0b50 error 4 in libQt5Core.so.5.6.0[7fb4a0263000+4bf000]
Jun 12 01:49:11 sindhu systemd[1]: Created slice system-systemd\x2dcoredump.slice.
Jun 12 01:49:11 sindhu systemd[1]: Started Process Core Dump (PID 5104/UID 0).
Jun 12 01:49:12 sindhu systemd[1]: Started Process Core Dump (PID 5107/UID 0).
Jun 12 01:49:13 sindhu systemd-coredump[5106]: Process 28517 (cantata) of user 1000 dumped core.
Jun 12 01:49:15 sindhu systemd-coredump[5108]: Process 943 (emacs) of user 1000 dumped core.

Which makes it look like the coredumps are a consequence rather than a cause of the issue.

But I don't see anything else about xdm or pam in the journal.

How do I proceed?