Restore Alt-Ctl-Backspace As Server Kill

[Tim Daneliuk]

Tim Daneliuk wrote:
> Jon TURNEY wrote:
>> Tim Daneliuk wrote:
>>> Tim Daneliuk wrote:
>>>> I really hate the assignment of Alt-F4 to kill a running X-server.
>>>> What magic must I perform to set it back to the more traditional
>>>> Alt-Ctl-Backspace combo?  Thanks.
>>> Let me ask this more properly.  I know how to use -nounixkill and
>>> -nowinkill to prevent keyboard initiated kills of the server.
>>>
>>> I use a VirtuaWin on a WinXP system to provide multiple desktops.
>>> One of them is activated via Ctrl-Alt-F4.  When I do this,
>>> it kills the running instance of Cygwin/X which apparently sees
>>> this key combo as a "kill server" command.  This is true whether
>>> or not -nounixkill and/or -nowinkill are in use.
>>>
>>> Ideas?
>> I'm afraid I'm not able to reproduce this.
>>
>> I see that the code doesn't consider the state of the control or shift
>> keys when looking for alt-f4 to close the server (so ctrl-alt-f4 also
>> closes it, which is possibly a bug), but this should also be disabled by
>> -nowinkill, which is what I observe.
>>
> 
> Very strange.  I start my Xserver instance like this:
> 
> run XWin :$SCREEN -nowinkill -unixkill -ac +kb -clipboard -silent-dup-error -nod
> ecoration&
> 
> 
> Then I login like this (both of these via a cygwin shell script):
> 
> ssh $USER@$REMOTE "export DISPLAY=$DISPLAY;$COMMAND;logout"
> 
> I can bounce between VirtuaWin sessions all like via Ctl-Alt-<Session #> and
> all is well until I try Ctl-Alt-4.  If I exit VirtuaWin, that key combination
> does not kills the session, so this hints at this being a VirtuaWin problem
> not one in cygwin ...
> 
> 
> 
> 

OK ... I've narrowed the problem down and it is REALLY strange:

In updating to VirtuaWin 4.01, I notice that I either misreported the
problem and/or the bug has expanded with this new release. Now when I
switch to any other virtual desktop, it randomly kills the Xsession.

What is *really* interesting about this is that it seems to do this
only if I launch a window manager as the $COMMAND argument above.
If I just kick off an xterm, and then manually launch the wm from there,
the problem disappears.

IOW, this works:

  ssh user@machine "export DISPLAY=mymachine:9;xterm;logout"

But both of these have the problem:

  ssh user@machine "export DISPLAY=mymachine:9;startfluxbox;logout"
  ssh user@machine "export DISPLAY=mymachine:9;exec startfluxbox;logout"


Now the "Narrowing It Down" and "Really Strange" part.  This works
just fine:

  ssh user@machine "export DISPLAY=mymachine:9;exec fluxbox;logout"

It seems that something (I have not figured out just what yet)
about the default fluxbox startup script (on FreeBSD 6-STABLE in this
case) is interacting with the cygwin X server and killing it.

Oiy, my head ...

---------------------------------------------------------------------------
Tim Daneliuk     tundra@tundraware.com
PGP Key:         http://www.tundraware.com/PGP/


--
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple
Problem reports:       http://cygwin.com/problems.html
Documentation:         http://x.cygwin.com/docs/
FAQ:                   http://x.cygwin.com/docs/faq/