Bug 514048 - Can only enter unicode with ctrl+shift+u when Virtual Keyboard is enabled and set to Ibus Wayland
Summary: Can only enter unicode with ctrl+shift+u when Virtual Keyboard is enabled and...
Status: RESOLVED LATER
Alias: None
Product: plasmashell
Classification: Plasma
Component: Input Method widget (other bugs)
Version First Reported In: 6.5.3
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2026-01-01 17:35 UTC by Russell Haley
Modified: 2026-01-06 17:29 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 Russell Haley 2026-01-01 17:35:46 UTC
SUMMARY

Can only enter unicode with ctrl+shift+u when Virtual Keyboard is enabled and set to Ibus Wayland

STEPS TO REPRODUCE

1. Have the default virtual keyboard setting, Maliit.
2. Open a non-GTK app with text entry, like kwrite or zed editor.
3. Press ctrl+shift+u
4. Change vitual keyboard to "Ibus Wayland" and click the widget to enable the virtual keyboard
5. Press ctrl+shift+u in the non-GTK text field again.

OBSERVED RESULT

Nothing happens at step 3.

At step 5, Underlined "u" appears in text entry field, ready for direct unicode codepoint entry. For example, ctrl+shift+u 394 -> Δ, b0 -> °, etc.

EXPECTED RESULT

Default configuration behaves as in step 5.

SOFTWARE/OS VERSIONS

Operating System: Fedora Linux 43
KDE Plasma Version: 6.5.3
KDE Frameworks Version: 6.20.0
Qt Version: 6.10.1
Kernel Version: 6.17.10-300.fc43.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i5-4670K CPU @ 3.40GHz
Memory: 24 GiB of RAM (23.0 GiB usable)
Graphics Processor 1: Intel® HD Graphics 4600
Graphics Processor 2: AMD Radeon RX 580 Series

ADDITIONAL INFORMATION

This is kind of a duplicate of 103788, but I am reporting it against the part of the software stack that seems to be best placed to resolve the problem, with a more searchable title that describes how to work around it locally.
Comment 1 Nate Graham 2026-01-06 17:29:34 UTC
That makes sense since this is an IBus-specific feature. :) 

Unfortunately right now input methods are mutually exclusive. You can use IBus or Maliit, but not both at the same time.

Ideally this would change in the future, but it's a multi-year project due to the technical complexities involved.