Looks like no one’s replied in a while. To start the conversation again, simply ask a new question.

Change in Aperture Trash Behavior

Was there a change to Aperture Trash emptying to OS X trash in a recent Aperture update?


I put a new SSD (OWC Accelsior 240GB) in my MacPro and installed OS X and various applications, including Aperture 3 (now 3.4.4).


There is a change in the behavior of Aperture Trash.


Previously, I would delete images (Command + Delete) which would put them in Aperture Trash.

Then 'Empty Aperture Trash' would put them in OS X Trash can.

Then it would be necessary to empty the OS Trash can to completely eliminate the image files.


Now, after I 'Empty Aperture Trash', the images are gone (they do not appear in OS X Trash).


This behavior is fine by me as long as it is working as intended, but the fact that it is a change has me concerned. I've been having problems with this machine - so I'm trying to determine whether I've got things working properly or whether this is a hint at further fixes required.


My Aperture library exists on a software RAID 0 array (2 Western Digital 1TB drives).


OS X and Aperture boot from the SSD (which replaced an older SSD).

Mac Pro, OS X Mountain Lion (10.8.3), 8 core, 32GB RAM

Posted on Jun 2, 2013 7:45 AM

Reply
20 replies

Jun 2, 2013 10:22 AM in response to Frank Caggiano

Yes, please.


I understand the concept of Terminal/command line, but don't know more than a couple commands.


Is this procedure risky? My data is well backed-up (though in several places, so would be tedious to put it back).


If re-formatting the drive and beginning again is better for long term stability, I could do that.

Frank Caggiano wrote:


The permissions are wrong. No one should have read access for security reasons.


If you need help deleting the .Trashes folder post back.

Jun 2, 2013 11:14 AM in response to Bruce Jordan

I understand the concept of Terminal/command line,


Good what you need to do is simple, you just need to be precise.

Is this procedure risky? My data is well backed-up (though in several places, so would be tedious to put it back).


Any time you use sudo in the Terminal it can be risky but having backups removes a lot of tension.

If re-formatting the drive and beginning again is better for long term stability, I could do that.

Don;t think that is necessary at this point but it might be needed if this doesn't fix the problem. Lets see what happens.


OK, read all this before staring. If you have any questions or something doesn;t make sense post back before trying it.


Open a Terminal window (/Applications/Utilities/Terminal)


(the first set of commands is to get you comfortable with the procedure and to make sure the .Trashes folder is where we believe it to be)


enter ls -ld then drag in the icon for the RAID 0 volume you should see something like (with your volume in there)

Pandora:~ frank$ ls -ld /Volumes/QQ


Note there will be a space after the volume name. Use the delete key to delete the space then enter

/.Tra followed by the TAB key (on the same line)

The TAB key will cause the .Tra to expand to .Trashes if the folder is there. Assuming the folder name expanded


you should see

Pandora:~ frank$ ls -ld /Volumes/QQ/.Trashes/


If it doesn't expand make sure you typed in everything as I showed and try again. If it still doesn;t expand post back with a screen shot of the terminal window.


now press return. You should see

Pandora:~ frank$ ls -ld /Volumes/QQ/.Trashes/

d-wx-wx-wt 2 frank staff 68 Jun 2 13:43 /Volumes/QQ/.Trashes//

Pandora:~ frank$


If all that goes OK. Now you'll delete the folder. Enter

sudo rm -rf then drag the RAID icon in again. Again use the delete key to delete the space after the volume name and enter

/.Tra followed by the TAB key. Agina it should expand to .Trashes


Pandora:~ frank$ sudo rm -rf /Volumes/QQ/.Trashes/


Now press return. If this is the first time using the sudo command you'll get a message telling you to be careful. Continue. The .Trashes folder should be removed.Rerun the ls -ld ccommand from above to make sure it is gone.


Assuming it is unmount then remount the volume and the .Trashes folder should be back with the correct permissions. Try deleting a file from the volume and hopefully it will work as it should.


Again if anything here is unclear post back. Also keep in mind that the output you will see will not be identical to the above. Name, dates and prompts will differ.

Change in Aperture Trash Behavior

Welcome to Apple Support Community
A forum where Apple customers help each other with their products. Get started with your Apple ID.