# emerge info Portage 2.0.51.19 (default-linux/x86/2005.0, gcc-3.3.5-20050130, glibc-2.3.4.20041102-r1, 2.6.11-gentoo-r6 i686) # epm -q gdm gdm-2.6.0.7 After a world update to stable, gdm no longer functions. The greeter will start, display the X background, and then immediately terminate. Rinse and repeat until gdm errors out. kdm, however, works without a problem. If I disable /etc/init.d/xdm altogether, I can startx without a problem. I've Google'd for hours on this subject. Only remotely similar references to gdm behavior have been cited in earlier (2.4) builds of gdm. I've tried updating to ~x86 gdm 2.6.0.9 but the error was not corrected. Further, I downgraded to gdm 2.6.0.4 (what was previously running on the system) and the behavior is the same. I enabled full debugging information (trace information that provides very little actual detail as to what happened). I get the following: /var/log/gdm/:0.log ------------------- X Window System Version 6.8.2 Release Date: 9 February 2005 X Protocol Version 11, Revision 0, Release 6.8.2 Build Operating System: Linux 2.6.11-gentoo-r6 i686 [ELF] Current Operating System: Linux pic 2.6.11-gentoo-r6 #1 SMP Mon Apr 18 12:45:19 CDT 2005 i686 Build Date: 17 May 2005 Before reporting problems, check http://wiki.X.Org to make sure that you have the latest version. Module Loader present Markers: (--) probed, (**) from config file, (==) default setting, (++) from command line, (!!) notice, (II) informational, (WW) warning, (EE) error, (NI) not implemented, (??) unknown. (==) Log file: "/var/log/Xorg.0.log", Time: Wed Jun 1 16:07:19 2005 (==) Using config file: "/etc/X11/xorg.conf" (EE) GARTInit: Unable to open /dev/agpgart (No such device) (WW) I810(0): Failed to set up write-combining range (0xf0000000,0x8000000) Could not init font path element /usr/share/fonts/local/, removing from list! Note: the /dev/agpgart error is normal (I believe it's a conflict with the vesafb). The error and warning above occur also when "startx" is manually invoked. Excerpt from /var/log/syslog ---------------------------- Jun 1 15:03:48 localhost gdm[22246]: Sending START_NEXT_LOCAL Jun 1 15:03:48 localhost gdm[22246]: gdm_slave_greeter: Running greeter on :0 Jun 1 15:03:48 localhost gdm[22082]: Handling message: 'START_NEXT_LOCAL' Jun 1 15:03:48 localhost gdm[22082]: (child 22246) gdm_slave_child_handler Jun 1 15:03:48 localhost gdm[22246]: gdm_slave_greeter: Greeter on pid 22299 Jun 1 15:03:48 localhost gdm[22246]: Sending GREETPID == 22299 for slave 22246 Jun 1 15:03:48 localhost gdm[22246]: Sending GREETPID 22246 22299 Jun 1 15:03:48 localhost gdm[22082]: Handling message: 'GREETPID 22246 22299' Jun 1 15:03:48 localhost gdm[22082]: Got GREETPID == 22299 Jun 1 15:03:48 localhost gdm[22082]: (child 22246) gdm_slave_usr2_handler: :0 got USR2 signal Jun 1 15:03:48 localhost gdm[22299]: failsafe dialog failed (inhibitions: 0 0) Jun 1 15:03:48 localhost gdm[22299]: failsafe dialog failed (inhibitions: 0 1) Jun 1 15:03:48 localhost gdm[22299]: failsafe dialog failed (inhibitions: 1 1) Jun 1 15:03:48 localhost gdm[22246]: term_quit: Final cleanup Jun 1 15:03:48 localhost gdm[22246]: gdm_slave_quick_exit: Will kill everything from the display Jun 1 15:03:48 localhost gdm[22246]: gdm_server_stop: Server for :0 going down! Jun 1 15:03:48 localhost gdm[22246]: gdm_server_stop: Killing server pid 22255 Jun 1 15:03:48 localhost gdm[22082]: (child 22246) gdm_slave_child_handler Jun 1 15:03:48 localhost gdm[22082]: (child 22246) gdm_slave_child_handler: 22299 died Jun 1 15:03:48 localhost gdm[22082]: (child 22246) gdm_slave_child_handler: 22299 returned 1 Jun 1 15:03:49 localhost gdm[22246]: gdm_server_stop: Server pid 22255 dead Jun 1 15:03:49 localhost gdm[22246]: gdm_slave_quick_exit: Killed everything from the display Jun 1 15:03:49 localhost gdm[22082]: mainloop_sig_callback: Got signal 17 Jun 1 15:03:49 localhost gdm[22082]: gdm_cleanup_children: child 22246 returned 65
I also filed a Gnome Bugzilla bug with the full debug output for one cycle of gdm. http://bugzilla.gnome.org/show_bug.cgi?id=306282
your 'emerge info' should be added to bugreports, please do so now.
reporter submitted upstream, did not respond to request for emerge info. marking upstream ( and theres responses )
