You are not logged in.

#1 2010-07-05 17:06:16

thunktone
Member
Registered: 2010-07-05
Posts: 2

Xorg stuck on US keymap

After doing a "yaourt -Syu --aur", I've been having problems with my keymap. I want to set it to uk, but it's stuck on us.

I searched this forum and google and found out about /etc/hal/fdi/policy/10-keymap.fdi. Here is the relevant bit:

      <merge key="input.xkb.layout" type="string">gb</merge>
      <merge key="input.xkb.variant" type="string">default,winkeys</merge>

I have tried changing gb to uk, but this does not help. My xorg.conf says nothing about any keyboard.

I also tried

18:01 ~→ lshal | egrep "key|layout"
  info.capabilities = {'input', 'button', 'input.keys'} (string list)
  input.xkb.layout = 'uk'  (string)
  input.xkb.variant = 'default,winkeys'  (string)
  info.capabilities = {'input', 'button', 'input.keys'} (string list)
  input.xkb.layout = 'uk'  (string)
  input.xkb.variant = 'default,winkeys'  (string)
  info.product = 'IBM Enhanced (101/102-key, PS/2 mouse support)'  (string)
  pnp.description = 'IBM Enhanced (101/102-key, PS/2 mouse support)'  (string)
  info.capabilities = {'input', 'input.keyboard', 'input.keypad', 'input.keys', 'button'} (string list)
  info.product = 'AT Translated Set 2 keyboard'  (string)
  input.product = 'AT Translated Set 2 keyboard'  (string)
  input.xkb.layout = 'uk'  (string)
  input.xkb.variant = 'default,winkeys'  (string)

The only thing that looks wrong here is "101/102-key", my keyboard is a uk 105-key keyboard.

Does anyone have any ideas what might be causing this?

Offline

#2 2010-07-05 17:49:29

Meyithi
Member
From: Wirral, UK
Registered: 2009-06-21
Posts: 550
Website

Re: Xorg stuck on US keymap


The mind roams more freely in empty rooms.
dwm - colours - ncmpcpp - system
irc://irc.freenode.net:meyithi

Offline

#3 2010-07-05 17:57:49

Inxsible
Forum Fellow
From: Chicago
Registered: 2008-06-09
Posts: 9,183

Re: Xorg stuck on US keymap

like Meyithi pointed out, Hal and its numerous fdi policies have been deprecated and replaced by udev. Search the forums for udev and keyboard layout and you will find a lot of threads having solved this issue.


Forum Rules

There's no such thing as a stupid question, but there sure are a lot of inquisitive idiots !

Offline

#4 2010-07-05 18:44:22

ApotheoZ
Member
Registered: 2009-08-10
Posts: 40

Re: Xorg stuck on US keymap

In the inputClass of your keyboard in /etc/X11/xorg.conf.d/10-evedev.conf, add
Option "xkblayout" "gb"

If you dont have xorg.conf.d update your system
If you dont have 10-evedev;conf ... Maybe instal xf86-input-evedev package.

Offline

#5 2010-07-05 20:43:26

thunktone
Member
Registered: 2010-07-05
Posts: 2

Re: Xorg stuck on US keymap

Thanks for the help, it works now. Not sure why I didn't find anything about udev when I was searching.

Offline

#6 2010-07-09 22:21:27

theking2
Banned
From: Romanshorn Switzerland
Registered: 2009-03-04
Posts: 372

Re: Xorg stuck on US keymap

So after every update this change has to be made? Despite what is in the rc.conf file.
This is why GNU/linux is still experimental isn't it? Do an update but spend hours to find out why the keyboard isn't working anymore.


archlinux on a Gigabyte C1037UN-EU, 16GiB
a Promise  PDC40718 based ZFS set
root on a Samsung SSD PB22-J
running LogitechMediaServer(-git), Samba, MiniDLNA, TOR

Offline

#7 2010-07-09 23:41:23

Gusar
Member
Registered: 2009-08-25
Posts: 3,605

Re: Xorg stuck on US keymap

theking2 wrote:

So after every update this change has to be made?

No, you can (and should) create an /etc/X11/xorg.conf and put your configuration there. That's the point of this file still existing, it's *your* file, whereas /etc/X11/xorg.conf.d/ is for the distribution. Your /etc/X11/xorg.conf should contain this:

Section "InputClass"
    Identifier    "keyboard"
    MatchIsKeyboard    "on"
    Driver        "evdev"
    Option        "XkbLayout"        "gb"
EndSection
theking2 wrote:

This is why GNU/linux is still experimental isn't it? Do an update but spend hours to find out why the keyboard isn't working anymore.

Err, simple end users don't screw around with config files, be it xorg.conf, hal .fdi files, or whatever. They enter the Gnome control center or KDE systemsettings and configure their keyboard there with a few clicks. It's only the pople not using one of the big DEs that have to deal with config files, and it was *their* choice to go down that route.

Offline

Board footer

Powered by FluxBB