Hi, i am experiencing a slow shutdown/reboot issue on a fresh endeavour os installation.
This is the output of sudo journalctl -b -1 -e --no-pager http://ix.io/3Tq2
The delay seems to be approximately here:
mar 25 10:33:14 octane audit[1]: SERVICE_STOP pid=1 uid=0 auid=4294967295 ses=4294967295 msg='unit=systemd-logind comm="systemd" exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success'
mar 25 10:33:14 octane audit: BPF prog-id=0 op=UNLOAD
mar 25 10:33:14 octane audit: BPF prog-id=0 op=UNLOAD
mar 25 10:33:14 octane audit: BPF prog-id=0 op=UNLOAD
mar 25 10:34:41 octane systemd[698]: app-rofi-07ca8f3c84b54fe48a40071a023cae6c.scope: Stopping timed out. Killing.
mar 25 10:34:41 octane systemd[698]: app-rofi-07ca8f3c84b54fe48a40071a023cae6c.scope: Killing process 1097 (Discord) with signal SIGKILL.
mar 25 10:34:41 octane systemd[698]: app-rofi-07ca8f3c84b54fe48a40071a023cae6c.scope: Killing process 1995 (Discord) with signal SIGKILL.
mar 25 10:34:41 octane systemd[698]: app-rofi-07ca8f3c84b54fe48a40071a023cae6c.scope: Killing process 2108 (renderer_crash_) with signal SIGKILL.
mar 25 10:34:41 octane systemd[698]: app-rofi-07ca8f3c84b54fe48a40071a023cae6c.scope: Killing process 2109 (renderer_crash_) with signal SIGKILL.
mar 25 10:34:41 octane systemd[698]: app-rofi-07ca8f3c84b54fe48a40071a023cae6c.scope: Killing process 1133 (Discord) with signal SIGKILL.
mar 25 10:34:41 octane systemd[698]: app-rofi-07ca8f3c84b54fe48a40071a023cae6c.scope: Killing process 1138 (utility_crash_u) with signal SIGKILL.
mar 25 10:34:41 octane systemd[698]: app-rofi-07ca8f3c84b54fe48a40071a023cae6c.scope: Failed with result 'timeout'.
mar 25 10:34:41 octane systemd[698]: Stopped rofi.
mar 25 10:34:41 octane systemd[698]: app-rofi-07ca8f3c84b54fe48a40071a023cae6c.scope: Consumed 36.766s CPU time.
mar 25 10:34:41 octane systemd[698]: Removed slice User Application Slice.
mar 25 10:34:41 octane systemd[698]: app.slice: Consumed 1min 4.418s CPU time.
mar 25 10:34:41 octane systemd[698]: Reached target Shutdown.
mar 25 10:34:41 octane systemd[698]: Finished Exit the Session.
mar 25 10:34:41 octane systemd[698]: Reached target Exit the Session.
mar 25 10:34:41 octane systemd[699]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8004 service=[systemd-user] terminal=[] user=[arcogabbo] ruser=[<unknown>] rhost=[<unknown>]
if so what is this? nothing installed per default I would bet ?
discord and some rofi app? and systems service/timer/socket involved?
and welcome here at the forum
That’s what i’m trying to understand. I just have installed some apps but i don’t think they are the main problem. Maybe some service that tries to terminate apps on system shutdown/reboot is bugged? What can i do to investigate more?
but rofi itself is not providing any systemd servicefiles… and discord is not using rofi in addition…
Not sure if this is even rofi could be some stuff with the name app-rofi
I removed rofi and the log now shows discord. In fact in the logs i posted you can see various applications other than rofi that got SIG KILL after the delay(including discord just after rofi). Maybe the issue has something to do with display manager or desktop environment? By the way i’m using SDDM and KDE plasma 5.24
Following the second link i added the kernel parameters, created the script and run grub-mkconfig. The problem was suddenly gone. For further analysis, i removed those kernel parameters and the debug script, launched again grub-mkconfig and the problem is still gone.
As a newbie i assume the solution i needed was regenerating the grub config file? Seems weird to me, but it’s all fixed now. Thanks to all who tried to resolve my problem, i’ll mark as solved.
EDIT 1: Turns out it’s all fixed when no applications are open on the os. Problem still persists then
EDIT 3: The issue does not occur when trying $ systemctl reboot or $ systemctl poweroff. However the problem always occurs when rebooting or powering off from plasma UI.
In comparison to what?
Have you logged timing data?
Have you searched the forum? I suppose you did, but I expected data (from systemd-analyze critical-chain or your clock).
Also it seems weird you have a system problem and not post system info (inxi -Faz and add system modifications you have done already, when etc…)