I've had a Logitech cordless desktop on my primary desktop for the last few years, and every once in a while the number pad would just "go out" - the <enter> key and num-lock would still work, but of all the others would do nothing except the 5, which would pop-up a subwindow in some app on the screen that didn't have the focus.
I thought this was aproblem with the keyboard, so I just switched to a wired keyboard, and voila - the number key pad misbehaves exactly the same way.
Is this a Linx / RHEL / CentOS bug? Has anyone else seen this?
I'm going to reboot to see what happens, but I'd be really, really disappointed if it all just comes back to life (meaning that it *is* a problem in the system and not the hardware)....
Let us know if you can, and I'll report after I reboot.
Thanks.
mhr
On Fri, Apr 16, 2010 at 6:02 PM, MHR mhullrich@gmail.com wrote:
I've had a Logitech cordless desktop on my primary desktop for the last few years, and every once in a while the number pad would just "go out" - the <enter> key and num-lock would still work, but of all the others would do nothing except the 5, which would pop-up a subwindow in some app on the screen that didn't have the focus.
Erk - the (wireless) keyboard behaves just fine after a reboot. This leads me to suspect a problem in either the kernel or the desktop, but I think I've tried restarting the gdm before for this with no luck (had to reboot), so I more strongly suspect the kernel (driver/s). The mouse works just fine in both cases. It's an EX110 wireless desktop, BTW.
My son uses the exact same hardware on his Windows machine, and it never does this. In fact, the first time this happened, Logitech sent me a whole new wireless set, and that's the one I've been using ever since, and this has happened before a couple of times. Once it just went away by itself, the other time I deliberately rebooted to fix it.
I should probably point out that I use the PS2 ports instead of the (optional) USB connection - does anyone know if that works better (I suspect it might, since the USB drivers seem to be more robust than most).
Rebooting is not a good solution, even if it works as a "fix."
mhr
On Fri, 2010-04-16 at 18:02 -0700, MHR wrote:
I'm going to reboot to see what happens, but I'd be really, really disappointed if it all just comes back to life (meaning that it *is* a problem in the system and not the hardware)....
You can't guarantee that, either way. It could still be a problem with the hardware (firmware) in the keyboard and when you reboot it gets a "kick" and restarts.
On Fri, Apr 16, 2010 at 9:19 PM, Frank Cox theatre@sasktel.net wrote:
You can't guarantee that, either way. It could still be a problem with the hardware (firmware) in the keyboard and when you reboot it gets a "kick" and restarts.
Perhaps, but wouldn't it get a bigger kick, if you will, by replacing the keyboard batteries? I've tried that and it doesn't make any difference. Even brushing the keys (to remove any internal static, per Logitech's suggestion many moons ago) makes no difference, nor does resynching the recever.
Still wondering if anyone else uses the EX110 and either has the same problem or has never seen it....
Thanks, though.
mhr
On Fri, 2010-04-16 at 22:53 -0700, MHR wrote:
Perhaps, but wouldn't it get a bigger kick, if you will, by replacing the keyboard batteries?
Replacing the batteries has no effect on the receiver that's plugged into your computer, and that's the part that's most likely getting the "kick" when you reboot.
On Fri, Apr 16, 2010 at 11:27 PM, Frank Cox theatre@sasktel.net wrote:
Replacing the batteries has no effect on the receiver that's plugged into your computer, and that's the part that's most likely getting the "kick" when you reboot.
If it's a problem with either the keyboard or the receiver, when I plugged in the wired keyboard the problem should have disappeared. The problem stayed with the computer and its OS, irrespective of the hardware attached.
The worst part is that this doesn't happen often enough to provide a good test environment - maybe once every six months or longer (I can't remember the last time, exactly, and that time it cleared up after about five days, all by itself, which also tells me this is a driver problem). This may also be the best part, except in terms of diagnosing and solving the problem.
My bottom line question remains: anyone else have this problem with a Logitech EX110 wireless desktop on CentOS (or any other Linux system) - with details?
mhr
-
Frank Cox -
MHR