Fluxbox questions

[Sharon Kimble]

I've been using 'fluxbox' for about a month now and really like it, but I do have some questions that I haven't been able to find answers for.

A - In the menu, how can I get working lines for logging off, I currently use '[exec] (Log off) {exit}' but aren't satisfied with it, and also for restarting fluxbox, currently '[restart] (Restart) {restart}' ?

B - Periodically, when logging back into fluxbox from another DE I get 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?

Hopefully thanks

Sharon.

--

A taste of linux = http://www.sharons.org.uk/index.html
efever = http://www.efever.blogspot.com/
efever = http://sharon04.livejournal.com/
Debian Wheezy,  Fluxbox 1.3.5, LibreOffice 4.0.3.3, 
Registered Linux user 334501

[Linux-Fan]

On 05/16/2013 05:35 PM, Sharon Kimble wrote:
> I've been using 'fluxbox' for about a month now and really like it, but I
> do have some questions that I haven't been able to find answers for.
>
> A - In the menu, how can I get working lines for logging off, I currently
> use '[exec] (Log off) {exit}' but aren't satisfied with it, and also for
> restarting fluxbox, currently '[restart] (Restart) {restart}' ?

Check /etc/X11/fluxbox/fluxbox-menu, on my system this ends:
[restart] (Restart)
[exit] (Exit)
Which does logout and restart. Are they a better solution for you?

> B - Periodically, when logging back into fluxbox from another DE I get 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).

> Hopefully thanks
> Sharon.

HTH
Linux-Fan

--
http://masysma.ohost.de/


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/51950375...@web.de

[André Nunes Batista]

[Frank McCormick]

On 05/16/2013 11:35 AM, Sharon Kimble wrote:
> I've been using 'fluxbox' for about a month now and really like it, but
> I do have some questions that I haven't been able to find answers for.
>
> A - In the menu, how can I get working lines for logging off, I
> currently use '[exec] (Log off) {exit}' but aren't satisfied with it,
> and also for restarting fluxbox, currently '[restart] (Restart) {restart}' ?

What exactly is wrong with those commands ?

>
> B - Periodically, when logging back into fluxbox from another DE I get
> 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?

To kill it you'll need its' PID - try ps -A in a terminal window.

--
Cheers
Frank

--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Archive: http://lists.debian.org/51951256...@videotron.ca

[Andrei POPESCU]

On Jo, 16 mai 13, 13:53:11, André Nunes Batista wrote:
> I do not wish to hijack this thread, but I have a similar question:

But you did hijack the thread and your question is not similar. I'm
changing the subject to make it more visible.

> I started using openbox a few days ago and since then I use pm-suspend
> on terminal to suspend my debian machine. The thing is pm-suspend
> requires root permission and obmenu runs with standard permissions.
>
> Is there a way out? Any group I should add my standard user?

One way would be sudo with the NOPASSWD option.

Kind regards,
Andrei
--
http://wiki.debian.org/FAQsFromDebianUser
Offtopic discussions among Debian users and developers:
http://lists.alioth.debian.org/mailman/listinfo/d-community-offtopic

[Frank McCormick]

On 05/16/2013 12:53 PM, Andr� Nunes Batista wrote:
> I do not wish to hijack this thread, but I have a similar question:

Why don't you just start a new thread ?

>
> I started using openbox a few days ago and since then I use pm-suspend
> on terminal to suspend my debian machine. The thing is pm-suspend
> requires root permission and obmenu runs with standard permissions.
>
> Is there a way out? Any group I should add my standard user?

Why don't you just run it from the menu using sudo ?

--
Cheers
Frank


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Archive: http://lists.debian.org/519510E4...@videotron.ca

[Sharon Kimble]

On 16 May 2013 17:04, Linux-Fan <Ma_S...@web.de> wrote:

On 05/16/2013 05:35 PM, Sharon Kimble wrote:
> I've been using 'fluxbox' for about a month now and really like it, but I
> do have some questions that I haven't been able to find answers for.
>
> A - In the menu, how can I get working lines for logging off, I currently
> use '[exec] (Log off) {exit}' but aren't satisfied with it, and also for
> restarting fluxbox, currently '[restart] (Restart) {restart}' ?

Check /etc/X11/fluxbox/fluxbox-menu, on my system this ends:
   [restart] (Restart)
   [exit] (Exit)
Which does logout and restart. Are they a better solution for you?

I cant get back into fluxbox yet I cant say.  

> B - Periodically, when logging back into fluxbox from another DE I get 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'? 

Thanks

Sharon. 

--

--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org
Archive: http://lists.debian.org/51950375...@web.de

[Sharon Kimble]

On 16 May 2013 18:07, Frank McCormick <debia...@videotron.ca> wrote:

On 05/16/2013 11:35 AM, Sharon Kimble wrote:

I've been using 'fluxbox' for about a month now and really like it, but
I do have some questions that I haven't been able to find answers for.

A - In the menu, how can I get working lines for logging off, I
currently use '[exec] (Log off) {exit}' but aren't satisfied with it,
and also for restarting fluxbox, currently '[restart] (Restart) {restart}' ?

  What exactly is wrong with those commands ?

They don't seem to work quickly, I'm looking for something which is speedy. 

 

B - Periodically, when logging back into fluxbox from another DE I get
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?

  To kill it you'll need its' PID - try ps -A in a terminal window.

But first I need to know what the programme name is, and there's the problem.  

Thanks

[Linux-Fan]

On 05/16/2013 08:09 PM, Sharon Kimble wrote:
> On 16 May 2013 17:04, Linux-Fan <Ma_S...@web.de> wrote:
>>> B - Periodically, when logging back into fluxbox from another DE I get
>> 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'?

It should actually output a tree which (on my system, lightdm will of
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.

--
http://masysma.ohost.de/

--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Archive: http://lists.debian.org/519524A0...@web.de

[Sharon Kimble]

This is my pstree http://dpaste.com/1168992/ and i close all wm programmes under lightdm, but its still not allowing me to log back into fluxbox.  

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.

This is really bugging me, and I may have to write a script to kill everything before I log into fluxbox.  

Thanks

Sharon.

[Linux-Fan]

On 05/16/2013 09:09 PM, Sharon Kimble wrote:
> On 16 May 2013 19:25, Linux-Fan <Ma_S...@web.de> wrote:

[...]

>> It should actually output a tree which (on my system, lightdm will of
>> 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.
>>
>
> This is my pstree http://dpaste.com/1168992/ and i close all wm programmes
> under lightdm, but its still not allowing me to log back into fluxbox.

I find this part most interesting:

├─2*[lightdm─┬─Xorg]
│ ├─lightdm─┬─lxsession─┬─caja───3*[{caja}]]
│ │ │ ├─claws-mail───{claws-mail}]
│ │ │ ├─clipit]
│ │ │ ├─lxpanel]
│ │ │ ├─openbox]
│ │ │ ├─pcmanfm]
│ │ │ ├─ssh-agent]
│ │ │ ├─zim]
│ │ │ └─{lxsession}]
│ │ └─{lightdm}]
│ ├─lightdm]
│ └─2*[{lightdm}]]

There is a whole lot of programs still running -- check the lxsession
subtree: An openbox (which is a window manager) is still running and
some other LXDE stuff as well (pcmanfm, lxpanel), also a mail client. To
kill the last window manager just terminate "openbox" via killall
openbox. However, it might be required to terminate the whole tree,
probably something like killall -s TERM lxsession or such. On the other
hand, I am unsure how much lxsession belongs to lightdm, i.e. might it
be necessary to keep lightdm running?

>> 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.
>>
> This is really bugging me, and I may have to write a script to kill
> everything before I log into fluxbox.

Or a script to terminate your session upon logoff.

HTH
Linux-Fan

--
http://masysma.ohost.de/


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Archive: http://lists.debian.org/51953D4A...@web.de

[Lisi Reisz]

On Thursday 16 May 2013 19:12:45 Sharon Kimble wrote:
> >   To kill it you'll need its' PID - try ps -A in a terminal window.
> >
> > But first I need to know what the programme name is,

Or be very patient, and read through all the applications running, starting at
the bottom of teh list ( <# ps ax>) until you get to a DE or WM, then note
its/their PID and kill it/them.

I have done this in similar circumstances.

HTH
Lisi

--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Archive: http://lists.debian.org/201305162300.1...@gmail.com

[Sharon Kimble]

I'm sorry I forgot to say that when I couldn't get into fluxbox I reverted to lxde for my working DE , which si why all the lxde stuff is running. 

>> 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.
>>
> This is really bugging me, and I may have to write a script to kill
> everything before I log into fluxbox.

Or a script to terminate your session upon logoff.

Yes, thats a good idea.

Thanks

Sharon. 

-- 

[Linux-Fan]

On 05/17/2013 09:13 AM, Sharon Kimble wrote:
> On 16 May 2013 21:10, Linux-Fan <Ma_S...@web.de> wrote:
>
>> On 05/16/2013 09:09 PM, Sharon Kimble wrote:

[...]

Of course you need to look at pstree while you are not logged into LXDE
in order to find out about processes remaining from before the logout.

--
http://masysma.ohost.de/


--
To UNSUBSCRIBE, email to debian-us...@lists.debian.org
with a subject of "unsubscribe". Trouble? Contact listm...@lists.debian.org

Archive: http://lists.debian.org/51967501...@web.de

[André Nunes Batista]

Thank you!

Sorry for the trouble. I did not create a new thread because I knew I
was being blind to a very trivial question. I forgot to mention I had
already tried sudo but it wouldn't suspend even so. The problem was I do
not normally use sudo and I was stupid enough to insert it directly to
obmenu without testing it on shell priorly. NOPASSWD was indeed what I
missed.

--
-- André Nunes Batista

[Sharon Kimble]

I've found the solution to this problem - it is that /tmp/.X0-lock is owned by root. Changed it to $USER and I was able to log back into fluxbox very easily. So far its worked okay. Thanks for all the ideas from various folks.

Sharon.