'Could not remove' errors

I just noticed a lot of these errors in the log:

Code: Select all: 2009-06-08 11:44:56.003 hazelfolderwatch[1144] File jalada has been sitting in the trash for too long. Purging. 2009-06-08 11:44:56.003 hazelfolderwatch[1144] Removing jalada. 2009-06-08 11:44:56.004 hazelfolderwatch[1144] Could not remove jalada: {Error = "Error removing"; Path = "/Users/thijs/.Trash/jalada"; } 2009-06-08 11:44:56.004 hazelfolderwatch[1144] [Error] Could not remove file: File jalada could not be removed from the Trash.

I have not counted the offenders, but there's a lot of them. What would cause this?

Are the trashed files hazelfolderwatch complains about locked?

No, not locked.
And no permissions issue either.

Are you doing secure deletes or regular ones? In the former case, the permissions required are different. Since it overwrites the files with random data, it needs write access to the file itself while a normal delete just needs write access to the trash folder.

Otherwise, you can try and use the 'rm' command in Terminal. I'll see if I can come up with any other diagnostics but being at WWDC right now, there may be some delays so I hope you can bear with me.

Regular, not secure, deletion.

A thought: if I can get Hazel to watch Trash as a regular folder, I could set a rule which is triggered by the error. How? I think this would require something like "on error" within Hazel.

Um, this might be another feature request: allow triggering of rule upon error within Hazel.
I know she can Growl me when something happens, that smells like there's a way for doing this.

Well, 't was permission errors, at least in some cases :oops:

Some packages contained stuff that didn't belong to me.

Ah yes, I always forget to tell people to check packages. Using the "Show Package Contents" function is useful in these cases.