• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 347
  • Last Modified:

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?

0
screwdriver
Asked:
screwdriver
  • 4
  • 3
1 Solution
 
ahoffmannCommented:
exec xlogout -confirm

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.
0
 
screwdriverAuthor Commented:
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


0
 
ahoffmannCommented:
your X session is over when the last command in the .xsession file terminates.
So if you remove xlogout there are no more running programs inside this shell. You need to start at least one program which does not terminate or put itself in background.
See  man xdm  for more details.
0
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
screwdriverAuthor Commented:
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 ?

 
0
 
ahoffmannCommented:
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.
0
 
screwdriverAuthor Commented:
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. :)


0
 
ahoffmannCommented:
.. take bike (if possible) and it gets down to 10 minutes :-))
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Subnet Calculator

The subnet calculator helps you design networks by taking an IP address and network mask and returning information such as network, broadcast address, and host range.

One of a set of tools we're offering as a way of saying thank you for being a part of the community.

  • 4
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now