| 1 |
On Wed, Aug 25, 2010 at 4:00 PM, Stroller <stroller@××××××××××××××××××.uk>wrote: |
| 2 |
|
| 3 |
> |
| 4 |
> On 25 Aug 2010, at 04:36, Kevin O'Gorman wrote: |
| 5 |
> |
| 6 |
>> ... My problem has been that going to /etc/init.d |
| 7 |
>> |
| 8 |
>> and commanding "./xdm stop" seems to work, but has no effect on KDE. |
| 9 |
>> Manually killing kde (ps -ef | grep kde, etc) just starts another one. I |
| 10 |
>> finally figured out that I have to find the 'kdm' process and kill that, |
| 11 |
>> then a logoff or Ctl_Alt_BS actually gets rid of X, so I can do things like |
| 12 |
>> "X -configure" and so on. |
| 13 |
>> |
| 14 |
> |
| 15 |
> If you run `/etc/init.d/xdm stop` and then log out of KDE using the logoff |
| 16 |
> button in the Start Menu, what happens, please? Does xdm return? |
| 17 |
> |
| 18 |
> Stroller. |
| 19 |
> |
| 20 |
> |
| 21 |
Things have changed slightly since the last reboot. Now it goes like this: |
| 22 |
/etc/init.d/xdm stop |
| 23 |
Kde dies, xdm dies, ps -ef shows no signs of either one, and Ctl-Alt-F7 gets |
| 24 |
me a blank screen with a blinking cursor, but no response to the keyboard. |
| 25 |
|
| 26 |
Back in a root console, |
| 27 |
/etc/init.d/xdm start or /etc/init.d/xdm status |
| 28 |
Now reports that xdm is stopping. This goes on until I run out of patience, |
| 29 |
and zap xdm |
| 30 |
/etc/init.d/xdm zap |
| 31 |
/etc/init.d/xdm start |
| 32 |
|
| 33 |
which seems to work -- it gets me to a KDE login. I'm not aware of doing |
| 34 |
anything that would have made this change. |
| 35 |
|
| 36 |
-- |
| 37 |
Kevin O'Gorman, PhD |
Archives