Bug 930357 - possible racing condition on startup of X.org (in combination with gdm?)
Summary: possible racing condition on startup of X.org (in combination with gdm?)
Status: RESOLVED DUPLICATE of bug 939594
Alias: None
Product: openSUSE Tumbleweed
Classification: openSUSE
Component: GNOME (show other bugs)
Version: 201503*
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: E-mail List
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-05-11 07:52 UTC by Dominique Leuenberger
Modified: 2015-10-07 14:32 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Dominique Leuenberger 2015-05-11 07:52:55 UTC
It seems to happen in a couple test runs on openQA, that X cannot be started by gdm.

Such a test run example is https://openqa.opensuse.org/tests/61970

The journal contains this error:

> May 11 03:25:41 linux-csza /usr/lib/gdm/gdm-x-session[1280]: Fatal server error:
> May 11 03:25:41 linux-csza /usr/lib/gdm/gdm-x-session[1280]: (EE) xf86OpenConsole: Cannot open virtual console 7 (Permission denied)

Considering that re-running the test generally works, this seems to be a racing condition at one point.
Comment 1 Stefan Dirsch 2015-05-11 08:51:35 UTC
So let's reassign to GNOME component ...
Comment 2 Dominique Leuenberger 2015-09-25 15:03:42 UTC
My next one to tackle...

After studying the journal of failed and successful boots, it becomes apparent that in failed state:

- starting service gdm... done
happens WAY after X already died on us.. which means: 'something' else (which does not know about logind!) started X for us beforehand, resulting in the permission denied error.

The log also shows "Started X Display Manager", which indicates xdm.service has been started up.
Comment 3 Dominique Leuenberger 2015-10-07 14:32:14 UTC
Let's mark this as DUP of 939594

The fix has been found in the package xdm.

*** This bug has been marked as a duplicate of bug 939594 ***