Scrivener Has Entirely Stopped Working

Scrivener Scrivener for macOS
1

Hi,

I’m on Mac OS 10.6.5, Build 10H574, and I’ve recently updated to the most recent Scrivener. It was working fine for awhile, but it has now stopped working entirely. The scrivener icon has broken and the application will not even open. I’m getting the following error:

Process: Scrivener [128]
Path: /Applications/Scrivener.app/Contents/MacOS/Scrivener
Identifier: com.literatureandlatte.scrivener2
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: launchd [87]

Date/Time: 2010-11-30 17:46:34.622 -0600
OS Version: Mac OS X 10.6.5 (10H574)
Report Version: 6

Interval Since Last Report: 78770 sec
Crashes Since Last Report: 2
Per-App Crashes Since Last Report: 2
Anonymous UUID: 3797927E-58C6-4DD7-98D0-F669AD831A8C

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread: 0

Dyld Error Message:
Library not loaded: @executable_path/…/Frameworks/Growl.framework/Versions/A/Growl
Referenced from: /Applications/Scrivener.app/Contents/MacOS/Scrivener
Reason: image not found

Binary Images:
0x8fe00000 - 0x8fe4162b dyld 132.1 (???) <28F0312C-0678-159E-34E2-9A4E3DEADB20> /usr/lib/dyld

Model: MacBookPro6,2, BootROM MBP61.0057.B0C, 2 processors, Intel Core i5, 2.4 GHz, 4 GB, SMC 1.58f16
Graphics: NVIDIA GeForce GT 330M, NVIDIA GeForce GT 330M, PCIe, 256 MB
Graphics: Intel HD Graphics, Intel HD Graphics, Built-In, 288 MB
Memory Module: global_name
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x93), Broadcom BCM43xx 1.0 (5.10.131.36.1)
Bluetooth: Version 2.3.8f7, 2 service, 12 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: Hitachi HTS545032B9SA02, 298.09 GB
Serial ATA Device: MATSHITADVD-R UJ-898
USB Device: Hub, 0x0424 (SMSC), 0x2514, 0xfd100000
USB Device: IR Receiver, 0x05ac (Apple Inc.), 0x8242, 0xfd120000
USB Device: Built-in iSight, 0x05ac (Apple Inc.), 0x8507, 0xfd110000
USB Device: Hub, 0x0424 (SMSC), 0x2514, 0xfa100000
USB Device: Apple Internal Keyboard / Trackpad, 0x05ac (Apple Inc.), 0x0236, 0xfa120000
USB Device: Internal Memory Card Reader, 0x05ac (Apple Inc.), 0x8403, 0xfa130000
USB Device: BRCM2070 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000
USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8218, 0xfa113000

2

UPDATE: I removed the application and re-installed it form the dmg. This seems to have fixed the problem. I am somewhat hesitant, however, to upgrade again to 2.0.2

3

Same problem here. I launched Scrivener today and saw the notification message that 2.0.2 was available. I clicked “Install and Relanch”, and instantly saw an error report:

Process: Scrivener [944]
Path: /Applications/Scrivener.app/Contents/MacOS/Scrivener
Identifier: com.literatureandlatte.scrivener2
Version: ??? (???)
Code Type: X86 (Native)
Parent Process: launchd [178]

Date/Time: 2010-12-01 06:22:25.370 +0200
OS Version: Mac OS X 10.6.5 (10H574)
Report Version: 6

Interval Since Last Report: 123287 sec
Crashes Since Last Report: 14
Per-App Crashes Since Last Report: 4
Anonymous UUID: 20D1370F-3C52-44D3-96DD-F98D010EFE4C

Exception Type: EXC_BREAKPOINT (SIGTRAP)
Exception Codes: 0x0000000000000002, 0x0000000000000000
Crashed Thread: 0

Dyld Error Message:
Library not loaded: @executable_path/…/Frameworks/Growl.framework/Versions/A/Growl
Referenced from: /Applications/Scrivener.app/Contents/MacOS/Scrivener
Reason: image not found

Binary Images:
0x8fe00000 - 0x8fe4162b dyld 132.1 (???) <39AC3185-E633-68AA-7CD6-1230E7F1CEF4> /usr/lib/dyld

Model: MacBookPro6,2, BootROM MBP61.0057.B0C, 2 processors, Intel Core i7, 2.66 GHz, 4 GB, SMC 1.58f16
Graphics: NVIDIA GeForce GT 330M, NVIDIA GeForce GT 330M, PCIe, 512 MB
Graphics: Intel HD Graphics, Intel HD Graphics, Built-In, 288 MB
Memory Module: global_name
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x93), Broadcom BCM43xx 1.0 (5.10.131.36.1)
Bluetooth: Version 2.3.8f7, 2 service, 12 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: Hitachi HTS545050B9SA02, 465.76 GB
Serial ATA Device: MATSHITADVD-R UJ-898, 561.5 MB
USB Device: Hub, 0x0424 (SMSC), 0x2514, 0xfa100000
USB Device: Internal Memory Card Reader, 0x05ac (Apple Inc.), 0x8403, 0xfa130000
USB Device: Apple Internal Keyboard / Trackpad, 0x05ac (Apple Inc.), 0x0236, 0xfa120000
USB Device: BRCM2070 Hub, 0x0a5c (Broadcom Corp.), 0x4500, 0xfa110000
USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8218, 0xfa113000
USB Device: Hub, 0x0424 (SMSC), 0x2514, 0xfd100000
USB Device: Built-in iSight, 0x05ac (Apple Inc.), 0x8507, 0xfd110000
USB Device: IR Receiver, 0x05ac (Apple Inc.), 0x8242, 0xfd120000

4

Just download and re-install from the main web page ( literatureandlatte.com/scrivener.php ), which will bring you up to date with 2.0.2 and get you up and running again. I’ve seen a few of these, but unfortunately they are inevitable - the udpater downloads Scrivener in a zip file, then extracts it and overwrites the current version. Occasionally a glitch with the connection will mean that the zip file gets corrupted during the download process, or the computer will have a minor problem unzipping the file, resulting in a partial version of the program. In this case, Scrivener some files are missing from within Scrivener which causes it to crash, because the zip file hasn’t extracted properly.

As I say, just re-download from the main page and you’ll be good to go.

Thanks,
Keith

5

Does Sparkle not have a function for hash verification? Seems like an obvious thing to implement, a check to make sure the .zip file actually matches the update zip on the server, before attempting to replace the application.

6

Yes, as of the latest version of Sparkle, the zip file has to be signed. What I am noticing - and I’ve e-mailed you about this separately Ioa - is that the zip files I’m creating for Sparkle result in a larger or smaller Scrivener app, bizarrely. But all the same, the update is working for the vast majority of users, so I think the problems may just be to do with download or extraction issues. There are a few more of these than I would expect, though…