syncthing / syncthing/syncthing-macos
v2.0.15: Model initialization blocks indefinitely when launched via launchd (macOS LaunchAgent)
Nobody has claimed this yet.
- Dominant language
- Objective-C
- Stars
- 3.9k
- Forks
- 203
- Avg merge
- 3d 14h
- Merged PRs (30d)
- 2
Description
Bug description
Syncthing v2.0.15 ("Hafnium Hornet") fails to initialize the folder model when launched
via a macOS LaunchAgent (launchd). The Ready to synchronize log entry is never emitted,
and all model-dependent API endpoints (/rest/db/status) block indefinitely.
The same binary initializes in <1 second when launched from a terminal (pty context).
Reproduction
- Any LaunchAgent plist (
RunAtLoad: true) pointing to the syncthing binary brew install syncthing && brew services start syncthing
Both block forever.
Works fine:
nohup /Applications/Syncthing.app/Contents/Resources/syncthing/syncthing \
--no-browser --no-restart &
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reproducing the initialization hang with a macOS LaunchAgent and compare it with the working terminal and nohup launches. Check whether the Ready to synchronize log entry appears and whether /rest/db/status remains blocked; done means the model initializes and the API responds when started through launchd.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- macos
- Domain
- desktop, operating-systems
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 45/100