Created attachment 350499 [details] Stripped down messages log Description of problem: After monitor power down if you try and login there is no gdm-greeter Version-Release number of selected component (if applicable): gdm-2.26.1-10.fc11.x86_64 How reproducible: Everytime Steps to Reproduce: 1.Logout 2.Monitor power off, which seems to be taking way too long 3.Try loging in again Actual results: Screen back drop is present, but the gdm-greeter and the bar at the bottom of the screen are missing. Expected results: Additional info: I find no errors in Xorg?.log, I compared the xorg.conf with the saved one after installing the latest Nvida driver. Init to level 1 and back to level 5 does not fix the issue, must reboot. From /var/log/messages it looks like gdm maybe faulting, see attached log extraction.
Should have added that this is a new install on new hardware. Video card is a EVGA 285 GTX card. All updates have been applied. I did turn off user list, restart button and shutdown button in the greeter using the following commands: gconftool-2 --config-source xml:readwrite:/etc/gconf/gconf.xml.defaults --direct --type bool --set /apps/gdm/simple-greeter/disable_user_list true gconftool-2 --config-source xml:readwrite:/etc/gconf/gconf.xml.defaults --direct --type bool --set /apps/gdm/simple-greeter/disable_restart_button true gconftool-2 --config-source xml:readwrite:/etc/gconf/gconf.xml.defaults --direct --type bool --set /apps/gdm/simple-greeter/disable_shutdown_button true I subsequently turned back on the restart and shutdown buttons but they are not showing up. Not sure this user interface is headed in the right direction.
More checking has found that processes appear not to be terminating. If I do an init 3 I still see many X11, gdm, and gnome processes. If I run this script: ps -efl | egrep "X11|gnome|gdm" | awk '{print $4}' | while read one do kill -9 $one done I'm able to do an init 5 and get logged back in at the console. Strange but running an init 5 from an ssh session off another system fails. Acts like it needs a display to run the init level change.
More research has found this to be a duplicate bug report. *** This bug has been marked as a duplicate of bug 499489 ***