-
Notifications
You must be signed in to change notification settings - Fork 590
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
Comments
It might be interesting what |
I'll post it here once it happens again. Thanks. |
im having the same problem right now ! awesome v3.5.6 (For Those About To Rock) Linux Arch 3.18.2-2-ARCH xev gives normal output it just take long time press to the key being recognized . |
ok after looking around looks like the problem is connected to GDM i just would like to know if nenadalm uses GDM also |
Does |
@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. |
I did change gdm for slim and i until the moment no problem an it was a frequent problem |
Sory i had did change before testing ibus restart |
just faced the same issue (and faced it few days before on other machine)
it seems to be what affected only mod4, arrow keys, home, end, insert, delete UPD: keysym in xev output not matches: UPD2: forgot to mention what that problem usually happens after reloading awesome |
@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) |
without reloading awesome |
Could this be the same issue as #415? |
Since no one complaint, I'll assume that this is the Qt issue from #415 ("Qt is stealing our |
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.
The text was updated successfully, but these errors were encountered: