search

Riey / kime

Korean IME
GNU General Public License v3.0
510 stars 53 forks source link

kime-indicator does not autostart in Gnome Wayland #645

Open butterdori opened 12 months ago

butterdori commented 12 months ago

Arch Linux kernel 6.5.5 with Gnome DE

Relevant journactl entry

Oct 02 14:45:39 rbs-arch systemd[1532]: app-gnome-kime\x2dindicator-2073.scope: Couldn't move process 2073 to requested cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-kime\x2dindicator-2073.scope': No such process Oct 02 14:45:39 rbs-arch systemd[1532]: app-gnome-kime\x2dindicator-2073.scope: Failed to add PIDs to scope's control group: No such process Oct 02 14:45:39 rbs-arch systemd[1532]: app-gnome-kime\x2dindicator-2073.scope: Failed with result 'resources'. Oct 02 20:58:06 rbs-arch kime-indicator.desktop[2175]: [ INFO] Receive exit message Oct 03 08:13:35 rbs-arch kime-indicator.desktop[2744]: [ INFO] Receive exit message Oct 03 15:29:46 rbs-arch kime-indicator.desktop[2072]: [ INFO] Receive exit message Oct 03 15:29:46 rbs-arch systemd[1530]: app-gnome-kime\x2dindicator-2072.scope: Couldn't move process 2072 to requested cgroup '/user.slice/user-1000.slice/user@1000.service/app.slice/app-gnome-kime\x2dindicator-2072.scope': No such process Oct 03 15:29:46 rbs-arch systemd[1530]: app-gnome-kime\x2dindicator-2072.scope: Failed to add PIDs to scope's control group: No such process Oct 03 15:29:46 rbs-arch systemd[1530]: app-gnome-kime\x2dindicator-2072.scope: Failed with result 'resources'. Oct 04 10:12:40 rbs-arch kime-indicator.desktop[2064]: thread '' panicked at 'called Result::unwrap() on an Err value: D-Bus error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (org.freedesktop.DBus.Error.NoReply)', /home/dk/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ksni-0.2.0/src/service.rs:84:37 Oct 04 10:12:40 rbs-arch kime-indicator.desktop[2064]: note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

Oct 05 15:23:46 rbs-arch kime-indicator.desktop[2135]: thread '' panicked at 'called Result::unwrap() on an Err value: D-Bus error: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. (org.freedesktop.DBus.Error.NoReply)', /home/dk/.cargo/registry/src/index.crates.io-6f17d22bba15001f/ksni-0.2.0/src/service.rs:84:37 Oct 05 15:23:46 rbs-arch kime-indicator.desktop[2135]: note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

https://github.com/Riey/kime/issues/471 Seems to be similar to this issue. However, the suggested X-DBUS-StartupType=Unique nor X-DBUS-StartupType=wait deos not work.

However, when manually started through the command line using kime-indicator, the indicator appears normally.

butterdori commented 12 months ago

Same as https://github.com/Riey/kime/issues/576 Resolved based on this https://github.com/Riey/kime/pull/629 I manually changed the kime.desktop file referring to the commit here https://github.com/Riey/kime/pull/629/files#diff-1519a1cbfed7ae378e0d7459d2bc0509e645165e2e28515e07535bc7de101233

Latest kime version on Arch AUR is January 2023. I guess this commit was not reflected there.

I had this issue for 2+ years. Finally resolved it.

Riey commented 12 months ago

Have you tested with kime-git package?

butterdori commented 11 months ago

Have you tested with kime-git package?

No I haven't. I will try. Thank you.