Created attachment 908843 [details] Journal output of a failed login attempt Description of problem: Several login attempts are necessary to sucessfuly start gnome-session. The required number of tries is variable, possibily indicating a race condition. When it fails the session start attempt, lightdm login screen is returned. Also, the following error is displayed on journal: gnome-session[1285]: (gnome-settings-daemon:1465): Gdk-WARNING **: gnome-settings-daemon: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. gnome-session[1285]: Window manager warning: Log level 16: gnome-shell: Fatal IO error 11 (Resource temporarily unavailable) on X server :0. Version-Release number of selected component (if applicable): 3.10.1 How reproducible: Variable reproducibility, but I have been able to consistently reproduce this behaviour since I installed this system. Steps to Reproduce: 1. Start lightdm. 2. Login with any user. 3. There's a try to load gnome-session, but it get's back to lightdm. Actual results: Lightdm is loaded again, and some error messages are printed in the log. Journal attached. Expected results: A deterministic sucessfull login.
Created attachment 908844 [details] Journal output of a successfull login attempt
Created attachment 911612 [details] Journal output of a failed login attempt with debug enabled I was able to log a failed login attempt with debug enabled.
I confirm this issue is also present when using gdm instead of lightdm as login manager. I'm attaching the journal logs.
Created attachment 937338 [details] Journal output of a failed login attempt with GDM
Created attachment 937339 [details] Journal output of a successfull login attempt with GDM
This bug is still present at a clean install of Fedora 21, and got even more frequent.
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.
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.