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.
