Skip to content
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

Can't restart syncthing from the tray - Only works when "Apply and launch now" from Startup settings #236

Open
1 of 6 tasks
sleepmaster91 opened this issue Mar 7, 2024 · 1 comment

Comments

@sleepmaster91
Copy link

sleepmaster91 commented Mar 7, 2024

Relevant components

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

Environment and versions

  • Versions of syncthingtray, qtutilities and c++utilities: 1.5.0
  • Qt version: ….….…
  • C++ compiler (name and version): …
  • C++ standard library (name and version): …
  • Operating system (name and version): …

Bug description
A clear and concise description of what the bug is.
When restarting Syncthing from the tray Syncthing won't restart causing SyncThingTray to not reconnect

Steps to reproduce

  1. Click on tray icon
  2. Click on "restart syncthing" icon

Expected behavior
A clear and concise description of what you expected to happen.
Syncthing restarting and reconnecting

Screenshots
If applicable, add screenshots to help explain your problem.

image

Additional context
Add any other context about the problem here.

@Martchus
Copy link
Owner

Martchus commented Mar 7, 2024

It works for me. Did you configure the re-connect interval accordingly? Note that the default re-connect interval is 30 seconds so you might be to impatient (or want to tweak the interval). It may run into "Connection refused" if Syncthing doesn't come up quick enough. When using the internal launcher¹ or Systemd-integration the error can be suppressed in this case by setting a grace period in the notification settings. Otherwise you cannot avoid the error except by disabling those errors completely.

¹ Maybe restarting Syncthing via the API - as the "Restart Syncthing" action does - does not count as restart when using the internal launcher because Syncthing's monitoring process is actually nevertheless constantly running. Then the "Connection refused" error also cannot be suppressed.


Maybe I should tweak default settings to disable showing notifications for this kind of error by default (as it cannot be suppressed reliably in all cases).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants