** Changed in: x11proto-core (Ubuntu)
Status: Incomplete => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/120788
Title:
(needs x11 protocol update) XKB cannot map multiple keyboard mo
** Changed in: x11proto-core (Ubuntu)
Status: Triaged => Incomplete
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/120788
Title:
(needs x11 protocol update) XKB cannot map multiple keyboard mo
** Changed in: xkeyboard-config
Status: Confirmed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/120788
Title:
(needs x11 protocol update) XKB cannot map multiple keyboard models
T
** Changed in: xkeyboard-config
Importance: Unknown => Medium
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/120788
Title:
(needs x11 protocol update) XKB cannot map multiple keyboard models
--
** Changed in: xkeyboard-config
Importance: Medium => Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/120788
Title:
(needs x11 protocol update) XKB cannot map multiple keyboard models
--
** Changed in: gnome-control-center
Status: Invalid => Unknown
** Changed in: gnome-control-center
Importance: Unknown => Wishlist
--
(needs x11 protocol update) XKB cannot map multiple keyboard models
https://bugs.launchpad.net/bugs/120788
You received this bug notification because yo
> What is needed is PnP solution on X level - chosing right model depending on
> the plugged keyboard. But that's not GNOME's task."
Is this what evdev now does?
With the right x11-input.fdi file can this now be worked around?
--
(needs x11 protocol update) XKB cannot map multiple keyboard model
** Description changed:
The X.org XKB protocol has a limitation in that it can map only one
keyboard model and a max of 4 layouts (bug #56912) in a given X session.
The data type used to communicate keyboard mappings between the server
and client apps simply doesn't provide room for the da
[Or rather, x11proto-core it seems is the best place for it.]
Also see related bug #56912
** Description changed:
The X.org XKB protocol has a limitation in that it can map only one
- keyboard model per layout. The data type used to communicate keyboard
- mappings between the server and client
