Can't restart Processing 4 because of read/write permissions for the modes folder

[processing-bot]

Created by: SmantikVJ

Hi!
I have an issue with Processing

Description
I have installed Processing 4.0.1. When I close the program and restart again, it shows me this error message:

I have changed permission for /Documents/Processing/modes folder, allowing to everybody to write and read, but it doesn't work.

After trying different things, I have found a way to make it work:

1. Uninstall Processing.
2. Delete /Documents/Processing folder.
3. Install Processing.
4. Run Processing - it says to me that there is no /Documents/Processing folder, so it's going to create it.
5. While running Processing, I go and change permission allowing to everybody write and read to /Documents/Processing folder. I do the same with every folder that is contained in it.
6. Now, I can close Processing and restarting with no problem.

I have opened this issue as @SableRaf told me. I think that it's a good idea because, if you fix it, some users will not have this problem.

My Environment

• Processing version: 4.0.1
• Operating System and OS version: macOS Big Sur

Possible Solution
Can't you modify /Processing folder permission when Processing creates them?

Thanks.

[processing-bot]

Created by: SmantikVJ

The method that I described above is not working today. The window of the image attached appears again and Processing doesn't start.
It's frustrating.

[processing-bot]

Created by: benfry

How did you install Processing? Is it installed as a different user, or have you changed the permissions in any way?

In a Terminal, can you enter:

cd ~/Documents
ls -l | grep Processing

and paste the result here?

Also, this one:

cd ~/Documents/Processing
ls -l

It shouldn't really be possible for you to run an app that creates folders that you don't have permissions to, because when you run Processing, it has the same permissions as you do. So we need to figure out what's happening with that.

And this is on a personal machine, right? Just one OS or are there multiple partitions?

[processing-bot]

Created by: SmantikVJ

Hi, @benfry.
I installed Processing as administrator. I work with my laptop as administrator everytime, so I run Processing as such.
After I installed it, I changed permission for /Documents/Processing folder, allowing to everybody to write and read. I did the same for every subfolder that it contains.

Terminal results for first command:

Terminal results for second command:

In this personal machine are two partitions: the first one contains High Sierra macOS 10.13.6 (I use it for 32 bits applications). Later, I installed Big Sur macOS (now is 11.5.2 version) for some applications that require a higher OS, and it is used generally.

Thanks.

[processing-bot]

Created by: SmantikVJ

Hi.
I think I have found the solution.
I have gone to Security & privacy, I have entered user administrator username / Password to unlock the editing screen and inside Privacy tab I have selected "Documents & folders" and let Processing to access (tick was deactivated before). I did the same selecting "Total access to disk".
Now, the window "We're on the wrong foot" does not appear (I didn't have to reinstall Processing).

Thanks, @benfry . With your comment you gave me a clue.

[processing-bot]

Created by: benfry

You shouldn't have to enable full disk access to use Processing. However, it sounds like an “allow Processing to access your Documents folder?” prompt was shown earlier and you didn't allow access, which later locked you out. Is that possible?

[processing-bot]

Created by: SmantikVJ

Allowing only Documents folder is enough. I tried.
Thanks again.

[processing-bot]

Created by: benfry

Confirmed that this is what happens when you click “Don't Allow” here:

[processing-bot]

Created by: benfry

Added additional warning detail about how to reset permissions for 4.0.2.

[processing-bot]

Created by: github-actions[bot]

This issue has been automatically locked. To avoid confusion with reports that have already been resolved, closed issues are automatically locked 30 days after the last comment. Please open a new issue for related bugs.