After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 732200 - Possible race condition on session start
Possible race condition on session start
Status: RESOLVED OBSOLETE
Product: gnome-session
Classification: Core
Component: gnome-session
3.10.x
Other Linux
: Normal critical
: ---
Assigned To: Session Maintainers
Session Maintainers
Depends on:
Blocks:
 
 
Reported: 2014-06-25 04:07 UTC by Bernardo Donadio
Modified: 2016-09-28 14:21 UTC
See Also:
GNOME target: ---
GNOME version: 3.9/3.10

Attachments
Journal output of gnome-session --debug (83.04 KB, text/plain)
2014-06-25 04:07 UTC, Bernardo Donadio 		Details

Description Bernardo Donadio 2014-06-25 04:07:20 UTC 
Created attachment 279167 [details]
Journal output of gnome-session --debug

Several login attempts are necessary to successfully start gnome-session. The required number of tries is variable, possibly 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.

Using gnome-session-3.10.1.1.fc20.

Attached there's the journal output of gnome-session being run with --debug enabled when there's a session start failure.
Comment 1 Michael Catanzaro 2016-09-13 22:04:29 UTC 
Can you reproduce it with a modern version of gnome-session?
Comment 2 Bernardo Donadio 2016-09-28 14:21:53 UTC 
I don't even have the original hardware anymore.

Closing since reproducibility is unlikely.