Bug 1314707 - System unusable after resume from standby with NFS mounts
System unusable after resume from standby with NFS mounts
Product: Fedora
Classification: Fedora
Component: gdm (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: ---
: ---
Assigned To: Ray Strode [halfline]
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2016-03-04 05:08 EST by Dan Dragomir
Modified: 2016-12-20 14:14 EST (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2016-12-20 14:14:13 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)

  None (edit)
Description Dan Dragomir 2016-03-04 05:08:58 EST
Description of problem:

If I have my T440s laptop connected to a NFS mount on my home network and put it into standby, when I resume it on my workplace network (where the NFS mounts are not available) the login screen hangs after I enter my password. The mouse is still moving but no buttons ca be clicked. Moreover, even switching to another virtual terminal to kill the login screen or force unmount the NFS share doesn't work. Instead of the virtual terminal login prompt all I get is a blank screen. At this point the system is not usable anymore and I have to reach for the power button.

Version-Release number of selected component (if applicable):
Name        : gdm
Arch        : x86_64
Epoch       : 1
Version     : 3.18.2
Release     : 2.fc23

Name        : kernel
Arch        : x86_64
Epoch       : 0
Version     : 4.4.3
Release     : 300.fc23

Not sure about earlier GDM versions, but this happened with earlier kernel versions also.

How reproducible:
Every time.

Steps to Reproduce:
1. Connect system to network and mount a NFS share
2. Put system to sleep
3. Move system to another network and resume
4. Enter password for unlock

Actual results:
The login screen hangs.

Expected results:
The session is unlocked.
Comment 1 Fedora End Of Life 2016-11-24 10:55:32 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 2 Fedora End Of Life 2016-12-20 14:14:13 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.