On Mon, Jan 27, 2003 at 06:57:22PM -0500, Kevin Brosius wrote: >David Dawes wrote: >> >> >> On Sun, Jan 26, 2003 at 03:06:36AM -0500, Kevin Brosius wrote: >> >> >> Does the server work correctly other than the key sequence not >> >> working? If it is stuck somewhere, it might explain both why >> >> SIGTERM and SIGHUP didn't do anything and why the terminate key >> >> sequence didn't work. >> > >> >Yes, the server seems to work fine, other than ignoring Ctl-Alt-BkSpc. >> >Other Alt sequences work, like Ctl-Alt-+. >> >> Those other sequences are handled in the same way as Ctl-Alt-BkSpc, >> so it does point to the mapping for that one getting overriden after >> the X server starts. >> >> >> Could you send the 'xmodmap -pk' output? Are you running any >> >> xmodmap script as part of your startx/xdm rc files that might be >> >> re-mapping the BackSpace key? >> > >> >The patch doesn't seem to make a difference. >> > >> >I've attached xmodmap -pk. >> >> The only difference I see between yours and mine is that mine has the >> following for the backspace key: >> >> 22 0xff08 (BackSpace) 0xfed5 (Terminate_Server) >> >> while yours is: >> >> 22 0xff08 (BackSpace) >> >> >xmodmap scripts, that may be it. It looks like SuSE uses a .xinitrc >> >which may call 'xmodmap /usr/X11R6/lib/X11/Xmodmap' if it exists and >> >XSESSION_IS_UP is set. Although it comments that XSESSION_IS_UP is set >> >by xdm, which I am not running. If it where set, it would use an old >> >Xmodmap, as I've changed ProjectRoot on this machine and that default >> >path is an older version, 4.1.0. >> > >> >Other than that, I don't see anything calling xmodmap. And I don't >> >think it's calling that one, since it's xdm related. >> >> A way to double-check this is to run something like: >> >> startx /path/to/your/twm >> >> or just: 'XFree86' >> >> and see if the server terminate sequence works then. > > >Yes, this case works. So, something in my setup (an xmodmap call I >haven't located yet?) is incompatible with the recent changes?
I think it'd be best if XKB and xmodmap weren't mixed, but that's not something we can rely on. I'm not sure how best to handle having the ability to remap the special key sequences via XKB and the fact that many existing configurations are probably going to unwittingly wipe out the mapping for some of them. One possible way would be to make the ability to remap them optional, defaulting to the old hard-coded mappings. At the moment we default to checking for the server terminate action in the XKB map loaded at startup, and fall back to the hard-coded mappings when it isn't there. I don't know if we could sensibly trap and handle the server terminate mapping being removed after startup. >When started this way, running xmodmap -pk against the server does show: > > 22 0xff08 (BackSpace) 0xfed5 (Terminate_Server) That confirms that it's being changed by something later. David -- David Dawes Release Engineer/Architect The XFree86 Project www.XFree86.org/~dawes _______________________________________________ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
