Bug 485183 - Widget explorer is forced to close when typing with input method in the search box under Wayland session
Summary: Widget explorer is forced to close when typing with input method in the searc...
Status: RESOLVED DUPLICATE of bug 489057
Alias: None
Product: plasmashell
Classification: Plasma
Component: Widget Explorer sidebar (show other bugs)
Version: 6.0.3
Platform: Arch Linux Linux
: NOR normal
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-04-07 13:24 UTC by Kirikaze Chiyuki
Modified: 2024-08-22 21:00 UTC (History)
4 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Kirikaze Chiyuki 2024-04-07 13:24:58 UTC
SUMMARY
CJK input method works incorrectly in the search box of "Add Widget". Once any characters are entered, the "Add Widget" sidebar will be forcibly closed.


STEPS TO REPRODUCE
1. Open widget explorer on Plasma Wayland session
2. Type some characters with CJK input method

OBSERVED RESULT
The widget explorer sidebar closes

EXPECTED RESULT
Search box works normally

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux 6.7.12
KDE Plasma Version: 6.0.3 (Wayland)
KDE Frameworks Version: 6.0.0
Qt Version: 6.6.3
Comment 1 fanzhuyifan 2024-04-08 21:25:43 UTC
Can reproduce. The widget explorer closes as soon as I switch to Chinese input method using fcitx5 -- I don't even need to type anything for the widget explorer to close.

But copying and pasting Chinese characters doesn't close the widget explorer.

Operating System: Arch Linux 
KDE Plasma Version: 6.0.80
KDE Frameworks Version: 6.1.0
Qt Version: 6.7.0
Kernel Version: 6.8.4-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 20 × 13th Gen Intel® Core™ i9-13900H
Memory: 15.2 GiB of RAM
Graphics Processor: Mesa Intel® Graphics
Manufacturer: ASUSTeK COMPUTER INC.
Product Name: ROG Zephyrus G16 GU603VV_GU603VV
System Version: 1.0
Comment 2 Nate Graham 2024-08-22 21:00:49 UTC

*** This bug has been marked as a duplicate of bug 489057 ***