Bug 753099

Summary: "Something has gone wrong" at Gnome login after F15->F16 upgrade
Product: [Fedora] Fedora Reporter: Skippy <lecotegougdelaforce>
Component: gnome-shellAssignee: Owen Taylor <otaylor>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: unspecified    
Version: 16CC: browning48ky, maxamillion, otaylor, samkraju, walters
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-02-13 20:00:19 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
.xsession-errors
none
Xorg.0.log
none
relevant part of /var/log/messages
none
lspci -vvv output none

Description Skippy 2011-11-11 10:55:25 UTC 
Description of problem:
After upgrading from F15 to F16 through yum, then rebooting, I experienced the "something has gone wrong" screen after trying to login through GDM.  No matter how many times I tried, it wouldn't log into the Gnome session — although my delayed conky screen appeared on top of the "something has gone wrong" screen…

The most relevant message I could find in the logs was the following in .xsession-errors :
"g_dbus_connection_real_closed: Remote peer vanished with error: Underlying GIOStream returned 0 bytes on an async read (g-io-error-quark, 0). Exiting."

In order to isolate the problem I first moved every hidden directory of my /home/user to a backup directory, then I tried to log again and it worked.  Then I tried to find which directory was the problematic one by replacing the new directories by the old ones and relogging until I could not log in again.  Unfortunately I couldn't reproduce the issue anymore.

Then I removed all the new directories and copied the content of the backup directory to /home/user, so it should have been an exact copy of when it failed, apart from the modification times.  Oddly enough, again I couldn't reproduce anymore, so I can't give any information about why it failed at first.  All I can tell is that at first I removed the following directory and it didn't help : .dbus, .gconf, .gconfd, .gnome2.


Version-Release number of selected component (if applicable):
gnome-shell.i686                      3.2.1-2.fc16                       @fedora
gnome-session.i686                     3.2.1-2.fc16                      @fedora
dbus.i686                        1:1.4.10-3.fc16                         @fedora
gdm.i686                        1:3.2.1.1-6.fc16                         @fedora


Steps to Reproduce:
1. Upgrade from F15 to F16 through yum.
2. Reboot.
3. Try to log in.
  

Actual results:
"Something has gone wrong".


Expected results:
Access to Gnome-shell.


Additional info:
I have to mention that I use Gnome-shell in its fallback mode, with good ol'gnome-panel.
Comment 1 Skippy 2011-11-11 10:58:20 UTC 
Created attachment 533020 [details]
.xsession-errors
Comment 2 Skippy 2011-11-11 10:59:16 UTC 
Created attachment 533021 [details]
Xorg.0.log
Comment 3 Skippy 2011-11-11 11:04:45 UTC 
Created attachment 533025 [details]
relevant part of /var/log/messages
Comment 4 Skippy 2011-11-11 11:05:19 UTC 
Created attachment 533026 [details]
lspci -vvv output
Comment 5 Skippy 2011-11-11 11:08:36 UTC 
See also bug 737037 (Note to triagers : by "see also" I don't mean it's a duplicate, but that the issue could be somehow related).
Comment 6 Fedora End Of Life 2013-01-16 16:24:06 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 7 Fedora End Of Life 2013-02-13 20:00:23 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.