Your message dated Wed, 17 May 2017 09:58:50 +0200
with message-id <[email protected]>
and subject line Re: Bug#862721: ibus-daemon should start automatically
has caused the Debian Bug report #862721,
regarding ibus-daemon should start automatically
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
862721: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=862721
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: ibus
Version: 1.5.14-2
Severity: important
Dear Maintainer,
Right now, just installing ibus and setting it up (im-config, ibus-setup)
results in a broken system (keyboard not working) after logging back out and in.
The problem is that ibus sets the environment variables to make ibus the input
method, but it fails to start ibus-daemon automatically. I had to manually
configure my desktop environment to start "ibus-daemon -drRx".
The ibus package should ship a .dekstop file in /etc/xdg/autostart/ to fix this,
and to make it harder to break the system using ibus. Alternatively, maybe
70im-config_launch should also launch the daemon.
Kind regards,
Ralf
-- Package-specific info:
default-display-manager: /usr/bin/sddm
ibus is /usr/bin/ibus
ibus-setup is /usr/bin/ibus-setup
im-config -l => ibus xim
im-config -m => default missing ibus ibus
XMODIFIERS=@im=ibus
GTK_IM_MODULE=ibus
QT4_IM_MODULE=ibus
QT_IM_MODULE=ibus
XDG_DATA_DIRS=/usr/share:/usr/share:/usr/local/share
XDG_MENU_PREFIX=
PATH=~/bin:~/.cargo/bin:~/.local/bin:~/.opam/system/bin:/usr/local/bin:/usr/bin:/bin:/usr/local/games:/usr/games
ls -l /usr/lib/ibus/
total 344
-rwxr-xr-x 1 root root 18504 Dec 10 07:26 ibus-dconf
-rwxr-xr-x 1 root root 14408 Dec 10 07:26 ibus-engine-simple
-rwxr-xr-x 1 root root 1925 Jan 14 14:56 ibus-engine-table
-rwxr-xr-x 1 root root 1068 Jan 14 14:56 ibus-setup-table
-rwxr-xr-x 1 root root 211080 Dec 10 07:26 ibus-ui-gtk3
-rwxr-xr-x 1 root root 91848 Dec 10 07:26 ibus-x11
-- System Information:
Debian Release: 9.0
APT prefers testing
APT policy: (990, 'testing'), (500, 'testing-debug'), (100, 'unstable')
Architecture: amd64
(x86_64)
Foreign Architectures: i386
Kernel: Linux 4.11.0+ (SMP w/8 CPU cores)
Locale: LANG=de_DE.utf8, LC_CTYPE=de_DE.utf8 (charmap=UTF-8)
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages ibus depends on:
ii adwaita-icon-theme 3.22.0-1
ii dconf-cli 0.26.0-2+b1
ii dconf-gsettings-backend [gsettings-backend] 0.26.0-2+b1
ii gir1.2-gtk-3.0 3.22.11-1
ii gir1.2-ibus-1.0 1.5.14-2
ii libatk1.0-0 2.22.0-1
ii libc6 2.24-10
ii libcairo2 1.14.8-1
ii libdconf1 0.26.0-2+b1
ii libgdk-pixbuf2.0-0 2.36.5-2
ii libglib2.0-0 2.50.3-2
ii libgtk-3-0 3.22.11-1
ii libibus-1.0-5 1.5.14-2
ii libnotify4 0.7.7-2
ii libpango-1.0-0 1.40.5-1
ii libpangocairo-1.0-0 1.40.5-1
ii librsvg2-common 2.40.16-1+b1
ii libx11-6 2:1.6.4-3
ii libxi6 2:1.7.9-1
ii python3-gi 3.22.0-2
pn python3:any <none>
Versions of packages ibus recommends:
ii ibus-gtk 1.5.14-2
ii ibus-gtk3 1.5.14-2
ii ibus-qt4 1.3.3-1
ii im-config 0.30-1
ii libqt5gui5 5.7.1+dfsg-3+b1
Versions of packages ibus suggests:
pn ibus-clutter <none>
pn ibus-doc <none>
ii ibus-qt4 1.3.3-1
ii libqt5gui5 5.7.1+dfsg-3+b1
-- no debconf information
--- End Message ---
--- Begin Message ---
Hi,
it turns out you were right, this is KDE's fault. I found the following
in .xsession-errors after startup:
org.kde.kcm_keyboard: ibus successfully stopped
So it seems like ibus-daemon is starting properly (though I still could
not figure out where and how it is started), and then killed
immediately. Hooray...
I reported this as <https://bugs.kde.org/show_bug.cgi?id=379930>.
; Ralf
On 16.05.2017 17:58, Osamu Aoki wrote:
> control: severity -1 wishlist
>
> Hi,
>
> On Tue, May 16, 2017 at 10:00:24AM +0200, Ralf Jung wrote:
>> Package: ibus
>> Version: 1.5.14-2
>> Severity: important
>>
>> Dear Maintainer,
>>
>> Right now, just installing ibus and setting it up (im-config, ibus-setup)
>> results in a broken system (keyboard not working) after logging back out and
>> in.
>
> Hmmm??? If properly logging back out and in, ibus should start!
>
> Did you add particular keyboard method or IM activated?
>
> Did you follow /usr/share/doc/ibus/README.Debian.gz
>
>> The problem is that ibus sets the environment variables to make ibus the
>> input
>> method, but it fails to start ibus-daemon automatically.
>
> You need to restart complete GDM session which is non-trivial. That's
> why I recommend reboot for most people in the above linked DOC.
>
> We can't do it for you since there are many use cases which may not
> compatible with the way to handle your case.
>
>> I had to manually
>> configure my desktop environment to start "ibus-daemon -drRx".
>>
>> The ibus package should ship a .dekstop file in /etc/xdg/autostart/ to fix
>> this,
>> and to make it harder to break the system using ibus.
>
> These may worked for you since they start ibus daemon. But these may be
> good for some apps but do they make ibus work on process started by the
> dbus etc. (Some telephony program) How much test did you do to assert
> this?
>
>> Alternatively, maybe 70im-config_launch should also launch the daemon.
>
> If you properly restart X session's start up code, this script starts
> ibus daemon.
>
> I agree the way we need to configure ibus is ugly.
>
> But so far, no one, including myself, came up with a solid solution
> which works for most desktop and on all IM programs: ibus/uim/fctx.
>
> If you have a solution as a patch to current packages, please propose.
>
> Thanks.
>
> Osamu
>
--- End Message ---
