I'm running Xfce on Fedora 17. Every so often (daily?) I loose the keyboard. Mouse works fine. I've been trying to discover what process is running before loss but not after. The only processes that I've been able to identify are kworkers.
Are there any suggestions as to what the cause might be?
The only processes that I can identify from ps before and after are kworkers, most often (but not exclusively) is [kworker/0:2] Is there any way to identify what the kworkers are assigned to? (The problem has continued over several kernels)
Logout-login cures the problem.
Thanks.
On 19.09.2012 22:04, Geoffrey Leach wrote:
I'm running Xfce on Fedora 17. Every so often (daily?) I loose the keyboard. Mouse works fine. I've been trying to discover what process is running before loss but not after. The only processes that I've been able to identify are kworkers.
Are there any suggestions as to what the cause might be?
The only processes that I can identify from ps before and after are kworkers, most often (but not exclusively) is [kworker/0:2] Is there any way to identify what the kworkers are assigned to? (The problem has continued over several kernels)
Logout-login cures the problem.
Thanks.
Sounds very mysterious, especially this part with lost keyboard. What exactly does it mean? Are you unable to type in characters or what? What apps are involved and how do you know that keyboard is lost?
kworker is a kernel thread and it has nothing to do with keyboard. The k in the beginning stands for kernel not keyboard.
Maybe you have broken keyboard? Does this happen with other keyboards attached to this computer?
Mateusz Marzantowicz
On Wed, Sep 19, 2012 at 01:04:30PM -0700, Geoffrey Leach wrote:
I'm running Xfce on Fedora 17. Every so often (daily?) I loose the keyboard. Mouse works fine. I've been trying to discover what
usb keyboard?
2012/9/19, Geoffrey Leach geoff@hughes.net:
I'm running Xfce on Fedora 17. Every so often (daily?) I loose the keyboard. Mouse works fine. I've been trying to discover what process is running before loss but not after. The only processes that I've been able to identify are kworkers.
Are there any suggestions as to what the cause might be?
Have a look at this:
http://forums.fedoraforum.org/showthread.php?t=277298
HTH, Andras
On Wed, 19 Sep 2012 14:23:39 -0700 Joe Zeff wrote:
On 09/19/2012 01:15 PM, Mateusz Marzantowicz wrote:
Maybe you have broken keyboard? Does this happen with other keyboards attached to this computer?
That's an interesting idea. After all, he says that he's "loosing" the keyboard not "losing" it.
So all he needs to do is tighten the nut between the keyboard and the chair?
On 9/19/2012 5:31 PM, Frank Cox wrote:
On Wed, 19 Sep 2012 14:23:39 -0700 Joe Zeff wrote:
On 09/19/2012 01:15 PM, Mateusz Marzantowicz wrote:
Maybe you have broken keyboard? Does this happen with other keyboards attached to this computer?
That's an interesting idea. After all, he says that he's "loosing" the keyboard not "losing" it.
So all he needs to do is tighten the nut between the keyboard and the chair?
Excellent! You have my kind of humor. :-)
Bill
On 2012-09-19 22:04, Geoffrey Leach wrote:
I'm running Xfce on Fedora 17. Every so often (daily?) I loose the keyboard. Mouse works fine. I've been trying to discover what process is running before loss but not after. The only processes that I've been able to identify are kworkers.
Are there any suggestions as to what the cause might be?
The only processes that I can identify from ps before and after are kworkers, most often (but not exclusively) is [kworker/0:2] Is there any way to identify what the kworkers are assigned to? (The problem has continued over several kernels)
Logout-login cures the problem.
Thanks.
Do you use the gdm desktop manager to log in? Do you perhaps hold the shift key down for longer than 8 seconds? Try holding the shift key for at least 8 seconds and see if that helps getting the keyboard back.
My solution was to switch over to lightdm.
El mié, 19-09-2012 a las 13:04 -0700, Geoffrey Leach escribió:
I'm running Xfce on Fedora 17. Every so often (daily?) I loose the keyboard. Mouse works fine. I've been trying to discover what process is running before loss but not after. The only processes that I've been able to identify are kworkers.
Are there any suggestions as to what the cause might be?
The only processes that I can identify from ps before and after are kworkers, most often (but not exclusively) is [kworker/0:2] Is there any way to identify what the kworkers are assigned to? (The problem has continued over several kernels)
Logout-login cures the problem.
Thanks.
Hello!
In the GDM/KDM menu there's an option to restart X. Also you can restart X with Ctrl+Alt+Backspace. Try choosing it (or typing it) and after this log in your user as usual. Tell us if it works.
Regards, Lailah
On 2012-09-21 00:54, Lailah wrote:
El mié, 19-09-2012 a las 13:04 -0700, Geoffrey Leach escribió:
I'm running Xfce on Fedora 17. Every so often (daily?) I loose the keyboard. Mouse works fine. I've been trying to discover what process is running before loss but not after. The only processes that I've been able to identify are kworkers.
Are there any suggestions as to what the cause might be?
The only processes that I can identify from ps before and after are kworkers, most often (but not exclusively) is [kworker/0:2] Is there any way to identify what the kworkers are assigned to? (The problem has continued over several kernels)
Logout-login cures the problem.
Thanks.
Hello!
In the GDM/KDM menu there's an option to restart X. Also youcan restart X with *Ctrl+Alt+Backspace*. Try choosing it (or typing it) and after this log in your user as usual. Tell us if it works.
/Regards,/ */Lailah/*
Have you VirtualBox(es) or somthing equivalent running?
If so: I lost the keyboard with VirtualBox sometimes, and the following action cured it: - Go into your VirtualBox Application. - Right-Hand Down from the USB selector select the keyboard. - The keyboard will then be irresponsive from your Main System, it will, however, be responsive in your VirtualBox application. - Again Right-Hand Down from the USB selector deselect the keyboard - Now the keybord should be responsive from both the Main System and from the VirtualBox application.
suomi
-
Andras Simon -
Bill Shirley -
fedora -
Frank Cox -
Geoffrey Leach -
Joe Zeff -
Mateusz Marzantowicz -
Matthew Miller -
Sjoerd Mullender -
Sylvia Sánchez