SDDM tries to restart after reboot/shutdown are initiated.

Bug #1955747 reported by TomasHnyk
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
SDDM
New
Unknown
sddm (Ubuntu)
New
Undecided
Unassigned

Bug Description

When I reboot or shutdown my computer, SDDM tries to restarts itself and slows down the halting process (by about five seconds).

`journalctl -b-1 |grep sddm` gives:

pro 25 14:19:13 GreenOne sddm-helper[15321]: [PAM] Starting...
pro 25 14:19:13 GreenOne sddm-helper[15321]: [PAM] Authenticating...
pro 25 14:19:13 GreenOne sddm-helper[15321]: [PAM] Preparing to converse...
pro 25 14:19:13 GreenOne sddm-helper[15321]: [PAM] Conversation with 1 messages
pro 25 14:19:13 GreenOne sddm-helper[15322]: pam_ecryptfs: Passphrase file wrapped
pro 25 14:19:13 GreenOne sddm-helper[15321]: pam_kwallet5(sddm:auth): (null): pam_sm_authenticate
pro 25 14:19:13 GreenOne sddm-helper[15321]: [PAM] returning.
pro 25 14:19:13 GreenOne sddm[955]: Authenticated successfully
pro 25 14:19:13 GreenOne sddm-greeter[15251]: Message received from daemon: LoginSucceeded
pro 25 14:19:13 GreenOne sddm-helper[15321]: pam_kwallet5(sddm:setcred): pam_kwallet5: pam_sm_setcred
pro 25 14:19:13 GreenOne sddm-helper[15321]: pam_unix(sddm:session): session opened for user drew by (uid=0)
pro 25 14:19:13 GreenOne sddm-helper[15321]: pam_kwallet5(sddm:session): pam_kwallet5: pam_sm_open_session
pro 25 14:19:13 GreenOne sddm-helper[15332]: pam_kwallet5: final socket path: /run/user/1000/kwallet5.socket
pro 25 14:19:13 GreenOne sddm-helper[15321]: Starting: "/etc/sddm/Xsession \"/usr/bin/startplasma-x11\""
pro 25 14:19:13 GreenOne sddm-helper[15334]: Adding cookie to "/home/drew/.Xauthority"
pro 25 14:19:13 GreenOne sddm[955]: Session started
pro 25 14:19:13 GreenOne sddm-helper[15238]: [PAM] Closing session
pro 25 14:19:13 GreenOne sddm-helper[15238]: pam_unix(sddm-greeter:session): session closed for user sddm
pro 25 14:19:13 GreenOne sddm-helper[15238]: [PAM] Ended.
pro 25 14:19:13 GreenOne sddm[955]: Auth: sddm-helper exited successfully
pro 25 14:19:13 GreenOne sddm[955]: Greeter stopped.
pro 25 14:20:14 GreenOne sddm[955]: Authentication error: "Process crashed"
pro 25 14:20:14 GreenOne sddm[955]: Auth: sddm-helper crashed (exit code 15)
pro 25 14:20:14 GreenOne sddm[955]: Authentication error: "Process crashed"
pro 25 14:20:14 GreenOne sddm[955]: Auth: sddm-helper exited with 15
pro 25 14:20:14 GreenOne sddm[955]: Socket server stopping...
pro 25 14:20:14 GreenOne sddm[955]: Socket server stopped.
pro 25 14:20:14 GreenOne sddm[955]: Display server stopping...
pro 25 14:20:15 GreenOne sddm[955]: Display server stopped.
pro 25 14:20:15 GreenOne sddm[955]: Running display stop script "/usr/share/sddm/scripts/Xstop"
pro 25 14:20:17 GreenOne sddm[955]: Removing display ":0" ...
pro 25 14:20:17 GreenOne sddm[955]: Adding new display on vt 1 ...
pro 25 14:20:17 GreenOne sddm[955]: Loading theme configuration from ""
pro 25 14:20:17 GreenOne sddm[955]: Display server starting...
pro 25 14:20:17 GreenOne sddm[955]: Adding cookie to "/var/run/sddm/{0d14fc72-608b-4648-a74c-e1209ec1ed6e}"
pro 25 14:20:17 GreenOne sddm[955]: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{0d14fc72-608b-4648-a74c-e1209ec1e
d6e} -background none -noreset -displayfd 18 -seat seat0 vt1
pro 25 14:20:18 GreenOne sddm[955]: Setting default cursor
pro 25 14:20:18 GreenOne sddm[955]: Running display setup script "/usr/share/sddm/scripts/Xsetup"
pro 25 14:20:21 GreenOne sddm[955]: Display server started.
pro 25 14:20:21 GreenOne sddm[955]: Socket server starting...
pro 25 14:20:21 GreenOne sddm[955]: Socket server started.
pro 25 14:20:21 GreenOne sddm[955]: Loading theme configuration from "/usr/share/sddm/themes/ubuntu-theme/theme.conf"
pro 25 14:20:21 GreenOne sddm[955]: Greeter starting...
pro 25 14:20:21 GreenOne sddm[955]: Signal received: SIGTERM
pro 25 14:20:21 GreenOne sddm-helper[17408]: [PAM] Starting...
pro 25 14:20:21 GreenOne sddm-helper[17408]: [PAM] Authenticating...
pro 25 14:20:21 GreenOne sddm-helper[17408]: [PAM] returning.
pro 25 14:20:21 GreenOne sddm[955]: Socket server stopping...
pro 25 14:20:21 GreenOne sddm[955]: Socket server stopped.
pro 25 14:20:21 GreenOne sddm[955]: Display server stopping...
pro 25 14:20:22 GreenOne sddm[955]: Display server stopped.
pro 25 14:20:22 GreenOne sddm[955]: Running display stop script "/usr/share/sddm/scripts/Xstop"
pro 25 14:20:23 GreenOne sddm[955]: QProcess: Destroyed while process ("/usr/lib/x86_64-linux-gnu/sddm/sddm-helper") is stil
l running.
pro 25 14:20:23 GreenOne systemd[1]: sddm.service: Deactivated successfully.
pro 25 14:20:23 GreenOne systemd[1]: sddm.service: Consumed 1min 43.509s CPU time.

It can be seen that the system went for shutdown at 14:20:14, got mostly shut down at 14:20:15 but then spent 8 seconds while SDDM was trying to start again.

I am on Kuubntu 21.10, I am using systemd-boot to start up my computer but this also happens to people with GRUB2 as confirmed here: https://www.kubuntuforums.net/forum/newbie-support/help-the-new-guy/659089-slow-shutdown?p=659107#post659107

A workaround was messing with /etc/systemd/system.con and tuning down these values:
DefaultTimeoutStartSec=1s
DefaultTimeoutStopSec=1s
DefaultStartLimitIntervalSec=500ms

Changing the restart values in /usr/lib/systemd/system/sddm.service on the other hand has not changed anything.
---
ProblemType: Bug
ApportVersion: 2.20.11-0ubuntu71
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: KDE
DistroRelease: Ubuntu 21.10
EcryptfsInUse: Yes
InstallationDate: Installed on 2021-12-24 (1 days ago)
InstallationMedia: Kubuntu 21.10 "Impish Indri" - Release amd64 (20211012)
NonfreeKernelModules: nvidia_modeset nvidia
Package: sddm 0.19.0-2ubuntu2 [modified: lib/systemd/system/sddm.service]
PackageArchitecture: amd64
ProcVersionSignature: Ubuntu 5.13.0-22.22-generic 5.13.19
Tags: impish
Uname: Linux 5.13.0-22-generic x86_64
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin lxd plugdev sambashare sudo
_MarkForUpload: True

Revision history for this message
Paul Loughman (snowhog) wrote :

I have almost identical entries in my journalctl log, but I don't have the slowness that the OP is experiencing.

Dec 25 11:29:31 barley-cat sddm[718]: Authentication error: "Process crashed"
Dec 25 11:29:31 barley-cat sddm[718]: Auth: sddm-helper crashed (exit code 15)
Dec 25 11:29:31 barley-cat sddm[718]: Authentication error: "Process crashed"
Dec 25 11:29:31 barley-cat sddm[718]: Auth: sddm-helper exited with 15
Dec 25 11:29:31 barley-cat sddm[718]: Socket server stopping...
Dec 25 11:29:31 barley-cat sddm[718]: Socket server stopped.
Dec 25 11:29:31 barley-cat sddm[718]: Display server stopping...
Dec 25 11:29:31 barley-cat sddm[718]: Display server stopped.
Dec 25 11:29:31 barley-cat sddm[718]: Running display stop script "/usr/share/sddm/scripts/Xstop"
Dec 25 11:29:31 barley-cat sddm[718]: Removing display ":0" ...
Dec 25 11:29:31 barley-cat sddm[718]: Adding new display on vt 1 ...
Dec 25 11:29:31 barley-cat sddm[718]: Loading theme configuration from ""
Dec 25 11:29:31 barley-cat sddm[718]: Display server starting...
Dec 25 11:29:31 barley-cat sddm[718]: Adding cookie to "/var/run/sddm/{4c84cd71-7817-4c65-b807-344789cc5ab7}"
Dec 25 11:29:31 barley-cat sddm[718]: Running: /usr/bin/X -nolisten tcp -auth /var/run/sddm/{4c84cd71-7817-4c65-b807-344789cc5ab7} -background none -noreset -displayfd 18 -seat seat0 vt1
Dec 25 11:29:32 barley-cat sddm[718]: Setting default cursor
Dec 25 11:29:32 barley-cat sddm[718]: Running display setup script "/usr/share/sddm/scripts/Xsetup"
Dec 25 11:29:32 barley-cat sddm[718]: Display server started.
Dec 25 11:29:32 barley-cat sddm[718]: Socket server starting...
Dec 25 11:29:32 barley-cat sddm[718]: Socket server started.
Dec 25 11:29:32 barley-cat sddm[718]: Loading theme configuration from "/usr/share/sddm/themes/ubuntu-theme/theme.conf"
Dec 25 11:29:32 barley-cat sddm[718]: Greeter starting...
Dec 25 11:29:32 barley-cat sddm[718]: Signal received: SIGTERM
Dec 25 11:29:32 barley-cat sddm[718]: Socket server stopping...
Dec 25 11:29:32 barley-cat sddm[718]: Socket server stopped.
Dec 25 11:29:32 barley-cat sddm[718]: Display server stopping...
Dec 25 11:29:32 barley-cat sddm-helper[35033]: [PAM] Starting...
Dec 25 11:29:32 barley-cat sddm-helper[35033]: [PAM] Authenticating...
Dec 25 11:29:32 barley-cat sddm-helper[35033]: [PAM] returning.
Dec 25 11:29:33 barley-cat sddm[718]: Display server stopped.
Dec 25 11:29:33 barley-cat sddm[718]: Running display stop script "/usr/share/sddm/scripts/Xstop"
Dec 25 11:29:33 barley-cat sddm[718]: QProcess: Destroyed while process ("/usr/lib/x86_64-linux-gnu/sddm/sddm-helper") is still running.
Dec 25 11:29:33 barley-cat systemd[1]: sddm.service: Deactivated successfully.
Dec 25 11:29:33 barley-cat systemd[1]: sddm.service: Consumed 4min 2.222s CPU time.

Whether it matters, I'm running Kubuntu 22.04, fully updated.

Revision history for this message
Chris Guiver (guiverc) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please execute the following command only once, as it will automatically gather debugging information, in a terminal:

apport-collect 1955747

When reporting bugs in the future please use apport by using 'ubuntu-bug' and the name of the package affected. You can learn more about this functionality at https://wiki.ubuntu.com/ReportingBugs.

I'll change the status to 'incomplete' as no package, version etc. details were provided in fields (done automatically when apport tools are used to file bug report; this detail will be added with the apport-collect). Please return the status to "New" after running 'apport-collect'; or if you believe I've made an error, leave a comment as to why & the status can be returned to 'New' (some version details were provided in text description; but not fields of the bug report)

Changed in sddm (Ubuntu):
status: New → Incomplete
Revision history for this message
TomasHnyk (sup) wrote : Dependencies.txt

apport information

tags: added: apport-collected impish
description: updated
Revision history for this message
TomasHnyk (sup) wrote : ProcCpuinfoMinimal.txt

apport information

Revision history for this message
TomasHnyk (sup) wrote : ProcEnviron.txt

apport information

Chris Guiver (guiverc)
Changed in sddm (Ubuntu):
status: Incomplete → New
Changed in sddm:
status: Unknown → New
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.