FS#16719 - [gdm] 2.28 prevents shutdown daemons from being displaying

Attached to Project: Arch Linux
Opened by John (graysky) - Sunday, 18 October 2009, 11:39 GMT
Last edited by Andrea Scarpino (BaSh) - Saturday, 26 March 2011, 11:31 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To Jan de Groot (JGC)
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 3
Private No

Details

Description: System shutdown does not display the daemons screen indicating progress of various daemons contained in /etc/rc.shutdown as the system goes down. All that is displayed is the standard login prompt (Arch 2.6.31: whatever"). Downgrading gdm back to gdm-2.20.10-2 fixes this problem.

Additional info:
* package version(s) - gdm-2.28.0-1

Steps to reproduce: Attempt a shutdown on a box running the gdm package mentioned above.
This task depends upon

Closed by  Andrea Scarpino (BaSh)
Saturday, 26 March 2011, 11:31 GMT
Reason for closing:  Fixed
Additional comments about closing:  gdm 2.32.0
Comment by John (graysky) - Saturday, 24 October 2009, 11:22 GMT
Also true with gdm-2.28.1-1
Comment by John (graysky) - Tuesday, 29 December 2009, 12:30 GMT
EDIT: after running the downgraded package I have noticed that the showdown progress is not always displayed so I am skeptical that this is solely related to the gdm package. I have also read in the forums about others not using gdm at all experiencing this behavior. For example: http://bbs.archlinux.org/viewtopic.php?id=87452
Comment by mattia (nTia89) - Saturday, 06 March 2010, 14:40 GMT
also for me with GDM=2.28.0 , 2.28.1 , 2.29.6 ....

maybe this isn't an 'gdm' bug ...
Comment by John (graysky) - Saturday, 06 March 2010, 15:31 GMT
Yeah, maybe not. If using the inittab method to load gdm the system seems to shutdown normally. It only acts as I have described when launching gdm from /etc/rc.d/gdm.
Comment by mattia (nTia89) - Saturday, 06 March 2010, 15:57 GMT
then the problem is connected to DAEMON launching mode ?
Comment by John (graysky) - Saturday, 06 March 2010, 16:10 GMT
I think so... when I opened the ticket originally, I didn't know about the inittab method and the timing of the error coincided with the 2.28 upgrade so it made sense to call it a gdm problem at the time.
Comment by mattia (nTia89) - Saturday, 06 March 2010, 16:32 GMT
we can start a thread where ask users to check if this inittab method works; i open a thread in my italian forum and if i've a positive match i post a comment here...
Comment by Francisco Pina (Stunts) - Sunday, 11 April 2010, 22:02 GMT
I'm using the inittab method for booting to GDM in 2 PC's running Arch.
In my x86_64 laptop I get to see the daemon during the shutdown process.
However, in my i686 eeePC I don't. what seems to be happening is that after the shutdown process begins, GDM is killed and I get a "flash" at the daemons being shut down; afterwards I get the GDM screen loading again - like it had been respawned. After a few seconds (GDM doesn't have a chance to fully load) I'm thrown into the console login prompt and the computer shutsdown.
The behaviour is the same both on shutdown and reboot, in case it makes any difference.
Comment by John (graysky) - Sunday, 11 July 2010, 16:09 GMT
probably safe to close this ticket - using the inittab method fixes the problem
Comment by Francisco Pina (Stunts) - Sunday, 11 July 2010, 22:45 GMT
Unfortunately the inittab method does not solve the problem for me... At least in one of my computers this is still an issue.
In fact, this didn't happen when I launched GDM as a daemon.
What I *think* is happening here is the following:
GNOME receives shutdown signal, and starts rebooting the computer;
GDM gets shutdown in the process;
GDM respawns, as it is the expected behaviour in case it gets killed for some reason when using the inittab method;
This forces a tty change and thus, the shutdown daemons are not displayed.

Has anyone got any opinions on this? Or how can I verify that what I think is happening really is happening? Where does all this get logged into (if at all)?

Thanks.
Comment by Heorhii Valakhanovich (tormoz) - Monday, 18 October 2010, 14:02 GMT
Looks like shutdown log can be seen in VT on which X was running (usually vt7), but screen switched back to vt0, for my point of view it's not comfortable.

Loading...