Then try running the regular version - does it work? (If it doesn't, please post the crash report if it's different - it is possible that the code-signing differences between the two versions will cause it to fail anyway.) I now tried the framework "transplantation", but still the regular...

KB wrote:I've just PM'd you a promo code for our MAS version to see if that makes any difference - I doubt it will, but at this stage it's worth a shot.

Interestingly, the MAS version does not cash!

I'll have a look and tell you later. I actually HAD growl installed before it was updated and went to the App Store. Even though I thought I deinstalled everything, I'll have a (more thorough) look again. Great, thanks. so, after a "look again" and also consulting the Growl homepage, I am...

I recommend sticking with the "legacy" 10.4+ version for now. The features are identical, the only difference being that it doesn't contain the Retina display graphics (which you don't need on your MacBook anyway) and you have to use the workaround the first time you open it to bypass Gat...

updated to 2.4.1 - but still crashes upon start.

Okay, I'm now officially baffled. I've just fired up the 2.3.1 code base to look at what has changed regarding Growl, and there is nothing. 2.3.1 and 2.4 use the same version of Growl and the same code calling on it. Moreover, the crash log seems to indicate that the crash is coming from the Growl ...

Transplanting the growl.framework from 2.3.1 to (non-legacy, crashing) 2.4 does not help, 2.4 still crashes.
Also transplanting growl.framework from (non-legacy, crashing) 2.4 to 2.3.1 does NOT make the old version crash.

Great, thanks. This gets curiouser and curiouser, since 2.3.1 had the same version of Growl in it as 2.4. When you rolled back to 2.3.1, where did you download 2.3.1 from (our version history page perhaps)? no, I just recovered the previously working (pre-update) version from the trash, where it wa...

Could you please try this anyway? The reason I ask is that the 10.4 + 10.5 version of Scrivener 2.4 contains a different version of Growl to the 10.6+ version. ok, done - and it actually does solve the problem. I can now start 2.4 (build 22541) without crashing. So, it indeed seems to be related to...

Just to clarify, you have definitely done the following things: 1. Created a brand new, fresh user account on your machine and tried running Scrivener from it. yes 2. Trashed the 10.6+ version of Scrivener and tested the 10.4 + 10.5 version on our site, opening it using Ctrl-click. no, that is not ...

done that before - doesn't help.

Actually, I have done all the typical debugging procedures before I mentioned the bug here in the forum. I am an experienced user (with my first Mac bought in 1984 indeed), so I am familiar with the things that might cause a program to crash.

trashing the plist was the first thing I tried when I got the crashes - did not help.

done both - no change. Scrivener crashes upon opening.

The top of the crash report is mentioning Growl, which Scrivener uses for notifications. Please try reinstalling the latest version of Growl, to see if that is causing the problem (if you don't have Growl installed, it shouldn't cause any problems, though). Thanks and all the best, Keith Hi Keith, ...

I just re-downloaded the dmg from your website and installed it again, it still behaves the same way. I have already moved the plist files because I thought it might be an incompatible plist, but it didn't work. Here's the latest crash report: Process: Scrivener [41497] Path: /Applications/Scrivener...