Page 1 of 1

Adium crashes with messages.

Posted: Fri Mar 25, 2005 12:54 am
by Nitz
I'm using Adium 0.77, build C42A.

This all started about 3-5 days ago (I can't remember), but for some reason, whenever I receive a message in Adium or try to change message styles Adium crashes. I've tried replacing the Adium 2.0 folder in ~/Library/Application Support, I've tried deleting the .plist, I've also tried it with the beta version of Adium. It's starting to get really annoying. I think it's having trouble loading the message style, it gets as far as loading the background image, and then proceeds to crash. Yes, I've submitted bug reports, probably 8....

Any solutions? I think I may have some sort of corrupt file system or something...

Posted: Fri Mar 25, 2005 6:31 pm
by Nitz
Nevermind, a simple replacement of the WebKit.framework (/System/Library/Frameworks/WebKit.framework) fixed it all up. It's good to be back with Adium. :D

Posted: Fri Mar 25, 2005 8:01 pm
by evands
Where'd you replace it from? I believe others have had a similar issue. Did it begin after installing the new security update?

Posted: Sat Mar 26, 2005 1:41 am
by Nitz
evands wrote:Where'd you replace it from? I believe others have had a similar issue. Did it begin after installing the new security update?

The Safari installer installs a new WebKit.framework if there's none there ;) I used that.

It may have, I can't really remember, that's probably likely, a couple of things went wrong with my computer after that update.


Edit: In short, I did the following steps. Very easy to do.

MAKE SURE TO DO STEP 1 FIRST OR YOU WILL WANT TO KICK YOURSELF.

1) Download the Safari installer from here.
2) Go to the folder /System/Library/Frameworks and move "WebKit.framework" into the trash. Don't delete it just yet. (The Finder will probably want to authenticate for you to do this.)
3) Install Safari (even if it's already installed) and restart.
Open Safari, see if you can get on the internet, and if you can, go ahead and empty the trash.
It is recommended you repair permissions right after this too.

That's it, worked for me...