Syncthingtray running on KDE Plasma does not automatically connect to a running systemd service as in the past

[iyanmv]

Relevant components

• Standalone tray application (based on Qt Widgets)
• Plasmoid/applet for Plasma desktop
• Dolphin integration
• Command line tool (syncthingctl)
• Integrated Syncthing instance (libsyncthing)
• Android app or mobile UI in general
• Backend libraries

Environment and versions

• Versions of syncthingtray, qtutilities and c++utilities: 1.7.3-1, 6.14.6-1, 5.27.3-1
• Qt version: 6.9.0 RC1
• C++ compiler (name and version): GCC 14.2.1 20250207
• C++ standard library (name and version): 14.2.1+r753+g1cd744a6828f-1
• Operating system (name and version): Arch Linux

Bug description
Since last update, I have to manually click on "Connect" button of the tray plasmoid for syncthintray to be aware of the systemd service running. Until I do that, the plasmoid is grayed out and show no information as if syncthing is not running.

I'm using Arch Linux systemd system service unit with my user, i.e., [email protected]

Steps to reproduce

1. Reboot computer
2. Click on syncthingtray icon and notice it is not connected
3. Click on "Connect" and it works just fine

Expected behavior
It should be aware that a systemd service is running already and connect automatically to it.

Screenshots

[Martchus]

This is the default behavior. How did you configure the launcher and systemd integration? And did you configure retries? If not it probably tried to connect just once but Syncthing wasn't ready. Are any errors logged by Syncthing Tray (shown as internal errors when right-clicking on the icon)?

[Martchus]

And since you mentioned that this is a regression: What was the last good version of Syncthing Tray? (I'm just wondering because 1.7.3 has been out for a few weeks.)

And does Syncthing Tray generally recognize the status of the unit in the systemd settings?

Note that I cannot reproduce this, at least not with a systemd user unit.

I also haven't tested against Qt 6.9 yet, at least not on GNU/Linux. So perhaps the update to 6.9 broke it.

[iyanmv]

Thanks for the quick reply!

This is the default behavior. How did you configure the launcher and systemd integration? And did you configure retries? If not it probably tried to connect just once but Syncthing wasn't ready. Are any errors logged by Syncthing Tray (shown as internal errors when right-clicking on the icon)?

In Extras -> Systemd -> Syncthing unit I have added my custom service: [email protected]

There are no errors in the logs.

And since you mentioned that this is a regression: What was the last good version of Syncthing Tray? (I'm just wondering because 1.7.3 has been out for a few weeks.)

I think 1.7.2 was working fine for me, or at least I never had to manually click on connect after booting. I think this started to happened, although not always, after the update to 1.7.3 which I installed on my system last March, 12. By "not always" I mean that sometimes the tray icon is not grayed out on boot, I cannot reproduce the issue 100% of the times.

And does Syncthing Tray generally recognize the status of the unit in the systemd settings?

Yes, it does.

I also haven't tested against Qt 6.9 yet, at least not on GNU/Linux. So perhaps the update to 6.9 broke it.

If it helps, I've been running with Qt 6.9 since the first Beta from [kde-unstable], and it used to work as well.

[Martchus]

Sounds all good so far. There's only one question you haven't answered yet:

And did you configure retries? If not it probably tried to connect just once but Syncthing wasn't ready.

Also see the 2nd last paragraph on https://github.com/Martchus/syncthingtray?tab=readme-ov-file#using-the-systemd-integration for more info on why retrying is required.