On Wed, Aug 25, 2010 at 4:00 PM, Stroller
<stroller@stellar.eclipse.co.uk> wrote:
On 25 Aug 2010, at 04:36, Kevin O'Gorman wrote:
... My problem has been that going to /etc/init.d
and commanding "./xdm stop" seems to work, but has no effect on KDE. Manually killing kde (ps -ef | grep kde, etc) just starts another one. I finally figured out that I have to find the 'kdm' process and kill that, then a logoff or Ctl_Alt_BS actually gets rid of X, so I can do things like
"X -configure" and so on.
If you run `/etc/init.d/xdm stop` and then log out of KDE using the logoff button in the Start Menu, what happens, please? Does xdm return?
Stroller.
Things have changed slightly since the last reboot. Now it goes like this:
/etc/init.d/xdm stop
Kde dies, xdm dies, ps -ef shows no signs of either one, and Ctl-Alt-F7 gets me a blank screen with a blinking cursor, but no response to the keyboard.
Back in a root console,
/etc/init.d/xdm start or /etc/init.d/xdm status
Now reports that xdm is stopping. This goes on until I run out of patience, and zap xdm
/etc/init.d/xdm zap
/etc/init.d/xdm start
which seems to work -- it gets me to a KDE login. I'm not aware of doing anything that would have made this change.