Forums

Skip to content

Advanced search
  • Quick links
    • Unanswered topics
    • Active topics
    • Search
  • FAQ
  • Login
  • Register
  • Board index Assistance Desktop Environments
  • Search

Keyboard stops working randomly [SOLVED]

Problems with GUI applications? Questions about X, KDE, Gnome, Fluxbox, etc.? Come on in. NOTE: For multimedia, go up one forum
Post Reply
Advanced search
22 posts • Page 1 of 1
Author
Message
srunni
Guru
Guru
User avatar
Posts: 365
Joined: Wed Dec 26, 2007 3:35 am

Keyboard stops working randomly [SOLVED]

  • Quote

Post by srunni » Tue Sep 09, 2008 1:18 am

Hi,

I'm running KDE 3.5.9, and sometimes my keyboard just randomly stops working (my mouse is fine). If I log out, my keyboard is working again. There doesn't seem to be any pattern to when this problem shows up. Any ideas?

Thanks!
Last edited by srunni on Fri Oct 24, 2008 11:46 pm, edited 1 time in total.
Patrick Ewing wrote:if it walks like a duck and talks like a duck, it’s a duck, right? So if this duck is not giving you the noise that you want, you’ve got to just punch that duck until it returns what you expect.
Top
d2_racing
Bodhisattva
Bodhisattva
User avatar
Posts: 13047
Joined: Mon Apr 25, 2005 2:25 pm
Location: Ste-Foy,Canada
Contact:
Contact d2_racing
Website

  • Quote

Post by d2_racing » Tue Sep 09, 2008 1:35 am

Do you have something inside /var/log/messages
Top
srunni
Guru
Guru
User avatar
Posts: 365
Joined: Wed Dec 26, 2007 3:35 am

  • Quote

Post by srunni » Tue Sep 09, 2008 2:04 am

Here is /var/log/messages right around when it happened:

Code: Select all

Sep  8 19:55:29 bebop ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Sep  8 19:55:29 bebop PM: Writing back config space on device 0000:02:00.0 at offset 1 (was 100102, writing 40100106)
Sep  8 19:55:29 bebop iwl4965: Radio disabled by HW RF Kill switch
Sep  8 19:55:29 bebop ACPI: PCI interrupt for device 0000:02:00.0 disabled
Sep  8 19:57:29 bebop ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Sep  8 19:57:29 bebop PM: Writing back config space on device 0000:02:00.0 at offset 1 (was 100102, writing 40100106)
Sep  8 19:57:29 bebop iwl4965: Radio disabled by HW RF Kill switch
Sep  8 19:57:29 bebop ACPI: PCI interrupt for device 0000:02:00.0 disabled
Sep  8 19:59:29 bebop ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Sep  8 19:59:29 bebop PM: Writing back config space on device 0000:02:00.0 at offset 1 (was 100102, writing 40100106)
Sep  8 19:59:29 bebop iwl4965: Radio disabled by HW RF Kill switch
Sep  8 19:59:29 bebop ACPI: PCI interrupt for device 0000:02:00.0 disabled
Sep  8 20:00:01 bebop cron[7785]: (root) CMD (rm -f /var/spool/cron/lastrun/cron.hourly)
Sep  8 20:00:01 bebop cron[7784]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Sep  8 20:00:46 bebop conky[5237]: segfault at 84 ip 0804e286 sp bffc4780 error 4 in conky[8048000+2c000]
Sep  8 20:00:46 bebop conky[5241]: segfault at 84 ip 0804e286 sp bfc03bc0 error 4 in conky[8048000+2c000]
Sep  8 20:00:46 bebop conky[5231]: segfault at 84 ip 0804e286 sp bf821f70 error 4<6>conky[5236]: segfault at 84 ip 0804e286 sp b
f977130 error 4<6>conky[5238]: segfault at 84 ip 0804e286 sp bfbe93a0 error 4<6>conky[5235]: segfault at 84 ip 0804e286 sp bf810
7d0 error 4<6>conky[5239]: segfault at 84 ip 0804e286 sp bf8b6070 error 4 in conky[8048000+2c000]
Sep  8 20:00:46 bebop in conky[8048000+2c000]
Sep  8 20:00:46 bebop in conky[8048000+2c000]
Sep  8 20:00:46 bebop conky[5242]: segfault at 84 ip 0804e286 sp bf88a840 error 4 in conky[8048000+2c000]
Sep  8 20:00:46 bebop in conky[8048000+2c000]
Sep  8 20:00:46 bebop in conky[8048000+2c000]
Sep  8 20:00:46 bebop conky[5233]: segfault at 84 ip 0804e286 sp bf99a7d0 error 4<6>conky[5240]: segfault at 84 ip 0804e286 sp b
f99d960 error 4 in conky[8048000+2c000]
Sep  8 20:00:46 bebop in conky[8048000+2c000]
Sep  8 20:00:49 bebop kdm: :0[4762]: pam_unix(kde:session): session closed for user srunni
Patrick Ewing wrote:if it walks like a duck and talks like a duck, it’s a duck, right? So if this duck is not giving you the noise that you want, you’ve got to just punch that duck until it returns what you expect.
Top
d2_racing
Bodhisattva
Bodhisattva
User avatar
Posts: 13047
Joined: Mon Apr 25, 2005 2:25 pm
Location: Ste-Foy,Canada
Contact:
Contact d2_racing
Website

  • Quote

Post by d2_racing » Tue Sep 09, 2008 2:17 am

conky, what is that. When he segfault, maybe it crash the keyboard driver inside the memory...
Top
srunni
Guru
Guru
User avatar
Posts: 365
Joined: Wed Dec 26, 2007 3:35 am

  • Quote

Post by srunni » Tue Sep 09, 2008 2:29 am

Conky is a system monitor which runs on my desktop. It regularly segfaults, and I've never bothered to figure out why. I don't think that's the problem though. But I'll try to figure out what's wrong with it and fix it in case it is.
Patrick Ewing wrote:if it walks like a duck and talks like a duck, it’s a duck, right? So if this duck is not giving you the noise that you want, you’ve got to just punch that duck until it returns what you expect.
Top
d2_racing
Bodhisattva
Bodhisattva
User avatar
Posts: 13047
Joined: Mon Apr 25, 2005 2:25 pm
Location: Ste-Foy,Canada
Contact:
Contact d2_racing
Website

  • Quote

Post by d2_racing » Tue Sep 09, 2008 2:59 am

Can you disable this conky and try if you keyboard will crash again ?
Top
srunni
Guru
Guru
User avatar
Posts: 365
Joined: Wed Dec 26, 2007 3:35 am

  • Quote

Post by srunni » Tue Sep 09, 2008 9:25 pm

I just had this error again, and it is not due to Conky. Conky's segfaulting during the logout procedure. I looked at the time before logging out, it was 16:22. Here are the messages for the 10 minutes before that:

Code: Select all

Sep  9 16:16:47 bebop ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Sep  9 16:16:47 bebop PM: Writing back config space on device 0000:02:00.0 at offset 1 (was 100102, writing 40100106)
Sep  9 16:16:47 bebop iwl4965: Radio disabled by HW RF Kill switch
Sep  9 16:16:47 bebop ACPI: PCI interrupt for device 0000:02:00.0 disabled
Sep  9 16:18:47 bebop ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Sep  9 16:18:47 bebop PM: Writing back config space on device 0000:02:00.0 at offset 1 (was 100102, writing 40100106)
Sep  9 16:18:47 bebop iwl4965: Radio disabled by HW RF Kill switch
Sep  9 16:18:47 bebop ACPI: PCI interrupt for device 0000:02:00.0 disabled
Sep  9 16:20:01 bebop cron[4807]: (root) CMD (test -x /usr/sbin/run-crons && /usr/sbin/run-crons )
Sep  9 16:20:47 bebop ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Sep  9 16:20:47 bebop PM: Writing back config space on device 0000:02:00.0 at offset 1 (was 100102, writing 40100106)
Sep  9 16:20:47 bebop iwl4965: Radio disabled by HW RF Kill switch
Sep  9 16:20:47 bebop ACPI: PCI interrupt for device 0000:02:00.0 disabled
Sep  9 16:22:18 bebop su[12761]: pam_unix(su:session): session closed for user root
Sep  9 16:22:24 bebop ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Sep  9 16:22:24 bebop PM: Writing back config space on device 0000:02:00.0 at offset 1 (was 100102, writing 40100106)
Sep  9 16:22:24 bebop iwl4965: Radio disabled by HW RF Kill switch
Sep  9 16:22:24 bebop ACPI: PCI interrupt for device 0000:02:00.0 disabled
Sep  9 16:22:47 bebop ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Sep  9 16:22:47 bebop PM: Writing back config space on device 0000:02:00.0 at offset 1 (was 100102, writing 40100106)
Sep  9 16:22:47 bebop iwl4965: Radio disabled by HW RF Kill switch
Sep  9 16:22:47 bebop ACPI: PCI interrupt for device 0000:02:00.0 disabled
It is most likely right before the ``session closed for user root'', because I had to kill a Konsole window running an emerge to log out.
Patrick Ewing wrote:if it walks like a duck and talks like a duck, it’s a duck, right? So if this duck is not giving you the noise that you want, you’ve got to just punch that duck until it returns what you expect.
Top
d2_racing
Bodhisattva
Bodhisattva
User avatar
Posts: 13047
Joined: Mon Apr 25, 2005 2:25 pm
Location: Ste-Foy,Canada
Contact:
Contact d2_racing
Website

  • Quote

Post by d2_racing » Wed Sep 10, 2008 1:42 am

Hi, are you having some problem with your wifi also ?
Top
srunni
Guru
Guru
User avatar
Posts: 365
Joined: Wed Dec 26, 2007 3:35 am

  • Quote

Post by srunni » Wed Sep 10, 2008 1:43 am

No, I'm not using wifi - I'm using my wired connection. I have the wifi switch turned off, so the hardware should be completely disabled. Wifi is a little flaky when I use it though (wpa_supplicant + Wicd).
Patrick Ewing wrote:if it walks like a duck and talks like a duck, it’s a duck, right? So if this duck is not giving you the noise that you want, you’ve got to just punch that duck until it returns what you expect.
Top
d2_racing
Bodhisattva
Bodhisattva
User avatar
Posts: 13047
Joined: Mon Apr 25, 2005 2:25 pm
Location: Ste-Foy,Canada
Contact:
Contact d2_racing
Website

  • Quote

Post by d2_racing » Wed Sep 10, 2008 2:02 am

You have a lot of error about your wifi :

Code: Select all

Sep  9 16:22:24 bebop iwl4965: Radio disabled by HW RF Kill switch
Sep  9 16:22:24 bebop ACPI: PCI interrupt for device 0000:02:00.0 disabled
Sep  9 16:22:47 bebop ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Sep  9 16:22:47 bebop PM: Writing back config space on device 0000:02:00.0 at offset 1 (was 100102, writing 40100106)
Sep  9 16:22:47 bebop iwl4965: Radio disabled by HW RF Kill switch
Sep  9 16:22:47 bebop ACPI: PCI interrupt for device 0000:02:00.0 disabled
Top
srunni
Guru
Guru
User avatar
Posts: 365
Joined: Wed Dec 26, 2007 3:35 am

  • Quote

Post by srunni » Wed Sep 10, 2008 2:29 am

I know, but I don't think that's it. It happened once more:

Code: Select all

Sep  9 21:14:09 bebop usblp0: removed
Sep  9 21:15:54 bebop ACPI: PCI Interrupt 0000:02:00.0[A] -> GSI 16 (level, low) -> IRQ 16
Sep  9 21:15:54 bebop PM: Writing back config space on device 0000:02:00.0 at offset 1 (was 100102, writing 40100106)
Sep  9 21:15:54 bebop iwl4965: Radio disabled by HW RF Kill switch
Sep  9 21:15:54 bebop ACPI: PCI interrupt for device 0000:02:00.0 disabled
Sep  9 21:17:25 bebop conky[5274]: segfault at 84 ip 0804e286 sp bfe305f0 error 4 in conky[8048000+2c000]
Sep  9 21:17:25 bebop conky[5267]: segfault at 84 ip 0804e286 sp bf80ffd0 error 4 in conky[8048000+2c000]
Sep  9 21:17:25 bebop conky[5276]: segfault at 84 ip 0804e286 sp bfe165d0 error 4 in conky[8048000+2c000]
Sep  9 21:17:25 bebop conky[5278]: segfault at 84 ip 0804e286 sp bf895050 error 4 in conky[8048000+2c000]
Sep  9 21:17:25 bebop conky[5277]: segfault at 84 ip 0804e286 sp bfa98a50 error 4 in conky[8048000+2c000]
Sep  9 21:17:25 bebop conky[5280]: segfault at 84 ip 0804e286 sp bf85c820 error 4 in conky[8048000+2c000]
Sep  9 21:17:25 bebop conky[5282]: segfault at 84 ip 0804e286 sp bfc40c00 error 4 in conky[8048000+2c000]
Sep  9 21:17:25 bebop conky[5279]: segfault at 84 ip 0804e286 sp bf83f800 error 4 in conky[8048000+2c000]
Sep  9 21:17:25 bebop conky[5284]: segfault at 84 ip 0804e286 sp bfb9a350 error 4 in conky[8048000+2c000]
Sep  9 21:17:25 bebop conky[5343]: segfault at 84 ip 0804e286 sp bf8ab120 error 4 in conky[8048000+2c000]
Sep  9 21:17:27 bebop kdm: :0[4824]: pam_unix(kde:session): session closed for user srunni
Look at the time. I logged out at 21:17:27. The error occured within 30 seconds before that. The error is not being logged.
Patrick Ewing wrote:if it walks like a duck and talks like a duck, it’s a duck, right? So if this duck is not giving you the noise that you want, you’ve got to just punch that duck until it returns what you expect.
Top
kokoko3k
n00b
n00b
Posts: 72
Joined: Fri May 06, 2005 4:16 pm

  • Quote

Post by kokoko3k » Wed Sep 10, 2008 7:18 am

Some times ago i got the same problem, now it's gone.
when it happens, try to open a terminal and press a key for very long time (10 seconds), and see if the character appears in the terminal.
If so, you have the same issue, but i can't provide a solution, sorry.
Top
srunni
Guru
Guru
User avatar
Posts: 365
Joined: Wed Dec 26, 2007 3:35 am

  • Quote

Post by srunni » Wed Sep 10, 2008 5:25 pm

Thanks for the help, I'll try that the next time it happens.
Patrick Ewing wrote:if it walks like a duck and talks like a duck, it’s a duck, right? So if this duck is not giving you the noise that you want, you’ve got to just punch that duck until it returns what you expect.
Top
srunni
Guru
Guru
User avatar
Posts: 365
Joined: Wed Dec 26, 2007 3:35 am

  • Quote

Post by srunni » Wed Sep 10, 2008 9:49 pm

So I had the problem again, and what you said worked - I could only type into the terminal, and only after holding down the key for a significant amount of time.
Patrick Ewing wrote:if it walks like a duck and talks like a duck, it’s a duck, right? So if this duck is not giving you the noise that you want, you’ve got to just punch that duck until it returns what you expect.
Top
kokoko3k
n00b
n00b
Posts: 72
Joined: Fri May 06, 2005 4:16 pm

  • Quote

Post by kokoko3k » Thu Sep 11, 2008 7:12 am

Of course is something X related (ctrl-alt-backspace, if you manage to hit them, will solve the problem, termporally), i'd try to upgrade or downgrade xf86-input-keyboard first...

Just curious, which keyboard do you use? mine is a wireless logitech desktop pro.
Top
srunni
Guru
Guru
User avatar
Posts: 365
Joined: Wed Dec 26, 2007 3:35 am

  • Quote

Post by srunni » Thu Sep 11, 2008 12:41 pm

kokoko3k wrote:Of course is something X related (ctrl-alt-backspace, if you manage to hit them, will solve the problem, termporally), i'd try to upgrade or downgrade xf86-input-keyboard first...
Does X control the login/logout from KDM? Or is all that behavior transparent to it and handled by KDE? In that case, wouldn't it be a KDE problem? Were you using KDE when you had the same problem?
kokoko3k wrote:Just curious, which keyboard do you use? mine is a wireless logitech desktop pro.
This is a laptop (HP Pavilion dv9700t), and I'm using the built-in keyboard. I will try connecting an external keyboard to see if it works (though I believe I tried that a while back and it didn't).
Patrick Ewing wrote:if it walks like a duck and talks like a duck, it’s a duck, right? So if this duck is not giving you the noise that you want, you’ve got to just punch that duck until it returns what you expect.
Top
kokoko3k
n00b
n00b
Posts: 72
Joined: Fri May 06, 2005 4:16 pm

  • Quote

Post by kokoko3k » Thu Sep 11, 2008 2:29 pm

srunni wrote:Does X control the login/logout from KDM? Or is all that behavior transparent to it and handled by KDE? In that case, wouldn't it be a KDE problem? Were you using KDE when you had the same problem?
When you log out from kde and return to kdm, X is restarted too.
Yes, i use kde, and it could be a kde issue, but my problem vanished and i've not upgraded any kde part, so i bet is an X issue.
Top
srunni
Guru
Guru
User avatar
Posts: 365
Joined: Wed Dec 26, 2007 3:35 am

  • Quote

Post by srunni » Fri Sep 12, 2008 8:07 pm

kokoko3k wrote:
srunni wrote:Does X control the login/logout from KDM? Or is all that behavior transparent to it and handled by KDE? In that case, wouldn't it be a KDE problem? Were you using KDE when you had the same problem?
When you log out from kde and return to kdm, X is restarted too.
Yes, i use kde, and it could be a kde issue, but my problem vanished and i've not upgraded any kde part, so i bet is an X issue.
Any idea how I can diagnose it?
Patrick Ewing wrote:if it walks like a duck and talks like a duck, it’s a duck, right? So if this duck is not giving you the noise that you want, you’ve got to just punch that duck until it returns what you expect.
Top
srunni
Guru
Guru
User avatar
Posts: 365
Joined: Wed Dec 26, 2007 3:35 am

  • Quote

Post by srunni » Fri Oct 24, 2008 11:45 pm

I finally figured out what was going on. Apparently, activating KDE's ``slow keys'' and ``sticky keys'' features via a gesture (not sure if mouse or keyboard) was enabled. All I had to do was go to KControl --> Regional & Accessibility --> Accessibility --> Activation Gestures and disable ``Use gestures for activating sticky keys and slow keys''. I guess that restarting X was resetting this option.
Patrick Ewing wrote:if it walks like a duck and talks like a duck, it’s a duck, right? So if this duck is not giving you the noise that you want, you’ve got to just punch that duck until it returns what you expect.
Top
TemplarKnight
Guru
Guru
User avatar
Posts: 311
Joined: Tue Jun 14, 2005 11:47 pm
Location: Greece/patras/

  • Quote

Post by TemplarKnight » Sun Oct 26, 2008 10:02 am

Disabling "slow keys" also worked for me (kde4.1) thanks 8)
Top
JanErik
Guru
Guru
Posts: 488
Joined: Mon Oct 28, 2002 9:02 pm
Location: Finland

  • Quote

Post by JanErik » Sun Oct 26, 2008 10:17 am

The same thing happened to me once yesterday in KDE 4.1.2 aswell.
Top
pcfreak85
n00b
n00b
Posts: 57
Joined: Fri Feb 11, 2005 9:10 am

  • Quote

Post by pcfreak85 » Sun Nov 16, 2008 3:01 pm

same issue here with 4.1.2, slow keys is already disabled.
---
Gentoo running on Lenovo Thinkpad T420 with KDE / SDDM
Intel(R) Core(TM) i7-2620M CPU @ 2.70GHz / 8GB memory / nvidia graphics
Top
Post Reply

22 posts • Page 1 of 1

Return to “Desktop Environments”

Jump to
  • Assistance
  • ↳   News & Announcements
  • ↳   Frequently Asked Questions
  • ↳   Installing Gentoo
  • ↳   Multimedia
  • ↳   Desktop Environments
  • ↳   Networking & Security
  • ↳   Kernel & Hardware
  • ↳   Portage & Programming
  • ↳   Gamers & Players
  • ↳   Other Things Gentoo
  • ↳   Unsupported Software
  • Discussion & Documentation
  • ↳   Documentation, Tips & Tricks
  • ↳   Gentoo Chat
  • ↳   Gentoo Forums Feedback
  • ↳   Duplicate Threads
  • International Gentoo Users
  • ↳   中文 (Chinese)
  • ↳   Dutch
  • ↳   Finnish
  • ↳   French
  • ↳   Deutsches Forum (German)
  • ↳   Diskussionsforum
  • ↳   Deutsche Dokumentation
  • ↳   Greek
  • ↳   Forum italiano (Italian)
  • ↳   Forum di discussione italiano
  • ↳   Risorse italiane (documentazione e tools)
  • ↳   Polskie forum (Polish)
  • ↳   Instalacja i sprzęt
  • ↳   Polish OTW
  • ↳   Portuguese
  • ↳   Documentação, Ferramentas e Dicas
  • ↳   Russian
  • ↳   Scandinavian
  • ↳   Spanish
  • ↳   Other Languages
  • Architectures & Platforms
  • ↳   Gentoo on ARM
  • ↳   Gentoo on PPC
  • ↳   Gentoo on Sparc
  • ↳   Gentoo on Alternative Architectures
  • ↳   Gentoo on AMD64
  • ↳   Gentoo for Mac OS X (Portage for Mac OS X)
  • Board index
  • All times are UTC
  • Delete cookies

© 2001–2026 Gentoo Foundation, Inc.

Powered by phpBB® Forum Software © phpBB Limited

Privacy Policy

 

 

magic