After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 646269 - Keyboard preferences limited to 4 (four) layouts
Keyboard preferences limited to 4 (four) layouts
Status: RESOLVED DUPLICATE of bug 640774
Product: gnome-control-center
Classification: Core
Component: Keyboard
2.32.x
Other Linux
: Normal normal
: ---
Assigned To: Control-Center Maintainers
Control-Center Maintainers
Depends on:
Blocks:
 
 
Reported: 2011-03-30 21:04 UTC by michibrandl
Modified: 2011-03-30 22:29 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description michibrandl 2011-03-30 21:04:25 UTC 
System->Preferences->Keyboard lets only define 4 layouts.

I consider this an unreasonable limitation.

It seems to stem from an protocoll used in xbd which leaves 2 bit which are used to set the keyboard.

I found this question discussed here:
http://ubuntuforums.org/showthread.php?t=1416646

and here:
http://askubuntu.com/questions/21842/why-is-there-a-4-layouts-limit-for-keyboards

but did not find any bug report here. If there is one already which I missed, please remove this one as a duplicate.

I would be thankful for a fix to this limitation, since it makes it unnecessarily complicated to write in several languages with different character sets.

If it is hard to fix, then at least this fact should be highlighted more clearly. Just greying out the "add"-field once 4 layouts are reached (and letting people google for the reason) is not a very transparant way to deal with it, some text explaining the limitation would be nice.
Comment 1 Sergey V. Udaltsov 2011-03-30 21:16:50 UTC 
Reported many times.
Comment 2 Bastien Nocera 2011-03-30 22:29:04 UTC 
(In reply to comment #1)
> Reported many times.

You could at least take the time to dupe it properly.

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