Bug 266399 - Wish concerning the maximum amount of installable keyboard-layouts under kxkb
Summary: Wish concerning the maximum amount of installable keyboard-layouts under kxkb
Status: RESOLVED DUPLICATE of bug 204144
Alias: None
Product: kxkb
Classification: Miscellaneous
Component: general (show other bugs)
Version: 2.0
Platform: Debian stable Linux
: NOR normal
Target Milestone: ---
Assignee: Andriy Rysin
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-02-15 20:18 UTC by h.schoettke
Modified: 2011-02-16 03:33 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
screenshot (146.91 KB, image/png)
2011-02-15 20:18 UTC, h.schoettke
Details

Note You need to log in before you can comment on or make changes to this bug.
Description h.schoettke 2011-02-15 20:18:42 UTC
Created attachment 57280 [details]
screenshot

Version:           2.0 (using KDE 4.4.5) 
OS:                Linux

I tried to make various keyboard-layouts active to my computer (some of them just for testing purposes). My kxkb limited the maximum amount to four.
In comparison: On my older computer, still running KDE 3.5.10 (debian oldstable, i.e. lenny), the kxkb-limit is not reached at 6 keyboard-layouts made available.

Reproducible: Didn't try

Steps to Reproduce:
I didn't try to reproduce it after a reboot, but this is the way I reached where I am (I apologise for the german terms coming up, but there is no other way, just right now):
systemsettings
-->Persönliches [3rd item]-->Land/Region & Sprache [1st item]-->Tastaturlayout [2nd item].

Actual Results:  
The right-facing arrow right of "Available layouts" switches from green to grey after having installed the fourth item in the active-layout-list. There is no way to drag and drop aditional items there, as well.

Expected Results:  
I expected to activate more than four keyboard-layouts.

OS: Linux (i686) release 2.6.32-5-686
Compiler: cc
Comment 1 Andriy Rysin 2011-02-15 20:28:00 UTC
Implemented in 4.6.0
Comment 2 Andriy Rysin 2011-02-16 03:33:22 UTC

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