Summary: | Numlock toggles Numlock/Scrolllock (LEDs) | ||
---|---|---|---|
Product: | xkeyboard-config | Reporter: | Stefan Dirsch <sndirsch> |
Component: | General | Assignee: | xkb |
Status: | RESOLVED FIXED | QA Contact: | |
Severity: | normal | ||
Priority: | high | CC: | mat, mfabian, michal.jnn, mike.auty |
Version: | unspecified | ||
Hardware: | Other | ||
OS: | Linux (All) | ||
Whiteboard: | |||
i915 platform: | i915 features: |
Description
Stefan Dirsch
2006-01-17 18:34:40 UTC
Removing all level5 files and all references to them (looks like a new feature) seems to fix this issue. Sergej, still no idea, what can be wrong here? Yes, level5 is the new feature introduced for supporting huge Canadian layout. I will have a look and try to find out what's wrong... Sure, ideas are welcome. It is an alpha-quality hack, so may well be buggy Using this patch fixes the issue for me. diff -u -r xkb.orig/types/complete xkb/types/complete --- xkb.orig/types/complete 2006-01-20 06:52:12.000000000 +0100 +++ xkb/types/complete 2006-01-20 07:06:51.000000000 +0100 @@ -11,6 +11,5 @@ include "mousekeys" include "pc" include "iso9995" - include "level5" include "extra" }; I'm using # setxkbmap "de(nodeadkeys)" -v Warning! Multiple definitions of keyboard layout Using command line, ignoring X server Trying to build keymap using the following components: keycodes: xfree86+aliases(qwerty) types: complete compat: complete symbols: pc(pc105)+de(nodeadkeys) geometry: pc(pc105) So this looks like a bug in types/level5. Ok, I can confirm the bug exists. Trying to find what's wrong. I did not notice it myself because none of my keyboards have scroll LED :) It seems I've fixed it by adding ScrollLock into the list of virtual_modifiers in types/level5 (yeah, just added it there - without any actual use!). The bad thing is that I do not really understand why it helps. At this time, I don't have much time to investigate it more - so explanations are welcome ;) |
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.