qmk/qmk_firmware

[Bug] Ctrl+C not registering. Help needed to root cause.

Open

#21,957 opened on Sep 8, 2023

View on GitHub
 (1 comment) (0 reactions) (0 assignees)C (43,867 forks)batch import
bughelp wanted

Repository metrics

Stars
 (20,368 stars)
PR merge metrics
 (Avg merge 20d 9h) (27 merged PRs in 30d)

Description

Describe the Bug

Hi,

I'm running QMK on my GMMK Pro. I have an issue with Ctrl+C not registering Copy fast enough. This causes me to have to press Ctrl+C multiple times for this to register.

I'm not sure how to debug what is happening, do you have any hints on how I can root cause this? I don't think it's a problem with the hardware, this was working as expected on stock GMMK Pro.

Thanks!

Keyboard Used

No response

Link to product page (if applicable)

No response

Operating System

Windows

qmk doctor Output

No response

Is AutoHotKey / Karabiner installed

  • AutoHotKey (Windows)
  • Karabiner (macOS)

Other keyboard-related software installed

No response

Additional Context

No response

Contributor guide

Research direction
Enable QMK debug console and inspect key press events. Check if the issue is specific to a keymap or default. Try swapping Ctrl and Caps Lock to rule out hardware. Review the matrix scanning code for potential delays.
Tech stack
c
Domain
backend
Issue type
Bug
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
2
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
Half day
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Needs investigation
Prerequisites
CQMK basics
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
65