Description of problem: When using the Corsair K70 keyboard and using the 'pipe' key and two 'pipe' symbols are displayed Version-Release number of selected component (if applicable): systemd-219-21.fc22.x86_64 How reproducible: 90% Steps to Reproduce: 1. type a command using '|' key Actual results: cat foo | | grep bar Expected results: cat foo | grep bar Additional info: Adding the following to /lib/udev/hwdb.d/60-keyboard.hwdb resolves the issue. # Corsair K70 keyboard #keyboard:name:*Corsair*:dmi:bvn*:bvr*:bd*:svn*:pn*:pvr* keyboard:usb:v1B1Cp1B09* KEYBOARD_KEY_70032=reserved
https://github.com/systemd/systemd/issues/1243
https://github.com/systemd/systemd/pull/1259 has a proposed fix for the current systemd hwdb syntax. Would be great if you could test this on a recent version (221 or later).
https://github.com/systemd/systemd/commit/0d9f6d4f615077a948af220e18d1b257ab466ba6
http://pkgs.fedoraproject.org/cgit/systemd.git/commit/?h=f22&id=8a1079d92317a5084e564d68a9f5881f953d884a
systemd-219-24.fc22 has been submitted as an update to Fedora 22. https://bodhi.fedoraproject.org/updates/FEDORA-2015-15821
systemd-219-24.fc22 has been pushed to the Fedora 22 testing repository. If problems still persist, please make note of it in this bug report.\nIf you want to test the update, you can install it with \n su -c 'yum --enablerepo=updates-testing update systemd'. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-15821
systemd-219-24.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.
Hi, bad Fix. On a german keyboard layout the #-key won´t work with the Fix. KEYBOARD_KEY_70032 is the "#" and "'" Key
systemd-222-3.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-16155
systemd-222-4.fc23 has been submitted as an update to Fedora 23. https://bodhi.fedoraproject.org/updates/FEDORA-2015-16165
systemd-222-4.fc23 has been pushed to the Fedora 23 testing repository. If problems still persist, please make note of it in this bug report.\nIf you want to test the update, you can install it with \n su -c 'yum --enablerepo=updates-testing update systemd'. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2015-16165
systemd-222-4.fc23 has been pushed to the Fedora 23 stable repository. If problems still persist, please make note of it in this bug report.
I just upgraded to systemd-219-24.fc22 and the hash '#' and tilde '~' key stopped working. I'm using a united kingdom layout. Bad fix guys.
Hello, I've tested it on one Fedora 22 PC and on two different Fedora 22 Notebooks and with the Corsair K70R keyboard (German layout) - Key # and ' didn't work after upgrade to systemd-219-24.fc22 on all of this Fedora 22 instances. No Events are generated (showkey) at any time. Even no "Key undefined"-messages. I've tried other Keyboards too, and they worked like a charm. I'm not sure where the error is located. The Corsair K70R keyboard works fine with other Linux Distributions (Debian 6 / Ubuntu 14.04) and Windows. Please let me know if I could provide any Log or other information that will support you by fixing that problem. Thank you very much, Benny
Note that the originally proposed patch was a bit unclear to begin with, and as it caused regressions it was reverted upstream the next day. From udev's point of view this is rather unfixable -- it's either some weird kind of hardware bug or a bug in the kernel driver for that keyboard.
Yes, that's really not easy to fix in that case. Perhaps the kernel driver team could take a look how to handle that "sometimes double event"-Problem from the US-Keybord, the others Layouts don't show this behavior. I'm using the latest firmware of this keyboard since a year and with an downgrade of systemd everything is working like it should. I never got double characters (in my case # ). Wondering if Jacob Hunt is using the latest firmware of it. It's only possible to upgrade the Keybord Firmware with a Windows instance. Corsair Gaming K70 (non-RGB), Vengeance K70 Firmware and documentation Firmware 1.09, Software 1.3 09/19/2013 http://softwaredownloads.corsair.com/Files/Gaming-Keyboards/K70-setup-091913.zip Did Jacob Hunt test it on a different PC or Distro, perhaps it's a HW bug by resending double character in 90 % of the cases. Thanks for your answer, Benny