I am using the latest kubuntu version: http://cdimage.ubuntu.com/kubuntu-plasma5/daily-live/20140919/utopic-desktop-amd64.iso 1, when do normally login, KDE doesn't launch the input method framework(e.g. ibus-daemon), thus input-method doesn't work. The corresponding ps tree is: 1 2848 2848 2848 ? -1 Ssl 0 0:00 sddm 2848 2854 2854 2854 ? -1 Ssl 0 0:30 \_ /usr/bin/X :0 -auth /var/run/sddm/:0 -nolisten tcp -background none -noreset vt1 2848 3193 2848 2848 ? -1 Sl 0 0:00 \_ /usr/lib/x86_64-linux-gnu/sddm/sddm-helper --socket /tmp/Auth2848.1411307271 --id 1 --start /usr/bin/startkde 3193 3205 2848 2848 ? -1 S 1000 0:00 \_ /bin/sh /usr/bin/startkde 3205 3256 2848 2848 ? -1 S 1000 0:00 \_ kwrapper5 ksmserver 2, However, when login on another VT, and use "startx" to launch the KDE, the input method framework works fine. The corresponding ps tree is: 1025 2160 2160 1025 tty2 3529 S 1000 0:00 \_ -bash 2160 3529 3529 1025 tty2 3529 S+ 1000 0:00 \_ /bin/sh /usr/bin/startx 3529 3546 3529 1025 tty2 3529 S+ 1000 0:00 \_ xinit /etc/X11/xinit/xinitrc -- /etc/X11/xinit/xserverrc :1 -auth /tmp/serverauth.YmIxtLE0hI 3546 3547 3547 3547 tty7 3547 Ssl+ 0 0:02 \_ /usr/bin/X -nolisten tcp :1 -auth /tmp/serverauth.YmIxtLE0hI 3546 3555 3555 1025 tty2 3529 S 1000 0:00 \_ /usr/bin/ck-launch-session /usr/bin/dbus-launch --exit-with-session /usr/bin/im-launch x-session- 3555 3617 3617 3617 ? -1 Ss 1000 0:00 \_ /usr/bin/ssh-agent env TMPDIR=/tmp /usr/bin/gpg-agent --daemon --sh --write-env-file=/home/ge 3555 3618 3618 3618 ? -1 Ss 1000 0:00 \_ /usr/bin/gpg-agent --daemon --sh --write-env-file=/home/gemfield/.gnupg/gpg-agent-info-CivilN 3555 3627 3555 1025 tty2 3529 S 1000 0:00 \_ /bin/sh /usr/bin/x-session-manager 3627 3736 3555 1025 tty2 3529 S 1000 0:00 \_ kwrapper5 ksmserver 3, seems sddm doesn't do im-launch like startx. Reproducible: Always Steps to Reproduce: 1. Power on kubuntu operation system 2. Check input method. 3. Check ps tree. Actual Results: input method cannot be used any more. Expected Results: sddm should launch the im-launch automatically.
I've noticed the same problem on my Fedora 21 system, however it's unclear to me that KDE was ever responsible for doing this. I can find no references to im-launch or ibus-daemon in KDE 4's startkde script. Perhaps it's up to the distribution to place a file in autostart?
CC'ing a few people who might know more, including Kubuntu staff.
Not sure how this is supposed to work on Fedora; in Debian, ibus installs a script in /etc/X11/Xsession.d/ which injects "im-launch" into the session launch process. I did not yet find out how or where im-launch starts ibus-daemon, but well. However, ibus still doesn't work in KDE -- not because it is not started, but because it is killed immediately. .xsession-errors: org.kde.kcm_keyboard: ibus successfully stopped I reported this as bug 379930.
Is this still happening for recent versions of Plasma, like 5.19 or later?
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!