Update decky-syncthing to 0.2.1

[theCapypara]

decky-syncthing (Syncthing)

Update to 0.2.0

This adds the following to the plugin:

• Services are now started, stopped & enabled via Systemd (user mode)
• Existing Systemd user services can be configured instead of using a Flatpak
• On the initial setup the user is guided through via a setup assistant
• The setup assistant auto-detects settings such as port, api key and whether basic auth credentials are required or not
• Clicking on devices or folders now shows the same details as in the Syncthing web UI.
• Fixes minor settings issues.

Update to 0.2.1

• Removes the compatibility for Syncthingy, since it doesn't work reliably (see comments in this PR)

Checklist:

Developer Checklist

• [x] I am the original author or an authorized maintainer of this plugin.
• [x] I have abided by the licenses of the libraries I am utilizing, including attaching license notices where appropriate.

Plugin Checklist

• [x] I have verified that my plugin works properly on the Stable and Beta update channels of SteamOS.
• [x] I have verified my plugin is unique or alternatively provides more/alternative functionality to a similar plugin already on the store.

Plugin Backend Checklist

• Yes: I am using a custom backend other than Python.
• Yes: I am using a tool or software from a 3rd party FOSS project that does not have it's dependencies statically linked.
• No: I am using a custom binary that has all of it's dependencies statically linked.

Testing

• [ ] Tested on SteamOS Preview Update Channel.

[TrainDoctor]

@SteamDeckHomebrew/decky-testers need a few testers for this when you get the chance.

[outerwinnie]

It's definily not working on Stable using "com.github.zocker_160.SyncThingy"

[theCapypara]

@OuterWinnie The service is installed as a user service. Can you repeat the command with --user and post the output?

In an upcoming patch I'll probably add the journal output to that error message...

Plus can you check "systemctl --user status decky-syncthing"?

[outerwinnie]

@OuterWinnie The service is installed as a user service. Can you repeat the command with --user and post the output?

In an upcoming patch I'll probably add the journal output to that error message...

Plus can you check "systemctl --user status decky-syncthing"?

With --user:

Systemctl log:

And just in case, it's this version right?:

[theCapypara]

Odd, it's trying to use the wrong Flatpak, I probably have a typo somewhere. I'll fix this soon and let you know once it's done.

[theCapypara]

@OuterWinnie Actually I just noticed something odd: Your journal you shared is 2 days old, yet the status shows new entries from today. Can you check the journal again for today?

[outerwinnie]

@OuterWinnie Actually I just noticed something odd: Your journal you shared is 2 days old, yet the status shows new entries from today. Can you check the journal again for today?

Oh, sorry. Here it is:

[theCapypara]

Hm interesting, there's just nothing logged... I'll try to reproducr this somehow. I only did minimal testing with that Flatpak.

[theCapypara]

I experimented a bit. I think the problem happens when switching to Game Mode when Syncthingy is still running. You need to stop it first I guess. It also seems to stop a few minutes after switching to Game Mode. I consider this a bug in the interaction between Flatpak/Syncthingy/Gamescope. I'll probably think about how to better handle this in a future update and recommend using Syncthing GTK for now.

In general if you enable Decky Syncthing you should not actually run the Syncthingy Flatpak in Desktop mode or set it to autostart. The plugin will manage Syncthing for you. Unless you configure the plugin to stop it's Syncthing integration in desktop mode, then you could run Syncthingy in Desktop mode.

But tldr: Just install the Flatpak, start it once, stop it and never actually start it again and disable its autostart. Just use the plugin and configure it to keep it running in desktop mode. Then you can still access the Syncthing web UI in Desktop Mode.

[outerwinnie]

I experimented a bit. I think the problem happens when switching to Game Mode when Syncthingy is still running. You need to stop it first I guess. It also seems to stop a few minutes after switching to Game Mode. I consider this a bug in the interaction between Flatpak/Syncthingy/Gamescope. I'll probably think about how to better handle this in a future update and recommend using Syncthing GTK for now.

In general if you enable Decky Syncthing you should not actually run the Syncthingy Flatpak in Desktop mode or set it to autostart. The plugin will manage Syncthing for you. Unless you configure the plugin to stop it's Syncthing integration in desktop mode, then you could run Syncthingy in Desktop mode.

But tldr: Just install the Flatpak, start it once, stop it and never actually start it again and disable its autostart. Just use the plugin and configure it to keep it running in desktop mode. Then you can still access the Syncthing web UI in Desktop Mode.

For what is worth, i have disable Syncthingy autostart and it's still not working (i have check it and it's definitely not auto-starting), do i need to uninstall and reinstall for it to work?

Either way, i think it would be better to remove Syncthingy from the plugin and re-added later when is more stable.

[theCapypara]

I removed the option and and added that commit to the PR. I also added a warning about "Syncthingy" to the custom Flatpak option.

[theCapypara]

@TrainDoctor To summarize findings for your issue from Discord:

Dbus communication with Systemd is not possible.

• This is either because the Dbus socket is set to a different non-standard path for you and DBUS_SESSION_BUS_ADDRESS is not set (defaults to "unix:path=/run/user/<userid>/bus)
• The variable is set but the path in it is wrong.
• Some kernel namespacing / cgroup issues (very unlikely)

I am unable to reproduce this on Preview or stable. Can anybody else reproduce this issue?

[theSt33v]

0.2.1 works perfectly for me on Decky Stable using the syncthing-gtk flatpak. I think it's ready for prime time.