Red Hat Bugzilla – Bug 1304897
When gnome is started using startx, it no longer honors the ~/.Xkbmap file
Last modified: 2016-03-09 10:33:45 EST
Description of problem:
I boot into multiuser in rawhide, f24 to be. I then use startx with
GSESSION="$(type -p gnome-session)" in ~/.Xclients to start Gnome. When Gnome comes up, it is using the US qwerty keyboard, even though I have ~/.Xkbmap with my custom keymapping in it, and that keymapping is in the right place. Other desktops that I start using this method have no trouble finding and using that custom keymap on start. Well, KDE crashes here in rawhide, so I couldn't test it, but xfce, cinnamon, mate, lxde all used the correct keymap.
Version-Release number of selected component (if applicable):
I'm not in rawhide right now, but it is the latest version in the repositories as of 2016-02-02
Steps to Reproduce:
1. Run rawhide
2. Put keymap in ~/.Xkbmap, put GSESSION="$(type -p gnome-session)" in ~/.Xclients
3. Run startx
Gnome starts with us qwerty keyboard
Gnome starts with keymapping in ~/.Xkbmap
I don't think this is running Wayland since I'm not running the greeter to start Gnome, unless it is being invoked behind the scenes (that is, Gnome always defaults to wayland, and ignores X configuration).
The selector in Gnome doesn't show the custom keymap in order to switch to it. I've been using the custom keymap so long that even though I was a fast touch typist with qwerty, I'm lost now when I have to use it, hunt and peck.
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.
More information and reason for this action is here:
This is no longer the case in rawhide (f25). So I am closing the ticket.