Description of problem: If I manually set the X keyboard layout, e.g. using "setxkbmap dvorak", then when I suspend/resume, the layout is reset back to the US layout. (I don't know if the GNOME layout changer has this issue, I didn't test that, but manually setting the layout is definitely broken.) Fedora 15 Alpha (power management test day snapshot) Reproducibility: 100%
I'm seeing what could be the same or a related bug. If I change modifier mappings with xmodmap then suspend/resume, they're reset. For example: xmodmap -e 'clear lock' xmodmap -e 'keycode 66 = Super_R' # was CapsLock xmodmap -e 'keycode 133 = Super_R' # was Super_L After suspend/resume these have been reset. Fedora 15, 100% reproducible. Is there a way to avoid this happening?
I've noticed this has stopped happening to me, I guess it's been weeks since I last noticed it (I'm running fc15 with all updates). Is it still affecting others?
(In reply to comment #2) > I've noticed this has stopped happening to me, I guess it's been weeks since I > last noticed it (I'm running fc15 with all updates). > > Is it still affecting others? Yes, I'm updated with all the updates and when I resume from suspend mode, I need to run xmodmap again to apply the key mapping again.
I use F15 with UK keyboard layout on a Dell 830 with German keyboard. Sometimes, individual xterms will switch to German layout (e.g I start with a dozen xterms with UK layout - suddenly I start getting y/z mixed, can't search in vi, can't quote... while the other 11 xterms are still fine). I haven't identified any particular trigger or remedy, except that I can close the defective xterm and open a new one.
(In reply to comment #4) That doesn't sound like this bug, it should probably be filed separately.
I'm having this too. Although on Arch Linux and using i3 as wm, and i3lock -d (where the -d turns off the screens) as my lock... I'm doing: setxkbmap no dvorak xmodmap .Xmodmap every day when I come. However, if I lock the screen when I leave for lunch or something, the keyboard is *not* changed. So it's going over a period of time.
Ah, searched some more, I have my keyboard connected to my screen, that's *my* problem! It turns the screen off -> keyboard off -> no settings... Found it in this answer: http://askubuntu.com/a/27466/49478 - it also has workarounds.
F15 is EOL. It is also reproducible on F17, moving on.
We could hack the restore functionality to pm-utils, but it would be really dirty solution. For X it seems to be the intended behaviour, see bug 664238 comment 1. Closing as notabug according to bug 664238 comment 1.