Bug 1904445

Summary: systemd waits 2 minutes for a usermanager to end, which never was running
Product: [Fedora] Fedora Reporter: customercare
Component: systemdAssignee: systemd-maint
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 34CC: bugzilla, fedoraproject, filbranden, flepied, kasong, lnykryn, msekleta, ssahani, s, systemd-maint, yuwatana, zbyszek, z
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-03-19 06:56:47 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description customercare 2020-12-04 13:38:45 UTC 
Description of problem:

systemd waits 2 minutes for a usermanager to end, which never was running

It's noticeable on reboots, when the timer for the "no longer loggedin" usersession counts to two minutes. 

I think it a bug in systemd to not recognize, that the sessions already ended.

Due to the nature of this bug, screenshoting it may only work in VMs. 

known systems to have shown this bug:

Xen VMs Fedora 31-32 x86_64
Bare Metal Fedora 31-32 x86_64
Surface Pro 4 Fedora 30-32 x86_64
Pinephone Fedora 34 aarch64


Version-Release number of selected component (if applicable):

Any for at least the last 12 months

How reproducible:

reboot a desktop Fedora.
Comment 1 Ben Cotton 2021-02-09 16:17:50 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 34 development cycle.
Changing version to 34.
Comment 2 Chris Murphy 2021-03-19 06:56:47 UTC 

*** This bug has been marked as a duplicate of bug 1909556 ***