Re: 4.2.99.4 Test report : Ctr-Alt-BkSpc status?
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
Re: 4.2.99.4 Test report : Ctr-Alt-BkSpc status?
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? When started this way, running xmodmap -pk against the server does show: 22 0xff08 (BackSpace) 0xfed5 (Terminate_Server) -- Kevin ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: 4.2.99.4 Test report : Ctr-Alt-BkSpc status?
On Sat, Jan 25, 2003 at 02:42:57PM -0500, Kevin Brosius wrote: I've upgraded a machine from an early version of 4.2.99 (.1 I think) and find a couple problems. I am unable to kill the server with Ctr-Alt-BkSpc as mentioned in several earlier list emails, although this problem is listed as resolved. Are there changes required in XF86Config or elsewhere to make this work? I expected XF86Config would be compatible with earlier versions of 4.2.99.x. It should still work with that keyboard config, and it does for me. There have been some changes to allow the key sequences like this to be redefined via XKB, but Joe added code recently to automatically fall back to the built-in sequences when they're not defined in the XKB maps. None of that should be a problem for a complete 4.2.99.4 installation. I noticed that your log file was also for the mouse auto-detect problem you reported in a separate message. Have you confirmed that the two things are not related (I don't see how they should be, but it's worth checking if you haven't already)? Here are relevant sections of XF86Config: Section ServerLayout Identifier XFree86 Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Section InputDevice Identifier Keyboard0 Driver keyboard EndSection Try adding the following to your ServerLayout section: Option HandleSpecialKeys Always and see if that makes a difference. If it does, we'll need to track down why either the XKB map isn't working or it's not falling back correctly to the built-in settings. David -- David Dawes Release Engineer/Architect The XFree86 Project www.XFree86.org/~dawes ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
Re: 4.2.99.4 Test report : Ctr-Alt-BkSpc status?
David Dawes wrote: On Sat, Jan 25, 2003 at 02:42:57PM -0500, Kevin Brosius wrote: I've upgraded a machine from an early version of 4.2.99 (.1 I think) and find a couple problems. I am unable to kill the server with Ctr-Alt-BkSpc as mentioned in several earlier list emails, although this problem is listed as resolved. Are there changes required in XF86Config or elsewhere to make this work? I expected XF86Config would be compatible with earlier versions of 4.2.99.x. It should still work with that keyboard config, and it does for me. There have been some changes to allow the key sequences like this to be redefined via XKB, but Joe added code recently to automatically fall back to the built-in sequences when they're not defined in the XKB maps. None of that should be a problem for a complete 4.2.99.4 installation. I noticed that your log file was also for the mouse auto-detect problem you reported in a separate message. Have you confirmed that the two things are not related (I don't see how they should be, but it's worth checking if you haven't already)? After changing the mouse protocol, the mouse works, but the server still cannot be killed with Ctr-Alt-BkSpc. I seem to have caught the more painful bugs, as I was unable to kill the server without a reboot (no keyboard sequence response and no mouse exit.) I thought the core server would terminate on a kill -SIGTERM or restart with kill -SUGHUP, but it ignored both of these. It was removed with a SIGKILL, however it did not go through the driver shutdown sequence, leaving the console unusable. Here are relevant sections of XF86Config: Section ServerLayout Identifier XFree86 Configured Screen 0 Screen0 0 0 InputDeviceMouse0 CorePointer InputDeviceKeyboard0 CoreKeyboard EndSection Section InputDevice Identifier Keyboard0 Driver keyboard EndSection Try adding the following to your ServerLayout section: Option HandleSpecialKeys Always and see if that makes a difference. If it does, we'll need to track down why either the XKB map isn't working or it's not falling back correctly to the built-in settings. This option works, and Ctr-Alt-BkSpc shuts down the server as expected with it. -- Kevin ___ Devel mailing list [EMAIL PROTECTED] http://XFree86.Org/mailman/listinfo/devel
