We’re having some issues with Audacity in a school lab environment.
These are network accounts on El Capitan machines. Local accounts have no problems launching Audacity, but network accounts (which all the students are) receive a pop up saying that there was an error locking the temporary folder. No lock file is created in the temporary folder when this occurs, and the application quits when selecting “Yes” to launch the Audacity anyway.
We currently have it running without issues on the same machines in Mavericks on those network accounts, but El Cap/Sierra is a no go so far. Hopefully one of those elfs will have a good suggestion or two
It appears no-one in our support or developer community has experience with Mac network accounts.
You say the Mavericks machines work but the El Cap and Sierra machines don’t. Is there any way to check where the lock file is, and then check the permissions of the folder(s) it resides in, then change the El Cap/Sierra permissions to match the Mavericks permissions?
With a local account, and using Audacity 2.1.3 (you are, aren’t you?) the lock file is in ~/Library/Application Support/Audacity/Session Data and is called “audacity-lock-”.
I don’t know where this would be with a network account.
This looks like a permissions issue (sorry if I’m stating the obvious), so examining the differences in permissions in the two cases may help solve the problem.
Thanks Bill, I’ll check permissions once again. During testing I did see the lock file being created in the appropriate directory.
Hi Cyrano, I think that you just may be onto something. I tested Audacity with a new 5.3.1 server and the network accounts had no issues. It seems to be related to our main server which is running an older version.