Bug 479568 - No way to set correct keyboard geometry for the launched Xserver
No way to set correct keyboard geometry for the launched Xserver
Product: Fedora
Classification: Fedora
Component: gdm (Show other bugs)
All Linux
low Severity medium
: ---
: ---
Assigned To: jmccann
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2009-01-11 08:22 EST by QingLong
Modified: 2015-01-14 18:22 EST (History)
3 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2009-12-18 02:34:23 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description QingLong 2009-01-11 08:22:39 EST
Description of problem:
GDM uses per-user language settings to choose keyboard geometry.

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

How reproducible:

Steps to Reproduce:
 Just a real example
1. Get Sony Vaio PCG-6Q1M (German keyboard).
2. Try to make the keyboard work correctly:
   either via xorg.conf (Xkb* options in Section "InputDevice"),
   or gnome keyboard switcher applet.
Actual results:
GDM ingores its own /etc/gdm/custom.conf (so no way to select ServerLayout),
and passes to Xserver command line options that make the latter ignore InputDevice section of xorg.conf and use rather strange Xkb* options
that do not match the real keyboard geometry and layout,
leading to a twisted keyboard layout...

Expected results:
There should exist a way to disable that idiotic ~gdm/.../%gconf.xml bullshit
and use normal custom.conf to configure hardware-related parameters of gdm.
That dynamic xml stuff should come after initial configuration via custom.conf.

Additional info:
At last (after a week of monkeying with this micro$oftish stuff)
I've derived that using ``German'' language menu choice prior to
actual user login does set (almost) correct keyboard geometry
and gives quite usable keyboard.
But what the hell a per user language settings do with the keyboard geometry?
Keyboard geometry is a hardware related parameter and is fixed for the given machine (as notebooks have builtin keyboards).
BTW there is no ``Sony Vaio'' geometry in gnome keyboard configurations set.
Comment 1 Bug Zapper 2009-11-18 05:43:19 EST
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10.  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 '10'.

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 10'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 10 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: 
Comment 2 Bug Zapper 2009-12-18 02:34:23 EST
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 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.

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