screwdriver
asked on
remove xlogout after changing from fvwm to windowmaker
My sysadmin setup the box to run fvwm window manager and xdm by default and I changed it to windowmaker.
At .xsession file, there's "exec xlogout -confirm" command that will display a logout button which I can press to logout from my session. I don't want to use this button with windowmaker and I prefer to choose "exit session" from windowmaker menu instead. So, I removed "exec xlogout -confirm" command from .xsession and this caused problem. Everytime I tried to login, the windowmaker started for a while, then I was sent back to xdm login&password window again.
How can I remove xlogout button, run windowmaker without any problem, and choose "exit session" from windowmaker menu to logout?
At .xsession file, there's "exec xlogout -confirm" command that will display a logout button which I can press to logout from my session. I don't want to use this button with windowmaker and I prefer to choose "exit session" from windowmaker menu instead. So, I removed "exec xlogout -confirm" command from .xsession and this caused problem. Everytime I tried to login, the windowmaker started for a while, then I was sent back to xdm login&password window again.
How can I remove xlogout button, run windowmaker without any problem, and choose "exit session" from windowmaker menu to logout?
ASKER
Yes, xlogout doesn't have & and I also don't have '&' right before the xlogout line.
Here is my .xsession looks like,
wmaker &
Xmailbox &
wmsetbg ~/picture/God2.jpg
sleep 2
exec xlogout -confirm
Here is my .xsession looks like,
wmaker &
Xmailbox &
wmsetbg ~/picture/God2.jpg
sleep 2
exec xlogout -confirm
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I still have no time to try your solution. If I don't run wmaker in background, will this solve the problem?
What's the different if I put 'exec' and if I don't ?
What's the different if I put 'exec' and if I don't ?
exec is not the problem. Exec executes the specified program and replaces the current one (where exec is called).
If you start wmaker in foreground, I suggest to change the order in your .xsession file, 'cause all following lines will only be executed if wmaker terminates.
But this may couse problems with Xmailbox or wmsetbg, check your man-pages for that.
> no time to try ...
Hmm, takes about 2 minutes.
If you start wmaker in foreground, I suggest to change the order in your .xsession file, 'cause all following lines will only be executed if wmaker terminates.
But this may couse problems with Xmailbox or wmsetbg, check your man-pages for that.
> no time to try ...
Hmm, takes about 2 minutes.
ASKER
Ok, I understand now. Still haven't tried it yet.
> no time to try ...
Hmm, takes about 2 minutes.
Correct! But I have to walk to school for 30 minutes, can't try it from home. :)
> no time to try ...
Hmm, takes about 2 minutes.
Correct! But I have to walk to school for 30 minutes, can't try it from home. :)
.. take bike (if possible) and it gets down to 10 minutes :-))
didn't have a final & , while all other lines befor have one, right?
If so, you must remove the & right before the line you removed.