-
Notifications
You must be signed in to change notification settings - Fork 116
"Full Disk Access" on a linux machine #86
Comments
You need to manually specify a backup location. Otherwise it looks for backups in the default directory, which is certainly not present on Ubuntu (without iTunes) and throws this error. |
that sounds really odd; definitely a bug as the code is supposed to detect if it's running on Mac and only emit that particular message if it is; certainly not supposed to happen on Linux. are you running it with the path to the backup directory suppplied? ie. I'll also try to take a look in the next day or two. |
I've found that by commenting out the contents of the exitBadMacPerms() method entirely in the pinfinder.go file of the source code, it then works perfectly on my Linux machine (Manjaro). However, instead of ~/backup, I needed to specify ~/backup/* in order to get it to work. |
Basically, the exitBadMacPerms() of my pinfinder.go file looks like this now and it works:
|
Thanks @sjoldzic43 that's useful; i'll fix it properly for the next release |
Cool! Sounds great.
I can also do further tests to see if there is a more elegant solution and post here what I find but for now, bypassing the method entirely by commenting it out works.
Regards,
-Stephan Joldzic
…Sent from my iPhone
On Nov 11, 2019, at 9:43 PM, Gareth Watts ***@***.***> wrote:
Thanks @sjoldzic43 that's useful; i'll fix it properly for the next release
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.
|
Im having the same problem in ubuntu 18.04 |
I'm trying to run pinfinder on my ubuntu 19.04 machine and when I run the binary, its telling me I need "Full Disk Access" and I don't know how to satisfy it. I've tried running it with sudo, from root, and putting the backup folder into the pinfinder folder. I've also tried running previous versions of pinfinder that didn't use this feature and it tells me my backup folder is invalid. I don't know what to do. Help!
The text was updated successfully, but these errors were encountered: