Bug 93914 - 2.17 breaks de(neo) layout
Summary: 2.17 breaks de(neo) layout
Status: RESOLVED INVALID
Alias: None
Product: xkeyboard-config
Classification: Unclassified
Component: General (show other bugs)
Version: unspecified
Hardware: All Linux (All)
: medium normal
Assignee: xkb
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-01-28 22:42 UTC by Oliver Ney
Modified: 2016-01-30 00:51 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description Oliver Ney 2016-01-28 22:42:40 UTC
Updating to xkeyboard-config 2.17-1 on Arch Linux broke the de(neo) layout for me. Downgrading back to 2.16 fixes the issues.

The keyboard is constantly on level 5 and the num lock LED is on. The level 5 modifier keys (e.g. [Alt Gr]) still toggle the level in some x11 apps (in chromium only the right hand side).

Since the num lock LED behavior changed i guess the changes from this report are involved:
https://bugs.freedesktop.org/show_bug.cgi?id=93763

My understanding from this is, that level 5 is locked and num lock should unlock it, but all it does is giving me the symbol '≠'. The activation of level 5 stays unchanged.

At session start X11 is logging the following:

(II) config/udev: Adding input device daskeyboard (/dev/input/event2)
(**) daskeyboard: Applying InputClass "evdev keyboard catchall"
(**) daskeyboard: Applying InputClass "system-keyboard"
(II) systemd-logind: got fd for /dev/input/event2 13:66 fd 34 paused 0
(II) Using input driver 'evdev' for 'daskeyboard'
(**) daskeyboard: always reports core events
(**) evdev: daskeyboard: Device: "/dev/input/event2"
(--) evdev: daskeyboard: Vendor 0x4d9 Product 0x2013
(--) evdev: daskeyboard: Found keys
(II) evdev: daskeyboard: Configuring as keyboard
(**) Option "config_info" "udev:/sys/devices/pci0000:00/0000:00:1a.0/usb1/1-1/1-1.5/1-1.5:1.0/0003:04D9:2013.0004/input/input4/event2"
(II) XINPUT: Adding extended input device "daskeyboard" (type: KEYBOARD, id 10)
(**) Option "xkb_rules" "evdev"
(**) Option "xkb_model" "pc105"
(**) Option "xkb_layout" "de"
(**) Option "xkb_variant" "neo"
The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Multiple interpretations of "Caps_Lock+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Warning:          Multiple interpretations of "Shift_L+AnyOfOrNone(all)"
>                   Using last definition for duplicate fields
> Error:            Key <HYPR> added to map for multiple modifiers
>                   Using Mod2, ignoring Mod4.
> Error:            Key <MDSW> added to map for multiple modifiers
>                   Using Mod3, ignoring Mod5.
Errors from xkbcomp are not fatal to the X server

If I can provide any further info, please let me know. Thanks!
Comment 1 Andreas Wettstein 2016-01-29 18:27:49 UTC
> My understanding from this is, that level 5 is locked and num lock should unlock it, but all it does is giving me the symbol '≠'. The activation of level 5 stays unchanged.

Neo has no Num Lock.  To unlock the level 5 lock, either press Shift+Mod3+Tab (Mod3 is # or CapsLock on German keyboards), or Mod4+Mod4 (< and AltGr). Does thin allow you to unlock the level 5 lock?
Comment 2 Oliver Ney 2016-01-30 00:51:04 UTC
I actually meant just the commonly "Num Lock" labelled key, not it's function. ;-)

But yes, these combinations worked fine. I did not know there is a lvl 5 lock at all and was a bit surprised about it suddenly being activated on boot in x11 (not the VC) after the update. Thanks!

I'm sorry about the hassle and close it as invalid.


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.