Gentoo Websites Logo
Go to: Gentoo Home Documentation Forums Lists Bugs Planet Store Wiki Get Gentoo!
Bug 313269 - xorg-server 1.8 upgrade guide: how to change the keyboard layout
Summary: xorg-server 1.8 upgrade guide: how to change the keyboard layout
Status: RESOLVED DUPLICATE of bug 305371
Alias: None
Product: [OLD] Docs on www.gentoo.org
Classification: Unclassified
Component: New Documentation (show other bugs)
Hardware: All Linux
: High enhancement (vote)
Assignee: Gentoo X packagers
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-04-05 17:31 UTC by Francis Galiegue
Modified: 2010-04-07 21:24 UTC (History)
1 user (show)

See Also:
Package list:
Runtime testing required: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Francis Galiegue 2010-04-05 17:31:17 UTC
xorg-server 1.8 doesn't use HAL anymore for configuration, so the HAL policy file to configure the keyboard layout doesn't work anymore. It uses udev instead.

Unfortunately, I couldn't make the udev way work, but there's another way (NOTE: works only if you use evdev)

* create an /etc/X11/xorg.conf.d directory;
* put these two files in:

1. 01-keyboard-layout.conf:
----
#
# 01-keyboard-layout.conf: how to set the keyboard layout via X (FIXME: could be
# done by udev instead, but I don't know how)
#
Section "InputClass"
        Identifier "keyboard-layout"
        Driver "evdev"
        MatchIsKeyboard "yes"
        Option "XkbLayout" "fr"
EndSection
#
# END of 01-keyboard-layout.conf
#
----

2. 99-evdev-catchall.conf:
----
#
# 99-evdev-catchall.conf: for the rest of evdev-handled input devices. This file
# is NECESSARY if you specify your own keyboard layout with Xorg, but not if you
# manage to set the keybaord layout using udev.
#
Section "InputClass"
        Identifier "evdev-catchall"
        Driver "evdev"
EndSection
#
# END of 99-evdev-catchall.conf
#
----


Reproducible: Always

Steps to Reproduce:
Irrelevant here.
Comment 1 Tomáš Chvátal (RETIRED) gentoo-dev 2010-04-07 21:24:04 UTC

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