Can't write anything into plasma dialogues, while I can write into KDE apps, gnome apps etc. Same behaviour in Ubuntu 16.04 and KDE NEON LTS.
To clarify, I can write into dolphin, firefox etc. I cannot write password into wireless widget in KDE5, I can't write password when KDE asks for password of admin and I can write only first letter in kickoff (other letters makes plasma freeze for a minutes). I also can'T writer into alf+f2 launcher (as always, nothing happens).
When I want to type password, I have to type it in kate for example and then copypaste into KDE's dialog. But I have to paste it using mouse, alt+v doesn't work, obviously.
can you include the output of running "env" in a terminal please.
Sure, here it is. tomas@Ubuntu-Tomas:~$ env XDG_VTNR=7 PAM_KWALLET5_LOGIN=/tmp/kwallet5_tomas.socket SSH_AGENT_PID=1723 XDG_SESSION_ID=2 CLUTTER_IM_MODULE=xim SHELL=/bin/bash TERM=xterm-256color KONSOLE_DBUS_SERVICE=:1.97 QT_LINUX_ACCESSIBILITY_ALWAYS_ON=1 KONSOLE_PROFILE_NAME=Výchozí GS_LIB=/home/tomas/.fonts WINDOWID=12582918 SHELL_SESSION_ID=65aae2a1e8e84f61bbbdefeb209d5bd2 QSG_RENDER_LOOP= KDE_FULL_SESSION=true XDG_SESSION_CLASS=user USER=tomas LS_COLORS=rs=0:di=01;34:ln=01;36:mh=00:pi=40;33:so=01;35:do=01;35:bd=40;33;01:cd=40;33;01:or=40;31;01:mi=00:su=37;41:sg=30;43:ca=30;41:tw=30;42:ow=34;42:st=37;44:ex=01;32:*.tar=01;31:*.tgz=01;31:*.arc=01;31:*.arj=01;31:*.taz=01;31:*.lha=01;31:*.lz4=01;31:*.lzh=01;31:*.lzma=01;31:*.tlz=01;31:*.txz=01;31:*.tzo=01;31:*.t7z=01;31:*.zip=01;31:*.z=01;31:*.Z=01;31:*.dz=01;31:*.gz=01;31:*.lrz=01;31:*.lz=01;31:*.lzo=01;31:*.xz=01;31:*.bz2=01;31:*.bz=01;31:*.tbz=01;31:*.tbz2=01;31:*.tz=01;31:*.deb=01;31:*.rpm=01;31:*.jar=01;31:*.war=01;31:*.ear=01;31:*.sar=01;31:*.rar=01;31:*.alz=01;31:*.ace=01;31:*.zoo=01;31:*.cpio=01;31:*.7z=01;31:*.rz=01;31:*.cab=01;31:*.jpg=01;35:*.jpeg=01;35:*.gif=01;35:*.bmp=01;35:*.pbm=01;35:*.pgm=01;35:*.ppm=01;35:*.tga=01;35:*.xbm=01;35:*.xpm=01;35:*.tif=01;35:*.tiff=01;35:*.png=01;35:*.svg=01;35:*.svgz=01;35:*.mng=01;35:*.pcx=01;35:*.mov=01;35:*.mpg=01;35:*.mpeg=01;35:*.m2v=01;35:*.mkv=01;35:*.webm=01;35:*.ogm=01;35:*.mp4=01;35:*.m4v=01;35:*.mp4v=01;35:*.vob=01;35:*.qt=01;35:*.nuv=01;35:*.wmv=01;35:*.asf=01;35:*.rm=01;35:*.rmvb=01;35:*.flc=01;35:*.avi=01;35:*.fli=01;35:*.flv=01;35:*.gl=01;35:*.dl=01;35:*.xcf=01;35:*.xwd=01;35:*.yuv=01;35:*.cgm=01;35:*.emf=01;35:*.ogv=01;35:*.ogx=01;35:*.aac=00;36:*.au=00;36:*.flac=00;36:*.m4a=00;36:*.mid=00;36:*.midi=00;36:*.mka=00;36:*.mp3=00;36:*.mpc=00;36:*.ogg=00;36:*.ra=00;36:*.wav=00;36:*.oga=00;36:*.opus=00;36:*.spx=00;36:*.xspf=00;36: XCURSOR_SIZE=0 QT_ACCESSIBILITY=1 XDG_SESSION_PATH=/org/freedesktop/DisplayManager/Session1 QT_AUTO_SCREEN_SCALE_FACTOR=0 XDG_SEAT_PATH=/org/freedesktop/DisplayManager/Seat0 SSH_AUTH_SOCK=/tmp/ssh-k4TxWQTn7Jej/agent.1670 DEFAULTS_PATH=/usr/share/gconf//usr/share/xsessions/plasma.default.path SESSION_MANAGER=local/Ubuntu-Tomas:@/tmp/.ICE-unix/2007,unix/Ubuntu-Tomas:/tmp/.ICE-unix/2007 XDG_CONFIG_DIRS=/etc/xdg/xdg-/usr/share/xsessions/plasma:/etc/xdg DESKTOP_SESSION=/usr/share/xsessions/plasma PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin QT_IM_MODULE=ibus PWD=/home/tomas XDG_SESSION_TYPE=x11 XMODIFIERS=@im=ibus KONSOLE_DBUS_WINDOW=/Windows/1 LANG=cs_CZ.UTF-8 KDE_SESSION_UID=1000 MANDATORY_PATH=/usr/share/gconf//usr/share/xsessions/plasma.mandatory.path KONSOLE_DBUS_SESSION=/Sessions/1 HOME=/home/tomas SHLVL=1 XDG_SEAT=seat0 COLORFGBG=15;0 LANGUAGE= KDE_SESSION_VERSION=5 XCURSOR_THEME=Breeze_Snow LOGNAME=tomas XDG_SESSION_DESKTOP=KDE QT4_IM_MODULE=xim XDG_DATA_DIRS=/usr/share//usr/share/xsessions/plasma:/usr/local/share/:/usr/share/:/var/lib/snapd/desktop DBUS_SESSION_BUS_ADDRESS=unix:abstract=/tmp/dbus-nZC1saBh08,guid=5b09848b0fcc42b698f6803058b15273 LESSOPEN=| /usr/bin/lesspipe %s DISPLAY=:0 XDG_RUNTIME_DIR=/run/user/1000 PROFILEHOME= XDG_CURRENT_DESKTOP=KDE GTK_IM_MODULE=xim LESSCLOSE=/usr/bin/lesspipe %s %s XAUTHORITY=/home/tomas/.Xauthority QMLSCENE_DEVICE= COLORTERM=truecolor _=/usr/bin/env tomas@Ubuntu-Tomas:~$ BTW I deleted ~/.local and ~/.cache and ~/.kde folders and after some hiccups it worked for a day... then, after reboot, the problem is the same.
The problem with disability to write into password dialogues can be solved by this, "The problem was due to ksshaskpass being called before KDE was fully loaded. " : http://askubuntu.com/questions/876375/plasma-5-8-from-backports-cant-type-into-authentication-dialogues/886068 But writing into plasma etc. has probably different origin.
not that this is a solution, but just to narrow it down can unset QT_ACCESSIBILITY and QT_IM_MODULE and determine if either of those make a difference
Ok, I tried to export QT_ACCESSIBILITY=0 and export QT_IM_MODULE=0 and export QT_IM_MODULE=xim and although in env it seems to be changed, it does not repair it.
It seems we can confirm it, as more users experience the same behaviour. http://askubuntu.com/questions/876375/plasma-5-8-from-backports-cant-type-into-authentication-dialogues
Another strange behaviour... can be connected. When I have opened qapt, installing app, I can write nowhere, doesn't matter whether in KDE/GTK/Plasma. After I close it, it is as I stated here.
Hi, I am the author of the thread on Stack Overflow. I tested it further, and I discovered that the solution I suggested there (moving the call to ksshaskpass from .bash_profile to the KDE autostart) does in fact NOT solve anything. It makes things more random, though: now I am usually able to enter the password prompt to initially open the wallet and connect to the network. But if later in the day I invoke anything that launches ksudo, then I usually still get the problem and I can't type there. Apart from the password prompts, only the FIRST letter typed into Kicker is accepted, the others get ignored for a long random time (eg. 10 seconds), then another key is registered, then silence again, and so on.
Just to add, I also have this problem after updating to Kubuntu 16.10. I can't type into search, wallet or any similar text fields, although applications like firefox or konsole have no problem.
I changed the version to 5.9.4 because it occurs in 5.9.4 too. Strange thing is that it does only on one computer I have. Others are without problem. I am really wondering if someone able is working on it :) Can someone set the status to "Confirmed"?
It occurred to me that I have two separate users on this computer. One is experiencing the issue, the other is not.
I have similar issue on two machines with Ubuntu 16.10 (one with default, on another I have kubuntu unstable ppa and KF5 from there). It seems that issue is not related to the applications itself. For example on login I can't type any character to krunner but restarting krunner fixes issue entirely. Probably something was not completely initalized because some app was not loaded for the startup moment. How ca we debug this? Maybe some strace attaching for a troublesome app instance can add more info?
(In reply to MM from comment #13) > It occurred to me that I have two separate users on this computer. One is > experiencing the issue, the other is not. I tried to recreate my user and for a day, it ran smoothly without problems. Then the bug came back.
I had the same problem after installing Kubuntu 17.04 in UEFI mode; I tried several times and many things but I always had the same issue - couldn't type in the search field, nor in the ALT+F2 launcher or any authentication dialogs. Then I tried installing Kubuntu in BIOS mode instead of UEFI, and all is good!
*** Bug 378887 has been marked as a duplicate of this bug. ***
The other solution from https://askubuntu.com/questions/838613/keyboard-not-working-properly-in-kde-after-upgrade-to-kubuntu-16-10 seems to be working: ################################### sudo apt purge ibus sudo apt install fcitx sudo dpkg-reconfigure fcitx sudo reboot ###################################
Comment 18 gives good workaround. Thanks, ochab@ichf.edu.pl
Possibly related to https://bugs.kde.org/show_bug.cgi?id=379649
Similar trouble, e.g. suddenly could not enter root pwd to run updates, could not enter text in Application Launcher "Type to search" edit box, etc. Solution mentioned in Comment 18 worked, except that the dpkg command failed, saying fcitx is not installed - perhaps the argument should be *.deb something, unsure. Whatever the case, worked without that line. Thanks.
*** Bug 379649 has been marked as a duplicate of this bug. ***
Haven't met this issue for a long time. Probably it has been fixed by himself. Unsubscribing.
Same here. Let's call it fixed, and re-open if it happens again to anyone.
I think I also suffer from this bug :/
Not fixed. Still happening to me in 2023 on fresh install of KDE on Ubuntu 22.04. Cannot type into launcher, which almost completely defeats its purpose. Weirdly, once you select a different menu item , the first keystroke gets through, and then the launcher stops accepting keyboard input again. Then when you move mouse to a different menu item, you can type a single character again. KDE Plasma 5.24.7 | KDE Framework 5.92.0 | Qt 5.15.3
That sounds like a different bug. Can you file a new bug report for it?
(In reply to amhog from comment #26) > Not fixed. Still happening to me in 2023 on fresh install of KDE on Ubuntu > 22.04. > Cannot type into launcher, which almost completely defeats its purpose. > Weirdly, once you select a different menu item , the first keystroke gets > through, and then the launcher stops accepting keyboard input again. > Then when you move mouse to a different menu item, you can type a single > character again. > > KDE Plasma 5.24.7 | KDE Framework 5.92.0 | Qt 5.15.3 Same here, but it looks to be not limited to the Application launcher, sometimes the clipboard history behaves the same way.
This is still occurring in Kali 2023. The workaround in comment 18 is still valid.