On 05/21/18 23:09, Patrick O'Callaghan wrote:
On Mon, 2018-05-21 at 10:06 +0930, Tim via users wrote:
> There are
> programs that just don't terminate every time when I log out. Various
> system/desktop daemons, sometimes web browsers.
Possibly unrelated, but I sometimes - not always - find that after
updating (using dnf with the tracer plugin) I'm advised to restart my
session, then on logging out and in I'm suddenly forced out again after
a short time, usually less than a minute.
FWIW, if you investigate a little I think you'd find that for every user that logs-in
for a GUI session there will be about 9+ processes that are left running and remain
running. It seems these processes are then reused on subsequent logins by the same
uid. I suppose this may be done to speed-up subsequent logins.
So, those processes may potentially keep copies of libraries that have been updated
and (guessing) clashes happen with new processes with new libraries.
Therefore, I don't logout/login after updates. If anything, I reboot. In my case a
reboot takes about 12 seconds so I'm not bothered by it.
I was considering asking on the KDE list if there is anyway to tell the system to end
all users processes after logout.
(Also, and only in this specific situation, Firefox forgets all the
windows it had open except one, but I had the same problem with
Chrome).
On logging in *again*, everything is fine. It's as if the session
manager isn't waiting long enough for things to terminate gracefully
before presenting the login screen, then when they do terminate it
panics. I haven't managed to narrow it down yet.
[egreshko@acer ~]$ date
Tue May 22 15:15:23 CST 2018
[egreshko@acer ~]$ ps -eaf | grep 14:02 | grep maria | wc
9 83 828
[egreshko@acer ~]$ finger
Login Name Tty Idle Login Time Office Office Phone Host
egreshko Ed Greshko pts/1 May 22 14:03
(192.168.2.190)
and "maria" has been logged-out of the GUI for over an hour.
--
Conjecture is just a conclusion based on incomplete information. It isn't a fact.