Bug 771118

Summary: Cannot login if network connection present, but no internet connection
Product: [Fedora] Fedora Reporter: Wolfgang Gradl <wolfgang.gradl>
Component: gnome-sessionAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 16CC: jmccann, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-13 21:58:40 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description Wolfgang Gradl 2012-01-01 16:10:14 UTC
Description of problem:
If the computer has a configured network connection which is not connected to the internet (e.g. active WLAN connection to a DSL router with a broken DSL connection), login does not work:  the session terminates almost immediately. A screen "Oh no, something has gone wrong" is shown briefly, but not long enough to actually read all the text displayed.

Steps to Reproduce:
1.  Have the computer connected to a local network (i.e. an active network
    connection at login) which itself is not properly setup (no connection to
    the internet)
2.  Try to log in to gnome desktop
3.  See session terminate almost immediately
  
Actual results:
On login, session aborts with a briefly shown screen "Oh no, something has gone wrong".  /var/log/messages contains

gnome-session[1858]: WARNING: Application 'gnome-settings-daemon.desktop' failed to register before timeout

Expected results:
Login should work regardless of network connectivity, just as in the case of no configured network.


Additional info:
Workaround:  switch off network connection for login (e.g. by using the RF kill switch on the laptop in question), and switch it back on after session has started.

Comment 1 Fedora End Of Life 2013-01-16 17:22:58 UTC
This message is a reminder that Fedora 16 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 16. 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 WONTFIX if it remains open with a Fedora 
'version' of '16'.

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 prior to Fedora 16's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 16 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 to click on 
"Clone This Bug" and open it against that version of Fedora.

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.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 2 Fedora End Of Life 2013-02-13 21:58:44 UTC
Fedora 16 changed to end-of-life (EOL) status on 2013-02-12. Fedora 16 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.

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