Bug 1904445 - systemd waits 2 minutes for a usermanager to end, which never was running
Summary: systemd waits 2 minutes for a usermanager to end, which never was running
Keywords:
Status: CLOSED DUPLICATE of bug 1909556
Alias: None
Product: Fedora
Classification: Fedora
Component: systemd
Version: 34
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ---
Assignee: systemd-maint
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-12-04 13:38 UTC by customercare
Modified: 2021-03-19 06:56 UTC (History)
13 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2021-03-19 06:56:47 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

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 ***
Note You need to log in before you can comment on or make changes to this bug.