I've tried everything I can think of but 1.2.1 crashes, sometimes a while after sometimes soon, after launch. I don't need to do anything.
I've upgraded to the latest Growl, I've removed Adium.app and re-installed 1.2.1, I've removed the old preference file (the main one, there are millions more in Application Support but fiddling with them one by one is crazy and I quite like my current Adium setup - except for crashiness of course).
I wish I could just get 1.2 again to see if that wouldn't just work.
Also, when logging into Google Talk I get a notification that their Security Certificate is not valid...
Edit: I seem to have found 1.2 but of course I'd rather see a fix than rollback. I used the reporting thingy after the crashes. Should I submit bugs differently?
Editedit: 1.2 suffers from the same problem. Before upgrade it worked fine, though.
1.2.1 crashes out of the blue
-
ssnickerer
- Harmless
- Posts: 3
- Joined: Sun May 22, 2005 6:48 pm
- evands
- Cocoaforge Admin
- Posts: 3152
- Joined: Thu Dec 02, 2004 10:55 pm
- Location: Decatur, GA
- Contact:
Please see http://adiumx.com/faq/ReportingBugs for the information we need to look at an issue like this.
Hmmm...
I'm not quite sure anymore that the problem was Adium. Things seem to be working at the moment, even on my work network. I found a disk error through DiskUtility, "Nesting of folders has exceeded the recommended limit of 100", which brought a dual message of disk checking out ok AND needing repair... The disk repair didn't change it but following it, a network change and some general desperation stuff Adium 1.2 did start to work ok. I'm afraid my methology was lacking so at what point Adium started behaving I'm not sure.
Good thing as I was starting to consider the benefits of restoring from a backup vs. an install and archive...
Well, if this turns up again I'll be sure to file a detailed bug report, unless the reason turns out to have not been Adium itself. Thanks!
I'm not quite sure anymore that the problem was Adium. Things seem to be working at the moment, even on my work network. I found a disk error through DiskUtility, "Nesting of folders has exceeded the recommended limit of 100", which brought a dual message of disk checking out ok AND needing repair... The disk repair didn't change it but following it, a network change and some general desperation stuff Adium 1.2 did start to work ok. I'm afraid my methology was lacking so at what point Adium started behaving I'm not sure.
Good thing as I was starting to consider the benefits of restoring from a backup vs. an install and archive...
Well, if this turns up again I'll be sure to file a detailed bug report, unless the reason turns out to have not been Adium itself. Thanks!