Can't install Scrivener

Just downloaded Scrivener for my first time. But I can’t get it installed on my Macbook. When I double click the dmg, I first get the information text and when I click “Agree”, a process indicator shows that the unpacking has begun. Then the indicator disappears, but there is no disk image on my desktop. If I double click again, on the dmg, nothing happens. But if I move it to the trashcan and tries to empty it, I can’t cause “the item is in use”.

So for some reason, it seems like the unpacking of the dmg never finishes. I’ve tried to re-download without any success.

Also, using Disk Utility to verify the dmg tells me it’s all right.

Any ideas?


This sounds odd but does suggest a permissions problem. Launch Disk Utility again but this time tell it to repair permissions on your hard drive. Then, click on the dmg and select Get Info from the file menu and look at the bottom of the window where it says Ownership & Permissions. Make sure you have Read & Write (you can change it easily if it’s otherwise).

By the way, repair permissions is not a panacea.

Good luck


I’d also try a disk utility like Disk Warrior on your drive.

Thanks. That fixed the problem.

I’m new in the Mac world. What causes permissions to be faulty set, and how does OS X track what they are supposed to be?



With more recent versions of the OS, which we are all obviously on anyway, Apple switched to a new scheduler which does not have this fault. The original one is good for servers which run forever on, but has that problem with desktop and laptop systems that you mentioned. The new scheduler detects when a job has been missed, and runs as soon as possible upon restarting. This is why sometimes the computer’s disk runs a lot right after you turn it on. So you needn’t worry about running them on your own unless there is something specifically wrong, or you made dramatic changes to your Spotlight configurations. One need not worry about these unless they are running an old operating system, 10.2.

That aside, it does not repair permissions on a regular basis, for good reason. It should only be run when problems like this crop up. Those problems are not at all connected to normal disk usage, but instead are created by poorly designed installers. Running that script simply goes through the base system with a huge checklist and makes sure that all of the read/write/execute flags have been set appropriately.