Make sure KDE Connect properly errors when it can't connect to the daemon

[ghost]

This would make i3status-rs crash for me, now it at least gives an error. Although maybe it would be better to wait until it can connect to the daemon? idk

[ammgws]

So I take it your kdeconnect daemon is started after the bar?

[ghost]

It seems like it :|

[ammgws]

OK, thanks!

Although maybe it would be better to wait until it can connect to the daemon?

It would be nice but would need to come up with a good way to do that. Other blocks using DBus etc also fail the same way.

[marzzzello]

How do you autostart kdeconnectd?
On every boot I get the error that kdeconnectd is not available (yet). So I manually restart i3 and then it works fine.
i3 and the status bar are just faster than kdeconnectd. Waiting for kdeconnectd to be ready would be a nice solution.

[ammgws]

I use a systemd user service (placed in /home/username/.config/systemd/user/kdeconnectd.service):

[Unit]
Description=Connect your computer to your smartphone or tablet

[Service]
ExecStart=/usr/lib/kdeconnectd
ExecStop=/usr/bin/kquitapp5 kdeconnectd
BusName=org.kde.kdeconnect
Environment=QT_QPA_PLATFORM=offscreen

[Install]
WantedBy=default.target

Waiting for it to come up might also be good, if not at least for the IBus block which suffers from the same issue.

[marzzzello]

Thanks, it works fine now 👍. I also tried a user service but without BusName or Environment.