-
Notifications
You must be signed in to change notification settings - Fork 14
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Syncthing Icon does not work with Ubuntu snap version of syncthing #35
Comments
Not sure, since I have zero experience with snaps, so far. What exactly does "does not work .. anymore" mean? Are there any errors? What is the output of Furthermore, I am not sure whether |
Thanks for your quick response!
It is weird that it cannot connect since I can connect without problems using firefox.. |
By TLS do you mean using the GUI over https? I have this disabled and connect without https. Does the extension rely on the config directory? If so, I would have to change the path somehow, because with the snap the config dir is in /home/trevor/snap/syncthing/common/syncthing |
Yes, I meant https. So this is not the problem, ok.
Yes, the config path To change the Web Interface URI, start |
Unfortunately entering the URL manually doesn't fix it (it was the same URL anyway). I also created a softlink from ~/.config/syncthing/ to ~/snap/syncthing/common/syncthing but that didn't help either. |
When you enter the URI manually, you also have to copy the API key from your config file to the corresponding field in the Syncthing Icon configuration box. I forgot to mention that, sorry. |
OK we're definitely getting closer! Now I can at least see the shared folders in the dropdown menu. But still it doesn't show that syncthing is running, even though it is and I cannot connect to the web interface from the extensions dropdown menu. These are the remaining errors:
|
The Syncthing Icon extension starts and stops Syncthing via systemd as a systemd user service. The above logging messages just say that there is no such systemd user service. How do you start and stop Syncthing via snap? |
I startup syncthing on system startup using the command:
|
Generally, you should start syncthing via the systemd user session as stated in the Requirements section of the README.md. Then the On/Off button should work and you should be able to connect to the web interface. Having said that, I guess it should be possible to rewrite the extension such that it also supports other technologies like flatpak and snap. I will look into it. |
There is an open issue in the syncthing bug tracker on how to manage a syncthing snap user service. |
Hi! I just got the extension to work using snap + system.d. I created a file called ~/.config/systemd/user/syncthing.service with the following contents:
and then used the commands:
in case that does not work straight away try Also make sure that no other instance of syncthing is running, else you got weird errors. To debug use: Hope this helps anybody! |
Hi, I've modified my file a little bit because I didn't understand some of the lines in yours. Mine looks like this (notice that path to syncthing folder doeasn't start with
I've also found a useful command to check service status:
|
Happy to hear that it helped! :] Thanks for sharing! I didn't understand all lines either, I just took the official user systemd file from the syncthing project on github and modified it a bit. |
The latest commit should now support reading the config file from However to start the syncthing snap package you still need to manually install the user unit as explained above. |
@lalop Perhaps a different issue. I updated the issue template. Could you file a new bug report for that? |
Hi!
Thanks for your useful extension, I used it quite a lot so far!
Now I switched to the snap version of syncthing on ubuntu since it is always updated to the current released version and I noticed that it does not work with Syncthing Icon anymore.. What would have to be done to adapt the current version of the extension to the snap version? Would it be sufficient to just change the paths for the config folder and the binary?
Greetings
Trevor
The text was updated successfully, but these errors were encountered: