Ok, forcing it in GNOME is not a proper solution, as one would expect. A possible solution (quoting daniels):
"libxklavier likes to compile the entire keymap on the client side, so the client doesn't know that the keyboard is evdev, and the server can't force the model. However, now we have (input-device) properties, the driver could set a xorg.driver prop or something, and if evdev, libxklavier could unconditionally force the evdev model." That should work. We'll most likely have input-device properties backported in Intrepid on top of current inputproto, libXi and xserver (I already have them built locallly), so only libxklavier needs to be patched so it'll force the model if evdev is used. -- Up arrow key mapped to Print [screen] https://bugs.launchpad.net/bugs/255008 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
