Closing programs in the systray makes keyboard unresponsive about awesome HOT 12 CLOSED

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

from awesome.

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

from awesome.

latter part can re related with #67

from awesome.

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

from awesome.

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

from awesome.

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

from awesome.

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.

from awesome.

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?

from awesome.

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

from awesome.

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

from awesome.

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

from awesome.

@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.

from awesome.