[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Couldn't load XKB keymap... Can't switch to terminal mode



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:
> > On Mon, 2007-02-12 at 22:40 +0100, Florian Kulzer wrote:
> > > On Sun, Feb 11, 2007 at 18:20:55 -0800, Kenward Vaughan wrote:
> 
> [...]
> 
> > > > (edited)
> > > > 
> > > > daddy:~# dpkg -l xlibs\*
> > > > ...
> > > > ||/ Name           Version  
> > > > +++-==============-==============
> > > > ii  xlibs          6.9.0.dfsg.1-6 
> > > > ii  xlibs-data     7.1.0-11 
> > > > 
> > > > 06:16:25
> > > > daddy:~# dpkg -l xkb-data\*
> > > > ...
> > > > ||/ Name           Version     
> > > > +++-==============-============
> > > > ii  xkb-data       0.9-4         
> > > > un  xkb-data-legac <none>  
> > > 
> > > I have the same versions and everything is OK for me. (AFAIK these
> > > packages should have the XKB definitions.)
> > > 
> > > What is your xorg keyboard config? You can run
> > > 
> > > awk '/Section "InputDevice/,/EndSection/' /etc/X11/xorg.conf
> > 
> > > to see the relevant part.
> > 
> > Seems same as usual to me:  
> > 
> > 09:03:46
> > daddy:~# awk '/Section "InputDevice/,/EndSection/' /etc/X11/xorg.conf
> > Section "InputDevice"
> ...
> That certainly looks OK to me, too.
> 
> > None of this has changed since before the problematic update. 
> ...
> > "xev" reports what I assume is a normal output for all those keys:
> > -----------
> > KeyPress event, serial 30, synthetic NO, window 0x1400001,
> >     root 0x119, subw 0x0, time 3112150093, (604,209), root:(752,380),
> >     state 0x0, keycode 64 (keysym 0xffe9, Alt_L), same_screen YES,
> >     XLookupString gives 0 bytes: 
> >     XmbLookupString gives 0 bytes: 
> >     XFilterEvent returns: False
> 
> [...]
> 
> Again, the same as for me (also the output for the other keys which I
> removed).
> 
> It might indeed be the time to try purging xlibs, xlibs-data and/or
> xkb-data. The quickest way is probably to use "dpkg -P --force-depends"
> and then to reinstall immediately. You could also try to downgrade to
> the previous versions of these packages to see if the bug was really
> caused by the upgrade. (You probably still have the necessary .deb files
> in your /var/cache/apt/archives/ unless you clean that out since the
> upgrade.)


This I have tried, with no success yet.  I don't have an older version
of xkb-data available, and honestly don't know where to get one.  All
the packages have been purged and reinstalled, and the xlibs-data
downgraded a few notches, but no good results.

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
...

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?]
...
X connection to :0.0 broken (explicit kill or server shutdown).
xinit:  connection to X server lost.
---------------

> Another thing to check is the output of xmodmap. Here is what I get:
> 
> $ xmodmap
> xmodmap:  up to 3 keys per modifier, (keycodes in parentheses):
> 
> shift       Shift_L (0x32),  Shift_R (0x3e)
> lock        Caps_Lock (0x42)
> control     Control_L (0x25),  Control_R (0x6d)
> mod1        Alt_L (0x40),  Alt_L (0x7d),  Meta_L (0x9c)
> mod2        Num_Lock (0x4d)
> mod3
> mod4        Super_L (0x7f),  Hyper_L (0x80)
> mod5        Mode_switch (0x5d),  ISO_Level3_Shift (0x7c)

06:32:52
daddy:~# xmodmap 
xmodmap:  up to 2 keys per modifier, (keycodes in parentheses):

shift       Shift_L (0x32),  Shift_R (0x3e)
lock        Caps_Lock (0x42)
control     Control_L (0x25),  Control_R (0x6d)
mod1        Alt_L (0x40),  Alt_R (0x71)
mod2        Num_Lock (0x4d)
mod3      
mod4      
mod5        Scroll_Lock (0x4e)


> $ 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?


Kenward
-- 
In a completely rational society, the best of us would aspire to be 
_teachers_ and the rest of us would have to settle for something less, 
because passing civilization along from one generation to the next 
ought to be the highest honor and the highest responsibility anyone 
could have.     - Lee Iacocca



Reply to: