Am Montag, 12. Oktober 2020, 17:33:46 CEST schrieb Alexander V. Makartsev:Got into a similar problem for years. Suddenly keyboard (the internal of my notebook) stopped and I had to restart the window manager.
This happened only in plasma5, not in LXDE or other window manager. I read in some forum, that the problem of installing the package "fcitx" should stop this. I did, and - well the bug was gone. However, I did not understand why, because fcitx has just something to do with chinese or japanese fonts. No clue, what it was related to, but the bug was gone. At the moment I got into trouble with the touchpad, but I think, this is more a kernel module issue. There is a bugreport, I filed to it. Hope this helps a little bit. Best Hans On 12.10.2020 17:18, Thomas George wrote: 10/12/20. Mouse working perfectly since reboot on 10/6/20 but this morning no response from keyboard. Tried ctl-alt-f1 and ctl-alt-f7 but no response. Not able to switch workplaces. Continued working in the current workspace using the mouse only. Verified mouse and keyboard batteries both at 50%. After several switches between open pages the keyboard recovered so I could write this. 2" All this on Ubuntu Studio. Again an intermittent problem. Keyboard just stopped working again and recovered after several minutes. Has anyone else experienced this? On 10/6/20 2:27 PM, Thomas George wrote: Mouse clicks don't work though mouse moves the pointer. This happens infrequently, once in a day or two. I am using two pc's, a raspberrypi and a Ubuntu Studio each with its own Logitech usb keyboard and have experienced this problem on both systems. I have tried to recover with various keyboard entries - ctl-c, cti-d, esc, q and by disconnecting and reconnecting the keyboard. Nothing but a reboot solves the problem. I use ctl-alt-f1 to open a terminal, sign in and enter shutdown -r now to do this. There is no problem with the keyboard. Is this a known problem? Is there a known solution? Taking into account that both devices now exhibit similar behavior, I'd start by looking into USB power saving functions [1] and try to disable them to see if it solves the problem.That could be done by setting "autosuspend" parameter of kernel module "usbcore" to a negative integer value (-1).You can change it temporarily on running system by typing: sudo echo -1 > /sys/module/usbcore/parameters/autosuspend https://www.kernel.org/doc/Documentation/usb/power-management.txt[1] -- With kindest regards, Alexander. ⢀⣴⠾⠻⢶⣦⠀ ⣾⠁⢠⠒⠀⣿⡁ Debian - The universal operating system ⢿⡄⠘⠷⠚⠋⠀ https://www.debian.org[2] ⠈⠳⣄⠀⠀⠀⠀ -------- [1] https://www.kernel.org/doc/Documentation/usb/power-management.txt [2] https://www.debian.org
signature.asc
Description: This is a digitally signed message part.
