dying when I send a message?

twistedpyxie · Post by **twistedpyxie** » Wed May 03, 2006 4:59 pm

Every time I try and send a message on Adium, it crashes and quits straight away. This just started happening today, and it's been happening all day- I tried re-installing it but it's still doing it. Any idea what's going on?

Post by **evands** » Wed May 03, 2006 5:26 pm

Email address on your submitted crash logs?

twistedpyxie · Post by **twistedpyxie** » Thu May 04, 2006 12:25 pm

I only submitted one or two of 'em.. would have been email glitterboi@gmail.com or aim msglitterboi?

Post by **evands** » Thu May 04, 2006 4:33 pm

Your system isn't providing helpful information with the crash; I'm not sure why. I recommend following the steps here:
http://trac.adiumx.com/wiki/TroubleshootingTips

Let us know if you have problems after following those steps.

Tipo 61 · Post by **Tipo 61** » Thu May 04, 2006 7:45 pm

Could it be because of a message style that he is using? Maybe it's crashing because it's failing to load the style when the first message is sent.

twistedpyxie · Post by **twistedpyxie** » Fri May 05, 2006 10:18 pm

I've reset everything and it still isn't working. Went through all the troubleshooting steps as well, and no luck.
So then I tried re-installing it.. and the same thing's happening. So I figure it's probably a problem at my side?

pinkwabbit · Post by **pinkwabbit** » Mon May 15, 2006 11:59 am

I'm experiencing the exact same problem, and even deleting everything to do with Adium and reinstalling doesn't help. I notice a lot of Console activity while running Adium, none of it reassuring:

Code: Select all

2006-05-15 19:49:56.106 Adium[10730] Caught exception: NSAccessibilityException - "AXVisibleChildren" attribute unsupported by: <NSScrollView: 0x4b7ce0>
2006-05-15 19:49:56.107 Adium[10730] The following unhandled exception was ignored: NSAccessibilityException ("AXVisibleChildren" attribute unsupported by: <NSScrollView: 0x4b7ce0>)
Stack trace:
atos cannot examine process 10730 for unknown reasons, even though it appears to exist.
2006-05-15 19:49:56.410 Adium[10730] Caught exception: NSInvalidArgumentException - *** +[NSArray arrayWithObject:]: attempt to insert nil
2006-05-15 19:49:56.411 Adium[10730] Launching the Adium Crash Reporter because an exception of type NSInvalidArgumentException occurred:
*** +[NSArray arrayWithObject:]: attempt to insert nil

Whatever that means.

Also, even when it's running, it's very, very slow.

I've noticed an entry in the Trac with a problem very similar to mine, and I've commented on it. It's very frustrating - until I first encountered this problem a week ago, Adium had been very good to use, and now I can't do a thing with it.

Oddly enough, when the rest of my family uses it on the same computer but on different accounts, it works fine - so what does it mean? Clearly something in my account doesn't agree with Adium, but I have not the skillz to fix it myself.

I submitted the Crash Reports with person.from.porlock (at) gmail.com.

Any suggestions? All I want is to make Adium work again.

I'm using an iMac Intel Duo Core 2.0Ghz with 1GB RAM.

Post by **evands** » Mon May 15, 2006 9:04 pm

It's something to do with your accessibility or voice-over settings. Did you change anything in those system preference panes (Universal Access) recently?

pinkwabbit · Post by **pinkwabbit** » Thu May 18, 2006 10:53 am

Oh! Hmm... yes, I did, actually - I'm a new Mac user, and was poking around the Systems Preferences recently to see what I could do.

I'm going to try and see what I can do to restore the default settings.

Do you think it might have been anything to do with the Speech Recognition/ Speakable Commands settings?

pinkwabbit · Post by **pinkwabbit** » Thu May 18, 2006 11:00 am

Gosh, you guys are gods! Yes, it worked - thanks a zillion! Back to using Adium again, after struggling with Fire for 3 days.

Really appreciate the help!

Just curious: how did you know what was wrong?

Tipo 61 · Post by **Tipo 61** » Thu May 18, 2006 11:23 am

pinkwabbit wrote:Just curious: how did you know what was wrong?

Because:

pinkwabbit wrote:Gosh, you guys are gods!

Adium Devs have mad skillz.

Post by **evands** » Thu May 18, 2006 1:29 pm

pinkwabbit: If you could point out specifically which options you changed that got it working again, that'd be great. I know from experience with other users that some combination of speech and accessibility settings causes that problem... but nobody on the dev team has been able to reproduce it just yet

pinkwabbit · Post by **pinkwabbit** » Thu May 18, 2006 4:27 pm

I can't really help on that, because when I tried to restore everything to default settings I looked for an automated way to do it as much as possible. Here's what I remember:

For Speech Recognition, I had it switched on (so the little circle with the microphone in the top half of it appears), set to Push To Talk, and had changed the listening key to the tilde ("~"). I do remember fiddling with the "Text to Speech" tab and playing with the settings, but I don't think I left anything switched on.

While trying to restore the Universal Access settings, I think I unchecked "Enable access for assistive devices". I also poked around "Voiceover Utility", and I did click "Reset..." just now while trying to fix it. Didn't poke in "Zoom" or "Display". Also didn't play with Hearing, Keyboard or Mouse.

That's all I can really remember. Hope it helps!

I don't think Speech Recognition by itself causes problems, as I'd been using it for at least a fortnight without any issues.

Post by **Catfish_Man** » Thu May 18, 2006 4:37 pm

pinkwabbit wrote: Just curious: how did you know what was wrong?

crash log wrote:2006-05-15 19:49:56.106 Adium[10730] Caught exception: NSAccessibilityException - "AXVisibleChildren" attribute unsupported by: <NSScrollView: 0x4b7ce0>

"Accessibility" is the term for the various speech recognition/handicapped access/etc... functionality in OSX, and AX is the prefix that it's known by internally. Combine that with the fact that we've had issues with it before, and it was fairly clear what was happening

It's quite possible that this will be improved by one of our Summer of Code students.