Zac Medico wrote: > George Roberts wrote: > >> Technically both are started at the end of the boot sequence. However >> if I use "/etc/init.d/xdm zap" and then "/etc/init.d/xdm start" I am >> now getting a message "Setting up gdm ..." followed by "ERROR: could not >> open the Display Manager..." and then it hangs and I have to ctrl-c out >> of it. When I type xdm, it brings up the xdm log in screen and I can >> get back into gnome. I want my gdm back! >> Now my /var/log/xdm.log is now showing: >> _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6 >> _XSERVTransOpen: transport open failed for inet6/George:0 >> _XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6 >> >> 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 George 2.6.11-gentoo-r6 #8 SMP Fri Apr >> 29 13:09:31 MDT 2005 i686 >> Build Date: 07 July 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: Sat Jul 16 20:45:27 2005 >> (==) Using config file: "/etc/X11/xorg.conf" >> Using vt 7 >> > > What do you mean "both are started at the end of the boot sequence". > Why both gdm and xdm? > > Since xdm seems to be working it seems like you should be more > interested in a gdm log (unless gdm uses xdm.log). I think you should > put DISPLAYMANAGER="xdm" in rc.conf, run env-update, and see it > "/etc/init.d/xdm start" works for plain xdm. That will tell you > whether the problem is isolated in the /etc/init.d/xdm script (part of > xorg-x11) or instead isolated in the gdm package. > > Zac
Yes changing rc.conf to xdm, starts X and brings me to the xdm log in screen. No need to run env-update. -- gentoo-user@gentoo.org mailing list
