You are not logged in.
When shutting down there is always displayed message "A stop job is running for simple desktop display manager [0s/1m 30s]", and it usually takes around 5 to 15 seconds to complete.
I would provided journalctl logs, but after following this wiki page, and configuring noclear.conf drop in file using
sudo systemctl edit getty@tty1.service/noclear.confmessages are still cleared by systemd.
"journalctl --list-boots", only displays current boot.
I also have found this post, which has the same issue, but in the end author didn't solve the issue with SDDM.
Last edited by someReallyRandomName (2022-10-19 12:03:20)
Offline
What is the content of /etc/systemd/journald.conf?
Are you using Wayland or X11?
Last edited by cfr (2022-10-19 00:58:57)
CLI Paste | How To Ask Questions
Arch Linux | x86_64 | GPT | EFI boot | refind | stub loader | systemd | LVM2 on LUKS
Lenovo x270 | Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz | Intel Wireless 8265/8275 | US keyboard w/ Euro | 512G NVMe INTEL SSDPEKKF512G7L
Offline
"journalctl --list-boots", only displays current boot.
stat /var/log/journal
grep -ir storage /etc/systemd/journald*Offline
$ stat /var/log/journal
stat: cannot statx '/var/log/journal': No such file or directory
$ grep -ir storage /etc/systemd/journald*
#Storage=autoOffline
No such file or directory
Why?
See the top of https://wiki.archlinux.org/title/Systemd/Journal and recreate the directory and restart journald.
Then reboot and hopefully get some log to share.
Offline
Okay, so now I can see my boots under journal --list-boots
Here is log https://termbin.com/eyng.
Offline
There's a bug if you end a Wayland KDE session that SDDM doesn't receive the signal properly. Is the shutdown instantaneous if you switch to the VT SDDM is on? Ctrl+Alt+F1 by default. You can "fix" that by opting for sddm-git which has quite a few fixes in that regard as well as native SDDM wayland support.
Online
Oh, I might have forgotten to mention that I am on X11, not wayland.
Offline
Yes I noticed after checking the logs and you don't really appear to have a "traditional" (90 secs by default due to the stop job actively not quiting) delay. What I'm seeing however is optimus running a stop job script, so this might be simply cleanup from there.
Last edited by V1del (2022-10-19 08:55:46)
Online
Plasma crashes out of the session and then there's
Oct 19 10:23:07 yesnt sddm[757]: Auth: sddm-helper crashed (exit code 15)
Oct 19 10:23:07 yesnt sddm[757]: Auth: sddm-helper exited with 15
Oct 19 10:23:15 yesnt sddm-helper[4560]: [PAM] Starting...
Oct 19 10:23:15 yesnt audit[4560]: USER_AUTH pid=4560 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_permit acct="sddm" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=? res=success'
Oct 19 10:23:15 yesnt audit[4560]: USER_ACCT pid=4560 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_permit acct="sddm" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=? res=success'
Oct 19 10:23:15 yesnt sddm-helper[4560]: [PAM] Authenticating...
Oct 19 10:23:15 yesnt sddm-helper[4560]: [PAM] returning.
Oct 19 10:23:15 yesnt kernel: audit: type=1100 audit(1666167795.834:143): pid=4560 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:authentication grantors=pam_permit acct="sddm" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=? res=success'
Oct 19 10:23:15 yesnt kernel: audit: type=1101 audit(1666167795.834:144): pid=4560 uid=0 auid=4294967295 ses=4294967295 msg='op=PAM:accounting grantors=pam_permit acct="sddm" exe="/usr/lib/sddm/sddm-helper" hostname=? addr=? terminal=? res=success'
Oct 19 10:23:16 yesnt sddm[757]: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still running.sddm-helper "crashes" with a SIGTERM and restarts/gets restarted
Try to log out of the KDE session and then shutdown/reboot from SDDM - does the stop job delay still happen?
Edit
Oct 19 10:11:49 yesnt systemd[866]: Starting Optimus Manager...
Oct 19 10:11:49 yesnt systemd[866]: Started Optimus Manager.
…
Oct 19 10:23:16 yesnt systemd[1]: Stopping Optimus Manager Commands Daemon...
Oct 19 10:23:16 yesnt systemd[1]: optimus-manager.service: Deactivated successfully.
Oct 19 10:23:16 yesnt systemd[1]: Stopped Optimus Manager Commands Daemon.
Oct 19 10:23:16 yesnt systemd[1]: optimus-manager.service: Consumed 6.289s CPU time.Last edited by seth (2022-10-19 08:56:56)
Offline
Try to log out of the KDE session and then shutdown/reboot from SDDM - does the stop job delay still happen?
After shut down directly from sddm, it's shutdowns normally without stop job.
And about optimus manager, I have already opened issue, because it seems that pr that once fixed the issue with long boot time was reverted.
Last edited by someReallyRandomName (2022-10-19 10:20:09)
Offline
Since the symptoms fit and I'm not sure about the plasma/wayland aspect, try sddm-git
Offline
It worked thanks!
Offline