Re: Couldn't load XKB keymap... Can't switch to terminal mode
On Tue, Feb 13, 2007 at 18:37:04 -0800, Kenward Vaughan wrote:
> On Tue, 2007-02-13 at 21:53 +0100, Florian Kulzer wrote:
> > On Mon, Feb 12, 2007 at 21:11:54 -0800, Kenward Vaughan wrote:
[...]
> I finally caught wind of one reported error (not found in the usual
> Xorg.X.log, but in the output of startx):
>
> ------------------
> xauth: creating new authority file /home/daddy/.serverauth.12797
>
>
> X Window System Version 7.1.1
> Release Date: 12 May 2006
> X Protocol Version 11, Revision 0, Release 7.1.1
> ...
> (==) Using config file: "/etc/X11/xorg.conf"
> xkb_keycodes { include "xfree86+aliases(qwerty)" };
> xkb_types { include "complete" };
> xkb_compatibility { include "complete" };
> xkb_symbols { include "pc(pc105)+us" };
> xkb_geometry { include "pc(pc104)" };
> The XKEYBOARD keymap compiler (xkbcomp) reports:
> > Error: bad length in CompatMap
> > Output file "/var/tmp/server-0.xkm" removed
> Errors from xkbcomp are not fatal to the X server
This might be an unrelated glitch. I currently find this error several
times in my xorg log:
(EE) Error loading keymap /var/lib/xkb/server-0.xkm
so there seems to be an issue at the moment with the server-0.xkm file,
but this has not blocked my terminal switching.
> BScreen::BScreen: managing screen 0 using visual 0x21, depth 24
> *** WARNING: 'Workspace<n>' actions are deprecated! Use 'Workspace <n>'
> instead
>
> [I have no idea what this BScreen stuff is... fluxbox perhaps?]
I do not know fluxbox, but the message sure seems to come from your DE.
[...]
> > $ xmodmap -pk | grep Switch_VT
> > 67 0xffbe (F1) 0x1008fe01 (XF86_Switch_VT_1)
> > 68 0xffbf (F2) 0x1008fe02 (XF86_Switch_VT_2)
> > 69 0xffc0 (F3) 0x1008fe03 (XF86_Switch_VT_3)
> > 70 0xffc1 (F4) 0x1008fe04 (XF86_Switch_VT_4)
> > 71 0xffc2 (F5) 0x1008fe05 (XF86_Switch_VT_5)
> > 72 0xffc3 (F6) 0x1008fe06 (XF86_Switch_VT_6)
> > 73 0xffc4 (F7) 0x1008fe07 (XF86_Switch_VT_7)
> > 74 0xffc5 (F8) 0x1008fe08 (XF86_Switch_VT_8)
> > 75 0xffc6 (F9) 0x1008fe09 (XF86_Switch_VT_9)
> > 76 0xffc7 (F10) 0x1008fe0a (XF86_Switch_VT_10)
> > 95 0xffc8 (F11) 0x1008fe0b (XF86_Switch_VT_11)
> > 96 0xffc9 (F12) 0x1008fe0c (XF86_Switch_VT_12)
>
> 06:32:58
> daddy:~# xmodmap -pk | grep Switch_VT
>
> 06:33:19
> daddy:~#
>
> Something's missing here, yes?
Yes, I think we may have found the problem. If I run
xmodmap -e "keycode 67 ="
to remove the keycode for XF86_Switch_VT_1 then I can no longer use
CTRL-ALT-F1 to switch to tty1. I can restore switching with:
xmodmap -e "keycode 67 = F1 XF86_Switch_VT_1"
I therefore hope that you can fix your problem by assigning these keycodes
again. Try to run
for ((i=1;i<=10;i++)); do xmodmap -e "keycode $((66+i)) = F$i XF86_Switch_VT_$i"; done
to set them all at once (to the values that work for me here).
This could be a bug of a package other than xlibs-* and xkb-*, which
would explain why your purging/reinstalling did not have any effect.
Something might screw around with the keycodes, for example the startup
scripts of fluxbox. You can try to find out where it happens and file a
bug report. If all else fails then it will hopefully be enough to
include the above "for ..." command into your own startup scripts to set
the keycodes at the beginning of each new X session.
--
Regards,
Florian
Reply to: