Bug 514476 - Backspace key fails to repeat when Virtual Keyboard (IBus) is enabled on Wayland
Summary: Backspace key fails to repeat when Virtual Keyboard (IBus) is enabled on Wayland
Status: RESOLVED DOWNSTREAM
Alias: None
Product: kwin
Classification: Plasma
Component: input (other bugs)
Version First Reported In: 6.5.4
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-01-12 03:52 UTC by Mesandu
Modified: 2026-01-13 15:16 UTC (History)
4 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mesandu 2026-01-12 03:52:56 UTC
SUMMARY_____________________
On Fedora KDE (Wayland), holding down the Backspace key registers only a single press. It does not repeat to delete multiple characters/words. This only affects Backspace; other keys like Space or letters repeat normally.                                           


STEPS TO REPRODUCE__________
1.  Go to System Settings -> Input Devices -> Virtual Keyboard.
2.  Select "IBus Wayland."
3.  Open any text editor (Kate, Konsole, etc.) and try to hold Backspace.

OBSERVED RESULT______________
The key does not repeat

EXPECTED RESULT_______________
The key should repeat based on the system keyboard repeat settings.

SOFTWARE/OS VERSIONS________
Operating System: Fedora Linux 43
KDE Plasma Version: 6.5.4
KDE Frameworks Version: 6.21.0
Qt Version: 6.10.1
Kernel Version: 6.17.12-300.fc43.x86_64 (64-bit)
Graphics Platform: Wayland


ADDITIONAL INFORMATION______
Setting Virtual Keyboard to "None" or "Maliit" restores normal Backspace behavior.
Comment 1 Nate Graham 2026-01-12 19:05:17 UTC
Since it only happens with IBus, that would suggest that IBus is interfering with the behavior of the key. I'd recommend reporting this to the IBus developers.
Comment 2 Nicolas Fella 2026-01-13 15:16:58 UTC
Possibly the same root cause as https://bugs.kde.org/show_bug.cgi?id=513637

Though I'd be surprised that it would affect Qt 6.10, AFAIK it should only affect 6.11