DESCRIPTION Starting with Kubuntu 16.10, and still under 17.04, the Application Launcher is refusing to accept keyboard input in the "Type to search..." input box section[1]. When the launcher is opened, I can give the keyboard focus to it, but hitting keyboard keys results in nothing being written to it, making it unusable during normal usage. EXPECTED BEHAVIOR The search box accepts keyboard inputs and performs its automatic search while the user is typing. OBSERVED BEHAVIOR Most of the time, nothing happens. In a few cases, the first key pressed will be registered, but nothing else after that. STEPS TO REPRODUCE 1. Open the Application Launcher 2. Place the cursor on the "Type to search..." input box within the launcher (e.g. mouse click) 3. Press keyboard keys VERSION INFORMATION I'm not sure what version the Application Launcher is, so I retrieved version values that I hope are relevant from Dolphin >> Help >> About Dolphin >> Libraries Tab: * KDE Frameworks 5.31.0 * Qt 5.7.1 (built against 5.7.1) REMARKS If I copy a word, and then paste it on to it, either by using Ctrl+V or Right-Mouse Button -> Paste, the text is actually added to the input box and it works as intended. The problem is only seen when trying to enter input with key presses directly. This actually used to work during the initial 16.10 install, but broke several months after that (perhaps during a package update). I don't know how long it had been broken by the time I noticed it was actually broken, unfortunately. I've tried removing/purging the kubuntu-desktop and plasma-desktop packages and configuration files, rebooting, and then re-installing those packages, but the issue is still present. I'll note that this is happening in a laptop. I've never seen this problem in my desktop[2], which was also running 16.10 and was also upgraded to 17.04. FOOTNOTES [1] I've noticed the same problem with the network manager, particularly when you need to enter a password (e.g. connecting to a VPN), but I'm filing under Application Launcher b/c it's the most visible and annoying of them. The issue, however, might be related. [2] Generally, my laptop experience is always more problematic than my desktop experience, including sddm's refusal to launch and having to rely on lightdm, among others, but I don't know why this is the case.
After additional use, I've observed that the problem is not limited to Application Launcher, but is also visible when authenticating to install package updates (e.g. authentication dialog pop up from Discover) and the network manager. I no longer know under what category this issue should be classified and would appreciate if someone more knowledgeable could set a more appropriate, and perhaps more general, classification.
Cannot reproduce this bug in: Distribution: KDE neon Developer Edition - Stable Branches Plasma: 5.11.3 Frameworks: 5.41.0 Qt: 5.9.2 Kernel 4.10.0-38-generic Type: 64-bit
I was able to "fix" the issue by completely resetting my KDE Workspace. Basically, this means I had to: 1. Log out from my session 2. Remove the ~/.config/ and ~/.local/ directories 3. Log back in I don't know why this happened and certainly not why resetting the KDE Plasma Workspace this way was necessary to "fix" it. This is the summary. For more details, please see my more user-friendly response to my own question at https://askubuntu.com/a/974082/535457 In any case, it's clear that something in the KDE Plasma Workspace configs got messed up hard enough that the only way to fix it was by resetting the workspace itself.
I encountered what seems to be a variation of the issue after configuring an additional keyboard layout. I added another keyboard layout as follows: 1. Open System Settings >> Input Devices >> Keyboard >> Layouts tab 2. Check "Configure layouts" to enable the widgets below 3. Click the "Add" button 4. Use the following settings: a. Limit selection by language: English b. Layout: English (US) c. Variant: English (US, international with dead keys) d. Label: es e. Shortcut: None 5. Click "Apply" It'll work fine immediately after adding it, but I encounter the issue after the PC wakes up from being suspended. 1. Open the Application Launcher >> Leave >> Suspend 2. Wake up PC after a while and log back into your session 3. Open Application Launcher and try to make a search Any setting may work, but I've not tested many and the ones above are the ones I used. I don't know if it'll happen with any possible keyboard layout, or if a specific layout needs to be "active" at some point to trigger it. In addition, after hitting the issue, trying to re-open the "Configure layouts" window after waking up the PC takes 1+ minute and often hangs, making it difficult to undo the cause. In order to fix it, I've had to (patiently) go back to the keyboard layouts, undo the steps I outlined above, and then reboot the PC for things to go back to normal. There seems to be a deeper issue here.
Please check if you have IBus and/or Gnome Keyring installed. It could be a duplicate of bug 376966.
(In reply to Christoph Feck from comment #5) > Please check if you have IBus and/or Gnome Keyring installed. It could be a > duplicate of bug 376966. I checked the bug report you mentioned. While I do have IBus and Gnome Keyring installed, I'm not convinced this is a duplicate, especially given what I said I had to do to fix the problem described in the initial report. I didn't have to interact with IBus or Gnome Keyring; I only had to reset my KDE Workspace as I explained in a prev. comment. It seems that if, in someone else's estimation, this is really a duplicate, then the question of how removing ~/.config/ and ~/.local/ does anything to "fix" problems caused by IBus and/or Gnome Keyring will need a good answer. It's at least not clear to me how that would be related. In addition, the other bug report points to running out of memory as a "trigger" for the problem, whereas my PC's memory usage doesn't fit that case for the initial report or keyboard layout issues I mentioned more recently.
I can confirm that the keyboard layout issue is still reproducible after quitting IBus.
To be more specific, I observed the issue without the need to suspend or restart the PC when I launched Discover to install some updates, and I wasn't able to enter my password at the prompt.
I reported the same bug here (workaround included): https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=922334
Still cannot reproduce. Is anyone able to reproduce this in Plasma 5.19 or 5.20 (released tomorrow)?
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!
*** This bug has been marked as a duplicate of bug 376866 ***