With some configuration, a login in GNOME can result in a broken keymap. Note that it only happens when there's no "interaction" with X before gnome-settings-daemon starts to play with XKB (where interaction means keyboard or mouse button usage).
Long discussion happening here: https://bugzilla.novell.com/show_bug.cgi?id=369263
Created attachment 16737 [details]
"xkbcomp -xkb :0 -" output before g-s-d starts
Created attachment 16738 [details]
"xkbcomp -xkb :0 -" output after g-s-d is started
To easily reproduce the bug:
+ apply the gconf dump from https://bugzilla.novell.com/attachment.cgi?id=212640 (with gconftool-2 --load)
+ enable GDM or KDM autologin (or timed login)
The latter is important since if you don't do that, then you will use your keyboard to enter the login/password and the bug does not occur anymore.
I can help debugging this, of course.
Created attachment 16739 [details]
"xkbcomp -xkb :0 -" output with autologin
Ok, forget about attachment 16738 [details]. Don't know why, but it looks broken. Here's the real broken version :-)
Created attachment 16740 [details]
"xkbcomp -xkb :0 -" output with normal login
And here's the xkbcomp dump when I don't use autologin.
All the previous dumps were done with the default group being 1. If I make the default group 0, then I get the same dumps, it seems.
(also note that I'm not using the exact same gconf config as in the novell bug -- I'm having 4 groups)
Any information you need?
can I have a look at your xorg.conf and log file please? At the moment it
looks like gnome sets azerty, but your keyboard inits with querty. We need to
find out why that is so.
(In reply to comment #8)
> can I have a look at your xorg.conf and log file please? At the moment it
> looks like gnome sets azerty, but your keyboard inits with querty. We need to
> find out why that is so.
So my system changed quite a lot since last time. Anyway, I will attach the files. Note that my X was probably never configured to be qwerty by default.
Created attachment 17886 [details]
Created attachment 17887 [details]
Xorg.0.log (compressed because too big, sorry)
Probably the same reason as 16364, don't have a solution yet though.
Could have been fixed with the commits leading up to c06e27b2f6fd9f7b9f827623a48876a225264132. We saw similar issues in Fedora and they are all fixed now (by the above commits).
And the hack as proposed in Bug 16364 of course.
Vincent, are you still seeing this? I'll try to find some time to check it myself soon.
(In reply to comment #14)
> Vincent, are you still seeing this?
No, I haven't seen this in ages.
happy days! \o/