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 590965 - gdm respawns on shutdown/restart from the menu
gdm respawns on shutdown/restart from the menu
Status: RESOLVED OBSOLETE
Product: gdm
Classification: Core
Component: general
2.27.x
Other Linux
: Normal normal
: ---
Assigned To: GDM maintainers
GDM maintainers
Depends on:
Blocks:
 
 
Reported: 2009-08-06 15:54 UTC by dinxter
Modified: 2013-12-16 19:57 UTC
See Also:
GNOME target: ---
GNOME version: 2.27/2.28



Description dinxter 2009-08-06 15:54:55 UTC
Please describe the problem:
gdm respawns on  shutdown/restart from the menu before being eventually automatically killed by the shutdown process

note i cant get this bug is usplash is disabled

seems something is happening with tty order as well
- on boot, system messages are on tty1, X on tty7 as normal
- on shutdown, system messages now appear on tty7 with gdm respawning on tty1

Steps to reproduce:
1. - boot to desktop with usplash enabled
2. - select shutdown or restart from desktop menu
3. - gdm respawns before being killed by the shutdown process


Actual results:
shutdown process begins, gdm closes(tty7). then it respawns on tty1 with system messages appearing on tty7 instead of tty1 as usual. the shutdown process then continues killing gdm 

Expected results:
shutdown process begins, gdm closes, usplash appears on tty7 and comp[uter eventually shuts down

Does this happen every time?
yes

Other information:
This is on ubuntu karmic up to date
gdm/karmic uptodate 2.27.4-0ubuntu6

launchpad bug
https://bugs.launchpad.net/ubuntu/+source/gdm/+bug/406962
Comment 1 Brian Cameron 2010-08-30 20:25:42 UTC
I can confirm that this problem also happens on OpenSolaris.  When this happens, it also seems that core files from various processes (e.g. metacity run by GDM) are left behind (perhaps because GDM is trying to launch such programs as needed services are being shut down).

I agree that GDM should inhibit restarting any display management when the system is in the process of shutting down.
Comment 2 Ray Strode [halfline] 2013-12-16 19:57:43 UTC
i think this probably got fixed when we redid the shutdown paths in the slave, if not, please reopen.