Red Hat Bugzilla – Bug 461563
Winkey/Mod4 does not work often after login to awesome WM
Last modified: 2013-03-07 21:04:39 EST
Created attachment 316147 [details]
Description of problem:
I am preparing package for awesome window manager, see bug 452427. It happened in lot of times that after startup of awesome the winkey/mod4 key does not work. It is very annoying because it's the primary functional key.
I am attaching three files, they are outputs from xev (just the winkey/mod4 key press and release). winkey.bad and winkey.bad2 are outputs from xev in awesome when the winkey does not worked and winkey.good when it worked OK. Running vimdiff on all three seems to be interesting in two points.
1) "KeyPress event, serial 2X"
is 25 in good, and 22 or 25 on bad case
2) "KeyRelease event -> state 0x40"
In both bad cases it's "state 0x0" and in good one it's "state 0x40"
It's not happening in GNOME, but I guess the problem is more on Xserver side then on the one of awesome.
Version-Release number of selected component (if applicable):
awesome-3.0-0.8.rc6.fc9.i386 from bug 452427
In half of cases the mod4 does not work, sometimes reset of Xserver does the job and mod4 key runs OK, but sometimes it does not did the trick.
Steps to Reproduce:
1. install awesome
2. log into in via GDM
3. mod4 key sometimes fails and sometimes it doesn't
It happens on RHEL with awesome-2 too, I ran, in the past, awesome on gentoo with no problem.
Created attachment 316148 [details]
Mod4 key does not work, #1
Created attachment 316149 [details]
Mod4 key does not work, #2
Created attachment 316150 [details]
Mod4 key works
Please cross-check with Bug 239409. I have not yet succeeded in tracking it down though.
It's dupe, thanks Peter, next time I'll do more querying next time.
*** This bug has been marked as a duplicate of bug 239409 ***