Unable to edit .stignore file via web GUI
See original GitHub issueVersion: 0.7.17, ST v0.12.22, Linux (ARM)
I tried to edit .stignore file via web GUI (from my PC) but it fails with error:
2016-05-10 16:10:50: Saving .stignore: chmod /storage/emulated/0/.syncthing.tmp.798561500: operation not permitted
I can only click on OK button for this message and I have to restart ST service (because it say to do it to activate the new configuration). After the restart .stignore is the same as before the editing.
Issue Analytics
- State:
- Created 7 years ago
- Comments:12 (10 by maintainers)
Top Results From Across the Web
.stignore problem - Android - Syncthing Community Forum
Can you open the Web GUI on Android using the left slide-out menu, then go to “Edit Folder” there and see what the...
Read more >syncthing-faq man page - ManKier
The web GUI contains a Recent Changes button under the device list which displays changes since the last (re)start of Syncthing. With the...
Read more >Set Up Android File Synchronization with GNU/Linux Using ...
One reason to set up file sync is to be able to share text files between Android and Linux. To do this we...
Read more >Ignore file on Windows : r/Syncthing - Reddit
I placed a .stignore file in my root folder on Windows with the following ... know I could see and edit the folder...
Read more >syncthing-config(5) - Arch manual pages
It can be changed at runtime using the --config flag. In this directory the following files are located: config.xml: The configuration file, ...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Should be fixed in the next release.
Did you file an issue at golang?