After update from kernel 7.2.8 to 7.2.9, shutdown and reboot take to much minutes.
Has anyone the same result ?
Check the journal for hints what delays the shutdown/start.
A graphical tool for the journal is in the Cockpit app or you use journalctl from the command line.
@hui
Hum, not able to search on the command line.
Cockpit seems installed but is not to find in the listed apps from the launcher.
Here are the installed packages of cockpit
You open cockpit via typing this adress in a browser:
https://localhost:9090
@hui
https://localhost:9090 connexion failed
The commande
sudo journalctl -b -1 -r -n 200 --no-pager
gave this (only the end ):
oct. 12 17:47:11 Zlinux systemd[1879]: Stopping KDE Session Management Server...
oct. 12 17:47:11 Zlinux systemd[1879]: plasma-plasmashell.service: Consumed 8.076s CPU time over 21min 28.219s wall clock time.
oct. 12 17:47:11 Zlinux systemd[1879]: Stopped KDE Plasma Workspace.
oct. 12 17:47:11 Zlinux plasmashell[2301]: QObject::disconnect: Unexpected nullptr parameter
oct. 12 17:47:11 Zlinux plasmashell[2301]: Failed to reconnect Argument invalide
oct. 12 17:47:11 Zlinux plasmashell[2301]: IPP_INTERNAL_ERROR: clearing cookies and reconnecting
oct. 12 17:47:11 Zlinux plasmashell[2301]: Failed to reconnect Argument invalide
oct. 12 17:47:11 Zlinux plasmashell[2301]: IPP_INTERNAL_ERROR: clearing cookies and reconnecting
oct. 12 17:47:11 Zlinux plasmashell[2301]: Failed to reconnect Argument invalide
oct. 12 17:47:11 Zlinux plasmashell[2301]: IPP_INTERNAL_ERROR: clearing cookies and reconnecting
oct. 12 17:47:11 Zlinux systemd[1879]: Stopped PipeWire Multimedia Service.
oct. 12 17:47:11 Zlinux kwin_wayland[1994]: PipeWire remote error: connection error
oct. 12 17:47:11 Zlinux systemd[1879]: Stopping PipeWire Multimedia Service...
oct. 12 17:47:11 Zlinux kwin_wayland[1994]: PipeWire remote error: connection error
oct. 12 17:47:11 Zlinux systemd[1879]: Stopping PipeWire Multimedia Service...
oct. 12 17:47:11 Zlinux systemd[1879]: Stopped Multimedia Service Session Manager.
oct. 12 17:47:11 Zlinux systemd[1879]: Removed slice Slice /app/dbus-:1.2-org.kde.kdeconnect.
oct. 12 17:47:11 Zlinux systemd[1879]: Stopped dbus-:1.2-org.kde.kdeconnect@0.service.
oct. 12 17:47:11 Zlinux systemd[1879]: sys-devices-pci0000:00-0000:00:14.0-usb1-1\x2d11-1\x2d11:1.0-sound-card2-controlC2.device: Failed to enqueue SYSTEMD_USER_WANTS job, ignoring: Transaction for sound.target/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction).
oct. 12 17:47:11 Zlinux systemd[1879]: Requested transaction contradicts existing jobs: Transaction for sound.target/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction).
oct. 12 17:47:11 Zlinux systemd[1879]: sys-devices-pci0000:00-0000:00:01.0-0000:01:00.1-sound-card1-controlC1.device: Failed to enqueue SYSTEMD_USER_WANTS job, ignoring: Transaction for sound.target/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction).
oct. 12 17:47:11 Zlinux systemd[1879]: Requested transaction contradicts existing jobs: Transaction for sound.target/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction).
oct. 12 17:47:11 Zlinux systemd[1879]: sys-devices-pci0000:00-0000:00:1f.3-sound-card0-controlC0.device: Failed to enqueue SYSTEMD_USER_WANTS job, ignoring: Transaction for sound.target/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction).
oct. 12 17:47:11 Zlinux systemd[1879]: Requested transaction contradicts existing jobs: Transaction for sound.target/start is destructive (shutdown.target has 'start' job queued, but 'stop' is included in transaction).
oct. 12 17:47:11 Zlinux systemd[1879]: Stopped Bluetooth OBEX service.
.
.
.
oct. 12 17:47:11 Zlinux systemd[1]: Stopped target Timer Units.
oct. 12 17:47:11 Zlinux systemd[1]: Stopped target Sound Card.
oct. 12 17:47:11 Zlinux sddm[1733]: Auth: sddm-helper exited with 1
oct. 12 17:47:11 Zlinux sddm[1733]: Authentication error: SDDM::Auth::ERROR_INTERNAL "Process crashed"
oct. 12 17:47:11 Zlinux sddm[1733]: Auth: sddm-helper (--socket /tmp/sddm-auth-f9a71dd0-db0c-4f3b-944e-a988a231ec66 --id 1 --start /usr/libexec/plasma-dbus-run-session-if-needed /usr/bin/startplasma-wayland --user herve) crashed (exit code 1)
oct. 12 17:47:11 Zlinux systemd[1]: Stopped target Graphical Interface.
oct. 12 17:47:11 Zlinux sddm[1733]: Authentication error: SDDM::Auth::ERROR_INTERNAL "Process crashed"
oct. 12 17:47:11 Zlinux systemd[1]: Stopped target Bluetooth Support.
oct. 12 17:47:11 Zlinux systemd[1]: Removed slice Slice /system/modprobe.
oct. 12 17:47:11 Zlinux systemd[1]: Removed slice Slice /system/dbus-:1.2-org.kde.powerdevil.discretegpuhelper.
oct. 12 17:47:11 Zlinux systemd[1]: Removed slice Slice /system/dbus-:1.2-org.kde.powerdevil.chargethresholdhelper.
oct. 12 17:47:11 Zlinux systemd[1]: Removed slice Slice /system/dbus-:1.2-org.kde.powerdevil.backlighthelper.
oct. 12 17:47:11 Zlinux systemd[1]: Removed slice Slice /system/dbus-:1.2-org.kde.kded.smart.
oct. 12 17:47:11 Zlinux systemd[1]: Removed slice Slice /system/dbus-:1.2-org.kde.kameleon.qmk.helper.
oct. 12 17:47:11 Zlinux systemd[1]: Stopping Session 3 of User herve...
oct. 12 17:47:11 Zlinux sddm-helper[1874]: Signal received: SIGTERM
oct. 12 17:47:11 Zlinux systemd[1879]: Stopped Proxies GTK DBus menus to a Plasma readable format.
oct. 12 17:47:11 Zlinux systemd-logind[1250]: The system will reboot now!
oct. 12 17:47:11 Zlinux systemd-logind[1250]: System is rebooting.
oct. 12 17:47:11 Zlinux systemd[1879]: Stopped KDE PolicyKit Authentication Agent.
oct. 12 17:47:11 Zlinux systemd-logind[1250]: reboot requested from client PID 5196 ('plasma-shutdown') (unit user@1000.service)...
.
.
.
oct. 12 17:47:11 Zlinux systemd[1879]: Stopped target plasma-workspace-wayland.target.
oct. 12 17:47:11 Zlinux systemd[1879]: app-gkrellm@745365a985d1467ca2894bf1390f6baf.service: Consumed 12.298s CPU time over 21min 24.226s wall clock time.
oct. 12 17:47:11 Zlinux xwaylandvideobridge[2508]: QObject::disconnect: Unexpected nullptr parameter
oct. 12 17:47:11 Zlinux systemd[1879]: Started dbus-:1.2-org.kde.Shutdown@0.service.
oct. 12 17:47:11 Zlinux systemd[1879]: Created slice Slice /app/dbus-:1.2-org.kde.Shutdown.
oct. 12 17:47:09 Zlinux systemd[1879]: Started dbus-:1.2-org.kde.LogoutPrompt@0.service.
oct. 12 17:47:09 Zlinux systemd[1879]: Created slice Slice /app/dbus-:1.2-org.kde.LogoutPrompt.
oct. 12 17:47:03 Zlinux systemd[1]: snapperd.service: Deactivated successfully.
oct. 12 17:47:03 Zlinux systemd[1879]: app-Waydroid@7a76e80ce41c48119646186b661ed12f.service: Consumed 3.857s CPU time over 20min 59.323s wall clock time.
herve@Zlinux:~>
That all what have problems (but i don’t understand it : no problem during session)
But here we see some 9 seconds, not minutes so the problem is somewhere else?
@OrsoBruno
At this time, i have wait on the reboot and … nothing during a few minutes.
Then i have hard rebooted.
As the last line is for waydroid, we can think the problem is here but not.
Before today waydroid was not installed
Don’t be mistaken, the log is in reverse order (the “-r” flag) so the last line in time is the first line in the command output.
The first few ines should read something like:
luna:~ # journalctl -b -1 -r -n 200 --no-pager
Oct 12 02:16:22 luna systemd-journald[524]: Journal stopped
Oct 12 02:16:22 luna haveged[660]: haveged starting up
Oct 12 02:16:22 luna haveged[660]: fills: 1, generated: 512 K bytes, RNDADDENTROPY: 48.5 K bytes
Oct 12 02:16:22 luna haveged[660]: tot tests(BA8): A:1/1 B:1/1 continuous tests(B): last entropy estimate 7.99949
Oct 12 02:16:22 luna haveged[660]: haveged: Stopping due to signal 15
Oct 12 02:16:22 luna systemd-shutdown[1]: Sending SIGTERM to remaining processes...
Oct 12 02:16:22 luna systemd-shutdown[1]: Syncing filesystems and block devices.
Oct 12 02:16:22 luna systemd[1]: Shutting down.
Oct 12 02:16:22 luna systemd[1]: Reached target System Power Off.
Oct 12 02:16:22 luna systemd[1]: Finished System Power Off.
Oct 12 02:16:22 luna systemd[1]: systemd-poweroff.service: Deactivated successfully.
If the first lines in the command line output are really “Stopping KDE Session…” there is something wrong in your KDE setup? Maybe a custom theme that does not work anymore?
As a check, can you successfully log out?
Then switch to a VT (for instance CTRL+ALT+F4), login as root and issue systemctl poweroff: does the system poweroff or hang?
And that brings us to the following: there should not be anything about KDE during boot.
Do you have switched on automatic login for a user?
And, when yes, does this mean that you do not know for certain that the problem is with boot or with login?
@OrsoBruno
Logout : yes but black screen during one or 2 minutes (with no possibility to reach a VT).
After the one or 2 minutes, SDDM appears (but now possibilty to reach a VT) and i can log in
@hcvv
No automatic login here. all users must enter name and password.
There are a few 1m30s timeouts at boot and shutdown, so some 4 minutes for a reboot makes sense. Now we must find which process times out and that should show in the journal as a 1m 30s gap (or similar) in the time line…
Thanks for that info, thus my guess was wrong, but
points to a problem during logout, not shutdown.
Kernel 7.2.9 was in snapshot TW20261007. In the same snapshot was a bluez upgrade and bluetooth might time out at login and logout if there is something expected that does not connect (or disconnect): sounds a bell?
@OrsoBruno
Now that’s a tricky one!
I know my PC has Bluetooth, but I don’t have any devices that use it.
sudo bluetoothctl list
[sudo] Mot de passe de root :
Controller FC:6D:77:8A:4A:11 Zlinux [default]
sudo rfkill list bluetooth
1: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
@OrsoBruno
It seems we will waiting on a next update and hope that close the problem
There is something like a KDE rebuild in the pipeline at the moment (see for instance New Tumbleweed snapshot 20261011 released! ) so if it is something linked to KDE Session Management it might well disappear automagically. If it doesn’t in a week or so please write back here.