Closing programs in the systray makes keyboard unresponsive

[Donearm]

Since awesome 3.5.6, closing a program from the systray (right click->close) makes the keyboard totally unresponsive. No keys work, neither the default ones nor my own keybinds. Tested with Dropbox and Google-MusicManager (I have no other programs that make use of the systray). To restore keyboard's functionality it's necessary to change tag by clicking with the mouse on the statusbar. No other action is sufficient to make the keyboard responsive again.

awesome v3.5.6 (For Those About To Rock)
 • Build: Jan 10 2015 23:18:34 for x86_64 by gcc version 4.9.2 (builduser@)
 • Compiled against Lua 5.2.3 (running with Lua 5.2)
 • D-Bus support: ✔

[actionless]

is that reproducible for you when using default rc.lua?

[Donearm]

Yes, and it's even worse: keyboard remains unresponsive even after clicking with the mouse (which still works though). I have to restart Awesome.

[actionless]

latter part can re related with #67

[Donearm]

It probably is. Just tested with xev launched before closing the program in the systray (in this case Dropbox) and the keyboard remained responsive throughout the test. If I close xev, the bug reappears.
Besides, I am launching awesome from startx, no DMs

[psychon]

Could this perhaps be the same issue as #415? As far as I know, dropbox does use Qt. No idea about google something music.

[Donearm]

It seems related indeed. Actually Dropbox doesn't cause the bug any more, Google Music still does (and yes, it uses QT too)

[psychon]

Then please try if running Google Music with QT_XCB_NO_XI2_MOUSE=1 in its environment makes this issue go away. That did at least help with "that other" issue.

[Donearm]

It doesn't exactly go away in my case, I have an unresponsive keyboard for about 2 seconds and then it is fully working again. Could it be that until the google music process is dead it still blocks the key presses?

[psychon]

Everything's possible :-) (I really don't know, but that could be... I guess)

[kiike]

Can't reproduce this issue on the Qt-based app SimpleScreenRecorder. Running Awesome from git built using the AUR script and running on a vanilla setup.

awesome v3.5.2-2163-gb2e0e55 (The Fox)
 • Compiled against Lua 5.3.3 (running with Lua 5.3)
 • D-Bus support: ✔
 • execinfo support: ✔
 • RandR 1.5 support: ✔
 • LGI version: 0.9.1

Here's what I have been trying to reproduce this issue (have a look at the terminal that's open on the top-right corner to see that there's no lag here.:

EDIT: Here I am trying to reproduce it using the GTK-based ibus-daemon

[Elv13]

@psychon Can we assume this is fixed and close this?

[psychon]

@Elv13 No idea. This is all a big mystery to me and I have no clue what causes it. Keyboard hangs for two seconds just dont make any sense.
@Donearm Sorry, but we cannot really do anything about this and I am out of debugging ideas (well, I never really had any). I'll close this now since it is unrealistic that anything will magically happen. Feel free to reopen if you have some "aha"-idea that provides more hints into what is going on.