Bug 378887

Summary: Keyboard doesn't work in text fields - some problem with polkit ?
Product: [Plasma] plasmashell Reporter: Anna Ochab-Marcinek <ochab>
Component: generalAssignee: David Edmundson <kde>
Status: RESOLVED DUPLICATE    
Severity: normal CC: bhush94, plasma-bugs
Priority: NOR    
Version: 5.9.4   
Target Milestone: 1.0   
Platform: Kubuntu   
OS: Linux   
Latest Commit: Version Fixed In:

Description Anna Ochab-Marcinek 2017-04-17 18:36:18 UTC 
Keyboard doesn't work in text fields of plasma applications, for example:
- When I use Alt+F2 to run an application, I can't enter any text in the text field.
- When I click on the main menu on bottom panel and try to search something in the text field "Type to search".
- When the updater notifies about a new updates and wants me to enter password.

I am using a system where Ubuntu packages were installed first, and then I additionally installed kubuntu-desktop and all the other corresponding packages.

The problem disappears after I run the following script to restart plasmashell,  krunner, and polkit-kde-authentication-agent-1 :

#############################################

killall plasmashell #to stop plasmashell
kstart plasmashell #to restart plasmashell
killall krunner #to stop krunner
krunner #to start krunner
killall polkit-kde-authentication-agent-1

#############################################
Comment 1 Anna Ochab-Marcinek 2017-04-17 18:38:18 UTC 
The same problem was reported here:

https://askubuntu.com/questions/838613/keyboard-not-working-properly-in-kde-after-upgrade-to-kubuntu-16-10

I used their script.
Comment 2 Anna Ochab-Marcinek 2017-04-17 18:47:41 UTC 
Finally, I used the other solution from https://askubuntu.com/questions/838613/keyboard-not-working-properly-in-kde-after-upgrade-to-kubuntu-16-10 :

###################################

sudo apt purge ibus
sudo apt install fcitx
sudo dpkg-reconfigure fcitx
sudo reboot

###################################

This solution seems to work.
Comment 3 David Edmundson 2017-04-24 01:31:47 UTC 

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