Bug#1014052: ibus:After rebooted, I must do `ibus-daemon -rxd` change japanese to anthy with kanji key.
- To: Yukiharu YABUKI <yyabuki@debian.org>
- Cc: 1014052@bugs.debian.org
- Subject: Bug#1014052: ibus:After rebooted, I must do `ibus-daemon -rxd` change japanese to anthy with kanji key.
- From: Osamu Aoki <osamu@debian.org>
- Date: Tue, 02 Aug 2022 21:01:49 +0900
- Message-id: <[🔎] ff4f3bd3aca04f9187968fb461efb6b5adc49e5d.camel@debian.org>
- Reply-to: Osamu Aoki <osamu@debian.org>, 1014052@bugs.debian.org
- In-reply-to: <20220801021411.b778b1521139b6cfe190de6e@debian.org>
- References: <165651013389.850048.18337183351502384711.reportbug@Orlanth> <ed92f86c-7c66-e3ef-5991-31aa6082eb4e@debian.org> <165651013389.850048.18337183351502384711.reportbug@Orlanth> <20220707155554.51292f0f711cf6c6d0b43914@debian.org> <0ad44975-68b1-b71a-bf77-a5d1db0c4434@debian.org> <20220708100602.7a70a8bac5cd45b5b64bede0@debian.org> <9e137ce6-6e77-db1e-ac22-55feef806d47@debian.org> <20220730003002.5428caa85b2bb7c32811049f@debian.org> <9af242ea3f62038b143416a94522d6c73f1c090e.camel@debian.org> <20220731013758.ed834258194a95e4600cdcbd@debian.org> <15ae94bb1ecb607dc549dcf39d0bcd2e7d0e5284.camel@debian.org> <20220801021411.b778b1521139b6cfe190de6e@debian.org> <165651013389.850048.18337183351502384711.reportbug@Orlanth>
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
Reply to: