Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keyboard issues: stops responsing #67

Closed
nenadalm opened this issue Dec 29, 2014 · 13 comments
Closed

Keyboard issues: stops responsing #67

nenadalm opened this issue Dec 29, 2014 · 13 comments
Labels

Comments

@nenadalm
Copy link

It happens to me time to time (about twice per month I think) that keyboard stops responding as usual. If I hit a key, nothing happens. But if I hold a key, it starts writing after a while (but I need to hold every key from that time to be able to write anything).

Restart of Awesome doesn't help.
Quit Awesome and login again does help.

nenadalm@localhost:~$ awesome -v
awesome v3.5.5 (Kansas City Shuffle)
 • Build: Apr 14 2014 18:44:32 for x86_64 by gcc version 4.8.2 (mockbuild@)
 • Compiled against Lua 5.2.2 (running with Lua 5.2)
 • D-Bus support: ✔

nenadalm@localhost:~$ cat /etc/issue
Fedora release 20 (Heisenbug)
Kernel \r on an \m (\l)


@blueyed
Copy link
Member

blueyed commented Dec 30, 2014

It might be interesting what xev gives you in this case. Does it behave normally?

@nenadalm
Copy link
Author

I'll post it here once it happens again. Thanks.

@WillianPaiva
Copy link

im having the same problem right now !

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: ✔

Linux Arch 3.18.2-2-ARCH

xev gives normal output it just take long time press to the key being recognized .

@WillianPaiva
Copy link

ok after looking around looks like the problem is connected to GDM i just would like to know if nenadalm uses GDM also

@blueyed
Copy link
Member

blueyed commented Jan 21, 2015

Does ibus restart help in this case?

@nenadalm
Copy link
Author

@WillianPaiva I did use gdm, but since I don't expect to use more window managers in the nearest future, I disabled it.

It didn't happen from the time I disabled it yet.

@WillianPaiva
Copy link

I did change gdm for slim and i until the moment no problem an it was a frequent problem

@WillianPaiva
Copy link

Sory i had did change before testing ibus restart
But a quick solution was holding shift for 10 seconds than it was back to normal

@blueyed blueyed changed the title Keyboard issues Keyboard issues: stops responsing Jan 24, 2015
@blueyed blueyed added the bug label Jan 24, 2015
@actionless
Copy link
Member

just faced the same issue (and faced it few days before on other machine)
so current is using slim, other is not using any DM
i don't have ibus

in xev keys output looks as usual

it seems to be what affected only mod4, arrow keys, home, end, insert, delete
page down behaves like menu key
page up behaves like /

UPD: keysym in xev output not matches:
http://sprunge.us/iBIj

UPD2: forgot to mention what that problem usually happens after reloading awesome

@nenadalm
Copy link
Author

@actionless - exactly the same happened to me a few days ago (since it was for the first time, I didn't pay attention to that)

@nenadalm
Copy link
Author

without reloading awesome

@psychon
Copy link
Member

psychon commented Nov 28, 2015

Could this be the same issue as #415?

@psychon
Copy link
Member

psychon commented Jan 17, 2016

Since no one complaint, I'll assume that this is the Qt issue from #415 ("Qt is stealing our jobs mouse events).

@psychon psychon closed this as completed Jan 17, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

5 participants