Bug 1114099

Summary: Oh no.Something has gone wrong - for only one user
Product: [Fedora] Fedora Reporter: jolarame <jolarame>
Component: gnome-sessionAssignee: Ray Strode [halfline] <rstrode>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: cschalle, jolarame, rstrode
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 21:22:18 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
last logs on concerned system
none
xorg log none

Description jolarame 2014-06-27 17:37:03 UTC
Description of problem: only one of 4 users encounter problem when trying to log in. no other explanation. Recently upgraded to fedora 20 (this users has been able to log in twice

tried to move.config for this user ==> same issue

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

gnome-session 3.10.1
How reproducible:


Steps to Reproduce:
1.try to login 
2.
3.

Actual results:
none

Expected results:
be able to login again

Additional info:

Comment 1 jolarame 2014-06-27 18:32:38 UTC
Created attachment 912909 [details]
last logs on concerned system

Comment 2 jolarame 2014-06-27 18:34:02 UTC
Created attachment 912910 [details]
xorg log

Comment 3 jolarame 2014-06-28 21:29:16 UTC
*** Bug 1113774 has been marked as a duplicate of this bug. ***

Comment 4 Ray Strode [halfline] 2014-07-07 12:14:40 UTC
so in a stock install that "Oh no!" message can come up in two cases:

1) gnome-settings-daemon doesn't start
2) the window manager doesn't start

You can identify which case by hitting alt-spacebar and seeing if a window menu appears over the splash.  If it does show a menu then that means it's gnome-settings-daemon that's not starting.  In that case:

From the menu choose minimize, then start a terminal and try to run 

/usr/libexec/gnome-settings-daemon --debug

to see if it says why it's not starting.

if it doesn't show a menu, then it's gnome-shell that's failing to start.  hit ctrl-alt-f6 to jump to a text login screen, log in as your user, then run

$ export DISPLAY=:0
$ gnome-shell --replace

and hit ctrl-alt-f1 to get back to your session.  Wait 10 seconds, then hit ctrl-alt-f6 again to see the messages.

Comment 5 Fedora End Of Life 2015-05-29 12:14:34 UTC
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. 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 '20'.

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 20 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 6 Fedora End Of Life 2015-06-29 21:22:18 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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
bug.

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