Welcome to the MacNN Forums.

If this is your first visit, be sure to check out the FAQ by clicking the link above. You may have to register before you can post: click the register link above to proceed. To start viewing messages, select the forum that you want to visit from the selection below.

You are here: MacNN Forums > Software - Troubleshooting and Discussion > Mac OS X > Tiger permissions wrong on Disk Images, Mail.app won't open either

Tiger permissions wrong on Disk Images, Mail.app won't open either
Thread Tools
WSE
Junior Member
Join Date: Feb 2001
Location: santa monica, CA
Status: Offline
Reply With Quote
Apr 30, 2005, 10:59 AM
 
Tiger treats file permissions on Disk Images differently than 10.3.9 and it is causing me big problems.

After converting to Tiger, files on encrypted disk images can still be opened and read; but they can no longer be moved or trashed without a file permissions error. Mail.app will not even open, because it is trying to open mail folders on one of these disk images (I keep my mail on an encrypted disk image). Trashing the Mail plist does not help.

Comparing the permissions for these files in 10.3.9 and 10.4, I notice that files on disk images in 10.3 have typical ownership attributes -- the owner is my username; while files on disk images in 10.4 have no username as the owner, and even though there is a "change user" option, it does not work. If I create a new disk image using Disk Utility in 10.4 and then create a brand new word file, it still has this "nouser" file ownership, but that file can be moved and deleted. If I make a copy of a file from a 10.3.9-created disk image to a 10.4-created disk image, that file starts behaving normally, i.e. I can move or delete it .. yet the permissions for the copy still have no user. The "read/write" is in black, whereas the "read/write" on the 10.3.9-created disk image file is in grey.

Any help greatly appreciated.
     
WSE  (op)
Junior Member
Join Date: Feb 2001
Location: santa monica, CA
Status: Offline
Reply With Quote
Apr 30, 2005, 01:19 PM
 
OK - I called AppleSupport and they solved it. In case this is happening to you, this is what they guy had me do:

1) Logout as a user
2) In the loginwindow, instead of typing in my username, type in ">console"
if your loginwindow gives a list of usernames to choose from, you might need to first go into systems prefs/accounts/login prefs to change it to get a window
3) In console type in username, or maybe "login (username)"
4) give password upon request
5) type "sudo chown -R $USER ~" without the quotes
6) after it finishes, type "exit"
7) log in as yourself, and everything now works

This was a super-global repair permissions exercise.
     
   
Thread Tools
Forum Links
Forum Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts
BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On
Top
Privacy Policy
All times are GMT -5. The time now is 12:26 AM.
All contents of these forums © 1995-2011 MacNN. All rights reserved.
Branding + Design: www.gesamtbild.com
vBulletin v.3.8.7 © 2000-2011, Jelsoft Enterprises Ltd., Content Relevant URLs by vBSEO 3.3.2