Earlier versions of Syncthing worked as expected in Termux, upgrading to 2.0.15 failed with errors indicating goruntime errors. (Changelog for 2.0.15 includes build with Go 1.26; use Go 1.25 features by @calmh in #10570. Could this be related? I have not been able to revert the Termux version to 2.0.14, any advice would helpful. This has also been reported on the Termux bug tracker. Termux version is googleplay.2026.02.11
Impossible to say when you keep the actual error secret.
1 Like
I’m not trying to keep the error ‘secret’, I simply don’t know how to capture the output/log from Termux. I’ll investigate further. Screenshots might suffice. Any advice?
I can say that I’ve been running my own binaries of Syncthing 2.0.15 compiled with Go 1.25 in Termux with no issues, so I’d also suspect Go 1.26 to be the culprit here (unless there’s simply some other breakage in the Syncthing build provided by Termux).
That error means Syncthing got back an empty path when looking up the path to itself, which shouldn’t happen. It could certainly be a Go 1.26 regression, but it’s not one of the ones we’ve seen so far.
You can probably work around it by running it as STMONITORED=1 syncthing, effectively lying to it that it’s being run under our monitoring process so it doesn’t do the extra execution. You’ll lose the ability to restart from the GUI etc.
OK, that works. I’m up and running again. Thanks @calmh .
The workaround suggested by @calmh for syncthing version 2.0.15 is not needed if the termux version is installed from f-droid (version 0.119.0-beta.3).