449630 – A stop job is running for Simple Desktop Display Manager

Bug 449630 - A stop job is running for Simple Desktop Display Manager

Summary: A stop job is running for Simple Desktop Display Manager

Status:	RESOLVED FIXED

Alias:	None

Product:	plasmashell
Classification:	Plasma
Component:	general (other bugs)
Version First Reported In:	5.23.5
Platform:	Arch Linux Linux

Importance:	NOR crash
Target Milestone:	1.0
Assignee:	David Edmundson

URL:
Keywords:

Depends on:
Blocks:

Reported:	2022-02-04 22:37 UTC by Allexus J
Modified:	2022-09-06 19:36 UTC (History)
CC List:	2 users (show)

See Also:
Latest Commit:
Version Fixed In:	5.24
Sentry Crash Report:

Attachments
all the entire journalctl shutdown log (63.92 KB, text/plain) 2022-02-04 22:37 UTC, Allexus J	Details
only sddm relative journalctl shutdown log (2.30 KB, text/plain) 2022-02-04 22:38 UTC, Allexus J	Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.

Description Allexus J 2022-02-04 22:37:40 UTC

Created attachment 146283 [details]
all the entire journalctl shutdown log

SUMMARY
Randomly, if I power off or reboot, the process of shutdown forces to hang because of SDDM, which blocks the shutdown and waits 1.30 min to actually kill SDDM process and continue shutdown. It's pretty annoying. I'm attaching two logs, one is the full shutdown journalctl log, the second is only sddm journalctl relevant part.


STEPS TO REPRODUCE
1. Reboot/Power off

OBSERVED RESULT
A stop job is running for Simple Desktop Display Manager. And the shutdown is forced to temporarily stops until it kills the SDDM process.

EXPECTED RESULT
It shouldn't happen.


SOFTWARE/OS VERSIONS
ArchLinux
KDE Plasma Version: 5.23.5
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION

Comment 1 Allexus J 2022-02-04 22:38:08 UTC

Created attachment 146284 [details]
only sddm relative journalctl shutdown log

Comment 2 Nate Graham 2022-02-05 22:31:59 UTC

This should be fixed in Plasma 5.24 already. If you discover that you are still experiencing it after upgrading, please feel free to re-open the bug report.