2.9 Freeze on OSX

[Bill Vlahos]

I see this problem on newly created stacks and I don't think it is a permissions issue.

It seems to be random when it crashes. It will work fine several times and then crash. Nothing apparently different on my end.

I never had this problem with any previous version of Rev or any other program I've ever seen.

Bill

On Wednesday, April 16, 2008, at 09:13AM, "J. Landman Gay" <jacque at hyperactivesw.com> wrote:
>Thomas McGrath III wrote:
>
>> Error on trying to save:
>> 
>> "Can't save stack libITS due to an error:
>> can't open stack backup file
>> Check the file path, and make sure you
>> have sufficient permissions."
>> 
>> I am not even using GLX2 in RR in this new user account, which is what 
>> normally is set to back up my stacks. So I look for an RR backup setting 
>> and find none. What is causing this backup file to happen and what path 
>> is it referring to? If I can find that maybe I can deal with the 
>> Permissions.
>
>When Rev saves a stack, it first renames the original by adding a tilde 
>at the end of the file name. Then it tries to copy the stack into a new 
>file. If for some reason the duplication doesn't succeed, you get that 
>error. The backup it is refering to is the original copy, now renamed, 
>which you should be able to find in its original enclosing folder. You 
>can restore the original by removing the tilde from the file name. It 
>won't have your new changes in it, of course, but you'll have the 
>orginal copy to work with again.
>
>The error when saving is almost always due to an inability to write to 
>the hard drive. That can be a permissions error, a hard drive error, a 
>disk full error, or anything else that prevents the duplicate stack from 
>being created.
>
>I would check the permissions on the stack file itself, on its enclosing 
>folder (you copied it from the shared directory, right? Does it still 
>belong to the "original" owner?), the permissions on the Rev app itself 
>as well as Rev's enclosing folder. Rev needs to be able to read and 
>write. As an experiment, give everyone all permissions for all the 
>folders and files -- the owner, the group, and everyone -- just to see 
>if that's the problem. Basically you want anyone to be able to copy and 
>write to that user's account. You can change the permissions back later, 
>but see if that fixes it for now.
>
>-- 
>Jacqueline Landman Gay         |     jacque at hyperactivesw.com
>HyperActive Software           |     http://www.hyperactivesw.com
>_______________________________________________
>use-revolution mailing list
>use-revolution at lists.runrev.com
>Please visit this url to subscribe, unsubscribe and manage your subscription preferences:
>http://lists.runrev.com/mailman/listinfo/use-revolution
>
>