what is the correct ownership for files in /ApplicationsWhat and how does macOS Mojave implement to restrict applications access to personal data?What is the PersonalizationPortrait process for?What are the '~previous', '-previous' and '~orig' files in /private/etc/?When I try to enter a user password to delete an account, it doesn't work. and I know the password I'm using is correctWhat's > About This Mac > System Report > Software > Applications for?Spotlight search not including Applications in the result [MacOS Mojave]Finder Tags not working for any SMB filesNo previews for Desktop files on MojaveMinimizing the use of APFS in Mojave by putting Users and Applications on HFS+What are the required conditions for Photos to start a facial scan?
Pressing Battery Charges
Can I install a back bike rack without attachment to the rear part of the frame?
Do photons bend spacetime or not?
Did this character show any indication of wanting to rule before S8E6?
Public transport tickets in UK for two weeks
Why most published works in medical imaging try reducing false positives?
5-hour layover in Denver
Why did Jon Snow admit his fault in S08E06?
A married couple
The roles understanding in the agile development / Is the PO always right?
Make 24 using exactly three 3s
Is this statement about cut time correct?
How did NASA Langley end up with the first 737?
How can an ordered pair be a set assuming there is no order in a set?
Best material to absorb as much light as possible
Are black holes spherical during merger?
Why did Jon Snow do this immoral act if he is so honorable?
Where have Brexit voters gone?
Of strange atmospheres - the survivable but unbreathable
Python program to find Armstrong numbers in a certain range
How to zoom and pan very quick in Illustrator?
What does $!# mean in Shell scripting?
Dad jokes are fun
How to politely tell someone they did not hit "reply to all" in an email?
what is the correct ownership for files in /Applications
What and how does macOS Mojave implement to restrict applications access to personal data?What is the PersonalizationPortrait process for?What are the '~previous', '-previous' and '~orig' files in /private/etc/?When I try to enter a user password to delete an account, it doesn't work. and I know the password I'm using is correctWhat's > About This Mac > System Report > Software > Applications for?Spotlight search not including Applications in the result [MacOS Mojave]Finder Tags not working for any SMB filesNo previews for Desktop files on MojaveMinimizing the use of APFS in Mojave by putting Users and Applications on HFS+What are the required conditions for Photos to start a facial scan?
.everyoneloves__top-leaderboard:empty,.everyoneloves__mid-leaderboard:empty,.everyoneloves__bot-mid-leaderboard:empty margin-bottom:0;
It has been a while since last using Fritzing, and I was trying to open one of the files I saved almost 2 years ago.
The iMac was purchased early 2018, and everything copied from my MacBook
I have updated my iMac to the latest Mojave release, and got strange errors.

I looked at /Applications/Fritzing.app to see what I could change and found it was owned by my daughter (who has a login on my computer)
I used chown to change this, but a few other apps were also owned by her.
I seem to have a collection of root, ian (me) and bec (even one owned by my wife).
Neither of these would have installed any apps on my computer, so I don't know why.
My question is what is the correct ownership for files in /Applications
mojave
add a comment |
It has been a while since last using Fritzing, and I was trying to open one of the files I saved almost 2 years ago.
The iMac was purchased early 2018, and everything copied from my MacBook
I have updated my iMac to the latest Mojave release, and got strange errors.

I looked at /Applications/Fritzing.app to see what I could change and found it was owned by my daughter (who has a login on my computer)
I used chown to change this, but a few other apps were also owned by her.
I seem to have a collection of root, ian (me) and bec (even one owned by my wife).
Neither of these would have installed any apps on my computer, so I don't know why.
My question is what is the correct ownership for files in /Applications
mojave
add a comment |
It has been a while since last using Fritzing, and I was trying to open one of the files I saved almost 2 years ago.
The iMac was purchased early 2018, and everything copied from my MacBook
I have updated my iMac to the latest Mojave release, and got strange errors.

I looked at /Applications/Fritzing.app to see what I could change and found it was owned by my daughter (who has a login on my computer)
I used chown to change this, but a few other apps were also owned by her.
I seem to have a collection of root, ian (me) and bec (even one owned by my wife).
Neither of these would have installed any apps on my computer, so I don't know why.
My question is what is the correct ownership for files in /Applications
mojave
It has been a while since last using Fritzing, and I was trying to open one of the files I saved almost 2 years ago.
The iMac was purchased early 2018, and everything copied from my MacBook
I have updated my iMac to the latest Mojave release, and got strange errors.

I looked at /Applications/Fritzing.app to see what I could change and found it was owned by my daughter (who has a login on my computer)
I used chown to change this, but a few other apps were also owned by her.
I seem to have a collection of root, ian (me) and bec (even one owned by my wife).
Neither of these would have installed any apps on my computer, so I don't know why.
My question is what is the correct ownership for files in /Applications
mojave
mojave
asked 9 hours ago
MilliwaysMilliways
3,811143960
3,811143960
add a comment |
add a comment |
2 Answers
2
active
oldest
votes
The correct owner of an application bundle within /Applications for preinstalled Apple apps is: root
The correct owner of an application bundle within /Applications for packaged installers user installed apps is: root
The correct owner of an application bundle within /Applications for drag and drop user installed apps is: $USER
Where $USER is typically the short name of the person who installed the app. Otherwise, use the short name of the USER who is to own the file.
Here are the results of the ls -leO@d command run from Terminal on the Fritzing application bundle:
$ ls -leO@d /Applications/Fritzing.app
drwxr-xr-x@ 3 me admin - 102 Jun 6 2016 /Applications/Fritzing.app
com.apple.quarantine 57
$
Same command run on the directory mentioned in the error message shown in the OP:
$ ls -leO@d /Applications/Fritzing.app/Contents/MacOS/fritzing-parts
drwxr-xr-x@ 15 me admin - 510 Jun 6 2016 /Applications/Fritzing.app/Contents/MacOS/fritzing-parts
com.apple.quarantine 57
$
To change owner of a user installed app, e.g. for Fritzing, use the following command in Terminal:
sudo chown -R $USER /Applications/Fritzing.app
Note you can leave $USER as is written if you are the logged in USER and you are taking ownership.
Also consider checking the permissions and adjust as needed. As in this case for Fritzing:
sudo chmod -R 0755 /Applications/Fritzing.app
As I have Fritzing installed and working, and its permission are as previously shown, I believe the error message is somewhat erroneous and is being caused by you not being the owner. Changing ownership as previously shown should resolve your issue.
add a comment |
Apps that are installed by the system, either out of the box or by an installer that asks for an admin password, will be owned by root. Everything installed by a user (i.e. drag and drop) will be owned by whoever installed them, which is where you seem to be running into issues if you require write permissions for updating and a different user installed that app. All of these possibilities are valid ownership.
You can safely change the ownership to yourself if you need to, or else you can use group permissions so that, for example, all users with admin privileges could update the app.
The below code changes the group (all files/folders in the .app package recursively) to the "admin" group, which all your users with admin privileges will be a member of, then adds write privileges for the group.
You may need to use "sudo" at the beginning of each line if you don't already have suitable privileges.
> chgrp -R admin /Applications/Fritzing.app
> chmod -R g+w /Applications/Fritzing.app
New contributor
Shannon is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I may edit this despite the +1 since root doesn’t really own much out of the box on macOS (or didn’t last time I checked). The correctness here is that a group of people should be able to modify third party apps and everyone should be able to read / run them without being “the” owner of the App bundle.
– bmike♦
5 hours ago
On my system there are 117 apps owned by root in /Applications, many of which are not the default ones that come out of the box. So I guess it depends on how the installation process functions on a per-app basis.
– Shannon
4 hours ago
add a comment |
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
The correct owner of an application bundle within /Applications for preinstalled Apple apps is: root
The correct owner of an application bundle within /Applications for packaged installers user installed apps is: root
The correct owner of an application bundle within /Applications for drag and drop user installed apps is: $USER
Where $USER is typically the short name of the person who installed the app. Otherwise, use the short name of the USER who is to own the file.
Here are the results of the ls -leO@d command run from Terminal on the Fritzing application bundle:
$ ls -leO@d /Applications/Fritzing.app
drwxr-xr-x@ 3 me admin - 102 Jun 6 2016 /Applications/Fritzing.app
com.apple.quarantine 57
$
Same command run on the directory mentioned in the error message shown in the OP:
$ ls -leO@d /Applications/Fritzing.app/Contents/MacOS/fritzing-parts
drwxr-xr-x@ 15 me admin - 510 Jun 6 2016 /Applications/Fritzing.app/Contents/MacOS/fritzing-parts
com.apple.quarantine 57
$
To change owner of a user installed app, e.g. for Fritzing, use the following command in Terminal:
sudo chown -R $USER /Applications/Fritzing.app
Note you can leave $USER as is written if you are the logged in USER and you are taking ownership.
Also consider checking the permissions and adjust as needed. As in this case for Fritzing:
sudo chmod -R 0755 /Applications/Fritzing.app
As I have Fritzing installed and working, and its permission are as previously shown, I believe the error message is somewhat erroneous and is being caused by you not being the owner. Changing ownership as previously shown should resolve your issue.
add a comment |
The correct owner of an application bundle within /Applications for preinstalled Apple apps is: root
The correct owner of an application bundle within /Applications for packaged installers user installed apps is: root
The correct owner of an application bundle within /Applications for drag and drop user installed apps is: $USER
Where $USER is typically the short name of the person who installed the app. Otherwise, use the short name of the USER who is to own the file.
Here are the results of the ls -leO@d command run from Terminal on the Fritzing application bundle:
$ ls -leO@d /Applications/Fritzing.app
drwxr-xr-x@ 3 me admin - 102 Jun 6 2016 /Applications/Fritzing.app
com.apple.quarantine 57
$
Same command run on the directory mentioned in the error message shown in the OP:
$ ls -leO@d /Applications/Fritzing.app/Contents/MacOS/fritzing-parts
drwxr-xr-x@ 15 me admin - 510 Jun 6 2016 /Applications/Fritzing.app/Contents/MacOS/fritzing-parts
com.apple.quarantine 57
$
To change owner of a user installed app, e.g. for Fritzing, use the following command in Terminal:
sudo chown -R $USER /Applications/Fritzing.app
Note you can leave $USER as is written if you are the logged in USER and you are taking ownership.
Also consider checking the permissions and adjust as needed. As in this case for Fritzing:
sudo chmod -R 0755 /Applications/Fritzing.app
As I have Fritzing installed and working, and its permission are as previously shown, I believe the error message is somewhat erroneous and is being caused by you not being the owner. Changing ownership as previously shown should resolve your issue.
add a comment |
The correct owner of an application bundle within /Applications for preinstalled Apple apps is: root
The correct owner of an application bundle within /Applications for packaged installers user installed apps is: root
The correct owner of an application bundle within /Applications for drag and drop user installed apps is: $USER
Where $USER is typically the short name of the person who installed the app. Otherwise, use the short name of the USER who is to own the file.
Here are the results of the ls -leO@d command run from Terminal on the Fritzing application bundle:
$ ls -leO@d /Applications/Fritzing.app
drwxr-xr-x@ 3 me admin - 102 Jun 6 2016 /Applications/Fritzing.app
com.apple.quarantine 57
$
Same command run on the directory mentioned in the error message shown in the OP:
$ ls -leO@d /Applications/Fritzing.app/Contents/MacOS/fritzing-parts
drwxr-xr-x@ 15 me admin - 510 Jun 6 2016 /Applications/Fritzing.app/Contents/MacOS/fritzing-parts
com.apple.quarantine 57
$
To change owner of a user installed app, e.g. for Fritzing, use the following command in Terminal:
sudo chown -R $USER /Applications/Fritzing.app
Note you can leave $USER as is written if you are the logged in USER and you are taking ownership.
Also consider checking the permissions and adjust as needed. As in this case for Fritzing:
sudo chmod -R 0755 /Applications/Fritzing.app
As I have Fritzing installed and working, and its permission are as previously shown, I believe the error message is somewhat erroneous and is being caused by you not being the owner. Changing ownership as previously shown should resolve your issue.
The correct owner of an application bundle within /Applications for preinstalled Apple apps is: root
The correct owner of an application bundle within /Applications for packaged installers user installed apps is: root
The correct owner of an application bundle within /Applications for drag and drop user installed apps is: $USER
Where $USER is typically the short name of the person who installed the app. Otherwise, use the short name of the USER who is to own the file.
Here are the results of the ls -leO@d command run from Terminal on the Fritzing application bundle:
$ ls -leO@d /Applications/Fritzing.app
drwxr-xr-x@ 3 me admin - 102 Jun 6 2016 /Applications/Fritzing.app
com.apple.quarantine 57
$
Same command run on the directory mentioned in the error message shown in the OP:
$ ls -leO@d /Applications/Fritzing.app/Contents/MacOS/fritzing-parts
drwxr-xr-x@ 15 me admin - 510 Jun 6 2016 /Applications/Fritzing.app/Contents/MacOS/fritzing-parts
com.apple.quarantine 57
$
To change owner of a user installed app, e.g. for Fritzing, use the following command in Terminal:
sudo chown -R $USER /Applications/Fritzing.app
Note you can leave $USER as is written if you are the logged in USER and you are taking ownership.
Also consider checking the permissions and adjust as needed. As in this case for Fritzing:
sudo chmod -R 0755 /Applications/Fritzing.app
As I have Fritzing installed and working, and its permission are as previously shown, I believe the error message is somewhat erroneous and is being caused by you not being the owner. Changing ownership as previously shown should resolve your issue.
edited 4 hours ago
answered 4 hours ago
user3439894user3439894
29.8k64669
29.8k64669
add a comment |
add a comment |
Apps that are installed by the system, either out of the box or by an installer that asks for an admin password, will be owned by root. Everything installed by a user (i.e. drag and drop) will be owned by whoever installed them, which is where you seem to be running into issues if you require write permissions for updating and a different user installed that app. All of these possibilities are valid ownership.
You can safely change the ownership to yourself if you need to, or else you can use group permissions so that, for example, all users with admin privileges could update the app.
The below code changes the group (all files/folders in the .app package recursively) to the "admin" group, which all your users with admin privileges will be a member of, then adds write privileges for the group.
You may need to use "sudo" at the beginning of each line if you don't already have suitable privileges.
> chgrp -R admin /Applications/Fritzing.app
> chmod -R g+w /Applications/Fritzing.app
New contributor
Shannon is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I may edit this despite the +1 since root doesn’t really own much out of the box on macOS (or didn’t last time I checked). The correctness here is that a group of people should be able to modify third party apps and everyone should be able to read / run them without being “the” owner of the App bundle.
– bmike♦
5 hours ago
On my system there are 117 apps owned by root in /Applications, many of which are not the default ones that come out of the box. So I guess it depends on how the installation process functions on a per-app basis.
– Shannon
4 hours ago
add a comment |
Apps that are installed by the system, either out of the box or by an installer that asks for an admin password, will be owned by root. Everything installed by a user (i.e. drag and drop) will be owned by whoever installed them, which is where you seem to be running into issues if you require write permissions for updating and a different user installed that app. All of these possibilities are valid ownership.
You can safely change the ownership to yourself if you need to, or else you can use group permissions so that, for example, all users with admin privileges could update the app.
The below code changes the group (all files/folders in the .app package recursively) to the "admin" group, which all your users with admin privileges will be a member of, then adds write privileges for the group.
You may need to use "sudo" at the beginning of each line if you don't already have suitable privileges.
> chgrp -R admin /Applications/Fritzing.app
> chmod -R g+w /Applications/Fritzing.app
New contributor
Shannon is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I may edit this despite the +1 since root doesn’t really own much out of the box on macOS (or didn’t last time I checked). The correctness here is that a group of people should be able to modify third party apps and everyone should be able to read / run them without being “the” owner of the App bundle.
– bmike♦
5 hours ago
On my system there are 117 apps owned by root in /Applications, many of which are not the default ones that come out of the box. So I guess it depends on how the installation process functions on a per-app basis.
– Shannon
4 hours ago
add a comment |
Apps that are installed by the system, either out of the box or by an installer that asks for an admin password, will be owned by root. Everything installed by a user (i.e. drag and drop) will be owned by whoever installed them, which is where you seem to be running into issues if you require write permissions for updating and a different user installed that app. All of these possibilities are valid ownership.
You can safely change the ownership to yourself if you need to, or else you can use group permissions so that, for example, all users with admin privileges could update the app.
The below code changes the group (all files/folders in the .app package recursively) to the "admin" group, which all your users with admin privileges will be a member of, then adds write privileges for the group.
You may need to use "sudo" at the beginning of each line if you don't already have suitable privileges.
> chgrp -R admin /Applications/Fritzing.app
> chmod -R g+w /Applications/Fritzing.app
New contributor
Shannon is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
Apps that are installed by the system, either out of the box or by an installer that asks for an admin password, will be owned by root. Everything installed by a user (i.e. drag and drop) will be owned by whoever installed them, which is where you seem to be running into issues if you require write permissions for updating and a different user installed that app. All of these possibilities are valid ownership.
You can safely change the ownership to yourself if you need to, or else you can use group permissions so that, for example, all users with admin privileges could update the app.
The below code changes the group (all files/folders in the .app package recursively) to the "admin" group, which all your users with admin privileges will be a member of, then adds write privileges for the group.
You may need to use "sudo" at the beginning of each line if you don't already have suitable privileges.
> chgrp -R admin /Applications/Fritzing.app
> chmod -R g+w /Applications/Fritzing.app
New contributor
Shannon is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
edited 4 hours ago
New contributor
Shannon is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
answered 5 hours ago
ShannonShannon
413
413
New contributor
Shannon is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
New contributor
Shannon is a new contributor to this site. Take care in asking for clarification, commenting, and answering.
Check out our Code of Conduct.
I may edit this despite the +1 since root doesn’t really own much out of the box on macOS (or didn’t last time I checked). The correctness here is that a group of people should be able to modify third party apps and everyone should be able to read / run them without being “the” owner of the App bundle.
– bmike♦
5 hours ago
On my system there are 117 apps owned by root in /Applications, many of which are not the default ones that come out of the box. So I guess it depends on how the installation process functions on a per-app basis.
– Shannon
4 hours ago
add a comment |
I may edit this despite the +1 since root doesn’t really own much out of the box on macOS (or didn’t last time I checked). The correctness here is that a group of people should be able to modify third party apps and everyone should be able to read / run them without being “the” owner of the App bundle.
– bmike♦
5 hours ago
On my system there are 117 apps owned by root in /Applications, many of which are not the default ones that come out of the box. So I guess it depends on how the installation process functions on a per-app basis.
– Shannon
4 hours ago
I may edit this despite the +1 since root doesn’t really own much out of the box on macOS (or didn’t last time I checked). The correctness here is that a group of people should be able to modify third party apps and everyone should be able to read / run them without being “the” owner of the App bundle.
– bmike♦
5 hours ago
I may edit this despite the +1 since root doesn’t really own much out of the box on macOS (or didn’t last time I checked). The correctness here is that a group of people should be able to modify third party apps and everyone should be able to read / run them without being “the” owner of the App bundle.
– bmike♦
5 hours ago
On my system there are 117 apps owned by root in /Applications, many of which are not the default ones that come out of the box. So I guess it depends on how the installation process functions on a per-app basis.
– Shannon
4 hours ago
On my system there are 117 apps owned by root in /Applications, many of which are not the default ones that come out of the box. So I guess it depends on how the installation process functions on a per-app basis.
– Shannon
4 hours ago
add a comment |