3 Replies Latest reply: Feb 9, 2013 9:00 PM by Ozjulie
Ozjulie Level 1 Level 1 (0 points)

The file “aaaa.jpg” couldn’t be opened because you don’t have permission to view it.

This message is coming up every time i try to look at a photo on my Mac .   This is new  ... does anyone know what has happened?


iMac, Mac OS X (10.7.4)
  • 1. Re: The file “aaa.jpg” couldn’t be opened because you don’t have permission to view it
    Linc Davis Level 10 Level 10 (117,715 points)

    Back up all data.

    This procedure will unlock all your user files (not system files) and reset their ownership and access-control lists to the default. If you've set special values for those attributes on any of your files, they will be reverted. In that case, either stop here, or be prepared to recreate the settings if necessary. Do so only after verifying that those settings didn't cause the problem. If none of this is meaningful to you, you don't need to worry about it.

     

    Step 1

    If you have more than one user account, and the one in question is not an administrator account, then temporarily promote it to administrator status in the Users & Groups preference pane. To do that, unlock the preference pane using the credentials of an administrator, check the box marked Allow user to administer this computer, then reboot. You can demote the problem account back to standard status when this step has been completed.

    Triple-click the following line to select it. Copy the selected text to the Clipboard (command-C):

    { sudo chflags -R nouchg,nouappnd ~ $TMPDIR.. ; sudo chown -Rh $UID:staff ~ $_ ; sudo chmod -R u+rwX ~ $_ ; chmod -R -N ~ $_ ; } 2> /dev/null

    Launch the Terminal application in any of the following ways:

    ☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)

    ☞ In the Finder, select Go Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.

    ☞ Open LaunchPad. Click Utilities, then Terminal in the icon grid.

    Paste into the Terminal window (command-V). You'll be prompted for your login password, which won't be displayed when you type it. You may get a one-time warning not to screw up. If you don’t have a login password, you’ll need to set one before you can run the command. If you see a message that your username "is not in the sudoers file," then you're not logged in as an administrator.

     

    The command will take a noticeable amount of time to run. Wait for a new line ending in a dollar sign (“$”) to appear, then quit Terminal.

    Step 2

     

    Boot into Recovery by holding down the key combination command-R at startup. Release the keys when you see a gray screen with a spinning dial.

    When the OS X Utilities screen appears, select

    Utilities Terminal

    from the menu bar. A Terminal window will open.

    In the Terminal window, type this:

    resetpassword

    That's one word, all lower case, with no spaces. Then press return. A Reset Password window will open. You’renot going to reset a password.

    Select your boot volume ("Macintosh HD," unless you gave it a different name) if not already selected.

    Select your username from the menu labeled Select the user account if not already selected.

    Under Reset Home Directory Permissions and ACLs, click the Reset button.

    Select

    Restart

    from the menu bar.

  • 2. Re: The file “aaa.jpg” couldn’t be opened because you don’t have permission to view it
    Terence Devlin Level 10 Level 10 (123,735 points)

    To correct permissions in the iPhoto Library

     

    Back Up and try rebuild the library: hold down the command and option (or alt) keys while launching iPhoto. Use the resulting dialogue to rebuild. Note the option to check and repair Library permissions.

  • 3. Re: The file “aaa.jpg” couldn’t be opened because you don’t have permission to view it
    Ozjulie Level 1 Level 1 (0 points)

    Thanks for all the suggestions. 

     

    As it happens I ended up shutting down then restarting the computer.

     

    Voila everything worked again.