Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

kime-indicator does not autostart in Gnome Wayland #645

Open
butterdori opened this issue Oct 6, 2023 · 3 comments
Open

kime-indicator does not autostart in Gnome Wayland #645

butterdori opened this issue Oct 6, 2023 · 3 comments
Labels

Comments

@butterdori
Copy link

butterdori commented Oct 6, 2023

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/[email protected]/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/[email protected]/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

#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
Copy link
Author

Same as #576
Resolved based on this #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
Copy link
Owner

Riey commented Oct 8, 2023

Have you tested with kime-git package?

@butterdori
Copy link
Author

Have you tested with kime-git package?

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

@Riey Riey added the question label Oct 18, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants