Bug#1014052: ibus:After rebooted, I must do `ibus-daemon -rxd` change japanese to anthy with kanji key.

[Yukiharu YABUKI]

Package: ibus
Version: 1.5.26-4
Severity: normal
X-Debbugs-Cc: yya...@debian.org

Dear Maintainer,

In unstable, after reboot, I hit kanji key, but ibus does not changed
japanse to anthy. Stable release version changed japanse to anthy.

So, I tried to fix. I do `ibus-daemon -xrd`. Then kanji key can
change japanse to anthy.

I set up same way between stable and unstable.


-- Package-specific info:
ibus is /usr/bin/ibus
ibus-setup is /usr/bin/ibus-setup
im-config -l => ibus xim
im-config -m => 'default' 'ibus' 'ibus' '' 'ibus'

XMODIFIERS=@im=ibus
GTK_IM_MODULE=ibus
QT_IM_MODULE=ibus
WAYLAND_DISPLAY=
XDG_CURRENT_DESKTOP=i3
XDG_MENU_PREFIX=
XDG_RUNTIME_DIR=/run/user/1000
XDG_SEAT=seat0
XDG_SESSION_CLASS=user
XDG_SESSION_DESKTOP=i3
XDG_SESSION_ID=2
XDG_SESSION_TYPE=x11

== ls -l /usr/lib/ibus/ibus-* /usr/libexec/ibus-* ==
/bin/ls: cannot access '/usr/lib/ibus/ibus-*': No such file or directory
-rwxr-xr-x 1 root root 22832 Apr 10 21:16 /usr/libexec/ibus-dconf
-rwxr-xr-x 1 root root 1119 Jan 2 05:25 /usr/libexec/ibus-engine-anthy
-rwxr-xr-x 1 root root 14640 Apr 10 21:16 /usr/libexec/ibus-engine-simple
-rwxr-xr-x 1 root root 166192 Apr 10 21:16 /usr/libexec/ibus-extension-gtk3
-rwxr-xr-x 1 root root 18736 Apr 10 21:16 /usr/libexec/ibus-memconf
-rwxr-xr-x 1 root root 92464 Apr 10 21:16 /usr/libexec/ibus-portal
-rwxr-xr-x 1 root root 1053 Jan 2 05:25 /usr/libexec/ibus-setup-anthy
-rwxr-xr-x 1 root root 121144 Apr 10 21:16 /usr/libexec/ibus-ui-emojier
-rwxr-xr-x 1 root root 321904 Apr 10 21:16 /usr/libexec/ibus-ui-gtk3
-rwxr-xr-x 1 root root 100280 Apr 10 21:16 /usr/libexec/ibus-x11

== dpkg-query -l 'ibus*' ==
Desired=Unknown/Install/Remove/Purge/Hold
| Status=Not/Inst/Conf-files/Unpacked/halF-conf/Half-inst/trig-aWait/Trig-pend
|/ Err?=(none)/Reinst-required (Status,Err: uppercase=bad)
||/ Name Version Architecture Description
+++-=================-============-============-====================================
ii ibus 1.5.26-4 amd64 Intelligent Input Bus - core
ii ibus-anthy 1.5.14-1 amd64 anthy engine for IBus
un ibus-array <none> <none> (no description available)
un ibus-clutter <none> <none> (no description available)
ii ibus-data 1.5.26-4 all Intelligent Input Bus - data files
un ibus-doc <none> <none> (no description available)
un ibus-el <none> <none> (no description available)
un ibus-googlepinyin <none> <none> (no description available)
ii ibus-gtk:amd64 1.5.26-4 amd64 Intelligent Input Bus - GTK2 support
ii ibus-gtk3:amd64 1.5.26-4 amd64 Intelligent Input Bus - GTK3 support
ii ibus-gtk4:amd64 1.5.26-4 amd64 Intelligent Input Bus - GTK4 support
un ibus-mozc <none> <none> (no description available)
un ibus-pinyin <none> <none> (no description available)
un ibus-qt5 <none> <none> (no description available)

=== gsettings ===
org.freedesktop.ibus.general dconf-preserve-name-prefixes ['/desktop/ibus/engine/pinyin', '/desktop/ibus/engine/bopomofo', '/desktop/ibus/engine/hangul']
org.freedesktop.ibus.general embed-preedit-text true
org.freedesktop.ibus.general enable-by-default false
org.freedesktop.ibus.general engines-order ['anthy', 'xkb:jp::jpn']
org.freedesktop.ibus.general preload-engines ['xkb:jp::jpn', 'anthy']
org.freedesktop.ibus.general switcher-delay-time 400
org.freedesktop.ibus.general use-global-engine true
org.freedesktop.ibus.general use-system-keyboard-layout false
org.freedesktop.ibus.general use-xmodmap true
org.freedesktop.ibus.general version '1.5.26'
org.freedesktop.ibus.general xkb-latin-layouts ['ara', 'bg', 'cz', 'dev', 'gr', 'gur', 'in', 'jp(kana)', 'mal', 'mkd', 'ru', 'ua']
org.freedesktop.ibus.general.hotkey disable-unconditional @as []
org.freedesktop.ibus.general.hotkey enable-unconditional @as []
org.freedesktop.ibus.general.hotkey next-engine ['Alt+Shift_L']
org.freedesktop.ibus.general.hotkey next-engine-in-menu ['Alt+Shift_L']
org.freedesktop.ibus.general.hotkey prev-engine @as []
org.freedesktop.ibus.general.hotkey previous-engine @as []
org.freedesktop.ibus.general.hotkey trigger ['Control+space', 'Zenkaku_Hankaku', 'Alt+Kanji', 'Alt+grave', 'Hangul', 'Alt+Release+Alt_R']
org.freedesktop.ibus.general.hotkey triggers ['Zenkaku_Hankaku']
org.freedesktop.ibus.panel auto-hide-timeout 10000
org.freedesktop.ibus.panel custom-font 'Sans 16'
org.freedesktop.ibus.panel follow-input-cursor-when-always-shown false
org.freedesktop.ibus.panel lookup-table-orientation 1
org.freedesktop.ibus.panel property-icon-delay-time 500
org.freedesktop.ibus.panel show 2
org.freedesktop.ibus.panel show-icon-on-systray true
org.freedesktop.ibus.panel show-im-name false
org.freedesktop.ibus.panel use-custom-font true
org.freedesktop.ibus.panel use-glyph-from-engine-lang true
org.freedesktop.ibus.panel x -1
org.freedesktop.ibus.panel xkb-icon-rgba '#ffffff'
org.freedesktop.ibus.panel y -1
org.freedesktop.ibus.panel.emoji favorite-annotations @as []
org.freedesktop.ibus.panel.emoji favorites ['?', '?', '?']
org.freedesktop.ibus.panel.emoji font 'Monospace 16'
org.freedesktop.ibus.panel.emoji has-partial-match false
org.freedesktop.ibus.panel.emoji hotkey ['<Control>period', '<Control>semicolon']
org.freedesktop.ibus.panel.emoji lang 'en'
org.freedesktop.ibus.panel.emoji load-emoji-at-startup true
org.freedesktop.ibus.panel.emoji load-unicode-at-startup false
org.freedesktop.ibus.panel.emoji partial-match-condition 0
org.freedesktop.ibus.panel.emoji partial-match-length 3
org.freedesktop.ibus.panel.emoji unicode-hotkey ['<Control><Shift>u']

=== localectl status ===
System Locale: LANG=ja_JP.UTF-8
VC Keymap: n/a
X11 Layout: jp
X11 Model: pc105

=== /etc/X11/default-display-manager ===
/usr/sbin/gdm3

=== setxkbmap -print ===


-- System Information:
Debian Release: bookworm/sid
APT prefers unstable
APT policy: (500, 'unstable')
Architecture: amd64 (x86_64)

Kernel: Linux 5.18.0-2-amd64 (SMP w/16 CPU threads; PREEMPT)
Locale: LANG=ja_JP.UTF-8, LC_CTYPE=ja_JP.UTF-8 (charmap=UTF-8), LANGUAGE not set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled

Versions of packages ibus depends on:
ii adwaita-icon-theme 42.0-2
ii dconf-cli 0.40.0-3
ii gir1.2-gtk-3.0 3.24.34-1
ii gir1.2-ibus-1.0 1.5.26-4
ii ibus-data 1.5.26-4
ii init-system-helpers 1.63
ii libatk1.0-0 2.38.0-1
ii libc6 2.33-7
ii libcairo2 1.16.0-5
ii libdconf1 0.40.0-3
ii libgdk-pixbuf-2.0-0 2.42.8+dfsg-1
ii libglib2.0-0 2.72.2-2
ii libgtk-3-0 3.24.34-1
ii libibus-1.0-5 1.5.26-4
ii libpango-1.0-0 1.50.7+ds-1
ii libpangocairo-1.0-0 1.50.7+ds-1
ii libx11-6 2:1.7.5-1
ii libxfixes3 1:6.0.0-1
ii libxi6 2:1.8-1
ii python3 3.10.4-1+b1
ii python3-gi 3.42.1-1
ii python3-ibus-1.0 1.5.26-4

Versions of packages ibus recommends:
ii ibus-gtk 1.5.26-4
ii ibus-gtk3 1.5.26-4
ii ibus-gtk4 1.5.26-4
ii im-config 0.52-1

Versions of packages ibus suggests:
pn ibus-clutter <none>
pn ibus-doc <none>

-- no debconf information

[Gunnar Hjalmarsson]

Control: tags -1 moreinfo

Thanks for your report.

I see that you use i3, which reminds me of the Ubuntu bug
<https://launchpad.net/bugs/1879352>. (Probably not related, since it
works for you in bullseye.)

Can you please show us the output of this command:

ps aux | grep ibus

I'd like to see the output both before and after your restarting of
ibus-daemon.

--
Gunnar Hjalmarsson

[Osamu Aoki]

Hi,

I had similar experience of loosing Japanese input upon system updates.

This happened only after system updates without rebooting.

I never investigated the packages involved in this problem.

Rebooing the system always fixed this problem for me based on my vague memory.

I don't recall this happened before moving to Wayland.

As you know, recent Debian system restarts some processes run under systemd upon
system updates. Maybe some ibus or ibus-anthy or even xwayland related process may
need to be included in the set of programs to be restarted to avoid rebooting the
system. This is my speculation of this situation.

If this is related to restarting xwayland startup scripts, Ubuntu bug mentioned by
Gunnar may be related.

Regards,

Osamu

[Yukiharu YABUKI]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Sorry I forgot attaching restarted status.

Now ibus-daemon can use Kanji(Zenkaku_Hankaku) key.

$ ibus-daemon -xrd
$ ps aux | grep ibus
yabuki 8643 1.6 0.0 382764 10760 ? Ssl 15:51 0:00
ibus-daemon -xrd yabuki 8659 0.0 0.0 233820 8056 ? Sl
15:51 0:00 /usr/libexec/ibus-dconf yabuki 8660 1.8 0.0 543364
45288 ? Sl 15:51 0:00 /usr/libexec/ibus-ui-gtk3 yabuki
8661 12.0 0.0 267756 29272 ? Sl 15:51
0:00 /usr/libexec/ibus-extension-gtk3 yabuki 8663 0.6 0.0 187120
20996 ? Sl 15:51 0:00 /usr/libexec/ibus-x11 --kill-daemon
yabuki 8668 0.0 0.0 233756 7444 ? Sl 15:51
0:00 /usr/libexec/ibus-portal yabuki 8687 2.0 0.0 281960
25156 ? Sl 15:51 0:00
python3 /usr/share/ibus-anthy/engine/main.py --ibus yabuki 8712
0.0 0.0 159976 7676 ? Sl 15:51
0:00 /usr/libexec/ibus-engine-simple yabuki 8739 0.0 0.0 4484
2240 pts/1 S+ 15:51 0:00 grep ibus

- --
Yukiharu YABUKI <yya...@debian.org>
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEZ4rGejxaFgWBItYhcagC0LzRvJIFAmLGg3oACgkQcagC0LzR
vJLH+BAAyKmXs76N5n95135O18ObxG54ex17h6Oj1xu5xJhN9S4u7yhXm9PrkH3+
Fkaa3zuLFnwwoUMZwDwe3mLqRtpgz7DEu+DG+9JV+N73Hrfc6FGY19h6BHow9Lol
UadmminVtnZddU1cz5bjLjfjYkVlsV8+4IuY9LhEjftJH+VOHfObbH6Km770fW9Y
FfWbOgKeosk5SRH4Fuc1oPOf6lRskH0xqCzT3QU7RU+GoAbTBVyDnmwim3xfs/r8
RU1zYCzvgxJXAOMHnsZiRDt4KjMm1Mv5Cc2GBpdPBpkm7496IIClCHkaN6vinzAc
44W9/yjrYcI99d2H5TaUwlyN0jxemNMwpG3CWKVihMArUREIy2l/j36VxAtW39Or
RCjm966kLGo77ftION3NxObTG+4+Iw5Hu2vsSTC4MWU3vVXplYgTXJIPMkESwLLu
VvMFKWpt82yJeGUZUEjVR21pjXiG+3QtOFE0IOCiMYef1V1W+aBRKBUMfVhuSALw
aGG4XRbZerVOwTqXHeINooMrgk4JuZ85KYeWpTPkYl3FTt4zR4vtgdZhv966gzAU
hGLdSack9hNDqNj1sLpIMgdygCflLZzrO3XGwtuMOU00vMFE5vk00S+oxvSEsjQs
nR6zL656+oaaMLvveijgtBhfkSJ/tvhBT5uZxc22ppkwGV64ET4=
=qhe/
-----END PGP SIGNATURE-----

[Gunnar Hjalmarsson]

Control: tags -1 - moreinfo

Thanks for additional info, Yukiharu YABUKI. Unfortunately it didn't
bring us closer to an explanation, since

/usr/bin/ibus-daemon --daemonize --xim

is basically the same as

ibus-daemon -xrd

On 2022-07-07 02:49, Osamu Aoki wrote:
> As you know, recent Debian system restarts some processes run under
> systemd upon system updates. Maybe some ibus or ibus-anthy or even
> xwayland related process may need to be included in the set of programs
> to be restarted to avoid rebooting the system.

Hmm.. If I understand it correctly, a reboot only is not sufficient for
the OP to work around this issue.

--
Gunnar

[Yukiharu YABUKI]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA256

Hi,

How I do check where started ibus read the ibus configration?

I did setup with im-config for ibus.

It seems to me that ibus-daemon re-read my home configration.

- --
Yukiharu YABUKI <yya...@debian.org>
-----BEGIN PGP SIGNATURE-----

iQIzBAEBCAAdFiEEZ4rGejxaFgWBItYhcagC0LzRvJIFAmLHgvoACgkQcagC0LzR
vJJqAxAAztTiOR5kvT+ZzqryIlvpO97yoC97oJ78A4k2BKAvIDZ2tCjlsXL6GwHB
UOr8kj9BmMLsC70Wi3ccXnzQQRVOr/bl193cPcGCv3YdbE7p4RQi1x/FUolPZ3qx
EjoqJky796nYlKOliGrCfnL5P5roh6xE5H3BfZ1DeNHMZGq1oXbJj8903784n1B1
2Qbz6YrTngKc4jbnLxNZVLmndrvW8Ep42PtTyzzqBypdcLvCJdqeEuB9foFI7VY0
PWWw4eWEYOXHCTm9xeflsPhESAvf8oypJwRTBdAvIiAmdj+Spjrty+dSQBeq3qSN
p/W9vMeA+W7fhpFQxexNCbMh8AnASAF6WvUpynGCr4rUrDqiBzyt+MUx0f5GXAxT
ty3fi8BoFwDtPXtPpZrslCRivgX+oKrnsaP4UOXpD4wn1dey2N/+uQibBn3zNZXi
ik1h1swDPAcQZYGV+SysH68IDLG47ewYsBV9Lr4t0s9LpIHh6lhVxwwSFzm71DlG
U30bt7SPKWnBkghjEDo5HDg2tUM7J8NbaKseuVcoLeJ3suE/rOfXZBALovlOw12w
0/kf9Tr7iE4LfNzk4CeMh6JKaZSZ2fTX5oOQCajz1NSbOL6d/T/p94iBacuGRhrK
fG0FXfcDQG1oxVwHqWKfiLPCKG5ySMi1HU87qz2RM2VCNecclw0=
=JMoK
-----END PGP SIGNATURE-----

[Gunnar Hjalmarsson]

On 2022-07-08 03:06, Yukiharu YABUKI wrote:
> How I do check where started ibus read the ibus configration?
>
> I did setup with im-config for ibus.
>
> It seems to me that ibus-daemon re-read my home configration.

What exactly do you mean by "home configuration"?

Actually, with im-config installed, there shouldn't be a need for any
kind of configuration in your $HOME. ibus should still be started and
properly configured.

Do you possibly have some extra configuration which conflicts with
im-config?

--
Gunnar

[Yukiharu YABUKI]

Hi,

I did execute im-config. Then I choose ibus.
So im-config made ~/.xinputrc

~/.xinput contains
````
# im-config(8) generated on Sat, 30 Jul 2022 00:23:42 +0900
run_im ibus
# im-config signature: f863f9b702709aac186b408cc110240c -
```

On Thu, 28 Jul 2022 22:51:10 +0200
Gunnar Hjalmarsson <gunn...@debian.org> wrote:

> Actually, with im-config installed, there shouldn't be a need for any
> kind of configuration in your $HOME. ibus should still be started and
> properly configured.
>
> Do you possibly have some extra configuration which conflicts with
> im-config?

--

Yukiharu YABUKI <yya...@debian.org>

[Gunnar Hjalmarsson]

On 2022-07-29 17:30, Yukiharu YABUKI wrote:
> I did execute im-config. Then I choose ibus.
> So im-config made ~/.xinputrc
>
> ~/.xinput contains
> ````
> # im-config(8) generated on Sat, 30 Jul 2022 00:23:42 +0900
> run_im ibus
> # im-config signature: f863f9b702709aac186b408cc110240c -
> ```

Ok, that should not be a problem. Explicitly choosing ibus just makes
sure that im-config starts/configures ibus rather than some other IM
framework (e.g. fcitx5) if that would be installed.

--
Gunnar

[Osamu Aoki]

Hi,

> -----Original Message-----
> From: Yukiharu YABUKI <yya...@debian.org>
> To: Gunnar Hjalmarsson <gunn...@debian.org>
> Cc: Osamu Aoki <os...@debian.org>, 101...@bugs.debian.org
> Subject: Re: Bug#1014052: ibus:After rebooted, I must do `ibus-daemon -rxd` change
> japanese to anthy with kanji key.

So you are still suffering ... Strange.

Do you have the same issue with any GTK program? Say lxterminal ?

If program using ibus/anthy is GTK, it doesn't access such daemon. It access library
instead. So the symptom reported is strange.

Are you suffering this problem with rxvt or xterm?

Please double check if your power-down is the real one (not sleep button) by shutting
down system from the virtual Linux console command line (ALT-CTRL-F3 etc.) with "sudo
shutdown -h now" or similar.

Osamu

> >

[Yukiharu YABUKI]

Hi,

Ok, I'll install lxterminal(lxterm)

My default terminal is uxterm.

I go over this issue with uxterm and lxterm.

Both of these terminal do not change between
"日本語 - anthy" and "日本語 - japanese".

I found one more strange behavior.

odd number I did `ibus-daemon -rxd` It works fine.
but even number I did `ibus-daemon -rxd` does not
accept ctrl+j.

It's time to learn how to use debuginfod. ...
I need to help how to setup and debug.

I'll try to ask mailling list.

When I reboot my desktop machine, I do `reboot` command.

On Sat, 30 Jul 2022 01:30:41 +0900
Osamu Aoki <os...@debian.org> wrote:


>
> So you are still suffering ... Strange.
>
> Do you have the same issue with any GTK program? Say lxterminal ?
>
> If program using ibus/anthy is GTK, it doesn't access such daemon. It access library
> instead. So the symptom reported is strange.
>
> Are you suffering this problem with rxvt or xterm?
>
> Please double check if your power-down is the real one (not sleep button) by shutting
> down system from the virtual Linux console command line (ALT-CTRL-F3 etc.) with "sudo
> shutdown -h now" or similar.
>
> Osamu

--
Yukiharu YABUKI <yya...@debian.org>

[Osamu Aoki]

Hi, Yabuki-san and Gunnar,

Gunnar,

im-config has gone through several changes last several years to accommodate non-ibus
for GNOME on wayland. We may have introduced some regression for X based system.

Since I don't use non-wayland system, we may have over looked problem there.

One point I am worried is ibus daemon starting process. The currently, we don't set
"-r" to replace existing daemon. Does im-config starts daemon twice? Should we add
"-r" option there? (I know it should not start twice.)

My GNOME start up has several start ups of ibus daemon. Do we need similar ?
```
$ journalctl -a -b |grep 'ibus'
Jul 31 15:35:25 goofy /usr/libexec/gdm-wayland-session[1037]: dbus-daemon[1037]:
[session uid=116 pid=1037] Activating service name='org.gtk.vfs.Daemon' requested by
':1.22' (uid=116 pid=1366 comm="ibus-daemon --panel disable")
Jul 31 15:35:25 goofy /usr/libexec/gdm-wayland-session[1037]: dbus-daemon[1037]:
[session uid=116 pid=1037] Activating service name='org.freedesktop.portal.IBus'
requested by ':1.22' (uid=116 pid=1366 comm="ibus-daemon --panel disable")
Jul 31 15:35:25 goofy /usr/libexec/gdm-wayland-session[1037]: dbus-daemon[1037]:
[session uid=116 pid=1037] Activating service name='org.freedesktop.portal.IBus'
requested by ':1.35' (uid=116 pid=1514 comm="ibus-daemon --panel disable -r --xim")
Jul 31 15:35:32 goofy dbus-daemon[1749]: [session uid=1000 pid=1749] Activating
service name='org.freedesktop.portal.IBus' requested by ':1.61' (uid=1000 pid=1986
comm="/usr/bin/ibus-daemon --panel disable")
```


Yabuki-san,

I don't understand your situation well. Maybe telling me minimum set up to reproduce
under KVM may be a good idea. Anyway, ....

`ctrl+j` key-binding sounds like something ibus-anthy preference menu sets if you
ever set it so or it is the default. (I may have changed it on my system so I can't
check for you ...) That's after having working ibus-anthy and using anthy as input
method. It only changs operational mode of anthy. You set it through anthy's
preference menu.

Switching between "日本語 - anthy" and "日本語 - japanese" sounds like switching between
different ibus engines. That's usually SUPER-SPACE and its binding is set by ibus-
setup for pure classic X system. (I usually don't bother enabling "日本語 - japanese"
as input method since I need more than Hiragana ... You can see which methods are
active by looking at ibus-setup GUI selection screen.)

Checking running processes on your system with "sudo ps axjf" may give you some idea.

As I checked on GNOME/wayland, it starts ibus daemon without --xim.
(excuse me for folded lines)

```
PPID PID PGID SID TTY TPGID STAT UID TIME COMMAND
0 2 0 0 ? -1 S 0 0:00 [kthreadd]
2 3 0 0 ? -1 I< 0 0:00 \_ [rcu_gp]
... skip
0 1 1 1 ? -1 Ss 0 0:01 /sbin/init
... skip
1 1719 1719 1719 ? -1 Ss 1000 0:00
/lib/systemd/systemd --user
... skip
1719 1983 1983 1983 ? -1 Ss 1000 0:00 \_ sh -c
/usr/bin/ibus-daemon --panel disable $([ "$XDG_SESSION_TYPE" = "x11" ] && echo "--
xim")
1983 1986 1986 1983 ? -1 Sl 1000 0:20 | \_
/usr/bin/ibus-daemon --panel disable
1986 2105 1986 1983 ? -1 Sl 1000 0:00 | \_
/usr/libexec/ibus-dconf
1986 2106 1986 1983 ? -1 Sl 1000 0:03 | \_
/usr/libexec/ibus-extension-gtk3
1986 2183 1986 1983 ? -1 Sl 1000 0:12 | \_
python3 /usr/share/ibus-anthy/engine/main.py --ibus
2183 6808 1986 1983 ? -1 Z 1000 0:00 | | \_
[python3] <defunct>
1986 2898 1986 1983 ? -1 Sl 1000 0:00 | \_
/usr/lib/ibus-mozc/ibus-engine-mozc --ibus
...
1719 5490 5490 5490 ? -1 Ssl 1000 0:24 \_
/usr/libexec/gnome-terminal-server
5490 5508 5508 5508 pts/0 7133 Ss 1000 0:00 | \_ bash
5508 7133 7133 5508 pts/0 7133 S+ 1000 0:00 | | \_
/usr/bin/mc -P /tmp/mc-osamu/mc.pwd.5508
7133 7135 7135 7135 pts/1 7135 Ss+ 1000 0:00 | | \_
bash -rcfile .bashrc
5490 7490 7490 7490 pts/2 8568 Ss 1000 0:00 | \_ bash
7490 8568 8568 7490 pts/2 8568 S+ 0 0:00 | | \_ sudo
ps axjf
8568 8569 8569 8569 pts/3 8570 Ss 0 0:00 | | \_
sudo ps axjf
8569 8570 8570 8569 pts/3 8570 R+ 0 0:00 | |
\_ ps axjf
5490 7951 7951 7951 pts/4 8044 Ss 1000 0:00 | \_ bash
7951 8044 8044 7951 pts/4 8044 S+ 1000 0:00 | | \_
/usr/bin/mc -P /tmp/mc-osamu/mc.pwd.7951
8044 8046 8046 8046 pts/5 8046 Ss+ 1000 0:00 | | \_
bash -rcfile .bashrc
5490 8238 8238 8238 pts/6 8238 Ss+ 1000 0:00 | \_ bash
...

```

Osamu

[Yukiharu YABUKI]

Aoki-san.

Thank you for your suggestion.

I did 'ps axjf'. This output was too big. I selected from output.

1) gdm3

1 1087 1087 1087 ? -1 Ssl 0
0:00 /usr/sbin/gdm3 1087 2337 1087 1087 ? -1
Sl 0 0:00 \_ gdm-session-worker [pam/gdm-password] 2337
2532 2532 2532 tty2 2532 Ssl+ 1000 0:00
\_ /usr/libexec/gdm-x-session --register-session --run-script i3 2532
2534 2532 2532 tty2 2532 Sl+ 1000 7:13
\_ /usr/lib/xorg/Xorg vt2 -displayfd 3 -auth /run/user/1000/gd 2532
2604 2532 2532 tty2 2532 S+ 1000 0:04 \_ i3
2604 2690 2690 2690 ? -1 Ss 1000
0:00 \_ /usr/bin/ssh-agent /usr/bin/im-launch i3

2) ibus-daemon

1 385641 385641 385641 ? -1 Ssl 1000 0:15
ibus-daemon -xrd 385641 385651 385641 385641 ? -1 Sl
1000 0:00 \_ /usr/libexec/ibus-dconf 385641 385652 385641
385641 ? -1 Sl 1000 0:03 \_ /usr/libexec/ibus-ui-gtk3
385641 385653 385641 385641 ? -1 Sl 1000 0:04
\_ /usr/libexec/ibus-extension-gtk3 385641 385679 385641
385641 ? -1 Sl 1000 0:00
\_ /usr/libexec/ibus-engine-simple 385641 385777 385641
385641 ? -1 Sl 1000 0:09 \_
python3 /usr/share/ibus-anthy/engine/main.py --ibus 1 385655 385641
385641 ? -1 Sl 1000 0:11 /usr/libexec/ibus-x11
--kill-daemon

3) ps axjf

1 8145 8144 8144 ? -1 S 1000
0:00 /bin/sh -c uxterm 8145 8146 8144 8144 ? -1
S 1000 0:00 \_ xterm -class UXTerm -title uxterm -u8 8146
8150 8150 8150 pts/7 845149 Ss 1000 0:00 \_ bash
8150 845149 845149 8150 pts/7 845149 S+ 0 0:00
\_ sudo ps axjf 845149 845293 845293 845293 pts/19 845294 Ss
0 0:00 \_ sudo ps axjf 845293 845294 845294 845293
pts/19 845294 R+ 0 0:00 \_ ps axjf


--
Yukiharu YABUKI <yya...@debian.org>

[Gunnar Hjalmarsson]

On 2022-07-31 10:39, Osamu Aoki wrote:
> im-config has gone through several changes last several years to
> accommodate non-ibus for GNOME on wayland. We may have introduced
> some regression for X based system.

It's possible, of course. OTOH I just installed an XFCE system (Xubuntu
22.04), installed ibus-anthy, and things just work. Even if my keyboard
does not include any special Japanese keys...

> `ctrl+j` key-binding sounds like something ibus-anthy preference menu
> sets if you ever set it so or it is the default. (I may have changed
> it on my system so I can't check for you ...)

It is the default.

> That's after having working ibus-anthy and using anthy as input
> method. It only changs operational mode of anthy. You set it
> through anthy's preference menu.
>
> Switching between "日本語 - anthy" and "日本語 - japanese" sounds like
> switching between different ibus engines. That's usually SUPER-SPACE
> and its binding is set by ibus- setup for pure classic X system.

That distinction is important. Ctrl+J for toggling between Hiragana and
latin typing, while the active input method is Anthy, vs. Super+Space
for switching to some other input source.

--
Gunnar

[Osamu Aoki]

Hi,

> -----Original Message-----
> From: Yukiharu YABUKI <yya...@debian.org>
> To: Osamu Aoki <os...@debian.org>
> Cc: 101...@bugs.debian.org
> Subject: Re: Bug#1014052: ibus:After rebooted, I must do `ibus-daemon -rxd` change
> japanese to anthy with kanji key.

> Date: Mon, 1 Aug 2022 02:14:11 +0900
>
> ...

> I did 'ps axjf'. This output was too big. I selected from output.

> ...

> python3 /usr/share/ibus-anthy/engine/main.py --ibus 1 385655 385641
> 385641 ? -1 Sl 1000 0:11 /usr/libexec/ibus-x11
> --kill-daemon
>

I don't know but "kill" sounds dangerous :-) but maybe OK. It's installed by ibus.

Anyway, since you are running relatively minor desktop with i3, this may be the
reason. Proper working of im-config rely on xdm/kdm like start up.

Since it is almost impossible to figure-out when did it broke, the best thing is to
set up testing VMs.

Then try different DE settings: GNOME -> KDE -> LXDE -> i3
Once you know when things break, we have better chance to identify issue.

Good luck.

Osamu

[Osamu Aoki]

Hi,

When I was doing something else, I accidentally see funny things in
/usr/lib/systemd/user, we now have 2 files:

* org.freedesktop.IBus.session.generic.service.in
* org.freedesktop.IBus.session.GNOME.service.in

This seems to come from new commits (salsa)
e6e270123 (Gunnar Hjalmarsson 2022-03-14 09:25:47 +0100 1)
in the source tree ibus/bus/services

I am wondering if we set
> $IBUS_DAEMON_ARGS
correctly before calling ?

In the source tree there, I see:
> org.freedesktop.IBus.service.in
> org.freedesktop.IBus.session.generic.service.in
> org.freedesktop.IBus.session.GNOME.service.in
>
The first one was used before. Now we don't seem to install the first one but
install other 2 files.

Any though?

[Gunnar Hjalmarsson]

On 2022-08-11 05:22, Osamu Aoki wrote:
> In the source tree there, I see:
>> org.freedesktop.IBus.service.in
>> org.freedesktop.IBus.session.generic.service.in
>> org.freedesktop.IBus.session.GNOME.service.in
>
> The first one was used before. Now we don't seem to install the
> first one but install other 2 files.

The first one is installed as

/usr/share/dbus-1/services/org.freedesktop.IBus.service

$ cat /usr/share/dbus-1/services/org.freedesktop.IBus.service
[D-BUS Service]
Name=org.freedesktop.IBus
Exec=/usr/bin/ibus-daemon --replace --panel disable --xim

--
Gunnar

[Osamu Aoki]

Hi,

Oh, wring file names in my original post and ... My original concern for installed
systemd configuration files are there. One for GNOME, one for others. And others
seems to relyon some variable substitution. Is it working correctly?

/usr/lib/systemd/user/ has followings:

> org.freedesktop.IBus.session.generic.service
> org.freedesktop.IBus.session.GNOME.service
>

Osamu

[Gunnar Hjalmarsson]

Hi again, Osamu!

On 2022-08-11 14:03, Osamu Aoki wrote:
> Oh, wring file names in my original post and ... My original concern
> for installed systemd configuration files are there. One for GNOME,
> one for others. And others seems to relyon some variable
> substitution. Is it working correctly?
>
> /usr/lib/systemd/user/ has followings:
>
>> org.freedesktop.IBus.session.generic.service
>> org.freedesktop.IBus.session.GNOME.service

At last I understand what you are concerned about.

Hmm.. While the GNOME one is used in GNOME sessions, it looks to me as
if the generic one is not used at all.

$ systemctl --user list-unit-files | grep IBus
org.freedesktop.IBus.session.generic.service static -
org.freedesktop.IBus.session.GNOME.service enabled enabled

If I put "none" in the ~/.xinputrc file on my Xubuntu installation, no
ibus-daemon process is started at login.

And if the generic service file isn't used, there shouldn't be a
conflict with im-config.

It would of course be good to know the intention with the
org.freedesktop.IBus.session.generic.service file.

--
Gunnar

[Yukiharu YABUKI]

Hi,

I have realized that this issue happended in GDM3 environment.
In LightDM environment, this issue does not happend.


--
Yukiharu YABUKI <yya...@debian.org>

[Gunnar Hjalmarsson]

On 2022-08-28 07:21, Yukiharu YABUKI wrote:
> I have realized that this issue happended in GDM3 environment.
> In LightDM environment, this issue does not happend.

Hmm.. So you have GDM3 installed, which depends on the core GNOME
packages including gnome-session-common. Maybe that GNOME user service
systemd file has something to do with it, after all.

Can we do an experiment?

1. Change your ~/.xinput file to "none" using this command:

im-config -n none

2. Change your default display manager to GDM3.

3. Reboot and log in.

4. Find out if ibus-daemon is still running:

ps aux | grep ibus

--
Gunnar

[Osamu Aoki]

Hi,

One think I noticed long time ago for GDM3 is it doesn't seem to use input method.

Now GNOME set up ibus infrastructure, it may be killing and cleaning input method to
provide clean start for GNOME. I didn't check but it may be worth checking
situation. Maybe this is something we can only deal as documenting limitation and
side effects for GDM3. Just a thought...

[Osamu Aoki]

Hi Yabuki-san,


Please check if new im-config 0.53-1 solves your issue.


We included patch proposed at:

https://salsa.debian.org/input-method-team/im-config/-/merge_requests/16

TBH, I am not even sure this is the right solution to your problem or any
others.

I have no idea how X session startup code are used by different DMs and I don't
have enough resource (or time) to investigate this in depth. (GDM3 vs. LightDM)

At least, this looks like a harmless patch which might solve double start of
ibus.

Regards,

Osamu

[Gunnar Hjalmarsson]

Control: affects -1 i3

For the record I installed gdm3 (and a lot of dependencies) on my
Xubuntu test installation, and accomplished these steps:

On 2022-09-11 01:44, Gunnar Hjalmarsson wrote:
> 1. Change your ~/.xinput file to "none" using this command:
>
>   im-config -n none
>
> 2. Change your default display manager to GDM3.
>
> 3. Reboot and log in.
>
> 4. Find out if ibus-daemon is still running:
>
>   ps aux | grep ibus

Found that ibus-daemon was not started. Tested with logging in to both a
Xubuntu and a Cinnamon session.

Actually I tried to use i3 too, but the barrier to set it up proved to
be high, and I'm not willing to spend the time needed for that.

So even if GDM is used as login manager, it's unlikely that the presence
of the systemd service files interferes with the IBus setup for
non-GNOME sessions.

It's possible that there is some issue with how i3 interacts with ibus
or im-config or both, and I'd say that the i3 maintainers should better
get involved if the intention is that input methods can be conveniently
configured also with i3. Marked this bug as affecting i3.

--
Rgds,
Gunnar