Bug 535871 - In YaST/SaX lacks the icon for the keyboard configuration
Summary: In YaST/SaX lacks the icon for the keyboard configuration
Status: RESOLVED DUPLICATE of bug 483554
Alias: None
Product: openSUSE 11.2
Classification: openSUSE
Component: SaX2 (show other bugs)
Version: Milestone 6
Hardware: Other Other
: P5 - None : Normal (vote)
Target Milestone: ---
Assignee: Forgotten User Wum0mkMcd8
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-09-01 08:58 UTC by Tim Fechtner
Modified: 2009-09-01 12:35 UTC (History)
1 user (show)

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Tim Fechtner 2009-09-01 08:58:14 UTC 
User-Agent:       Mozilla/5.0 (X11; U; Linux x86_64; es-ES; rv:1.9.1.2) Gecko/20090730 SUSE/3.5.2-2.4 Firefox/3.5.2

In YaST/SaX lacks the icon for the keyboard configuration.

That's bad because there is no possibility anymore to configure the localization of the keyboard.

I've done an installation in Spanish, but the keyboard layout seems to be en_US (or at least not Spanish).

Furthermore, in "languae configuration" in YaST, the language setting isn't appied to the keyboard layout, and the checkbox "adapat keyboard settings" is always greyed out.

Reproducible: Always

Actual Results:  
I have to work with English keyboard layout on my Spanish keyboard.

Expected Results:  
I want to be able to change the keyboard layout to "Spanish"
Comment 1 J. Daniel Schmidt 2009-09-01 12:35:53 UTC 
The icon is not there because it got removed, so it is not missing.
There will no longer be a xorg.conf that YaST needs to configure. All locale/language settings are done by the user now. Please use the tool of your Window-Manager.

Btw. there are already bugs that deal with the default keyboard layout being the one from the installation:
bug #498314 , bug #518281 , bug #534856

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