Hi have the same issue like:
Hello,
I work on Linux an wanted to use the following ignore list:
!.local/share/rhythmbox/
.*
In general all hidden files and folders of my whole home folder shall be ignored, but not the sub folder .local/share/rhythmbox.
But I get the error message:
error while traversing /home/dirk/.gvfs: permission denied.
If I remove the line !.local/share/rhythmbox/ the error is gone, but then I miss this folder.
My ignore list:
.*
.**
.gvfs
But I-m getting the message:
error while traversing /home/USER/.gvfs: permission denied
I’m using the standard installation of ubuntu 20.4:
syncthing/focal,now 1.1.4~ds1-4ubuntu1 amd64 [installiert]
What’s should I do to get rid of the error message?
Regards
You need to know which user Syncthing is running as, and then make sure that that user have the permissions necessary to read and write the files and directories you expect it to read and write.
speedy-10
(M. Sprau)
July 10, 2021, 10:18am
3
Since it is in the ignore list that should not matter IMHO.
calmh
(Jakob Borg)
July 10, 2021, 11:50am
5
I don’t think that should apply when there are no negative patterns? We should avoid scanning an explicitly mentioned directory as far as I know…
speedy-10
(M. Sprau)
July 10, 2021, 11:57am
6
So, I had to use:
~$ sudo chmod -R 744 .gvfs/
to avoid that error message.
speedy-10:
.*
.**
.gvfs
Not exactly related related to the error in question, but if these are all the patterns actually used, then the first one already covers the other two, i.e. .*
is enough.
@tomasz86 : Thanks, I assumed that, but wanted to be sure not to forget something. I remove the last two lines.
Sorry, you are right.
I somehow interpreted the dots on the first two lines as !
1 Like
speedy-10
(M. Sprau)
July 10, 2021, 1:22pm
10
Now I updated to 1.18 via: https://apt.syncthing.net/
Then I reset the rights: sudo chmod -R 700 .gvfs/
and scanned again syncthing.
So far the mentioned error doesn’t appear again.
Thanks to all.
3 Likes
speedy-10
(M. Sprau)
July 11, 2021, 7:08am
11
Was necessary again: ~$ sudo chmod -R 744 .gvfs/
calmh
(Jakob Borg)
July 11, 2021, 8:01am
12
So for what it’s worth this doesn’t reproduce for me. I tried this in an existing folder:
mkdir foo
touch foo/bar
chmod 000 foo
echo foo > .stignore
and I’m not seeing any errors related to foo
.
system
(system)
Closed
August 10, 2021, 8:01am
13
This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.