On 06/13/17 19:00, Patrick O'Callaghan wrote:
This has happened to me frequently over the past year, but is
difficult
to pin down. I thought I'd mention it here in case anyone else has seen
it. What happens is this:
1) I run "sudo dnf update".
2) The tracer plugin says I need to restart my session, usually because
some library has changed.
3) I log out (this often crashes kdeinit5).
4) I log in again. This takes longer than usual, giving the impression
that some stuff is still being cleaned up from the previous session.
5) I start working.
6) A minute or so later, I am suddenly thrown out and am back at the
login screen.
7) I log in again and everything is fine.
The journal shows several lines reading:
Attempted to re-run an already running session
These are associated with konsole and kdeinit5. Also yakuake which most
people probably don't have.
It's notable that a) this never happens if I've rebooted the system
between sessions, and b) it seems not to happen if I've delayed a few
minutes before logging in again, even without rebooting.
I haven't poked around further in the journal (too much information)
but I conjecture this may be related to a bad systemd recipe, where
some component is not waiting for a previous instance to terminate.
Any thoughts on what to look for?
Prior to logging out, open a TTY session. Switch back to the GUI
session and logout. Switch to back to the TTY session and see what
processes linger. Find out why... :-) :-)
FWIW, something similar happens to me....but I don't get thrown to a
login screen. If I logout and quickly log back in the speaker icon in
the systray will show as if volume is 0 but no x so not muted and I may
or may not have the ibus icon showing. But after a minute or so they
will come back. Being a sometimes lazy person, I'm just gotten into the
habit when logging out to take the time to get a drink of water or walk
around a bit before logging in again. :-)
--
Fedora Users List - The place to go to speculate endlessly