Noob question but what command kills x server?
Hi,
Off the top of my head try...
press Alt+Ctrl+F1, and log into workspace 1 and execute this...
init3
or try...
sudo /etc/init.d/kdm stop
Hope it works.
Using the init states might kill more than the Xserver, as any other things that take place only on higher init states will also fail to launch. I used to know more about these processes when I used RPM based distros, so I'm rusty here. And, while I'm not sure of this, LinuxMCE may add more wrinkles to the mix.
Another thing is that, if I am recalling correctly, Ubuntu/Debian based distros set up init states differently than their RPM counterparts. I haven't used init states to control the Xserver since switching to DEB based distros as a result. I think your second suggestion of killing KDM may be the more productive route.
My general quick and dirty goto is: pkill X
If you are trying to kill KDE then on 1004: service kdm stop
and maybe follow with a pkill X
Tell me what you really want to happen and I can give you a better prescription.
Guys... hmm.
Would you PLEASE use Stop_X.sh in /usr/pluto/bin to kill the X server?
Come on, please, actually look at what we have in src/BootScripts instead of hacking at it with a club like a caveman. :)
-Thom
Thanks, I'll have another shot after work... had big problems that after a rebuild I have worked out to be stuffed HD or corrupt files and I think each time updatemedia hits one of those files the system turns to crap.
So drive is now out and I have the issues with nvidia 260 drivers so need to update.
I was going to do another reinstall since latest builds look to have newer drivers but swmbo is at breaking point so I need a stable machine quick... so if I still have issues after fixing that, well it was nice to know you all :p
Uhh... don't update.
I brokeded alotta stuff... esp nvidia stuff.
New build should fix everything, no clear answer on when that will happen.
Cool, no worries I pulled out an old backup so up and running for now.