Bug 568936 - gdm is not setting the default keyboard according to /etc/syconfig/keyboard
Summary: gdm is not setting the default keyboard according to /etc/syconfig/keyboard
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gdm
Version: 13
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Ray Strode [halfline]
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-02-27 00:40 UTC by Matias Kreder
Modified: 2011-07-18 20:51 UTC (History)
8 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-27 15:03:30 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Xorg.log (31.94 KB, text/x-log)
2010-03-16 07:30 UTC, Ales Kozumplik
no flags Details

Description Matias Kreder 2010-02-27 00:40:12 UTC
Description of problem:

In Fedora 13 Alpha RC 4, anaconda is not seting keyboard layout in /etc/sysconfig/i18n after the installation, I should set the keyboard layout in GDM.

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

How reproducible:
Always

Steps to Reproduce:
1. Install fedora 13 Alpha RC4 
2. Set Latin American keyboard layout or any
3. Wait the installation to end
  
Actual results:
Anaconda is not setting the keyboard layout in /etc/sysconfig/i18n 

Expected results:
Anaconda setting the correct keyboard layout after installation

Additional info:

Comment 1 Hans de Goede 2010-03-01 10:33:22 UTC
Hmm, this might have something to do with the recent instdata removal, or
it is a system-config-keyboard issue.

Chris assigning this to you based on the suspicion this might be instdata removal related.

Comment 2 Chris Lumens 2010-03-01 22:09:33 UTC
Does updates=http://clumens.fedorapeople.org/568528.img fix this?

Comment 3 Matias Kreder 2010-03-09 21:17:53 UTC
How could I test it with that .img?

Comment 4 Chris Lumens 2010-03-09 21:34:43 UTC
Assuming you are booting via the CD/DVD, you want to interrupt the automatic boot by pressing any key.  Then hit "tab" on the default to edit options, add the above updates= parameter to the options, and hit enter.

Comment 5 Matias Kreder 2010-03-09 23:13:04 UTC
The bug persist with that Update, the  /etc/sysconfig/i18n is still wrong and the keyboard layout in GDM is wrong too, Maybe an interesting point is that in firstboot the keyboard layout was ok, as was set in anaconda.

Comment 6 Chris Lumens 2010-03-10 15:25:42 UTC
Ales - can you take a look into this?  Chances are you use a different keyboard layout than me (and the default) and so might have some insight here.  I've committed the patch from comment #2 to both master and f13-branch (it's 7df1b6ae3f837ed6e6acc714bc3a1200141d8cb3 on f13-branch), so that part of it at least should be fixed.

Comment 7 Ales Kozumplik 2010-03-11 12:23:59 UTC
Yes.

Couple of things:
1) Matias, what makes you think that we should write the keyboard information into /etc/sysconfig/i18n? I haven't find any documentation about this.

2) Currently we use s-c-keyboard library to write the keyboard info into /etc/sysconfig/keyboard for us. This really happens and the file looks allright on the installed system. The console still uses English keyboard, don't know why. But I tried running s-c-keyboard on an installed f13 system and while the command changes the file, it doesn't change the console keyboard, not even after reboot. Broken s-c-keyboard? Documentation missing.. the system-config-keyboard is owned by lkundrak which I am told is probably going to have a different bz account now.

3) I don't think this bug is a regression from f12. Chris, should we even be setting keyboard for X the same as installation? What if the computer is installed by a Chinese person but the user wants to use a Mexican keyboard? 

4) If yes, setting X keyboard is probably going to be a whole different story then calling s-c-keyboard. It needs to be done on the X level so it works for all kinds of desktops. I can't think of anything better than writing the keyboard info under xorg.conf.d/.

My suggestion: close as not a bug.

Comment 8 Ales Kozumplik 2010-03-11 12:28:12 UTC
Allright, I am not able to find the owner for system-config-keyboard in bugzilla. Denise, you are the owner for RHEL, can you help out please?

Comment 9 Ales Kozumplik 2010-03-15 16:15:20 UTC
If, during installation, Czech language and Czech keyboard is selected so that /etc/sysconfig/i18n contains:
LANG="cs_CZ.UTF-8"
SYSFONT="latarcyrheb-sun16"

and /etc/sysconfig/keyboard is:
KEYTABLE="cz-lat2"
MODEL="pc105"
LAYOUT="cz"
KEYBOARDTYPE="pc"
VARIANT="qwerty"

Then gdm offers Czech keyboard as the default upon the first login. If however only the keyboard is selected and language stays English, the keyboard is English in gdm too.

Comment 10 Ales Kozumplik 2010-03-15 17:16:36 UTC
I made one more experiment, using Danish for language and Czech for keyboard. The resulting keyboard is USA again.

/etc/sysconfig/i18n:
LANG="da_DK.UTF-8"
SYSFONT="latarcyrheb-sun16"

/etc/sysconfig/keyboard:
KEYTABLE="cz-lat2"
MODEL="pc105"
LAYOUT="cz"
VARIANT="qwerty"

I think this is problem is a bug in gdm. Anaconda does set correctly i18n and keyboard, but the keyboard setting is only respected when language is set correspondingly.

gdm maintainer, you can contact me directly if you have any questions or suggestions for me to test.

Thanks.

Comment 11 Peter Hutterer 2010-03-16 00:22:56 UTC
What's your version of system-setup-keyboard? There was a bug (fixed with 0.8.2-1) that the upstart file didn't get installed and it never started.

In F-13, system-setup-keyboard has an inotify monitor on /etc/sysconfig/keyboard so should pick up any changes automatically. These changes are written into /etc/xorg.conf.d and picked up whenever X restarts.

The Xorg.log file would be handy so we can see if it's gdm or X screwing up.

Comment 12 Ales Kozumplik 2010-03-16 07:30:26 UTC
Created attachment 400392 [details]
Xorg.log

Peter,

I am testing this on F13. The system-setup-keyboard version is 0.8-1.fc13. So that should be a buggy one right?

I am attaching Xorg.log.

Comment 13 Ales Kozumplik 2010-03-16 07:47:08 UTC
Okay, after I updated system-setup-keyboard to 0.8.3-1 the keyboard is the one specified by /etc/sysconfig/keyboard. 

So I guess we can close this one.

Comment 14 Thomas Woerner 2010-03-16 15:55:50 UTC
I have reproduced the behaviour on the console with RHEL-5-U4, F-10, F-11, F-12, rawhide and RHEL-6. It is the same for all, therefore it is no regression.

Setting the keyboard layout is not working as expected, while the system is running, but it might work after reboot. For some layouts/mappings there are missing fonts and I do not know if it is possible to provide these. 

Changing the keyboard layout in a running system results in incorrect mappings, especially for special chars, which are not part of ASCII.

This is a generic kbd or kernel problem in my opinion.

Comment 15 Bug Zapper 2011-06-02 16:23:06 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 16 Fedora Admin XMLRPC Client 2011-06-21 15:36:23 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 17 Fedora Admin XMLRPC Client 2011-06-21 15:38:46 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 18 Fedora Admin XMLRPC Client 2011-06-21 15:40:31 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 19 Fedora Admin XMLRPC Client 2011-06-21 15:43:15 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 20 Fedora Admin XMLRPC Client 2011-06-21 15:52:54 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 21 Fedora Admin XMLRPC Client 2011-06-21 15:55:50 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 22 Fedora Admin XMLRPC Client 2011-06-21 15:58:22 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 23 Fedora Admin XMLRPC Client 2011-06-21 15:59:30 UTC
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.

Comment 24 Bug Zapper 2011-06-27 15:03:30 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.

Comment 25 Arturo 2011-07-18 20:51:44 UTC
The best way to configure the keyboard what i have found is using the setup command, is a old command but very practical.


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