Re: Logitech wireless keyboard problems
On 2024-09-26 10:49, Mihai Moldovan wrote: * On 9/26/24 16:29, G.W. Haywood wrote: I am running a Logitech wireless keyboard and mouse, with Logitech's USB transmitter/receiver plugged into a USB port. I have tried other USB ports and the problem continues. Does anyone have any ideas .. it sounds like a bug to me. To begin with I'd look in the logs (usually in /var/log) and e.g. use 'dmesg' to see if there's anything intersting. If USB communication is somehow being broken for the kernel I'd expect that there would be something which mentions it. Nothing interesting in the logs Since the user hasn't mentioned anything about USB passthrough, and the normal USB emulation is very reliable in my experience, I'd look for something else. We're not even quite sure if the keyboard is using the USB subsystem - isn't the default PS/2-based? I know that there are USB tablet (mouse) and keyboard devices, but they aren't the only ones and libvirt, if I remember correctly, defaults to the non-USB components. In all the setups it seems Qemu is defaulting to PS/2 but initially both the keyboard and mouse work fine. Crucially, there's *no* connection between VMs and hosts regarding keyboard and mouse input. It doesn't matter what technology you use on the host. Since the issue only happens after some idle time, I suspect a screensaver to become active. They typically catch keyboard input, but no mouse input. I will check for a screensaver, not sure if one is loaded in any of the 3 distros but it's a distinct possibility. Never thought of that. Thanks
Re: Logitech wireless keyboard problems
* On 9/26/24 16:29, G.W. Haywood wrote: I am running a Logitech wireless keyboard and mouse, with Logitech's USB transmitter/receiver plugged into a USB port. I have tried other USB ports and the problem continues. Does anyone have any ideas .. it sounds like a bug to me. To begin with I'd look in the logs (usually in /var/log) and e.g. use 'dmesg' to see if there's anything intersting. If USB communication is somehow being broken for the kernel I'd expect that there would be something which mentions it. Since the user hasn't mentioned anything about USB passthrough, and the normal USB emulation is very reliable in my experience, I'd look for something else. We're not even quite sure if the keyboard is using the USB subsystem - isn't the default PS/2-based? I know that there are USB tablet (mouse) and keyboard devices, but they aren't the only ones and libvirt, if I remember correctly, defaults to the non-USB components. Crucially, there's *no* connection between VMs and hosts regarding keyboard and mouse input. It doesn't matter what technology you use on the host. Since the issue only happens after some idle time, I suspect a screensaver to become active. They typically catch keyboard input, but no mouse input. xlock, for instance, won't give you any indication of the amount of characters that were typed when unlocking the screen - which is actually a security measure (just like login(1) doesn't echo password characters by default). Mihai OpenPGP_signature.asc Description: OpenPGP digital signature
Logitech wireless keyboard problems
I am running QEMU emulator version 9.1.0 (openSUSE Tumbleweed) I have three Linux distros, and all three are affected by this keyboard problem. If I leave any of them idle for more than 5 or 10 minutes, the keyboard become unresponsive. To get it back I have to shutdown and re-run the distro. The mouse is not affected - it continues to respond normally. I am running a Logitech wireless keyboard and mouse, with Logitech's USB transmitter/receiver plugged into a USB port. I have tried other USB ports and the problem continues. Does anyone have any ideas .. it sounds like a bug to me. Thanks
Re: Logitech wireless keyboard problems
Hi there, On Thu, 26 Sep 2024, Frank McCormick wrote: I am running QEMU emulator version 9.1.0 (openSUSE Tumbleweed) I have three Linux distros, and all three are affected by this keyboard problem. If I leave any of them idle for more than 5 or 10 minutes, the keyboard become unresponsive. To get it back I have to shutdown and re-run the distro. The mouse is not affected - it continues to respond normally. I am running a Logitech wireless keyboard and mouse, with Logitech's USB transmitter/receiver plugged into a USB port. I have tried other USB ports and the problem continues. Does anyone have any ideas .. it sounds like a bug to me. To begin with I'd look in the logs (usually in /var/log) and e.g. use 'dmesg' to see if there's anything intersting. If USB communication is somehow being broken for the kernel I'd expect that there would be something which mentions it. As you say the mouse continues to respond it might be something in the keyboard itself over which you might not have a lot of control. There are all sorts of tools for hacking with USB, have you tried anything like 'usbreset' for example? If that helps, at least it would be better than a reboot and maybe you could put something in a crontab, to ping it every few minutes to keep it alive. I've done worse. ;) -- 73, Ged.
Re: Logitech wireless keyboard problems
On 2024-09-26 10:29, G.W. Haywood wrote: Hi there, On Thu, 26 Sep 2024, Frank McCormick wrote: If I leave any of them idle for more than 5 or 10 minutes, the keyboard become unresponsive. To get it back I have to shutdown and re-run the distro. The mouse is not affected - it continues to respond normally. . To begin with I'd look in the logs (usually in /var/log) and e.g. use 'dmesg' to see if there's anything intersting. If USB communication is somehow being broken for the kernel I'd expect that there would be something which mentions it. Checked the logs but I don't see anything there. As you say the mouse continues to respond it might be something in the keyboard itself over which you might not have a lot of control. There are all sorts of tools for hacking with USB, have you tried anything like 'usbreset' for example? If that helps, at least it would be better than a reboot and maybe you could put something in a crontab, to ping it every few minutes to keep it alive. I've done worse. ;) That's a thought. Still hope to find the root cause. Thanks
