SUMMARY Typing on keyboard doesn't produce any inputs in text fields used in plasma widgets / plasmoids. STEPS TO REPRODUCE 1. Open "Application Launcher" 2. Type something in the "Search" field or 1. Right-click on the desktop 2. Select "Create New..." -> "Text File" 3. Type something for filename or 1. Right-click on a panel 2. Select "Add Widgets..." 3. Type something in the search box OBSERVED RESULT No text is entered EXPECTED RESULT The typed text is entered SOFTWARE/OS VERSIONS Operating System: KDE neon 5.27 KDE Plasma Version: 5.27.2 KDE Frameworks Version: 5.103.0 Qt Version: 5.15.8 Kernel Version: 6.2.0-060200-generic (64-bit) Graphics Platform: X11 Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor Memory: 62,7 GiB of RAM Graphics Processor: AMD Radeon RX 6700 XT Product Name: B550M Pro4 ADDITIONAL INFORMATION Note 1: When I press "Super" key to open the application launcher and start typing immediately after that, sometimes I see one character being entered in the Search field. It doesn't accept any keyboard input after that, though. Note 2: I experience this behavior on two separate installations of KDE Neon (a laptop and a desktop PC). Both machines have relatively fresh installation of KDE Neon (mid-January 2023) and, IIRC, I noticed the bug soon or right after installing the OS.
Could you mention some details about your input settings? Keyboard layout? Input method used (Ibus, FCITX)? Locale settings (system-wide from /etc/dault/locale vs inside KDE ? I've been noticing that locale and input settings can create chaos in all sorts of weird places in KDE.
Created attachment 157487 [details] KDE Locale Settings
(In reply to David from comment #1) > Could you mention some details about your input settings? > > Keyboard layout? I use English and Russian keyboard layouts. > Input method used (Ibus, FCITX)? How can I get this information. > Locale settings > (system-wide from /etc/dault/locale vs inside KDE ? I've been noticing that > locale and input settings can create chaos in all sorts of weird places in > KDE. $ cat /etc/default/locale LANG=en_US.UTF-8 LC_ADDRESS=ru_RU.UTF-8 LC_IDENTIFICATION=ru_RU.UTF-8 LC_MEASUREMENT=ru_RU.UTF-8 LC_MONETARY=ru_RU.UTF-8 LC_NAME=ru_RU.UTF-8 LC_NUMERIC=ru_RU.UTF-8 LC_PAPER=ru_RU.UTF-8 LC_TELEPHONE=ru_RU.UTF-8 LC_TIME=ru_RU.UTF-8 For KDE settings, see attachment.
You can find out if you are using an input method like Fcitx by typing "echo $XMODIFIERS" in Konsole. If you have an input method installed it would look like: @im=fcitx No input method would like: @im=none or nothing at all. One last thing, type "locale" in Konsole or xterm and see if it matches the output of "cat /etc/default/locale".
(In reply to David from comment #4) > You can find out if you are using an input method like Fcitx by typing "echo > $XMODIFIERS" in Konsole. If you have an input method installed it would look > like: > > @im=fcitx > > No input method would like: > > @im=none > > or nothing at all. $ echo $XMODIFIERS @im=ibus > One last thing, type "locale" in Konsole or xterm and see if it matches the > output of "cat /etc/default/locale". $ locale LANG=en_US.UTF-8 LANGUAGE= LC_CTYPE="en_US.UTF-8" LC_NUMERIC=ru_RU.UTF-8 LC_TIME=ru_RU.UTF-8 LC_COLLATE="en_US.UTF-8" LC_MONETARY=ru_RU.UTF-8 LC_MESSAGES="en_US.UTF-8" LC_PAPER=ru_RU.UTF-8 LC_NAME=ru_RU.UTF-8 LC_ADDRESS=ru_RU.UTF-8 LC_TELEPHONE=ru_RU.UTF-8 LC_MEASUREMENT=ru_RU.UTF-8 LC_IDENTIFICATION=ru_RU.UTF-8 LC_ALL= As you see, there are some differences between `locale` output and `/etc/default/locale` (see my comment above)
(In reply to Andrey Fedoseev from comment #5) > (In reply to David from comment #4) > As you see, there are some differences between `locale` output and > `/etc/default/locale` (see my comment above) It looks like they match closely enough, in that UTF-8 is explicitly specified at both levels (system and KDE). I think we can rule out keyboard and input problems. Not sure what to look at next, hopefully somebody else can put up an idea.
I seem to be having this same issue suddenly after rebooting by Kubuntu 22.04 machine, presumably caused by a previous update that I didn't close my session for (I'd had about 90 days of uptime). For me it's broader than this ticket suggests though, as it seems to have impacted Konsole as well, at least. It was fine upon first logging in, but after several hours, I had the same issue with the application launcher including only being able to type a single letter, and Konsole stopped accepting input from the keyboard as well. If I tried to open a new window from that existing Konsole, I could not type in that one either, but opening Konsole separately from the Alt+Space launcher did allow me to type in the new Konsole window. The keyboard continued to work on other programs including Firefox at the same time. I found a few other posts in other places apparently mentioning the issue as well. https://forum.kde.org/viewtopic.php?f=289&t=175962 https://bbs.archlinux.org/viewtopic.php?id=265917 My system is an Asus G752VY-RH71. My KDE version is 5.24.7. Please let me know what other information I can provide.
*** This bug has been marked as a duplicate of bug 465519 ***