Repository: dnschneid/crouton

Issue #2639: Can't get Search to work as Super_L
Created: 2016-06-22T01:34:42Z
$ sudo edit-chroot -all
name: sid
encrypted: no
crouton: version 1-20160620130246~master:c39102d9
release: sid
architecture: amd64
xmethod: xiwi
targets: lxde,keyboard,cli-extra,xiwi,extension
host: version 8350.31.0 (Official Build) beta-channel peppy
kernel: Linux greenarrow 3.8.11 #1 SMP Tue Jun 14 21:57:05 PDT 2016 x86_64 GNU/Linux
freon: yes
Please describe your issue:
I'm not sure what changed but I noticed the other day that the Search button no longer worked as Super_L. I did some searching and found this wiki. I then installed the keyboard target:
$ sudo bash crouton -u -p /media/removable/64GB_USB/crouton -n sid -t keyboard
This caused some permissions issues when starting my chroot. Most likely because I have umask 077 in my bashrc, and I think that gets persisted into the chroot so the updates from the previous command get installed with no group or other permissions. The following command fixed my issue:
$ sudo bash enter-chroot -x chmod -R go+rX /usr/share/X11/
Running umask 022 before crouton updates also seems to fix the problem. It might be worth adding a umask 022 at the beginning of crouton but this likely isn't critical.
After I got that worked out I used the xmodmap command inside the chroot:
$ xmodmap -e "keycode 133 = Super_L"
Unfortunately this didn't fix my problem. I still can't get the Search button to behave as Super_L as before. Any help would be greatly appreciated.

Duplicate issue #2728: Search key doesn't register in chroot
Created: 2016-08-15T05:00:29Z
Please paste the output of the following command here: sudo edit-chroot -all

encrypted: no
Entering /mnt/stateful_partition/crouton/chroots/jessie...
crouton: version 1-20160715134041~master:0dc76a22
release: jessie
architecture: amd64
xmethod: xiwi
targets: extension,xiwi,keyboard,x11
host: version 8350.68.0 (Official Build) stable-channel peppy
kernel: Linux localhost 3.8.11 #1 SMP Tue Aug 2 21:29:22 PDT 2016 x86_64 GNU/Linux
freon: yes
Please describe your issue:
The search key doesn't get registered by the chroot at all. This happens both with and without the keyboard target.
To clarify, on my chromebook, I have swapped the search and control keys through chromeOS's own settings. In the chroot, xev shows that pressing the physical search key (which, in chromeOS, is mapped to Control), registers as Control_L. Pressing the control key (which, in chromeOS, is mapped to search), doesn't get registered at all. However, ChromeOS's own shortcuts involving search still work.
This behavior is only present in some recent update of ChromeOS (probably around 3 months). It used to work fine, so somehow the "search" function (which my physical Control key is mapped to) got grabbed by ChromeOS?
If known, describe the steps to reproduce the issue:
I have already reinstalled a new chroot (still jessie, with keyboard extension), and the problem is still reproduced. I am using awesome WM if that matters. In my old setup, the "search" function was mapped to Super_L, which in xmodmap has modifier Mod4.
I have followed these updated steps: https://github.com/dnschneid/crouton/wiki/awesome
However, the pressing the physical control key (which is mapped to "search") doesn't even get registered in xev, so it didn't help.

Closing comment (2016-10-13T18:07:59Z): Duplicate of #2639.