Bugzilla Bug 201047

Full description is avaliable via upsteam bug.

Reproducible: Always




Patch has already been applied/queued upstream so perfect for inclusion in next
revision bump.

Should be fixed in 1.4.0.90, please reopen if it's not.

*** Bug 202322 has been marked as a duplicate of this bug. ***

Reopen wrt Bug 202322 

I had some problems with xmodmap and fixed them by adding the following lines
to /usr/kde/3.5/bin/startkde:
[[ -f $HOME/.Xmodmap ]] && /usr/bin/xmodmap $HOME/.Xmodmap
[[ -f /etc/X11/Xmodmap ]] && /usr/bin/xmodmap /etc/X11/Xmodmap

This needs to be added to kde-base/kdebase-startkde so that it works
automatically.

(In reply to comment #4)
> I had some problems with xmodmap and fixed them by adding the following lines
> to /usr/kde/3.5/bin/startkde:
> [[ -f $HOME/.Xmodmap ]] && /usr/bin/xmodmap $HOME/.Xmodmap
> [[ -f /etc/X11/Xmodmap ]] && /usr/bin/xmodmap /etc/X11/Xmodmap
> 
> This needs to be added to kde-base/kdebase-startkde so that it works
> automatically.
> 

This belongs on a seperate bug report, it has nothing to do with xorg-server
and its ability to load the xmodmap on startup anymore.

Rafał, are you using the evdev driver? That sounds like it could be evdev
taking over the keyboard and ignoring your xorg.conf setup. Please attach
/etc/X11/xorg.conf and /var/log/Xorg.0.log.

Please reopen the bug when you reply.

*** Bug 202322 has been marked as a duplicate of this bug. ***

As I noted in 202322, I can't reopen this one, as I'm not the orginal reporter. 
Well, yes.
I'm using evdev 1.2.0 and hal 0.5.10. I've got correct fdi but even then
setxkbmap is needed, cause although keymap is polish, the problem from other
bugs happens (the one about arrow keys not working, or they do work but left
arrow is not repeated when held.
I'm talking about bugs 205077, 200061 and similar in the forums.

It sounds like your xkb setup may not reflect the changes required by the evdev
driver. What's `setxkbmap -print` show immediately after starting X, and then
again after running whatever setxkbmap command you use? Also, what is that
command?

Well, the funny thing is it prints exactly the same before and after I run
`setxkbmap` and this is all I run - hal-device reports keyboard is setup
correctly even before running setxkbmap (I've got a correct fdi file).
It prints:
xkb_keymap {
        xkb_keycodes  { include "evdev+aliases(qwerty)" };
        xkb_types     { include "complete"      };
        xkb_compat    { include "complete"      };
        xkb_symbols   { include "pc+pl+inet(evdev)+altwin(menu)"        };
        xkb_geometry  { include "pc(pc104)"     };
};

But the interesting thing is what `xkb -xkb :0` prints before running setxkbmap
(afterwards it prints correct keymap). Namely it prints:
Warning:          Could not load keyboard geometry for :0
                  BadAlloc (insufficient resources for operation)
                  Resulting keymap file will not describe geometry

I completely forgot about this bug.
I found a solution of this problem and posted it as comment #9 of bug 200060.
BTW. what syntax I should have used for the above comment to be pointed to the
correct bug instead of this one ?