public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Igor Pechtchanski <pechtcha@cs.nyu.edu>
To: cygwin-xfree@cygwin.com
Subject: Re: -nounixkill doesn't seem to work (Was Re: Ctrl-Alt-Backspace)
Date: Sat, 06 Dec 2003 18:35:00 -0000	[thread overview]
Message-ID: <Pine.GSO.4.56.0312061324070.16580@slinky.cs.nyu.edu> (raw)
In-Reply-To: <Pine.LNX.4.55.0312061413130.2705@lupus.ago.vpn>

On Sat, 6 Dec 2003, Alexander Gottwald wrote:

> Igor Pechtchanski wrote:
>
> > Well, technically, adding "-nounixkill" to the XWin.exe parameter list
> > should do it, but it doesn't work for me.  When I open an XWin session on
> > a Win2k SP3 machine, Ctrl-Alt-Backspace still happily kills the server,
> > even with -nounixkill.  The command I used to start the X server was
>
> add the option -unixkill. This will ask you indstead of just killing the
> server.

Thanks, this worked like a charm.

> The problem is that the 4.3 release of XFree binds the killing of the server
> to the keycode "TerminateServer". There is currently no way to override this
> but you can remove that binding from keycode 22.
>
>  xmodmap -e "keycode 22 = BackSpace"

This, however, not only didn't change anything (Ctrl-Alt-Backspace still
exited X), but also crashed XWin.exe.  I doubt the stack dump is of any
use with a non-debug version of XWin, but I can provide it if people
request, as well as the corresponding XWin.log (which doesn't contain any
details of the crash).  I believe I've also posted the details of my setup
earlier in this thread.  To reproduce the problem, run

$ XWin :1.0 -unixkill &

Try exiting it with Ctrl-Alt-Backspace, and press "Cancel".

$ xmodmap -display :1.0 -e "keycode 22 = BackSpace"

Try exiting again with Ctrl-Alt-Backspace, and press "Exit".

XWin will crash with a segfault.  I'd be willing to try a debug version
and get a real stack trace if developers can't reproduce it.
	Igor
-- 
				http://cs.nyu.edu/~pechtcha/
      |\      _,,,---,,_		pechtcha@cs.nyu.edu
ZZZzz /,`.-'`'    -.  ;-;;,_		igor@watson.ibm.com
     |,4-  ) )-,_. ,\ (  `'-'		Igor Pechtchanski, Ph.D.
    '---''(_/--'  `-'\_) fL	a.k.a JaguaR-R-R-r-r-r-.-.-.  Meow!

"I have since come to realize that being between your mentor and his route
to the bathroom is a major career booster."  -- Patrick Naughton


  reply	other threads:[~2003-12-06 18:35 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-05 23:17 Ctrl-Alt-Backspace Jack Tanner
2003-12-06  0:51 ` Ctrl-Alt-Backspace linda w
2003-12-06 13:12   ` Ctrl-Alt-Backspace Alexander Gottwald
2003-12-06  5:18 ` -nounixkill doesn't seem to work (Was Re: Ctrl-Alt-Backspace) Igor Pechtchanski
2003-12-06 13:15   ` Alexander Gottwald
2003-12-06 18:35     ` Igor Pechtchanski [this message]
2003-12-08 11:18       ` Alexander Gottwald
2003-12-08 17:58         ` Requesting a debug XFree86 snapshot (Was Re: -nounixkill doesn't seem to work) Igor Pechtchanski
2003-12-08 19:08           ` Alexander Gottwald
2003-12-08 21:37             ` Igor Pechtchanski
2003-12-09  1:34               ` Alexander Gottwald
2003-12-18  2:58       ` -nounixkill doesn't seem to work (Was Re: Ctrl-Alt-Backspace) Takuma Murakami
2003-12-18  3:02         ` Harold L Hunt II
2003-12-18 17:55         ` Harold L Hunt II
2003-12-18 19:10           ` Igor Pechtchanski

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=Pine.GSO.4.56.0312061324070.16580@slinky.cs.nyu.edu \
    --to=pechtcha@cs.nyu.edu \
    --cc=cygwin-xfree@cygwin.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).