Fedora Account System
Red Hat Associate
Red Hat Customer
When selecting text on kwrite, the text gets corrupted and in an inconsistent state. Undo does not undo the corruption. The same problem happens on Fedora 44 beta KDE live boot, and on Fedora 43 with the latest updates. Reproducible: Always Steps to Reproduce: 1. Open kwrite on a new file. 2. Type a line with "//test" (without the quotes) 3. Press home to go the beginning of the line 4. Hold down the shift key and press the right arrow a few times to select the text Actual Results: The two initial slashes // disappear. Control z does not bring them back. Trying to select text from the beginning of the document remains broken. Expected Results: The text is selected and not changed. Additional Information: There are many other cases where similar problems happen. For example, when starting a line with backslash \ instead of slash.
Bug 2441633 is a duplicate of this bug. https://bugzilla.redhat.com/show_bug.cgi?id=2441633
For reference, the upstream bug report on this is here: https://bugs.kde.org/show_bug.cgi?id=516511 - I don't know that it's clear right now where this one falls in the stack, but this impacts all Qt applications in Wayland seemingly?
Thanks for the mainstream bug link. It gives a good workaround: Goto to settings -> Virtual Keyboard and choose anything other than Plasma Keyboard.
The problem arrives even when renaming files on Dolphin. Select a hidden file (for example .bashrc), press F2 to rename it. Try to select the beginning of the file. The dot in the beginning of the file disappears!
Proposed as a Blocker for 44-final by Fedora user gfonsecabr using the blocker tracking app because: The bug affects essentially all text input of all KDE and QT applications of the KDE editon, from editing a text on kwrite to renaming a file on dolphin. The problem happens when selecting (either with the mouse or the keyboard shift key) from left to right a text that starts with a symbol (punctuation, slash, backslash, greater than...). The start symbols get removed and the text remains in a weird inconsistent state.
If there isn't an upstream fix in time for Fedora 44, perhaps a workaround would be to override the default Virtual Keyboard to anything other than Plasma Keyboard? Another user summarized the likely related ways this issue can manifest on the Fedora Discussion board here: https://discussion.fedoraproject.org/t/plasma-keyboard-can-cause-various-input-issues-on-kde-plasma-6-6-systems/184098
I can reproduce, but I don't think the issue is in qt6-qtbase, because I can reproduce with Qt 6.10.0 (released in October 2025) and this issue is somewhat new.
Looks like a bug in plasma-keyboard, see https://bugs.kde.org/show_bug.cgi?id=516511#c37. I can get rid of it with older checkouts of plasma-keyboard. As we workaround we can disable plasma-keyboard for now?
Can we just revert the problematic commit you identified, instead? Disabling OSK entirely seems a radical step and is bad for a11y and tablets.
AGREED AcceptedFinalBlocker Discussed at the 2026-03-30 (blocker / freeze exception) review meeting: accepted as a violation of Final criterion "For all release-blocking desktop / arch combinations, the following applications must start successfully and withstand a basic functionality test: ... text editor." https://meetbot-raw.fedoraproject.org//blocker-review_matrix_fedoraproject-org/2026-03-30/f44-blocker-review.2026-03-30-16.00.log.txt
F44 scratch build with revert: https://koji.fedoraproject.org/koji/taskinfo?taskID=143883609 F43 scratch build with revert: https://koji.fedoraproject.org/koji/taskinfo?taskID=143884030 Seems to work here, but I would appreciate anyone else giving this a try.
(In reply to Jan Grulich from comment #11) > F44 scratch build with revert: > https://koji.fedoraproject.org/koji/taskinfo?taskID=143883609 > F43 scratch build with revert: > https://koji.fedoraproject.org/koji/taskinfo?taskID=143884030 > > Seems to work here, but I would appreciate anyone else giving this a try. I tested your F44 scratch build with revert on my baremetal F44 KDE system and the fix works fine. Operating System: Fedora Linux 44 KDE Plasma Version: 6.6.3 KDE Frameworks Version: 6.24.0 Qt Version: 6.10.2 Kernel Version: 6.19.10-300.fc44.x86_64 (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5700U with Radeon Graphics Memory: 24 GiB of RAM (22.8 GiB usable) Graphics Processor: AMD Radeon Graphics
FEDORA-2026-172dd38027 (plasma-keyboard-6.6.3-2.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2026-172dd38027
FEDORA-2026-0fb6ca0047 (plasma-keyboard-6.6.3-2.fc44) has been submitted as an update to Fedora 44. https://bodhi.fedoraproject.org/updates/FEDORA-2026-0fb6ca0047
FEDORA-2026-0fb6ca0047 has been pushed to the Fedora 44 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-0fb6ca0047` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-0fb6ca0047 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-172dd38027 has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-172dd38027` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-172dd38027 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2026-0fb6ca0047 (plasma-keyboard-6.6.3-2.fc44) has been pushed to the Fedora 44 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2026-90336e873b (aurorae-6.6.4-1.fc43, bluedevil-6.6.4-1.fc43, and 145 more) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report.