Bug 124238 - kde kcontrol has empty keyboard layouts list
Summary: kde kcontrol has empty keyboard layouts list
Keywords:
Status: CLOSED DUPLICATE of bug 121950
Alias: None
Product: Fedora
Classification: Fedora
Component: kdebase
Version: 2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Than Ngo
QA Contact: Ben Levenson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-05-24 22:20 UTC by Doncho Gunchev
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:03:42 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Doncho Gunchev 2004-05-24 22:20:53 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040510

Description of problem:
I tryed to add keyboard layouts from kcontrol (Regional &
Accessability -> Keyboard Layout) and got empty list. I did a full
install of Fedora Core 2.

Version-Release number of selected component (if applicable):
kdebase-3.2.2-4

How reproducible:
Always

Steps to Reproduce:
1. install FC2 with kde
2. start kde, go to 'Regional & Accessability' -> 'Keyboard Layout'
3. Try adding any layout
    

Actual Results:  No keyboard layouts available

Expected Results:  All keyboard layouts there

Additional info:

A friend of mine has the same problem too. This was working with
FC2-test3 I think and with FC1+kde-3.2.x too. With 'kcontrol --nofork'
from konsole I only get 'QComboBox::changeItem: (comboModel) Index 0
out of range'. ~/.kde/share/config/kxkbrc from FC1 let me start kxkb,
but there was nothing to configure too (I wanted phonetic, but only
got BDS layout this way). Kde also looks for
/usr/share/locale/l10n/C/flag.png (and so on), which does not exist,
so we have no country flags.

Comment 1 Doncho Gunchev 2004-05-25 23:13:22 UTC

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

Comment 2 Red Hat Bugzilla 2006-02-21 19:03:42 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


Note You need to log in before you can comment on or make changes to this bug.