Am 13.06.2017 um 14:27 schrieb Patrick O'Callaghan:
On Tue, 2017-06-13 at 14:16 +0200, Reindl Harald wrote:
Am 13.06.2017 um 13:51 schrieb Ed Greshko:
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... :-) :-)
there are lingering a lot of processes after logout from KDE and such
dirty bugs are the reason why systemd guys came to crazy solutions like
https://linux.slashdot.org/story/16/05/29/212204/systemd-starts-killing-your-background-processes-by-default
while they if it comes to their own bugs always preach fix them at the
root cause in other software
I should note that I have "KillUserProcesses=yes" in
/etc/systemd/logind.conf, so in theory this shouldn't happen. I may
file a bug against systemd if I can discover which processes are
hanging around
point is that "KillUserProcesses=yes" should not be needed at all and
has terrible side-effects for non 08/15 users just because desktop
managers are broken and don't cleanup their stuff properly
frankly i am tired when update my remote machines and fine there are
updated files in use by processes running as my desktop users while
there is no KDE session at all and i have to kill them always by hand
because otherwise the whole purpose of library updates is broken
on a clean environment "systemctl restart displaymanager" should be
enough to close/restart any process related to GUI sessions
_______________________________________________
kde mailing list -- kde@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to kde-leave@xxxxxxxxxxxxxxxxxxxxxxx
