Am 31.01.24 um 03:55 schrieb Simon Lees:
On 1/31/24 13:04, Bob Rogers wrote:
From: Simon Becherer <simon@becherer.de> Date: Tue, 30 Jan 2024 08:13:08 +0100
Am 29.01.24 um 23:46 schrieb Bob Rogers: > From: Simon Becherer <simon@becherer.de> > Date: Mon, 29 Jan 2024 16:20:17 +0100 > > Hi, > > . . . > > how could i investigate what is here "session3" and still > running? > > thanks, > > simoN > > Try > > journalctl | grep 'New session 3 ' > > (don't forget the trailing space) and see if the timing of when the > session started is any help. If not, looking at what else was logged > around that time might be useful. > > -- Bob Rogers > http://www.rgrjr.com/
hi bob, from "nov 16." up to jan 30. about 30 entry's as i see always around the time when i start my sytem. before nothing . . .
There does seem to be a pattern here . . . it seems that "session 3" is what you get when you first log in under sddm. So it appears that the console logout is not complete. Or that it is complete, but the shutdown somehow doesn't think so.
today i have opend a lot of windows and already closed. so the only thing at this time still open ist /usr/bin/kded5 and usr/bin/startplasma-x11
After logging out? Seems to me those should be gone as well, shouldn't they?
On openSUSE we don't set KillUserProcesses=yes unlike upstream systemd, which means that applications that don't exit cleanly on logout won't be killed. This is because users expect things like tmux to continue running.
From memory if you add KillUserProcesses=yes in /etc/systemd/logind.conf that should force non behaving applications to quit if you don't feel like debugging and fixing whatever apps those are properly.
thanks for the tips, at the moment i tested to log out and inside an other strg+alt+F-key as root in. systemctl status session-3.scope but there was nohting. is this the correct command to find still running things in session 3? or what would be the command? simoN -- www.becherer.de