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?