Closed khogeland closed 2 years ago
6 presses on Caps Lock has the same effect
Noticed both keys trigger led_set_kb
in led.c
. Commenting out the body of that function prevents the issue, so something's broken in there. I don't even have LEDs, so for my personal use I'm going to leave that commented and call it fixed. :stuck_out_tongue:
Do you know the last version that worked?
This is a new keyboard, so it never worked for me. If the stock firmware was compiled from one of those keymaps, @skullydazed might know which version that was compiled with.
This issue has been automatically marked as resolved because it has not had activity in the last 90 days. It will be closed in the next 30 days unless it is tagged properly or other activity occurs.
Was this still happening?
This issue has been automatically marked as stale because it has not had activity in the last 90 days. It will be closed in the next 30 days unless it is tagged properly or other activity occurs.
For maintainers: Please label with bug
, in progress
, on hold
, discussion
or to do
to prevent the issue from being re-flagged.
Closing due to inactivity.
Using a Clueboard 60% v1.0.1. The third key up event of a MO key causes the firmware to hang. I'm using this simple keymap, everything seems to work fine including the MO key/function layer. I've tried putting the MO mapping on other physical keys, so I don't think it's a hardware problem. Compiled at QMK firmware v0.6.209 (https://github.com/qmk/qmk_firmware/commit/f3cbb7bd6e307186e5802fa0366a21a5f9f5e41c) using the Docker build, same bug also present in the firmware built by the QMK configurator (v0.6.203).