Linux Mint and Updater issue about syncthing-gtk

[kozec]

On another note, Syncthing-GTK somehow doesn't seem to update the syncthing binary. My openSUSE system was still at 0.10.9 - manually updated meanwhile - while Windows had already happily updated to 0.10.11. Any chance something went wrong with the "Updated URL for Syncthing updater" change in v0.5.2?

Yes, either that or internal version that updater is using is wrong. Can you please try to run
grep INTERNAL /usr/lib/python2.7/site-packages/syncthing_gtk/app.py
and post result here?

It reads "v0.5.2", but you misunderstood me...

Syncthing-GTK doesn't seem to update the SYNCTHING BINARY (~/bin/syncthing).
Updates of Syncthing-GTK you publish to your OBS repo are offered for update anyway.

The issue was that syncthing (the daemon binary) was at 0.10.9 while there's already 0.10.11 out ... and Syncthing-GTK didn't update. Saw no error/warn/debug message in any log that would give a clue about why it wouldn't pickup the newer syncthing binary release.

EDIT: On Windows it works fine ... both of my Windows boxes are updated to syncthing 0.10.11 (again, the EXE, not Syncthing-GTK). Also, the binary update worked with Syncthing-GTK 0.5.1 (on Linux).

[kozec]

It reads "v0.5.2", but you misunderstood me...

I undetstood what do you mean, this INTERNAL_VERSION is used when Syncthing daemon binary is updated. It helps to prevent ST-GTK to download too new, incompatible daemon version. If that's the case, message like Note: Not using latest, unsupported Syncthing version v0.10.11 ; Using v0.10.8 instead is printed to stdout durring update.

Now, with INTERNAL_VERSION = v0.5.2 that shouldn't be a problem.

Two other things may prevent upgrading: If Syncthing daemon is not launched by Syncthing-GTK, but, for example, by rc.script, manually, or just left running by prior ST-GTK instance. And update checking happens only once per day normally, so if last one happened just before v0.10.11 was released, it may take a while until it's downloaded.
In any case, you can force update check by opening UI Settings dialog and closing it with Save button. If there is any problem preventing update, it will be printed to stdout.

[kozec]

Can you, please, confirm if this is still problem with release 0.5.3?

Gave it a quick test with openSUSE (Andrew needs to make the DEB for Mint/Ubuntu first;)) ...

• Exited Synthing-GTK.
• mv ~/.config/autostart ~/.config/nostart
• Installed the new openSUSE release
• Started Syncthing GTK
• Went into the Preferences
• Unchecked/Checked the Autostart option
• Directory + .desktop file got created perfectly

Yet another problem solved (never dared to imagine that a Linux distro would ship without ~/.config/autostart already existing - I love that "edge case" scenarios that reveal bugs one never thought about).

[kozec]

And how about updater bug?

Exited and replaced ~/bin/syncthing with 0.10.9 from my last week's /home backup.

Fired it back up and it does what I expected it to do ... it found the newer 0.10.11 release, downloaded the file, and issued the "will restart in 60 seconds" notification.

While you said it checks once a day I somehow always had the impression it also checks at starting up - maybe I was just lucky that it always updated right after booting up the computer and logging in.

[kozec]

Well, it check on startup, but only if at least one day passed since last check.

Anyway, thanks for reporting :)