Camino crashes on start
 

Suddenly (and for discernable reason) Camino has started crashing as it starts up. I removed the application and tried reinstalling, I checked the system and the disk.

Everything else is functioning normally. I don't recall doing anything that might have led to this sudden cessation.

I tended to use Camino regularly and would really like to get it back.

Not having Camino installed, I cannot tell you the exact name of the pref to look for, but have you tried moving the preference file from your ~/Library/Preferences/ directory to your desktop and then opened Camino? If that fixes it, trash the pref, if that doesn't fix it, throw it back where you got it and nothing lost.

solution...dont use camino...;)

Trash the following:

/Users/username/Library/Preferences/org.mozilla.navigator.plist

and

/Users/username/Library/Application Support/Chimera

Note - your bookmarks and prefs will be erased. You may want to back up the Chimera folder and restore your bookmarks from there.

Hugh

I already removed the pref
 

I already removed

/Users/username/Library/Preferences/org.mozilla.navigator.plist

It showed up when I ran

sudo fs_usage | grep -i camino | grep -v CACHE | grep -v fstat

I'm pretty sure I removed

/Users/username/Library/Application Support/Chimera

but I'll check to be sure.

I removed both App Support Directories
 

I removed both

/Users/username/Library/Application Support/Chimera

and

/Library/Application Support/Chimera

No luck. Still fails on start up.

And what do your crashlogs say?

How do I access the crashlogs?
 

How specifically do I access the crashlogs?

open /Users/gibblehey/Library/Logs/CrashReporter/Camino.crash.log

The crash log
 

Date/Time: 2003-07-11 00:50:26 -0400
OS Version: 10.2.6 (Build 6L60)
Host: gibblehey-Computer.local.

Command: Camino
PID: 1343

Exception: EXC_BAD_ACCESS (0x0001)
Codes: KERN_PROTECTION_FAILURE (0x0002) at 0x00000001

Thread 0 Crashed:
#0 0x90004f90 in strcmp
#1 0x900b2208 in names_match
#2 0x900b20f0 in NSVersionOfRunTimeLibrary
#3 0x02dfde54 in _ZN11FCModuleMgr13GetNextModuleEv
#4 0x02dfdf40 in _ZN11FCModuleMgr10FindModuleEm
#5 0x02dfc88c in _Z19FindSpiralDirectoryPcmm
#6 0x02dfc978 in _Z18InitializeInternaliPKcm
#7 0x02dfc208 in _ZN17nsQfaServicesImpl12StartServiceEv
#8 0x001312a0 in _ZN20nsAppStartupNotifier7ObserveEP11nsISupportsPKcPKt
#9 0x00053c10 in _Z16NS_InitEmbeddingP12nsILocalFileP27nsIDirectoryServiceProvider
#10 0x00031338 in -[PreferenceManager initMozillaPrefs]
#11 0x00030e00 in -[PreferenceManager init]
#12 0x00030d5c in +[PreferenceManager sharedInstance]
#13 0x0000989c in -[MainController preferenceManager]
#14 0x00007a88 in -[MainController applicationDidFinishLaunching:]
#15 0x97dfab58 in _nsNotificationCenterCallBack
#16 0x901684d0 in _postNotification
#17 0x90165be4 in _CFNotificationCenterPostLocalNotification
#18 0x9318a720 in -[NSApplication _sendFinishLaunchingNotification]
#19 0x93161624 in _requiredAEEventHandler
#20 0x91b56570 in _Z20aeDispatchAppleEventPK6AEDescPS_mPh
#21 0x91b590cc in _Z25dispatchEventAndSendReplyPK6AEDescPS_
#22 0x91b56478 in aeProcessAppleEvent
#23 0x96a83778 in AEProcessAppleEvent
#24 0x9308e0a8 in _DPSNextEvent
#25 0x930a0158 in -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:]
#26 0x930b1d88 in -[NSApplication run]
#27 0x9315fc58 in NSApplicationMain
#28 0x00004ff0 in _start
#29 0x00004e70 in start

Thread 1:
#0 0x90073c28 in mach_msg_trap
#1 0x90005f70 in mach_msg
#2 0xc0009190 in __ape_internal
#3 0xc0000efc in __ape_agent
#4 0x90020d28 in _pthread_body

PPC Thread State:
srr0: 0x90004f90 srr1: 0x0000d030 vrsave: 0x00000000
xer: 0x20000000 lr: 0x900b2208 ctr: 0x90004f80 mq: 0x00000000
r0: 0x900b2208 r1: 0xbfffdc50 r2: 0x00000182 r3: 0x00000043
r4: 0x00000001 r5: 0x90cd0333 r6: 0x80808080 r7: 0x00000003
r8: 0x00000004 r9: 0x90cd0331 r10: 0x00000000 r11: 0xa0004374
r12: 0x90004f80 r13: 0xbfffe7c4 r14: 0xbfffe790 r15: 0xbfffe7d4
r16: 0xbfffe750 r17: 0x050b31f0 r18: 0xbfffe830 r19: 0xbfffe7e0
r20: 0x008a7f58 r21: 0xbfffe870 r22: 0xbfffe7d0 r23: 0xbfffe7c0
r24: 0x0076f8ac r25: 0x00000001 r26: 0x0000004b r27: 0x00000004
r28: 0x00000001 r29: 0x90cd02fc r30: 0x90cd0332 r31: 0x900b21d4

I don't have any input that isn't already here, but I'd just like to say that "not using Camino" isn't a solution at all. What if there's something else wrong with the machine that is just screwing with Camino?

Camino's a great browser. I like Safari, I like Camino. The more the merrier, I say, as long as they're good.

The Moz Project owns. ;-)

Does the crash log help anyone?
 

Does the crash log help anyone figure out why Camino is crashing and how I can fix it?

Something to try...

Use the finder to navigate to:
/Library/Internet Plug-Ins/
(note - NOT Users/<yourname>/Library/Internet Plug-Ins)

and look for a folder called 'Java Applet.plugin'.

Temporarily drag this folder onto your desktop. Now try to start camino. If it works now, then you have the same problem as I do. You will probably find that you get the same crash with any mozilla-based browser.

The bad news is that I don't know how to correct the problem. The good news is that safari is a great browser!

Jeremy

Nope, that didn't work
 

Despite doubting that this was a solution for the Camino problem, I gave it a shot. It didn't work.

The reason for my doubts: you describe all Mozilla browsers as problematic. That's just the point: Camino is the only one that is giving me a problem. I'm writing this on straight Mozilla, and I'm also using Mozilla Firebird (which I had installed awhile ago but didn't use much).

Anybody else have an idea as to the cause of this extremely unexpected change in functionality?

Have you attempted to log in as another user to open Camino?

Just noticed on Versiontracker a new version of DivX (5.07). Among the bugs fixed is this: "Problem that caused Camino to crash on startup". Have you by chance installed DivX recently?

Another user and DivX: No and No
 

I created a new account, logged in and tried Camino. Same thing happened.

I then tried to download DivX 5.07 (but download.com only downloaded the installer for 5.06). I ran uninstall and got the following messages in the log:

Error Deleting: .DS_Store -1
Error Deleting: DivX® 5.component The file is in use by another application
Error Deleting: .DS_Store -1

I rebooted and tried Camino and again, it failed.

Umm, you sort of lost me. *IF* you have a version of DivX less than 5.07 installed *AND* your attempt to remove it failed, it could still be the DivX bug that was fixed in version 5.07 that is causing your crashes.

I would guess that installing DivX 5.07 would replace your older version with the bug-fix version. Don't have it installed myself, so don't really know.

Versiontracker's links lead here:

http://www.divx.com/divx/mac/

Maybe you can get the new installer from this page and find some updating instructions.

I just pulled one of the daily builds of Camino from mozilla.org after it started crashing for me.

Works fine now.

And I had installed DivX 5.06. I have now installed 5.07. I will still use the new daily build though. It works fine for me.

Did you try going back to an older version of Camino, just to eliminate that possibility. I know you can download older versions from Versiontracker as well as the Camino Project History page.

Daily build did the trick
 

I downloaded the daily build. It works fine.

Of course, it would be nice to understand why it suddenly decided to stop functioning, but I guess that is for some other time.

Thank you, thank you, thank you, thank you. I have lost all my weekend trying to fix that issue (in my case not only with Camino, but with Explorer, Disk Copy and others apps). I finally fixed all of them but no Camino neither Explorer.
Never, in my life, I would suspect the culprit was DivX 5.0.6. Now I have simply moved it from ~/Library/QuickTime to an ~/Library/QuickTimeCodecsDisabled folder and all works fine again.