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 608024 - gdm does not wait for its components termination (possible race condition)
gdm does not wait for its components termination (possible race condition)
Status: RESOLVED OBSOLETE
Product: gdm
Classification: Core
Component: general
2.28.x
Other Linux
: Normal minor
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks:
 
 
Reported: 2010-01-25 12:21 UTC by Stanislav Brabec
Modified: 2013-12-16 20:27 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Stanislav Brabec 2010-01-25 12:21:05 UTC 
It seems that gdm starts user session without confirmation that all gdm components (e. g. metacity) successfully finished.

Under some circumstances it can cause broken session. For example when metacity is affected by some bug that prevents from quitting, gdm continues to start session. But the session is gdm's metacity.

It is also possible to reproduce this problem by pausing gdm's metacity in debugging session.

Symptoms:

In case on metacity as user session window manager, ~/.xsession-errors contains:

Window manager warning: Screen 0 on display ":0.0" already has a window manager; try using the --replace option to replace the current window manager.

Example of bug triggering misbehavior: bug 604867.
Comment 1 Ray Strode [halfline] 2013-12-16 20:27:04 UTC 
Thanks for taking the time to report this bug.
However, you are using a version that is too old and not supported anymore. GNOME developers are no longer working on that version, so unfortunately there will not be any bug fixes for the version that you use.

By upgrading to a newer version of GNOME you could receive bug fixes and new functionality. You may need to upgrade your Linux distribution to obtain a newer version of GNOME.
Please feel free to reopen this bug if the problem still occurs with a newer version of GNOME.