On Thu, Mar 28, 2013 at 1:34 PM, Robert Benjamin <benjie1 at cox.net> wrote: > > On 3/28/2013 1:29 PM, Les Mikesell wrote: >> On Thu, Mar 28, 2013 at 12:19 PM, Robert Benjamin <benjie1 at cox.net> wrote: >>>> Things never work very well for me before having coffee either, but >>>> that's probably not the real solution. So when you established that >>>> your network and DNS was working, Gnome was working too? Can you log >>>> in on a virtual character-mode terminal session (control-alt-F2) and >>>> try the ifconfig and dig commands again? If everything appears to >>>> work there, I'd try a 'yum update' just on general principles. >>> Sure. Will do dig and ifconfig again. Did yum update this morning, >>> 23 packets updated .Worked fine. You need the output from dig and >>> ifconfig again? >> No, if yum update worked we know the network is OK. What happens if >> run 'init 3' (should shut down the partly-working X session), and then >> 'startx' which will start a new one under your existing login? >> > init 3 it did shutdown the partly working X session. Several line > flashed on screen and 2 had FAILED at end of line. Too fast to readtwhat > it said. > startx Fatal server error: > Server is already active for display 0 > If the server is no longer running, remove /tmp/ > .X0-lock and start again. > I did yum remove /tmp/ .X0-lock. It removed 17 packages and > then I did startx (again) Got the same re: remove /tmp/ .X0-lock. One > other line I saw Unable to connect to X server was present in output of > startx. That should have just been an 'rm /tmp/.X0-lock' (a file, not packages). Not sure how much damage has been done at this point. If you know the package names, try to 'yum install' them back again. And rm the file, and try startx again. -- Les Mikesell lesmikesell at gmail.com