Groups > linux.debian.bugs.dist > #1111268 > unrolled thread

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

Started by	Gunnar Hjalmarsson <gunnarhj@debian.org>
First post	2022-07-28 23:00 +0200
Last post	2022-09-12 15:40 +0200
Articles	12 — 3 participants

Back to article view | Back to linux.debian.bugs.dist

This discussion starts older than the indexed window; earlier articles aren't shown. The article labeled Started by below is the oldest one visible, not the original post.

  Bug#1014052: ibus:After rebooted, I must do `ibus-daemon -rxd` change japanese to anthy with kanji key. Gunnar Hjalmarsson <gunnarhj@debian.org> - 2022-07-28 23:00 +0200
    Bug#1014052: ibus:After rebooted, I must do `ibus-daemon -rxd` change japanese to anthy with kanji key. Yukiharu YABUKI <yyabuki@debian.org> - 2022-07-29 17:40 +0200
      Bug#1014052: ibus:After rebooted, I must do `ibus-daemon -rxd` change japanese to anthy with kanji key. Gunnar Hjalmarsson <gunnarhj@debian.org> - 2022-07-29 17:50 +0200
      Bug#1014052: ibus:After rebooted, I must do `ibus-daemon -rxd` change japanese to anthy with kanji key. Osamu Aoki <osamu@debian.org> - 2022-07-29 18:40 +0200
        Bug#1014052: ibus:After rebooted, I must do `ibus-daemon -rxd` change japanese to anthy with kanji key. Yukiharu YABUKI <yyabuki@debian.org> - 2022-07-30 18:40 +0200
          Bug#1014052: ibus:After rebooted, I must do `ibus-daemon -rxd` change japanese to anthy with kanji key. Osamu Aoki <osamu@debian.org> - 2022-07-31 10:50 +0200
            Bug#1014052: ibus:After rebooted, I must do `ibus-daemon -rxd` change japanese to anthy with kanji key. Yukiharu YABUKI <yyabuki@debian.org> - 2022-07-31 19:20 +0200
              Bug#1014052: ibus:After rebooted, I must do `ibus-daemon -rxd` change japanese to anthy with kanji key. Osamu Aoki <osamu@debian.org> - 2022-08-02 14:10 +0200
            Bug#1014052: ibus:After rebooted, I must do `ibus-daemon -rxd` change japanese to anthy with kanji key. Gunnar Hjalmarsson <gunnarhj@debian.org> - 2022-08-01 14:50 +0200
        Bug#1014052: ibus:After rebooted, I must do `ibus-daemon -rxd` change japanese to anthy with kanji key. Yukiharu YABUKI <yyabuki@debian.org> - 2022-08-28 07:30 +0200
          Bug#1014052: ibus:After rebooted, I must do `ibus-daemon -rxd` change japanese to anthy with kanji key. Gunnar Hjalmarsson <gunnarhj@debian.org> - 2022-09-11 01:50 +0200
            Bug#1014052: ibus:After rebooted, I must do `ibus-daemon -rxd` change japanese to anthy with kanji key. Osamu Aoki <osamu@debian.org> - 2022-09-12 15:40 +0200

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

From	Gunnar Hjalmarsson <gunnarhj@debian.org>
Date	2022-07-28 23:00 +0200
Subject	Bug#1014052: ibus:After rebooted, I must do `ibus-daemon -rxd` change japanese to anthy with kanji key.
Message-ID	<EOiLT-esJC-1@gated-at.bofh.it>

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

[toc] | [next] | [standalone]

#1111341

From	Yukiharu YABUKI <yyabuki@debian.org>
Date	2022-07-29 17:40 +0200
Message-ID	<EOAfL-eDvt-21@gated-at.bofh.it>
In reply to	#1111268

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 <gunnarhj@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 <yyabuki@debian.org>

[toc] | [prev] | [next] | [standalone]

#1111342

From	Gunnar Hjalmarsson <gunnarhj@debian.org>
Date	2022-07-29 17:50 +0200
Message-ID	<EOApr-eDyy-1@gated-at.bofh.it>
In reply to	#1111341

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

[toc] | [prev] | [next] | [standalone]

#1111345

From	Osamu Aoki <osamu@debian.org>
Date	2022-07-29 18:40 +0200
Message-ID	<EOBbP-eE30-5@gated-at.bofh.it>
In reply to	#1111341

Hi,

> -----Original Message-----
> From: Yukiharu YABUKI <yyabuki@debian.org>
> To: Gunnar Hjalmarsson <gunnarhj@debian.org>
> Cc: Osamu Aoki <osamu@debian.org>, 1014052@bugs.debian.org
> Subject: Re: Bug#1014052: ibus:After rebooted, I must do `ibus-daemon -rxd` change
> japanese to anthy with kanji key.
> Date: Sat, 30 Jul 2022 00:30:02 +0900
> 
> 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 <gunnarhj@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 <yyabuki@debian.org>

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

> >

[toc] | [prev] | [next] | [standalone]

#1111483

From	Yukiharu YABUKI <yyabuki@debian.org>
Date	2022-07-30 18:40 +0200
Message-ID	<EOXFo-eRrL-29@gated-at.bofh.it>
In reply to	#1111345

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 <osamu@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 <yyabuki@debian.org>

[toc] | [prev] | [next] | [standalone]

#1111520

From	Osamu Aoki <osamu@debian.org>
Date	2022-07-31 10:50 +0200
Message-ID	<EPcO5-f0sI-1@gated-at.bofh.it>
In reply to	#1111483

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

[toc] | [prev] | [next] | [standalone]

#1111596

From	Yukiharu YABUKI <yyabuki@debian.org>
Date	2022-07-31 19:20 +0200
Message-ID	<EPkLD-f5lk-7@gated-at.bofh.it>
In reply to	#1111520

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 <yyabuki@debian.org>

[toc] | [prev] | [next] | [standalone]

#1111755

From	Osamu Aoki <osamu@debian.org>
Date	2022-08-02 14:10 +0200
Message-ID	<EPYSJ-fteI-3@gated-at.bofh.it>
In reply to	#1111596

Hi,

> -----Original Message-----
> From: Yukiharu YABUKI <yyabuki@debian.org>
> To: Osamu Aoki <osamu@debian.org>
> Cc: 1014052@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

[toc] | [prev] | [next] | [standalone]

#1111663

From	Gunnar Hjalmarsson <gunnarhj@debian.org>
Date	2022-08-01 14:50 +0200
Message-ID	<EPD1T-fg0U-5@gated-at.bofh.it>
In reply to	#1111520

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

[toc] | [prev] | [next] | [standalone]

#1114782

From	Yukiharu YABUKI <yyabuki@debian.org>
Date	2022-08-28 07:30 +0200
Message-ID	<EZj1T-3ACB-1@gated-at.bofh.it>
In reply to	#1111345

Hi,

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


--
Yukiharu YABUKI <yyabuki@debian.org>

[toc] | [prev] | [next] | [standalone]

#1116807

From	Gunnar Hjalmarsson <gunnarhj@debian.org>
Date	2022-09-11 01:50 +0200
Message-ID	<F4iox-6Ijw-1@gated-at.bofh.it>
In reply to	#1114782

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

[toc] | [prev] | [next] | [standalone]

#1116944

From	Osamu Aoki <osamu@debian.org>
Date	2022-09-12 15:40 +0200
Message-ID	<F4RPj-73D0-9@gated-at.bofh.it>
In reply to	#1116807

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...

On Sun, 2022-09-11 at 01:44 +0200, Gunnar Hjalmarsson wrote:
> 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
>

[toc] | [prev] | [standalone]

csiph-web

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

Contents

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

#1111341

#1111342

#1111345

#1111483

#1111520

#1111596

#1111755

#1111663

#1114782

#1116807

#1116944