Bug 713876 - Oh no! Something has gone wrong! upon startx with GNOME3 if connected to varying LANs
Summary: Oh no! Something has gone wrong! upon startx with GNOME3 if connected to vary...
Keywords:
Status: CLOSED WORKSFORME
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-shell
Version: 15
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: ---
Assignee: Owen Taylor
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-16 16:31 UTC by Alessandro Suardi
Modified: 2011-07-31 16:17 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-07-31 16:17:19 UTC
Type: ---


Attachments (Terms of Use)
copy/paste of output of GNOME3 session to framebuffer console (2.93 KB, application/octet-stream)
2011-06-16 16:31 UTC, Alessandro Suardi
no flags Details

Description Alessandro Suardi 2011-06-16 16:31:10 UTC
Created attachment 505098 [details]
copy/paste of output of GNOME3 session to framebuffer console

Description of problem:
GNOME3 session doesn't start up, Log Out button asks to retry.

Version-Release number of selected component (if applicable):
gnome-shell-3.0.2-1.fc15.x86_64

How reproducible: twice in 10 days


Steps to Reproduce:
1. configure system to start at systemd equivalent of runlevel 3
2. at console, log in with unprivileged user
3. run 'startx'
  
Actual results:
Occasional GNOME3 session failure to start, with Log Out button asking to retry

Expected results:
GNOME3 session starts up normally

Additional info:
- No .xsession-errors file exists
- Problem happens if system boots with an Ethernet cable attached, after NetworkManager is used with different LANs (I travel to multiple customer sites, some have DHCP, some have DHCP but require me to use fixed IP addresses, some do not have DHCP and require me to use fixed IP addresses, etc.)

As a workaround,
 1. log out of failed GNOME3 session
 2. disconnect Ethernet cable
 3. re-issue 'startx' from console session
 4. observe GNOME3 session fire up correctly
 5. reconnect Ethernet cable
 6. see NetworkManager happily give me back my wired connection


Attaching what I was able to capture at framebuffer console session upon logout.

Comment 1 Alessandro Suardi 2011-07-22 10:11:20 UTC
The issue has not surfaced in the last two attempts, after maintaining F15 updated constantly - and there have been for sure NetworkManager updates.

I will maintain this bug open for an extra week, where I am supposed to visit three different customers with distinct LAN address schemes, and if the issue doesn't pop up again I'll close the bug.

Comment 2 Alessandro Suardi 2011-07-31 16:17:19 UTC
Closing, as the issue hasn't been reproducing anywhere.


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