Keyboard mods lost after screensaver kicks in...

[hkoster1]

I've collected a few keyboard modifications on my Samsung ARM Chromebook (using xmodmap) in my script /usr/local/bin/keyboard, and have this file executed automatically when starting the LXDE chroot. Those modifications are then active, but are lost whenever I switch back-and-forth to ChromeOS or whenever the screensaver kicks in, requiring me to run my keyboard script again. Not a big issue, but more a puzzle...

[dnschneid]

That's really strange, although it's not unheard of for xephyr to do strange things. If you switch to a different keyboard layout in Xephyr or use setxkbmap, do those settings stay in place?

[hkoster1]

Yep, the "setxkbmap" command will lose the mods. One of those mods is to assign the middle mouse click to the right Ctrl key, for which I also add the command "xkbset m", but that does not cause problems.

[dnschneid]

Sorry, I meant that if you use setxkbmap to change your settings, do those changes survive the switch?

[dnschneid]

Also, what version of Ubuntu did you install?

[hkoster1]

When I switch between us and nl keymaps, or v.v., then the mods also disappear. I'm running the default "precise" distro.

[hkoster1]

I think I know the problem -- bought the Chromebook here in Holland, keyboard in ChromeOS set to nl or us international layout (they're the same), while I always install Linux (Debian usually) with US particulars. Now that I specify "setxkbmap us" the problem is gone: the mods survive switching back-and-forth between ChromeOS and the chroot.

[hkoster1]

....but the mods still don't survive the screensaver activating...

[dnschneid]

You may need to restart the screensaver daemon after setting the keyboard settings.

[hkoster1]

OK, I'll try that, be back in a couple of days to report on that. Meanwhile, thanks for all your work on crouton.

[hkoster1]

I've narrowed the problem to my remapping of the right Ctrl key as middle mouse click. Using 'xev' shows that this remapping is still active, except it doesn't work any more after the screensaver has kicked in automatically (no problem when I start the screensaver manually). Remapping of Shift-BackSpace to Delete works fine within a ViM session (but not in an LXTerminal command line). In the ChromeOS shell I get tons of error messages like
"Open-box-Message: Requested key "XF86Terminal" does not exist on display", which points to an LXDE problem.

I can live with that, like setting screensaver to kick in after 30 minutes or so.

At any rate, it doesn't appear to be a crouton problem or a ChromeOS problem, so I'll close this thread (if I may be so bold).

[dnschneid]

Cool; glad you have it mostly figured out. Depending on the screensaver, you may be able to set the screensaver to launch a command after it exits, if you can't manage to root-cause the reset.

[hkoster1]

Right, I like puzzles... may also try a newer version of LXDE since the version in "precise" seems a bit dated.

[matttproud]

Hi, I know that this issue is old and marked as closed, but I see something similar on a Ubuntu Trusty install with any screensaver (using XScreenSaver at the moment). Did anyone find a root cause for why the XServer (or whatever it is) is resetting the setxkbmap after the unlocking?