On 05/16/2013 08:09 PM, Sharon Kimble wrote:
> On 16 May 2013 17:04, Linux-Fan <Ma_Sys.ma@web.de> wrote:
>>> B - Periodically, when logging back into fluxbox from another DE I getIt should actually output a tree which (on my system, lightdm will of
>> this
>>> error message showing in the logs 'BScreen::BScreen: an error occured
>> while
>>> querying the X server.
>>> another window manager already running on display:0
>>> Error: Couldn't find screens to manage.
>>> Make sure you don't have another window manager running.'
>>> I'm not aware of another window manager still running, but how do I kill
>> it
>>> if it is please?
>>
>> If you have htop installed you could use it to interactively find out
>> which processes are running on a virtual console. If you do not have
>> htop, you might also try pstree and kill (-s TERM) processes still
>> running below your login manager (if any).
>>
>
> I've installed 'htop' and am having a play with it. 'Pstree' seems to be
> showing everything in alpha order, how to get it showing what is below
> my log on manager, which is 'lightdm'?
course be different) ends with
~$ pstree | tail -n 10
|-udevd---2*[udevd]
|-xdm-+-Xorg
| `-xdm---ck-launch-sessi-+-fluxbox-+-icedove-bin-...
| | |-java---17*[{java}]
| | |-xcompmgr
| | |-xscreensaver
| | `-xterm---bash-+-pstree
| | `-tail
| `-ssh-agent
`-z_space_dapp
With lightdm I guess there should be some sort of "lightdm"-subtree
(instead of xdm on my system). You could look for its subprocesses and
terminate those which could be a window manager left from your DE.
However, I have also seen processes which no longer stick below the
correct part of the tree but instead go directly below init after their
parent was terminated. Therefore you might also try to look at pstree
(or htop) while in your DE to find out about the window manager and
check the whole tree for that process afterwards.
Htop has a similar view activated by pressing F5 but you can
additionally browse it and check how much of your CPU the process occupies.