Re: [gentoo-user] [~amd64] Keyboard stops working several times/day
Am 16.08.2015 um 18:45 schrieb walt: I've been seeing this keyboard problem for the past few weeks: after running some command from a bash prompt (haven't tried zsh yet) the keyboard stops working. Almost like somebody unplugged the keyboard from its usb port (except that the LED on the keyboard stays lit so I know the power is still on). I don't have this issue, but I guess you're using a terminal emulator in a desktop environment. Which terminal emulator and which desktop environment are you using? Maybe the problem is just that the terminal emulator takes the control over the keyboard or the desktop environment gives the keyboard controls to the terminal emulator. There are no error messages in journalctl That doesn't mean much. When I unplug the keyboard from the usb port I can see the kernel recognize the unplug event, which makes me think that it's not a kernel/usb bug or a broken wire in the keyboard cable. When I re-plug the keyboard into a usb port the keyboard immediately starts working normally again until the next time I happen to trigger the problem by running some black-magical command from a command prompt. There is no particular command that causes it--it can be any arbitrary command AFAICT. Could theoretically also be a bug in systemd and/or udev? That wouldn't surprise me. And it wouldn't surprise me if Poettering and Sievers would blame the kernel developers for it again if it is a systemd and/or udev bug.
Re: [gentoo-user] [~amd64] Keyboard stops working several times/day
Am Sun, 16 Aug 2015 09:45:52 -0700 schrieb walt w41...@gmail.com: I've been seeing this keyboard problem for the past few weeks: after running some command from a bash prompt (haven't tried zsh yet) the keyboard stops working. Almost like somebody unplugged the keyboard from its usb port (except that the LED on the keyboard stays lit so I know the power is still on). There are no error messages in journalctl or in /var/log/Xorg.0.log I don't know how to change to a console without using a ctrl-alt-Fn keystroke from the keyboard (anyone know if it's possible?). When I unplug the keyboard from the usb port I can see the kernel recognize the unplug event, which makes me think that it's not a kernel/usb bug or a broken wire in the keyboard cable. When I re-plug the keyboard into a usb port the keyboard immediately starts working normally again until the next time I happen to trigger the problem by running some black-magical command from a command prompt. There is no particular command that causes it--it can be any arbitrary command AFAICT. Just one weird example: I can be typing a URL in a web browser window when a bash command finishes running in a terminal window and the keyboard stops working in the middle of my typing :( Any debugging suggestions would be most welcome. I don't think you mention precisely which (type of) keyboard you use within this thread (please forgive me if I overlooked it). Does it happen to be a Logitech Unifying Receiver model? My experience with the one I have is that the relative position and orientation of the keyboard to the receiver can strongly affect its reliability. Specifically, when the orientation is bad, the keyboard will stop working intermittently (workarounds included moving the keyboard, but that never helped permanently). Moving the receiver to a USB slot in the side of the desktop case (as opposed to one in the back), thus changing its orientation by 90°, made the keyboard perform reliably again. (My suspicion is that the directionality of the receiver and/or keyboard is not uniform, though I can also imagine that the problem is (also?) caused by interference with WLAN or something like that.) HTH -- Marc Joliet -- People who think they know everything really annoy those of us who know we don't - Bjarne Stroustrup pgppWyKsFU4TP.pgp Description: Digitale Signatur von OpenPGP
[gentoo-user] [~amd64] Keyboard stops working several times/day
I've been seeing this keyboard problem for the past few weeks: after running some command from a bash prompt (haven't tried zsh yet) the keyboard stops working. Almost like somebody unplugged the keyboard from its usb port (except that the LED on the keyboard stays lit so I know the power is still on). There are no error messages in journalctl or in /var/log/Xorg.0.log I don't know how to change to a console without using a ctrl-alt-Fn keystroke from the keyboard (anyone know if it's possible?). When I unplug the keyboard from the usb port I can see the kernel recognize the unplug event, which makes me think that it's not a kernel/usb bug or a broken wire in the keyboard cable. When I re-plug the keyboard into a usb port the keyboard immediately starts working normally again until the next time I happen to trigger the problem by running some black-magical command from a command prompt. There is no particular command that causes it--it can be any arbitrary command AFAICT. Just one weird example: I can be typing a URL in a web browser window when a bash command finishes running in a terminal window and the keyboard stops working in the middle of my typing :( Any debugging suggestions would be most welcome.
Re: [gentoo-user] [~amd64] Keyboard stops working several times/day
On 16/08/2015 18:45, walt wrote: I've been seeing this keyboard problem for the past few weeks: after running some command from a bash prompt (haven't tried zsh yet) the keyboard stops working. Almost like somebody unplugged the keyboard from its usb port (except that the LED on the keyboard stays lit so I know the power is still on). There are no error messages in journalctl or in /var/log/Xorg.0.log I don't know how to change to a console without using a ctrl-alt-Fn keystroke from the keyboard (anyone know if it's possible?). When I unplug the keyboard from the usb port I can see the kernel recognize the unplug event, which makes me think that it's not a kernel/usb bug or a broken wire in the keyboard cable. When I re-plug the keyboard into a usb port the keyboard immediately starts working normally again until the next time I happen to trigger the problem by running some black-magical command from a command prompt. There is no particular command that causes it--it can be any arbitrary command AFAICT. Just one weird example: I can be typing a URL in a web browser window when a bash command finishes running in a terminal window and the keyboard stops working in the middle of my typing :( Any debugging suggestions would be most welcome. First step (more to half the problem space than anything else): Does the same happen if you use another keyboard? -- Alan McKinnon alan.mckin...@gmail.com
