Lucid makes custom X11 keyboard layouts impossible
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ubuntu |
Expired
|
Undecided
|
Unassigned |
Bug Description
I use a custom keyboard layout, which I used to install with xkbcomp called from a script started as one of the session start programs. In lucid, the program is still started, it can still communicate with the X server to install the layout, but by the time I can interact with the session, it has absolutely no effect anymore. Some unidentifiable and unconfigurable component seems to overwrite the layout after the start programs have run. The only way to get the layout I want is to open a terminal window and start my script by hand after *every* *single* *login*. I always thought the start programs where meant to take care of these stupid menial tasks.
$ lsb_release -rd
Description: Ubuntu 10.04.1 LTS
Release: 10.04
Using the normal reaction to gnome problems (log in on a text console and rm -rf ~/.gnom* ~/.gconf*) "solves" this, but as soon as you do anything with the keyboard properties (like removing the useless second "nodeadkeys" default layout to get rid of the braindead layout switcher in the notification area, it resurfaces.