Bug 21312

Summary: setxkbmap doesn't recognise multiple keyboards
Product: xorg Reporter: Tim Nelson <wayland>
Component: App/setxkbmapAssignee: Xorg Project Team <xorg-team>
Status: RESOLVED DUPLICATE QA Contact: Xorg Project Team <xorg-team>
Severity: enhancement    
Priority: medium CC: daniel, e.a.b.piel, peter.hutterer
Version: 7.4 (2008.09)Keywords: love
Hardware: Other   
OS: All   
Whiteboard: 2011BRB_Reviewed
i915 platform: i915 features:
Bug Depends on: 21669    
Bug Blocks:    

Description Tim Nelson 2009-04-20 22:27:06 UTC
My original post to the xorg list (with responses by Peter Hutterer) was:

---------------------------------------------------------------------------

>       One thing I just noticed is that the root window property for XKB only 
> contains the information for one keyboard.  When I run setxkbmap -print, the 
> device parameter doesn't make it read the settings for that device, it simply 
> relies on this property, which is presumably the most recent one set:
> 
> _XKB_RULES_NAMES(STRING) = "evdev", "pc105+inet", "ang,el", "", \
>       "grp:switch,grp:scroll_toggle,grp_led:scroll"
> 
>       Should that somehow represent multiple keyboards?

yes, it should. but can't at the same time. basically this property has been
around for long enough that we can't change it. for the multi-keyboard case we
should just introduce a new property. patches appreciated of course.

note that you will need to modify setxkbmap as well, xkbcomp already takes a
device parameter.
---------------------------------------------------------------------------

HTH
Comment 1 Eric Piel 2009-11-16 08:09:36 UTC
I'm playing with the new "-query" option, and it seems I'm hit by the same bug. Which ever device I specify with "-device", it's just the latest RLMVO applied which are displayed. 
Comment 2 Peter Hutterer 2013-07-14 10:47:04 UTC

*** This bug has been marked as a duplicate of bug 21669 ***

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.