as stop job is running of session 3 for user....
Hi, since a couple of weeks always when i try to shutdown my tumbleweed (not actual updated, so an update is not the case of the problem) a delay for the shutdown: "a stop job is running for session 3 of user simon" i am user "simon" and i have before closed kde regularly with the shut down option and nothing left open. its a "normal" desktop kde system, with connections to and from it, inside the lan over nfs and sometimes over ssh. but the most times 3 tumbleweed computers who are running inside this lan who have theoretically access, i and my wife are the operators, so nobody should have "logged in" when i shut down. from outside the internet there should be nothing open to come in to the lan. how could i investigate what is here "session3" and still running? thanks, simoN -- www.becherer.de
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/
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. who -u shows tty2 and pts/0 and pts/1 at this time i will tomorrow morining ps fax|grep number at the processes startet at this time and look if i see someting. 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 i checked at the moment zypper history but there is nothing installed 2023-11-x at 2023-11-14 i see inside yast2 y2log a lot of entry's, but i do not know if i have there something installed, or only checked. - what shoul i search there? simoN -- www.becherer.de
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? i checked at the moment zypper history but there is nothing installed 2023-11-x at 2023-11-14 i see inside yast2 y2log a lot of entry's, but i do not know if i have there something installed, or only checked. - what shoul i search there? simoN -- www.becherer.de That would be the place to check if you know that zypper has failed you; I don't think it will help here. In any case, I would try logging out from KDE, then logging in on an xterm as root, and seeing if there are still any "simom" processes lying around, and check that the "Removed session 3" stuff in the log is complete. If all that looks good, then the next question would be to figure out how shutdown determines that a session is still live . . . -- Bob ------------------------------------------------------------------------ root@orion> journalctl | grep -E 'New session [13] |^-- Boot' -- Boot 8299a9100c914b90a90fd284c3b7fd49 -- Sep 04 17:21:08 orion systemd-logind[841]: New session 1 of user sddm. Sep 04 17:21:52 orion systemd-logind[841]: New session 3 of user rogers. -- Boot 536d470095fb486382d904f5b9a0083c -- Sep 17 13:21:11 orion systemd-logind[848]: New session 1 of user sddm. Sep 17 13:21:21 orion systemd-logind[848]: New session 3 of user rogers. -- Boot 4a5cc6526003429dabf0a45d2915bad5 -- Sep 30 20:12:23 orion systemd-logind[846]: New session 1 of user sddm. Sep 30 20:12:48 orion systemd-logind[846]: New session 3 of user rogers. -- Boot f0957f2a879840129220ef4c494d48e2 -- Oct 10 14:33:01 orion systemd-logind[847]: New session 1 of user sddm. Oct 10 14:41:36 orion systemd-logind[847]: New session 3 of user rogers. -- Boot 7e7753f40a694dc7b06bbc1fe2407dd1 -- Oct 18 20:38:24 orion systemd-logind[847]: New session 1 of user sddm. Oct 18 20:40:26 orion systemd-logind[847]: New session 3 of user rogers. -- Boot 762c1c5c715144deb362f8ec9b87dfc2 -- Oct 19 12:53:13 orion systemd-logind[827]: New session 1 of user sddm. Oct 19 12:56:26 orion systemd-logind[827]: New session 3 of user rogers. -- Boot 476d5a0ac76b4ffbaa082e0b29e7edcb -- Oct 20 13:12:45 orion systemd-logind[839]: New session 1 of user sddm. Oct 20 13:14:01 orion systemd-logind[839]: New session 3 of user rogers. -- Boot 2840613d982a4fe3a74bc2f5b20b46ee -- Oct 28 19:42:03 orion systemd-logind[836]: New session 1 of user sddm. Oct 28 19:50:45 orion systemd-logind[836]: New session 3 of user rogers. -- Boot 2306365c3f9d49f5843cb5c4ce8f618f -- Nov 10 21:39:01 orion systemd-logind[852]: New session 1 of user sddm. Nov 10 21:39:14 orion systemd-logind[852]: New session 3 of user rogers. -- Boot 4918d2031965461ebd1a10267d96737b -- Nov 17 18:56:03 orion systemd-logind[836]: New session 1 of user sddm. Nov 17 18:58:06 orion systemd-logind[836]: New session 3 of user rogers. -- Boot c8bf0043d5f3466ab431fe0328a71337 -- Nov 21 18:54:50 orion systemd-logind[831]: New session 1 of user sddm. Nov 21 18:56:28 orion systemd-logind[831]: New session 3 of user rogers. -- Boot 84ca5f4e807c462c96a8e37afba1bd1e -- Nov 29 16:45:50 orion systemd-logind[781]: New session 1 of user sddm. Nov 29 16:46:05 orion systemd-logind[781]: New session 3 of user rogers. -- Boot 50c9b4a1640e4d8b9ac1ae6f8b06113f -- Dec 01 17:12:31 orion systemd-logind[835]: New session 1 of user sddm. Dec 01 17:12:48 orion systemd-logind[835]: New session 3 of user rogers. -- Boot acb9eb08d5ad427b938e77d81fc0d430 -- Dec 03 16:31:51 orion systemd-logind[786]: New session 1 of user sddm. Dec 03 16:33:06 orion systemd-logind[786]: New session 3 of user rogers. -- Boot a39c0dd0ecc146beb4537f73c2825306 -- Dec 27 15:10:39 orion systemd-logind[780]: New session 1 of user sddm. Dec 27 15:17:09 orion systemd-logind[780]: New session 3 of user rogers. -- Boot c77b10993c1e411295734a3e289a2ac1 -- Jan 04 15:06:12 orion systemd-logind[785]: New session 1 of user sddm. Jan 04 15:07:04 orion systemd-logind[785]: New session 3 of user rogers. -- Boot ac3e12786e2b44b4bfaba726ebe63bbe -- Jan 06 10:49:47 orion systemd-logind[848]: New session 1 of user sddm. Jan 06 10:50:00 orion systemd-logind[848]: New session 3 of user rogers. -- Boot 387651c31865462dbcb63c189ac1617d -- Jan 13 23:30:15 orion systemd-logind[844]: New session 1 of user sddm. Jan 13 23:39:39 orion systemd-logind[844]: New session 3 of user rogers. -- Boot b2305e042778428086887fd3bd32fdcc -- Jan 22 17:01:14 orion systemd-logind[786]: New session 1 of user sddm. Jan 22 17:01:58 orion systemd-logind[786]: New session 3 of user rogers. root@orion>
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. -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
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
On Wed, Jan 31, 2024 at 9:41 AM Simon Becherer <simon@becherer.de> wrote: ...
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?
Show full output of systemd-cgls
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1 Sidetracking. El 2024-01-31 a las 13:09 +0300, Andrei Borzenkov escribió:
Show full output of
systemd-cgls
Interesting command. I saw something curious on mine (not related to the OP problem): Control group /: ├─user.slice │ └─user-1000.slice │ │ ├─app.slice │ │ │ ├─xdg-document-portal.service │ │ │ │ ├─ 6212 /usr/lib/xdg-document-portal │ │ │ │ └─ 6220 fusermount -o rw,nosuid,nodev,fsname=portal,auto_unmount,subtype=portal -- /run/user/1000/doc Indeed, there is a mount there: cer@Telcontar:~> tree /run/user/1000/doc /run/user/1000/doc └── by-app 1 directory, 0 files cer@Telcontar:~> Curious! What would be the purpose? - -- Cheers, Carlos E. R. (from openSUSE 15.4 x86_64 at Telcontar) -----BEGIN PGP SIGNATURE----- iHoEARECADoWIQQZEb51mJKK1KpcU/W1MxgcbY1H1QUCZbo2kBwccm9iaW4ubGlz dGFzQHRlbGVmb25pY2EubmV0AAoJELUzGBxtjUfVep0AnRYTgnSy6GprsWtS/TrE KH49UqX7AJsE9vFhl4iLcq8ynXITQMeT0Bsdow== =O2bd -----END PGP SIGNATURE-----
Am 31.01.24 um 11:09 schrieb Andrei Borzenkov:
On Wed, Jan 31, 2024 at 9:41 AM Simon Becherer <simon@becherer.de> wrote: ...
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?
Show full output of
systemd-cgls
here is the output of systemd-cgls (short after log in to plasma) https://paste.opensuse.org/546b35aebbba but its interesting, since i tried a couple of days first log out of the plasma desktop, strg+alt+Fx and check there with the commands here mentioned and shut down, my system shuts down normal. even when i shut down today without first log out everything normal. only thing i have done in the last days, kill some processes with the kill command, but i do not think this has anything to do after a shut down and start new. after starting plasma, and session-status the session 3 seems to be the normal session: loginctl session-status -> WITH or WITHOUT "3" 3 - simon (1000) Since: Sun 2024-02-04 15:16:19 CET; 4min 7s ago Leader: 2022 (sddm-helper) Seat: seat0; vc2 TTY: tty2 Service: sddm; type x11; class user Desktop: KDE State: active Unit: session-3.scope ├─2022 /usr/libexec/sddm/sddm-helper --socket /tmp/sddm-auth-05ed13a2-c875-41f6-abc9-95b6c2884dd8 --id 1 --start /usr/bin/startplasma-x11 --user simon ├─2043 /usr/bin/kwalletd5 --pam-login 13 14 ├─2044 /usr/bin/startplasma-x11 ├─2113 /usr/bin/ssh-agent /usr/bin/gpg-agent --sh --daemon --keep-display /usr/libexec/xinit/xinitrc └─2114 /usr/bin/gpg-agent --sh --daemon --keep-display /usr/libexec/xinit/xinitrc Feb 04 15:16:19 becherer2.site systemd[1]: Started Session 3 of User simon. Feb 04 15:16:19 becherer2.site startplasma-x11[2044]: org.kde.plasma.libkworkspace: Skipping syncing of environment variable "BASH_FUNC_mc%%" as name contains unsupported characters Feb 04 15:16:20 becherer2.site startplasma-x11[2044]: org.kde.plasma.libkworkspace: Skipping syncing of environment variable "BASH_FUNC_mc%%" as name contains unsupported characters Feb 04 15:16:21 becherer2.site startplasma-x11[2044]: kf.coreaddons.kaboutdata: QGuiApplication::applicationDisplayName "" is out-of-sync with KAboutData::applicationData().displayName> Feb 04 15:16:21 becherer2.site startplasma-x11[2044]: kf.coreaddons.kaboutdata: QGuiApplication::applicationDisplayName "" is out-of-sync with KAboutData::applicationData().displayName> shows me this. so at the moment i think i could not do anything to figure out what was not ok, andrei, did you see somthing not normal inside the output of systemd-cgls ? simoN -- www.becherer.de
On 04.02.2024 17:40, Simon Becherer wrote:
Am 31.01.24 um 11:09 schrieb Andrei Borzenkov:
On Wed, Jan 31, 2024 at 9:41 AM Simon Becherer <simon@becherer.de> wrote: ...
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?
Show full output of
systemd-cgls
here is the output of systemd-cgls (short after log in to plasma)
And how is it going to help? The question is not what is running in your normal session, but what is left when session is stopped.
https://paste.opensuse.org/546b35aebbba
but its interesting, since i tried a couple of days first log out of the plasma desktop, strg+alt+Fx and check there with the commands here mentioned and shut down, my system shuts down normal. even when i shut down today without first log out everything normal. only thing i have done in the last days, kill some processes with the kill command, but i do not think this has anything to do after a shut down and start new.
after starting plasma, and session-status the session 3 seems to be the normal session:
loginctl session-status -> WITH or WITHOUT "3" 3 - simon (1000) Since: Sun 2024-02-04 15:16:19 CET; 4min 7s ago Leader: 2022 (sddm-helper) Seat: seat0; vc2 TTY: tty2 Service: sddm; type x11; class user Desktop: KDE State: active Unit: session-3.scope ├─2022 /usr/libexec/sddm/sddm-helper --socket /tmp/sddm-auth-05ed13a2-c875-41f6-abc9-95b6c2884dd8 --id 1 --start /usr/bin/startplasma-x11 --user simon ├─2043 /usr/bin/kwalletd5 --pam-login 13 14 ├─2044 /usr/bin/startplasma-x11 ├─2113 /usr/bin/ssh-agent /usr/bin/gpg-agent --sh --daemon --keep-display /usr/libexec/xinit/xinitrc └─2114 /usr/bin/gpg-agent --sh --daemon --keep-display /usr/libexec/xinit/xinitrc
Feb 04 15:16:19 becherer2.site systemd[1]: Started Session 3 of User simon. Feb 04 15:16:19 becherer2.site startplasma-x11[2044]: org.kde.plasma.libkworkspace: Skipping syncing of environment variable "BASH_FUNC_mc%%" as name contains unsupported characters Feb 04 15:16:20 becherer2.site startplasma-x11[2044]: org.kde.plasma.libkworkspace: Skipping syncing of environment variable "BASH_FUNC_mc%%" as name contains unsupported characters Feb 04 15:16:21 becherer2.site startplasma-x11[2044]: kf.coreaddons.kaboutdata: QGuiApplication::applicationDisplayName "" is out-of-sync with KAboutData::applicationData().displayName> Feb 04 15:16:21 becherer2.site startplasma-x11[2044]: kf.coreaddons.kaboutdata: QGuiApplication::applicationDisplayName "" is out-of-sync with KAboutData::applicationData().displayName>
shows me this.
so at the moment i think i could not do anything to figure out what was not ok, andrei, did you see somthing not normal inside the output of systemd-cgls ?
simoN
Am 04.02.24 um 16:23 schrieb Andrei Borzenkov:
On 04.02.2024 17:40, Simon Becherer wrote:
Am 31.01.24 um 11:09 schrieb Andrei Borzenkov:
On Wed, Jan 31, 2024 at 9:41 AM Simon Becherer <simon@becherer.de> wrote: ...
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?
Show full output of
systemd-cgls
here is the output of systemd-cgls (short after log in to plasma)
And how is it going to help? The question is not what is running in your normal session, but what is left when session is stopped.
yes you are right, but at the moment there is nothing left of session 3 (as i think) shutdown works as normal. after logging out of graphic: loginctl session-status 7 - root (0) <------> Since: Sun 2024-02-04 16:28:58 CET; 1min 18s ago <------> Leader: 1629 (login) <------> Seat: seat0; vc1 <------> TTY: tty1 <------> Service: login; type tty; class user <------> State: active <------> Unit: session-7.scope <------><------> ├─1629 "login -- root" <------><------> ├─7054 -bash <------><------> └─7098 loginctl session-status Feb 04 16:28:59 becherer2.site systemd[1]: Started Session 7 of User root. loginctl session-status 3 failed to get session path: no session 3 known so this is the systemd-cgls after logging out of graphical session: https://paste.opensuse.org/62b6de060aca think this will not help :-(( simoN
https://paste.opensuse.org/546b35aebbba
but its interesting, since i tried a couple of days first log out of the plasma desktop, strg+alt+Fx and check there with the commands here mentioned and shut down, my system shuts down normal. even when i shut down today without first log out everything normal. only thing i have done in the last days, kill some processes with the kill command, but i do not think this has anything to do after a shut down and start new.
after starting plasma, and session-status the session 3 seems to be the normal session:
loginctl session-status -> WITH or WITHOUT "3" 3 - simon (1000) Since: Sun 2024-02-04 15:16:19 CET; 4min 7s ago Leader: 2022 (sddm-helper) Seat: seat0; vc2 TTY: tty2 Service: sddm; type x11; class user Desktop: KDE State: active Unit: session-3.scope ├─2022 /usr/libexec/sddm/sddm-helper --socket /tmp/sddm-auth-05ed13a2-c875-41f6-abc9-95b6c2884dd8 --id 1 --start /usr/bin/startplasma-x11 --user simon ├─2043 /usr/bin/kwalletd5 --pam-login 13 14 ├─2044 /usr/bin/startplasma-x11 ├─2113 /usr/bin/ssh-agent /usr/bin/gpg-agent --sh --daemon --keep-display /usr/libexec/xinit/xinitrc └─2114 /usr/bin/gpg-agent --sh --daemon --keep-display /usr/libexec/xinit/xinitrc
Feb 04 15:16:19 becherer2.site systemd[1]: Started Session 3 of User simon. Feb 04 15:16:19 becherer2.site startplasma-x11[2044]: org.kde.plasma.libkworkspace: Skipping syncing of environment variable "BASH_FUNC_mc%%" as name contains unsupported characters Feb 04 15:16:20 becherer2.site startplasma-x11[2044]: org.kde.plasma.libkworkspace: Skipping syncing of environment variable "BASH_FUNC_mc%%" as name contains unsupported characters Feb 04 15:16:21 becherer2.site startplasma-x11[2044]: kf.coreaddons.kaboutdata: QGuiApplication::applicationDisplayName "" is out-of-sync with KAboutData::applicationData().displayName> Feb 04 15:16:21 becherer2.site startplasma-x11[2044]: kf.coreaddons.kaboutdata: QGuiApplication::applicationDisplayName "" is out-of-sync with KAboutData::applicationData().displayName>
shows me this.
so at the moment i think i could not do anything to figure out what was not ok, andrei, did you see somthing not normal inside the output of systemd-cgls ?
simoN
-- HINWEIS: Wenn Sie diese "reintext" Mail mit Outlook oeffnen kann es sein, dass Outlook diese Mail nicht korrekt formatiert anzeigt. Das ist ein Fehler oder eine Misskonfiguration in Outlook. Informieren Sie ihren Systemadministrator. (von "Wenn... bis ... Systemadministrator." sind das hier 6 Zeilen.) (Zeilenumbruchzeichen ist HEX 0A) ========== B e c h e r e r GmbH Sondermaschinenbau Mauermattenstrasse 22 79183 Waldkirch Germany Tel.: (+49) (0)7681 3134 Fax: (+49) (0)7681 4378 Mail: info@becherer.de Web: www.becherer.de USt-ID-Nr.: DE 814912198 Registergericht: Freiburg HRB 701860 Geschaeftsfuehrer: Dipl.-Ing. (FH), EWE Simon H. Becherer Gerichtsstand / Sitz: Waldkirch Es gelten ausschliesslich unsere allgemeinen Liefer- und Zahlungsbedingungen / Einkaufsbedingungen: www.becherer.de/AGB
On 04.02.2024 18:43, Simon Becherer wrote:
Am 04.02.24 um 16:23 schrieb Andrei Borzenkov:
On 04.02.2024 17:40, Simon Becherer wrote:
Am 31.01.24 um 11:09 schrieb Andrei Borzenkov:
On Wed, Jan 31, 2024 at 9:41 AM Simon Becherer <simon@becherer.de> wrote: ...
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?
Show full output of
systemd-cgls
here is the output of systemd-cgls (short after log in to plasma)
And how is it going to help? The question is not what is running in your normal session, but what is left when session is stopped.
yes you are right, but at the moment there is nothing left of session 3 (as i think) shutdown works as normal. after logging out of graphic:
loginctl session-status 7 - root (0) <------> Since: Sun 2024-02-04 16:28:58 CET; 1min 18s ago <------> Leader: 1629 (login) <------> Seat: seat0; vc1 <------> TTY: tty1 <------> Service: login; type tty; class user <------> State: active <------> Unit: session-7.scope <------><------> ├─1629 "login -- root" <------><------> ├─7054 -bash <------><------> └─7098 loginctl session-status
Feb 04 16:28:59 becherer2.site systemd[1]: Started Session 7 of User root.
loginctl session-status 3
failed to get session path: no session 3 known
so this is the systemd-cgls after logging out of graphical session:
https://paste.opensuse.org/62b6de060aca
think this will not help :-((
simoN
https://paste.opensuse.org/546b35aebbba
but its interesting, since i tried a couple of days first log out of the plasma desktop, strg+alt+Fx and check there with the commands here mentioned and shut down, my system shuts down normal. even when i shut down today without first log out everything normal. only thing i have done in the last days, kill some processes with the kill command, but i do not think this has anything to do after a shut down and start new.
after starting plasma, and session-status the session 3 seems to be the normal session:
loginctl session-status -> WITH or WITHOUT "3" 3 - simon (1000) Since: Sun 2024-02-04 15:16:19 CET; 4min 7s ago Leader: 2022 (sddm-helper) Seat: seat0; vc2 TTY: tty2 Service: sddm; type x11; class user Desktop: KDE State: active Unit: session-3.scope ├─2022 /usr/libexec/sddm/sddm-helper --socket /tmp/sddm-auth-05ed13a2-c875-41f6-abc9-95b6c2884dd8 --id 1 --start /usr/bin/startplasma-x11 --user simon ├─2043 /usr/bin/kwalletd5 --pam-login 13 14 ├─2044 /usr/bin/startplasma-x11 ├─2113 /usr/bin/ssh-agent /usr/bin/gpg-agent --sh --daemon --keep-display /usr/libexec/xinit/xinitrc └─2114 /usr/bin/gpg-agent --sh --daemon --keep-display /usr/libexec/xinit/xinitrc
Feb 04 15:16:19 becherer2.site systemd[1]: Started Session 3 of User simon. Feb 04 15:16:19 becherer2.site startplasma-x11[2044]: org.kde.plasma.libkworkspace: Skipping syncing of environment variable "BASH_FUNC_mc%%" as name contains unsupported characters Feb 04 15:16:20 becherer2.site startplasma-x11[2044]: org.kde.plasma.libkworkspace: Skipping syncing of environment variable "BASH_FUNC_mc%%" as name contains unsupported characters Feb 04 15:16:21 becherer2.site startplasma-x11[2044]: kf.coreaddons.kaboutdata: QGuiApplication::applicationDisplayName "" is out-of-sync with KAboutData::applicationData().displayName> Feb 04 15:16:21 becherer2.site startplasma-x11[2044]: kf.coreaddons.kaboutdata: QGuiApplication::applicationDisplayName "" is out-of-sync with KAboutData::applicationData().displayName>
shows me this.
so at the moment i think i could not do anything to figure out what was not ok, andrei, did you see somthing not normal inside the output of systemd-cgls ?
simoN
Yes, there are no processes of user 1000. Does the problem happen during shutdown when you do not logout first? Does the problem happen when you do logout first?
Am 04.02.24 um 17:02 schrieb Andrei Borzenkov:
Yes, there are no processes of user 1000. Does the problem happen during shutdown when you do not logout first? Does the problem happen when you do logout first?
no, at the moment, as i wrote, the problem disappeared in the same way it appeared :-((( if it comes back i will try to use the commands and will mail here again. simoN -- www.becherer.de
On 1/30/24 01:50, Simon Becherer wrote:
Hi,
since a couple of weeks always when i try to shutdown my tumbleweed (not actual updated, so an update is not the case of the problem) a delay for the shutdown:
"a stop job is running for session 3 of user simon"
i am user "simon" and i have before closed kde regularly with the shut down option and nothing left open.
its a "normal" desktop kde system, with connections to and from it, inside the lan over nfs and sometimes over ssh. but the most times 3 tumbleweed computers who are running inside this lan who have theoretically access, i and my wife are the operators, so nobody should have "logged in" when i shut down. from outside the internet there should be nothing open to come in to the lan.
how could i investigate what is here "session3" and still running?
sudo systemctl status session-3.scope I just created a session-3 by sshing in from a second machine, it looks something like this ├─session-3.scope │ ├─2250 "sshd: simon [priv]" │ ├─2252 "sshd: simon@pts/15" │ └─2253 -fish sudo systemctl status will list all users so you can work out who the session belongs to by looking at something like this. └─user.slice └─user-1000.slice ├─session-1.scope │ ├─ 727 /opt/hexchat/bin/hexchat -- Simon Lees (Simotek) http://simotek.net Emergency Update Team keybase.io/simotek SUSE Linux Adelaide Australia, UTC+10:30 GPG Fingerprint: 5B87 DB9D 88DC F606 E489 CEC5 0922 C246 02F0 014B
On Tue, Jan 30, 2024 at 11:43 AM Simon Lees <sflees@suse.de> wrote:
On 1/30/24 01:50, Simon Becherer wrote:
Hi,
since a couple of weeks always when i try to shutdown my tumbleweed (not actual updated, so an update is not the case of the problem) a delay for the shutdown:
"a stop job is running for session 3 of user simon"
i am user "simon" and i have before closed kde regularly with the shut down option and nothing left open.
its a "normal" desktop kde system, with connections to and from it, inside the lan over nfs and sometimes over ssh. but the most times 3 tumbleweed computers who are running inside this lan who have theoretically access, i and my wife are the operators, so nobody should have "logged in" when i shut down. from outside the internet there should be nothing open to come in to the lan.
how could i investigate what is here "session3" and still running?
sudo systemctl status session-3.scope
I just created a session-3 by sshing in from a second machine, it looks something like this
├─session-3.scope │ ├─2250 "sshd: simon [priv]" │ ├─2252 "sshd: simon@pts/15" │ └─2253 -fish
loginctl session-status 3 shows the same information without needing to know implementation details (scopes, slices, etc) or how exactly they are named. The practical problem is that you need to get this list when the system is shutting down.
sudo systemctl status will list all users so you can work out who the session belongs to by looking at something like this.
└─user.slice └─user-1000.slice ├─session-1.scope │ ├─ 727 /opt/hexchat/bin/hexchat
Do you mean systemd-cgls? Because "systemctl status" most certainly does not show it.
participants (5)
-
Andrei Borzenkov -
Bob Rogers -
Carlos E. R. -
Simon Becherer -
Simon Lees