gdm doesn't set the correct keyboard layout in the session
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
GNOME Settings Daemon |
Fix Released
|
Medium
|
|||
gnome-settings-daemon (Ubuntu) |
Fix Released
|
Medium
|
Unassigned |
Bug Description
Binary package hint: gdm
My symptoms are the same as in bug 421212, but as requested there, I am filing a new bug, as that one is believed to be fixed.
I'm running gdm 2.28.0-0ubuntu14. I tried removing /var/lib/
ProblemType: Bug
Architecture: i386
Date: Wed Oct 7 23:07:35 2009
DistroRelease: Ubuntu 9.10
NonfreeKernelMo
Package: gdm 2.28.0-0ubuntu14
ProcEnviron:
LC_COLLATE=C
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/zsh
ProcVersionSign
SourcePackage: gdm
Tags: ubuntu-unr
Uname: Linux 2.6.31-11-generic i686
XsessionErrors:
(gnome-
(gnome-
(nautilus:6547): Eel-CRITICAL **: eel_preferences
(polkit-
summary: |
- gdm still doesn't set the correct keyboard layout in the session + gdm doesn't set the correct keyboard layout in the session for us-dvorak |
Changed in gnome-settings-daemon: | |
importance: | Unknown → Medium |
status: | Unknown → Fix Released |
I tried to replicate this here. If I configure /etc/default/ console- setup for us dvorak, then gdm correctly displays "US (Dvorak)" as default layout type, and $GDM_KEYBOARD_ LAYOUT = "us dvorak" in the session, and I actually end up with Dvorak.
However, it _only_ does that if you don't have any other configured US layout in your gconf settings. This is because of gnome-settings- daemon trying to find a "closest match" amongst the already configured layouts before actually applying $GDM_KEYBOARD_ LAYOUT. This is discussed in detail in https:/ /bugzilla. gnome.org/ show_bug. cgi?id= 585290, and so far it is not clear whether this is a bug or a feature.
To verify this, please check that
gconftool -g /desktop/ gnome/periphera ls/keyboard/ kbd/layouts
has any "us" layout already. If you reset it with
gconftool -u /desktop/ gnome/periphera ls/keyboard/ kbd/layouts
things should work for you again. Can you confirm that this is the problem for you?