> 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?
It sounds like it.
>
> When started this way, running xmodmap -pk against the server does show:
>
> 22 0xff08 (BackSpace) 0xfed5 (Terminate_Server)
When Ctl-Alt-BkSpc won't kill the server (i.e. when the server is started
with xdm and without the HandleSpecialKeys Always option), is the terminate
action perhaps bound to some other key sequence? That would why the fallback
didn't happen.
A good way to check would be to run this command:
xkbcomp -xkb $DISPLAY -o - | grep -i -3 terminate
Normally this should show the interpretation of the Terminate_Server keysym
which should look like this:
interpret Terminate_Server+AnyOfOrNone(all) {
action= Terminate();
};
which means whenever it sees the Terminate_Server keysym, with or without any
modifiers, that it should perform the Terminate() action (i.e. cause the server
to terminate).
Additionally, there should be some binding of one or more keys to either the
Terminate_Server keysym or the Terminate() action. The default map has this
binding:
key <BKSP> {
type="CTRL+ALT",
symbols[Group1]= [ BackSpace, Terminate_Server ]
};
meaning that the backspace key usually will generate a BackSpace keysym, except
that when modified by CTRL and ALT, it will generate a Terminate_Server keysym,
which is exactly the result that xmodmap -pk showed for you when things are
working.
So what does the xkb map show when things aren't working?
_______________________________________________
Devel mailing list
[EMAIL PROTECTED]
http://XFree86.Org/mailman/listinfo/devel
