The problem started for me also after some upgrade. Somehow the IM env.
variables are set to ibus on my system:
GTK_IM_MODULE=ibus
QT4_IM_MODULE=ibus
QT_IM_MODULE=ibus
XMODIFIERS=@im=ibus
Since KDE/Plasma has its own keyboard icon in the system tray, I advise
to run ibus-daemon without icon:
ibu
@EliasTurner I don't know. However, after updating to 17.04 Ibus was
reinstalled and I had to purge it again and reconfigure fcitx to get
things working.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
@Denny that Ubuntu documentation only seeks to confuse me more... So if
my keyboard input isn't controlled with fcitx, or ibus (I had to install
it) then what was it being controller by? 0_o spooky
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
Never mind what is default, installing fcitx worked fine. Thank you.
Lets see what happens tomorrow when I update to 17.04 ;-).
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633721
Title:
Weird inp
This:
https://help.ubuntu.com/stable/ubuntu-help/keyboard-layouts.html
seems to indicate that fcitx is default only for Asian languages.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633721
Title:
@EliasTurner Are you sure about this?
I get:
sudo dpkg-reconfigure fcitx
dpkg-query: package 'fcitx' is not installed and no information is available
Use dpkg --info (= dpkg-deb --info) to examine archive files,
and dpkg --contents (= dpkg-deb --contents) to list their contents.
/usr/sbin/dpkg-re
I will reiterate to everyone that ibus is not the default input method
for Ubuntu/Kubuntu/Xubuntu etc. They all use fcitx. If everyone having
this problem could just do as comment #25 suggests I strongly believe
their problem will be solved.
--
You received this bug notification because you are a
Joel, Please do the following in a terminal:
sudo apt purge ibus
sudo dpkg-reconfigure fcitx
sudo reboot
Everything should be back to normal after this.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1
I can confirm I have the same issue. For now, I run "ibus-daemon -d -n
--desktop=KDE" as a workaround when I am using KDE. I have ubuntu 16.10
installed, with KDE and unity.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.
Thank you, you got further in solving this problem than everyone else :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633721
Title:
Weird input behaviour in some Plasma stuff (Kicker, KRunner, pri
I am truly sorry for wasting everyone's time with so many junk posts. I
finally figured out what to do instead of messing around with ibus which
isn't even the default input method. it's this simple, go to a terminal
and type
sudo dpkg-reconfigure fcitx
and then reboot. This works perfectly for m
One last thing everyone... you're gonna wanna put that code
ibus-daemon -d -n --desktop=KDE
on your list of autostart programs so it boots up every time the PC
does. Also you will wanna change it if you end up using a different
desktop environment of course (and possibly why I was having errors in
meant to say "it's because ibus is improperly installed." I found this
out because I was getting errors opening Synaptic using KDEsudo that
basically said "could not find ibus daemon" etc. Now if only I could get
Synaptic to run outside of opening it with the terminal...
--
You received this bug
I found the solution! It's because ibus is properly installed. so do
`sudo apt remove --purge ibus`
after this, do
`sudo apt install ibus` (or build it from source using the tar.gz file here
http://packages.ubuntu.com/xenial/ibus)
reboot your PC.
Now do
`ibus-daemon -d -n --desktop=KDE`
This wor
Whoah, finally I found other people experiencing the same bug. I was on
Ubunut 16.04.01 plasma 5.7 which was working fine, but somehow broke.
Then my troubles began. I installed 5.8 and experienced this bug for the
first time. I decided to upgrade to Ubuntu 16.10 - the bug persisted. I
upgraded to
I get the exact same error. Like comment #15 says the workarounds from
comment #5 and #9 work but only for certain text input fields i.e.
trying to input my password for administrative activity popups is almost
impossible. Same with inputting the wi-fi password. I have to resort to
using my browser
I am affected too after upgrading to 16.10 (from 16.04). Workaround from
comment #5 works, but I also have to restart other affected applications
(e.g. Yakuake) after restart plasmashell.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to the bu
The workaround also does not work for the wifi-password entry. Changed
the Wifi password at work today but it is impossible to enter. Any ideas
which process I should restart for this to work?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ub
I faced this issue on Kubuntu 16.04 when upgraded plasma to 5.8.4.
Workaround seems to work, except when entering password for openvpn
connection.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633721
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: polkit-kde-agent-1 (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: plasma-workspace (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633721
Ti
Sure.
** Also affects: plasma-workspace (Ubuntu)
Importance: Undecided
Status: New
** Also affects: polkit-kde-agent-1 (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
htt
Confirmed. Still would like to find where the problem is.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633721
Title:
Weird input behaviour in some Plasma stuff (Kicker, KRunner, privilege
window
I have managed to workaround problems with priviledge windows by
restarting polkit-kde-authentication-agent-1:
killall polkit-kde-authentication-agent-1
/usr/lib/x86_64-linux-gnu/libexec/polkit-kde-authentication-agent-1 &
Seems to work fine. Please confirm if it works for you.
--
You received
Can confirm both workarounds.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1633721
Title:
Weird input behaviour in some Plasma stuff (Kicker, KRunner, privilege
window)
To manage notifi
Ok, so krunner also works, if killed and restarted (did not know that
this was something separate). The bug however remains on reboot. Which
probably means that plasma and krunner get started to early or something
like that.
Is there something I could kill and restart to get my priviledge
escalati
The latter is unfortunately true only for Kicker, not for Krunner or
privilege windows.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633721
Title:
Weird input behaviour in some Plasma stuff (Kicke
Restarting plasma with:
killall plasmashell
kstart plasmashell
resolves the problem until the next reboot.
--
You received this bug notification because you are a member of Kubuntu
Bugs, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1633721
Title:
Weird input behavio
So, we have the same case :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633721
Title:
Weird input behaviour in some Plasma stuff (Kicker, KRunner, privilege
window)
To manage notifications ab
This bug affects me too. I have tried deleting cache to no avail. In my
case this is not on a fresh install but on an update from Kubuntu 16.04
to 16.10. Would be happy with a workaround (preferably not involving
having to change UID).
--
You received this bug notification because you are a membe
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: kubuntu-settings (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633721
Ti
As I have found out today, the problem affects only one user -
administrator. And what's more, it does not occur under Wayland.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1633721
Title:
Weird inp
32 matches
Mail list logo
