Actually i’m really afraid what’s going on at my manjaro install. for a longer timer now the shutdown is always delayed with the message "“a stop job is running for session 2 of user … 1m30s…”. i checked with “journalctrl --list-catalog” and i’m getting this output:
there is something weird with the “Unit” and i’m more than afraid. i need any help to sort this out.
0027229ca0644181a76c4e92458afa2e systemd: One or more messages could not be forwarded to syslog
0e4284a0caca4bfc81c0bb6786972673 systemd: Unit skipped
1675d7f172174098b1108bf8c7dc8f5d systemd: DNSSEC validation failed
1b3bb94037f04bbf81028e135a12d293 systemd: Failed to generate valid unit name from path '@MOUNT_POINT@'.
1c0454c1bd2241e0ac6fefb4bc631433 systemd: systemd-udev-settle.service is deprecated.
1dee0369c7fc4736b7099b38ecb46ee7 systemd: Mount point is not empty
24d8d4452573402496068381a6312df2 systemd: A virtual machine or container has been started
3354939424b4456d9802ca8333ed424a systemd: Session @SESSION_ID@ has been terminated
36db2dfa5a9045e1bd4af5f93e1cf057 systemd: DNSSEC mode has been turned off, as server doesn't support it
39f53479d3a045ac8e11786248231fbf systemd: A start job for unit @UNIT@ has finished successfully
45f82f4aef7a4bbf942ce861d1f20990 systemd: Time zone change to @TIMEZONE@
4d4408cfd0d144859184d1e65d7c8a65 systemd: A DNSSEC trust anchor has been revoked
50876a9db00f4c40bde1a2ad381c3a1b systemd: The system is configured in a way that might cause problems
58432bd3bace477cb514b56381b8a758 systemd: A virtual machine or container has been terminated
5aadd8e954dc4b1a8c954d63fd9e1137 systemd: Core file was truncated to @SIZE_LIMIT@ bytes.
5eb03494b6584870a536b337290809b3 systemd: Automatic restarting of a unit has been scheduled
641257651c1b4ec9a8624d7a40a9e1e7 systemd: Process @EXECUTABLE@ could not be executed
6bbd95ee977941e497c48be27c254128 systemd: System sleep state @SLEEP@ entered
7ad2d189f7e94e70a38c781354912448 systemd: Unit succeeded
7b05ebc668384222baa8881179cfda54 systemd: A reload job for unit @UNIT@ has finished
7d4958e842da4a758f6c1cdc7b36dcc5 systemd: A start job for unit @UNIT@ has begun execution
8811e6df2a8e40f58a94cea26f8ebf14 systemd: System sleep state @SLEEP@ left
8d45620c1a4348dbb17410da57c60c66 systemd: A new session @SESSION_ID@ has been created for user @USER_ID@
98268866d1d54a499c4e98921d93bc40 systemd: System shutdown initiated
98e322203f7a4ed290d09fe03c09fe15 systemd: Unit process exited
9d1aaa27d60140bd96365438aad20286 systemd: A stop job for unit @UNIT@ has finished
a596d6fe7bfa4994828e72309e95d61e systemd: Messages from a service have been suppressed
ae8f7b866b0347b9af31fe1c80b127c0 systemd: Resources consumed by unit runtime
b07a249cd024414a82dd00cd181378ff systemd: System start-up is now complete
b480325f9c394a7b802c231e51a2752c systemd: Special user @OFFENDING_USER@ configured, this is not safe!
b61fdac612e94b9182285b998843061f systemd: Accepting user/group name @USER_GROUP_NAME@, which does not match strict user/group name rules.
be02cf6855d2428ba40df7e9d022f03d systemd: A start job for unit @UNIT@ has failed
c14aaf76ec284a5fa1f105f88dfb061c systemd: System factory reset initiated
c7a787079b354eaaa9e77b371893cd27 systemd: Zeitänderung
d34d037fff1847e6ae669a370e694725 systemd: A reload job for unit @UNIT@ has begun execution
d93fb3c9c24d451a97cea615ce59c00b systemd: The journal has been stopped
d9b373ed55a64feb8242e02dbe79a49c systemd: Unit failed
de5b426a63be47a7b6ac3eaac82e2f6f systemd: A stop job for unit @UNIT@ has begun execution
e7852bfe46784ed0accde04bc864c2d5 systemd: Seat @SEAT_ID@ has now been removed
e9bf28e6e834481bb6f48f548ad13606 systemd: Journal messages have been missed
ec387f577b844b8fa948f33cad9a75e6 systemd: Disk space used by the journal
eed00a68ffd84e31882105fd973abdd1 systemd: User manager start-up is now complete
f77379a8490b408bbe5f6940505a777b systemd: The journal has been started
fc2e22bc6ee647b6b90729ab34a250b1 systemd: Speicherabbild für Prozess @COREDUMP_PID@ (@COREDUMP_COMM@) generiert
fcbefc5da23d428093f97c82a9290f7b systemd: A new seat @SEAT_ID@ is now available
fe6faa94e7774663a0da52717891d8ef systemd: A process of @UNIT@ unit has been killed by the OOM killer.
The option --list-catalog displays a list of default messages that can be used. Everything between the @ sings is replaced if a default message is used by a service.
The list is for everyone the same, since this are possible messages, predefined. There is nothing to worry about this.
i feel a little bit better, i misunderstood the --list-catalog output but there is still something wrong at shutdown that causes the “a stop job is running for session 2 of user … 1m30s…” message. what 2nd session ? i don’t understand to figure out the problem nor how to solve it. any help is appreciated.
It will be in a pager like less, use the arrow keys. Depending on your Display Manager (for exmaple lightDM) you see different session scopes.
I use lightDM and see something like
And everything in this session-2.scope is part of the second session. Keep in mind that your DM might also create a session for itself. If your UID is not 1000, you will see a different user slice.
If you grep in your journal like
journalctl -b -g Session --no-hostname --no-pager
You might see something like
Jan 21 13:43:02 systemd[1]: Started Session c1 of User lightdm.
Jan 21 13:43:49 systemd[1]: Stopping Session c1 of User lightdm...
Jan 21 13:43:49 systemd[1]: Stopped Session c1 of User lightdm.
Jan 21 13:43:49 systemd[1]: Started Session 2 of User xabbu.
You can’t really see which process delays the shutdown with this status command. I showed this command so you can see what session 2 means and which processes are part of it. (by the way, tracker on KDE?)
You need to check the journal as @mithrial showed you. The -b -1 option is important to see the messages from the last boot. It will be again in a pager like less, use your arrow keys. Maybe hit the End-key to jump to the end and go backwards. Compare the time stamps to find the gap.
If you did not had the problem on your last shutdown, you can also use -b -2 and so on. List all boots with
shows up this session 2. but can you or somebody else explain what’s going on and why this breaks at shutdown ? And what the heck is a “Slice-User” ?
Jan 21 15:47:28 systemd[1]: Created slice User and Session Slice.
Jan 21 15:47:29 systemd[1]: Starting Permit User Sessions...
Jan 21 15:47:29 systemd[1]: Finished Permit User Sessions.
Jan 21 15:47:35 systemd[1]: Started Session c1 of User sddm.
Jan 21 15:47:51 sddm[4537]: Session "/usr/share/xsessions/plasma.desktop" selected, command: "/usr/bin/startplasma-x11"
Jan 21 15:47:51 systemd[1]: Started Session 2 of User olaf.
Jan 21 15:47:51 sddm[4537]: Session started
Jan 21 15:47:52 ksmserver[8130]: Qt: Session management error: networkIdsList argument is NULL
Jan 21 15:47:52 kded5[8084]: kscreen.kded: PowerDevil SuspendSession action not available!
Jan 21 15:47:53 systemd[8021]: Created slice User Core Session Slice.
Jan 21 15:47:54 systemd[8021]: Started PipeWire Media Session Manager.
Jan 21 15:48:01 systemd[4560]: Activating special unit Exit the Session...
Jan 21 15:48:01 systemd[4560]: Finished Exit the Session.
Jan 21 15:48:01 systemd[4560]: Reached target Exit the Session.
Jan 21 17:39:31 kioslave5[12478]: Qt: Session management error: networkIdsList argument is NULL
Jan 21 17:40:24 kioslave5[12526]: Qt: Session management error: networkIdsList argument is NULL
Jan 21 17:40:31 kioslave5[12556]: Qt: Session management error: networkIdsList argument is NULL
Jan 21 17:40:32 kioslave5[12571]: Qt: Session management error: networkIdsList argument is NULL
Jan 21 17:40:33 kioslave5[12589]: Qt: Session management error: networkIdsList argument is NULL
Jan 21 17:40:33 kioslave5[12601]: Qt: Session management error: networkIdsList argument is NULL
Jan 21 17:40:36 kioslave5[12623]: Qt: Session management error: networkIdsList argument is NULL
Jan 21 17:43:31 kioslave5[12866]: Qt: Session management error: networkIdsList argument is NULL
Jan 21 17:43:33 kioslave5[12878]: Qt: Session management error: networkIdsList argument is NULL
Jan 21 17:43:54 kioslave5[12923]: Qt: Session management error: networkIdsList argument is NULL
Jan 21 17:43:56 kioslave5[12945]: Qt: Session management error: networkIdsList argument is NULL
Jan 21 17:44:07 kioslave5[12976]: Qt: Session management error: networkIdsList argument is NULL
Jan 21 17:44:15 kioslave5[12989]: Qt: Session management error: networkIdsList argument is NULL
Jan 21 17:44:16 kioslave5[13002]: Qt: Session management error: networkIdsList argument is NULL
Jan 21 17:45:28 kioslave5[13047]: Qt: Session management error: networkIdsList argument is NULL
Jan 21 17:45:30 kioslave5[13069]: Qt: Session management error: networkIdsList argument is NULL
Jan 21 17:45:32 kioslave5[13082]: Qt: Session management error: networkIdsList argument is NULL
Jan 21 17:45:33 kioslave5[13095]: Qt: Session management error: networkIdsList argument is NULL
Jan 21 17:45:34 kioslave5[13108]: Qt: Session management error: networkIdsList argument is NULL
Jan 21 17:45:35 kioslave5[13121]: Qt: Session management error: networkIdsList argument is NULL
Jan 21 17:45:37 kioslave5[13134]: Qt: Session management error: networkIdsList argument is NULL
thanks for your support even if i was a little bit scared. special thanks to xabbu who lead me to the way i have to search on further. this hanging is a problem of plasma and i will open a different thread to this.
This command journalctl -b -g Session --no-hostname --no-pager will not help you with your shutdown problem. It is just so you get an idea what systemd means by Session. (Since I used the -b option in my example, it shows log messages form your current boot. The shutdown has not yet started for this boot.)
It is nice to read up on systemd internals, but it will not help you with your shutdown problem. You really need to check the journal for the last boot with your shutdown problem.
But if you interested to see how systemd uses cgroups