Bug 1601154 - Input and display freeze when joining existing session after another user logged in
Summary: Input and display freeze when joining existing session after another user log...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gdm
Version: 28
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-07-14 11:52 UTC by Ray
Modified: 2019-05-02 20:17 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-05-02 19:55:01 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description Ray 2018-07-14 11:52:36 UTC
Description of problem:

Under certain circumstances the display and input methods freeze while trying to log in.  No input is accepted via the keyboard, e.g. the 
Alt+SysRq combinations do not work.  The computer is accessible remotely via ssh.

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

This did not happen under Fedora 27 and only started after updating to 28.

How reproducible:


Steps to Reproduce:
1. User A establishes a graphical login session.
2. User B establishes a concurrent graphical login session
3. User B logs out
4. User A attempts to log in again.

Actual results:

The login for user A fails to ever return.  At this point I try Ctrl-Alt-F1 to get back to the 'choose a user screen'.  However, logging in from this virtual terminal never succeeds.  Then I have tried Ctrl-Alt-F2, which seems to be associated with user A.  I can successfully log in, but the session is not fully functional, e.g. starting applications like Terminal never succeed.  I suspect that the user actually has two sessions at this point but I do not know how to verify that.  Once the computer is in this state if I need to log in again the system freezes and keyboard and mouse input cease to be recognized.  It is necessary to log in remotely and reboot the system.

Expected results:

The existing session of user A is rejoined and all applications are functional.  Repeated logins do not cause issues.

Additional info:

Let me know what I can do to provide more information and troubleshoot.

I would also like to know if there is a less drastic step than rebooting which might repair the problem.

Comment 1 Ray 2018-07-27 17:37:58 UTC
I forgot to mention in my original description - this started after updating from F27 to F28.  Had none of this behavior in F27.

Also, I have noticed that the "Switch User" option in the upper right Gnome menu, under the currently logged in user is not always present.  (This is located where "Log Off" is, in case I have not been clear.

Comment 2 Ben Cotton 2019-05-02 19:23:27 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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 Ray 2019-05-02 19:55:01 UTC
Closing as we do not experience the problem in F29.

Comment 4 Ben Cotton 2019-05-02 20:17:38 UTC
This message is a reminder that Fedora 28 is nearing its end of life.
On 2019-May-28 Fedora will stop maintaining and issuing updates for
Fedora 28. 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 '28'.

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 28 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.


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