mailing_list:
Hi,
yesterday I had a coule of nasty experiences with xdm, the X display manager. Indeed I discovered the when pressing mod-q repeatedly XMonad will quit, instead of restarting, and you will be prompted with a new xdm login screen.
I can always reproduce it: start X with xdm, and then login. Press mod-q twice or more and you are out.
I cannot reproduce if I connect to Xmd from a remote X server launched with the -query option.
For instance: /usr/bin/Xnest -ac -query localhost :1
will not reproduce the error.
I cannot reproduce it with Kdm (I did not try with Gdm since it's not installed on my system).
Can this be related to the way Xdm manages local sessions? I have the feeling that this could be the problem.
By the way it is quite a nasty experience, not different from a crash. And the user should be at least warned.
What's in your .xsession-errors? Are you breaking a pipe in your .xsession script? Are you in a race condition of some kind, so you end up forking and failing? -- Don