Bug 1263749 - User has to wait to login after some other user just logged off
User has to wait to login after some other user just logged off
Product: Fedora
Classification: Fedora
Component: systemd (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: systemd-maint
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2015-09-16 11:12 EDT by Petr Schindler
Modified: 2016-12-20 09:39 EST (History)
12 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-12-20 09:39:03 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
output of journalctl -a -b (150.81 KB, text/plain)
2015-09-16 11:12 EDT, Petr Schindler
no flags Details

  None (edit)
Description Petr Schindler 2015-09-16 11:12:07 EDT
Created attachment 1074077 [details]
output of journalctl -a -b

Description of problem:
When user wants to log in to the system after some another user just logged off he/she has to wait few seconds (about 30). Before that time it returns back to gdm after log in attempt.

The user which just logged off can log in immediately.

In attached output of journalctl you can find one correct attempt to log in. Then I logged out and three time tried to log in as another user.

Version-Release number of selected component (if applicable):
The system was installed from Beta RC1 Workstation Live

How reproducible:

Steps to Reproduce:

Actual results:

Expected results:

Additional info:
Comment 1 Stephen Gallagher 2015-09-16 16:21:49 EDT
From that log, it's timing out in pam_systemd, which seems like it's related to the root cause of BZ #1263752 which I reported earlier today. I'm not sure it's a strict duplicate, so I'm not closing it as such, but I am moving the component to systemd.
Comment 2 Fedora End Of Life 2016-11-24 07:31:12 EST
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 3 Fedora End Of Life 2016-12-20 09:39:03 EST
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this

Thank you for reporting this bug and we are sorry it could not be fixed.

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