Luckily I don't use gdm, but my friend does. It was completely impossible to fix keyboard indicator during weekend on his install, so we installed gdm-old from AUR and fixed the keyboard indicator issues.
Further woes with gdm, it does not accept own background pics either, only themed and black works.
]]>I tried gdm 2.28.1-2, it really reads active keybord. But problem still unsolved: if you don't use gnome, then you have only one keyboard layout defined in GDM, other you have to define by yourself, using setxkbmap.
]]>maybe this can be usefull for someone: following an advice of one of my collegue I used the command "setxkbmap it" in a terminal for using an italian keybord and this set it for the whole X environment.. I've to say that I'm using fluxbox instead of gnome but the login manager is gdm and I'm having the same problems as you are.
Bye all (hope this will help),
Armando
I ve the same issue.
Now I use Slim, don t want to, but it s the only way to fix it without patch I found...
]]>Hopefully Gnome will include the patch in the next official release. 2.28.1 is out now, but when I look at the changelog I don't think it's included already:
Version 2.28.1
===============
- GDM will now avoid calling XAddHosts for remote connections. Refer to bug
#598142 for more information.
- Now GDM uses DeviceKit-power instead of gnome-power-manager for Suspend
support.
- Now the at-spi-registryd-wrapper.desktop GDM autostart file will run
at-spi-registryd directly instead of calling at-spi-registryd-wrapper.
- Fix to the visibility check for the "Other" button which corrects some
situations where the button would not appear when it was supposed to.
- Now the GDM daemon will make the /var/log/gdm directory if it does not exist.
- Fixes to avoid autologin failure when a NULL username is passed in.
- Restore CTYPE when canonicalizing codesets.
- Several fixes to avoid warnings.
===============
]]>I have the same symptoms with GDM and if I start a session with SLiM via ck-launch-session (so it is likely a ConsoleKit issue). You can sort of fix the touchpad issue by installing gsynaptics and configuring there (although not all options are available). When I restore from suspend, I have to repeat my setxkbmap and xmodmap. Do you have this issue as well?
]]>1) The keymap is set to us. Even if I select another keymap in GDM at boot time, it's not read and it's still us. I have to do "setxkbmap ch fr" in order to get the right keymap.
2) My touchpad, ruled by synaptics and a HAL fdi file, isn't managed as it should be. The options I had turned on (like the "tapping") aren't read.
So both 10-keymap and 20-synaptics aren't read. GDM just doesn't look at my HAL config files.
]]>Probably the following can help us? https://bugzilla.gnome.org/show_bug.cgi?id=596897
This patch is for a particular keyboard variant like no dead keys and should be applied to gnome-settings-daemon.
]]>I have just read a little through the Bug-Reports on Gnome and found one interesting point. If you change the Layout property in the file ~/.dmrc (where ~ is your personal home-directory) as soon as you have typed in your Username then the correct Layout is read from the .dmrc-File. Now this is annoying as well, since the keyboard layout is different for the username and the password.
The patch I linked to in #4 solved this particular issue for me. See #5 and #8 as well for more information.
]]>1. Yes
2. Arch packages are predominantly unpatched. So, in all likelihood, no.
Thanks for clearing that up
Installed the patch using the pkgbuild in this thread and it's working indeed. That'll do for now.
I'm kinda curious if and when there will come a new GUI and official Gnome patch for this problem.
Will I still be able to update gdm via pacman -Syu after rebuilding gdm with this patch?
And will there come an official Arch GDM update with this patch to solve the problem or is the only way to get it solved dealing with the patch now?