You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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.
The text was updated successfully, but these errors were encountered:
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 anErr
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:37Oct 04 10:12:40 rbs-arch kime-indicator.desktop[2064]: note: run with
RUST_BACKTRACE=1
environment variable to display a backtraceOct 05 15:23:46 rbs-arch kime-indicator.desktop[2135]: thread '' panicked at 'called
Result::unwrap()
on anErr
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:37Oct 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.
The text was updated successfully, but these errors were encountered: