cocoaforge

So eah. I absolutely love adium and cant imagine using any other messenger. can someone please help. every time i open adium is says quit unexpectedly and then reboots and its on going. i tried deleting and reinstalling and that did not help. i dont know what to do . i seem to be out of my own solutions. can someone please help? ill post the error message here

Process: Adium [426]
Path: /Applications/Adium.app/Contents/MacOS/Adium
Identifier: com.adiumX.adiumX
Version: 1.3.1 (1.3.1)
Code Type: X86 (Native)
Parent Process: launchd [62]

Date/Time: 2008-09-14 15:56:37.326 -0700
OS Version: Mac OS X 10.5.2 (9C2028)
Report Version: 6

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

Dyld Error Message:
Symbol not found: __CSAOSCopyStringForKey
Referenced from: /System/Library/Frameworks/AddressBook.framework/Versions/A/AddressBook
Expected in: /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices

Model: MacBook4,1, BootROM MB41.00C1.B00, 2 processors, Intel Core 2 Duo, 2.1 GHz, 1 GB
Graphics: kHW_IntelGMA965Item, GMA X3100, spdisplays_builtin, 144 MB
Memory Module: BANK 0/DIMM0, 512 MB, DDR2 SDRAM, 667 MHz
Memory Module: BANK 1/DIMM1, 512 MB, DDR2 SDRAM, 667 MHz
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0x88), Broadcom BCM43xx 1.0 (4.170.46.9)
Bluetooth: Version 2.1.0f16, 2 service, 1 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: Hitachi HTS542512K9SA00, 111.79 GB
Parallel ATA Device: MATSHITACD-RW CW-8221
USB Device: iPod, Apple Inc., high_speed, 500 mA
USB Device: Built-in iSight, Micron, high_speed, 500 mA
USB Device: Apple Internal Keyboard / Trackpad, Apple Computer, full_speed, 500 mA
USB Device: IR Receiver, Apple Computer, Inc., low_speed, 500 mA
USB Device: Bluetooth USB Host Controller, Apple, Inc., full_speed, 500 mA

Please upgrade to the latest release of OS X.

i should have it and where do i do that if not? i am new to mac sorry

Apple menu -> Software Update

You're running 10.5.2 currently, the newest is 10.5.4.

i have the same problem and im running the latest 10.5.4

this is my error

Process: Adium [3854]
Path: /Applications/Adium.app/Contents/MacOS/Adium
Identifier: com.adiumX.adiumX
Version: 1.3.1 (1.3.1)
Code Type: X86 (Native)
Parent Process: launchd [72]

Date/Time: 2008-09-15 11:52:38.565 +0100
OS Version: Mac OS X 10.5.4 (9E25)
Report Version: 6

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 0

Wesjones wrote:this is my error

Process: Adium [3854]
Path: /Applications/Adium.app/Contents/MacOS/Adium
Identifier: com.adiumX.adiumX
Version: 1.3.1 (1.3.1)
Code Type: X86 (Native)
Parent Process: launchd [72]

Date/Time: 2008-09-15 11:52:38.565 +0100
OS Version: Mac OS X 10.5.4 (9E25)
Report Version: 6

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 0

"KERN_PROTECTION_FAILURE" tells me it's something more messed up on your system than we have control over.

Edit: This was wrong, I was not thinking well enough: this is just dereferencing a NULL pointer.

its a brand new machine, plus new to the world of mac? is there something i can try?

this only seems to happen when connecting to msn using http, if i use facebook its fine?

Is that the full extent of the crash log?

http://trac.adiumx.com/wiki/ReportingBugs

Sorry this is the full message which is long,

Process: Adium [212]
Path: /Applications/Adium.app/Contents/MacOS/Adium
Identifier: com.adiumX.adiumX
Version: 1.3.1 (1.3.1)
Code Type: X86 (Native)
Parent Process: launchd [142]

Date/Time: 2008-09-16 07:28:55.001 +0100
OS Version: Mac OS X 10.5.4 (9E25)
Report Version: 6

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 0

Thread 0 Crashed:
0 libpurple 0x1772dc62 read_impl + 389
1 libpurple 0x1772b5a5 pecan_node_read + 50
2 libpurple 0x1772ceea read_cb + 220
3 libglib 0x175a7832 g_io_unix_dispatch + 137
4 libglib 0x17568506 g_main_dispatch + 498
5 libglib 0x17569aa8 g_main_context_dispatch + 138
6 libglib 0x1756a033 g_main_context_iterate + 1312
7 libglib 0x1756a273 g_main_context_iteration + 163
8 com.apple.CoreFoundation 0x940639c2 __CFRunLoopDoObservers + 466
9 com.apple.CoreFoundation 0x94064d32 CFRunLoopRunSpecific + 866
10 com.apple.CoreFoundation 0x94065cf8 CFRunLoopRunInMode + 88
11 com.apple.HIToolbox 0x9021fda4 RunCurrentEventLoopInMode + 283
12 com.apple.HIToolbox 0x9021fbbd ReceiveNextEventCommon + 374
13 com.apple.HIToolbox 0x9021fa31 BlockUntilNextEventMatchingListInMode + 106
14 com.apple.AppKit 0x95dd7505 _DPSNextEvent + 657
15 com.apple.AppKit 0x95dd6db8 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 128
16 com.apple.AppKit 0x95dcfdf3 -[NSApplication run] + 795
17 com.apple.AppKit 0x95d9d030 NSApplicationMain + 574
18 com.adiumX.adiumX 0x00002dc2 0x1000 + 7618
19 com.adiumX.adiumX 0x00002ce9 0x1000 + 7401

Thread 1:
0 libSystem.B.dylib 0x95c154a6 mach_msg_trap + 10
1 libSystem.B.dylib 0x95c1cc9c mach_msg + 72
2 com.apple.CoreFoundation 0x940650ce CFRunLoopRunSpecific + 1790
3 com.apple.CoreFoundation 0x94065cf8 CFRunLoopRunInMode + 88
4 com.apple.audio.CoreAudio 0x90c2d464 HALRunLoop::OwnThread(void*) + 160
5 com.apple.audio.CoreAudio 0x90c2d300 CAPThread::Entry(CAPThread*) + 96
6 libSystem.B.dylib 0x95c466f5 _pthread_start + 321
7 libSystem.B.dylib 0x95c465b2 thread_start + 34

Thread 2:
0 libSystem.B.dylib 0x95c154a6 mach_msg_trap + 10
1 libSystem.B.dylib 0x95c1cc9c mach_msg + 72
2 com.apple.CoreFoundation 0x940650ce CFRunLoopRunSpecific + 1790
3 com.apple.CoreFoundation 0x94065cf8 CFRunLoopRunInMode + 88
4 com.apple.CFNetwork 0x9431ea32 CFURLCacheWorkerThread(void*) + 396
5 libSystem.B.dylib 0x95c466f5 _pthread_start + 321
6 libSystem.B.dylib 0x95c465b2 thread_start + 34

Thread 3:
0 libSystem.B.dylib 0x95c7f07a __workq_ops + 10
1 libSystem.B.dylib 0x95c7f0aa start_wqthread + 30

Thread 4:

Thread 5:
0 libSystem.B.dylib 0x95c655e2 select$DARWIN_EXTSN + 10
1 libSystem.B.dylib 0x95c466f5 _pthread_start + 321
2 libSystem.B.dylib 0x95c465b2 thread_start + 34

Thread 6:
0 libSystem.B.dylib 0x95c154a6 mach_msg_trap + 10
1 libSystem.B.dylib 0x95c1cc9c mach_msg + 72
2 com.apple.CoreFoundation 0x940650ce CFRunLoopRunSpecific + 1790
3 com.apple.CoreFoundation 0x94065cf8 CFRunLoopRunInMode + 88
4 com.apple.Foundation 0x9228f460 +[NSURLConnection(NSURLConnectionReallyInternal) _resourceLoadLoop:] + 320
5 com.apple.Foundation 0x9222bf1d -[NSThread main] + 45
6 com.apple.Foundation 0x9222bac4 __NSThread__main__ + 308
7 libSystem.B.dylib 0x95c466f5 _pthread_start + 321
8 libSystem.B.dylib 0x95c465b2 thread_start + 34

Thread 7:
0 libSystem.B.dylib 0x95c1c68e __semwait_signal + 10
1 libSystem.B.dylib 0x95c4736d pthread_cond_wait$UNIX2003 + 73
2 libGLProgrammability.dylib 0x945c7432 glvmDoWork + 162
3 libSystem.B.dylib 0x95c466f5 _pthread_start + 321
4 libSystem.B.dylib 0x95c465b2 thread_start + 34

Thread 8:
0 libSystem.B.dylib 0x95c15506 semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x95c4784f _pthread_cond_wait + 1244
2 libSystem.B.dylib 0x95c490d3 pthread_cond_timedwait_relative_np + 47
3 com.apple.Foundation 0x92271e8c -[NSCondition waitUntilDate:] + 236
4 com.apple.Foundation 0x92271ca0 -[NSConditionLock lockWhenCondition:beforeDate:] + 144
5 com.apple.Foundation 0x92271c05 -[NSConditionLock lockWhenCondition:] + 69
6 com.apple.AppKit 0x95e3d470 -[NSUIHeartBeat _heartBeatThread:] + 753
7 com.apple.Foundation 0x9222bf1d -[NSThread main] + 45
8 com.apple.Foundation 0x9222bac4 __NSThread__main__ + 308
9 libSystem.B.dylib 0x95c466f5 _pthread_start + 321
10 libSystem.B.dylib 0x95c465b2 thread_start + 34

Thread 9:
0 libSystem.B.dylib 0x95c1c68e __semwait_signal + 10
1 libSystem.B.dylib 0x95c4736d pthread_cond_wait$UNIX2003 + 73
2 com.apple.QuartzCore 0x926c6e51 fe_fragment_thread + 54
3 libSystem.B.dylib 0x95c466f5 _pthread_start + 321
4 libSystem.B.dylib 0x95c465b2 thread_start + 34

Thread 10:
0 libSystem.B.dylib 0x95c15506 semaphore_timedwait_signal_trap + 10
1 libSystem.B.dylib 0x95c4784f _pthread_cond_wait + 1244
2 libSystem.B.dylib 0x95c490d3 pthread_cond_timedwait_relative_np + 47
3 ...ple.CoreServices.CarbonCore 0x94d2f1ba TSWaitOnConditionTimedRelative + 246
4 ...ple.CoreServices.CarbonCore 0x94d2ef9a TSWaitOnSemaphoreCommon + 422
5 ...ickTimeComponents.component 0x92ec3dee ReadSchedulerThreadEntryPoint + 4724
6 libSystem.B.dylib 0x95c466f5 _pthread_start + 321
7 libSystem.B.dylib 0x95c465b2 thread_start + 34

Thread 11:
0 libSystem.B.dylib 0x95c154e2 semaphore_wait_trap + 10
1 ...ickTimeComponents.component 0x93552c6e QTThreadWaitSignal + 100
2 ...ickTimeComponents.component 0x92f4fdc5 audioprepThreadEntry + 92
3 ...ickTimeComponents.component 0x93552a2c start_thread + 54
4 libSystem.B.dylib 0x95c466f5 _pthread_start + 321
5 libSystem.B.dylib 0x95c465b2 thread_start + 34

Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0x1772daee ecx: 0x00000000 edx: 0x00000003
edi: 0x18385e58 esi: 0x18385e50 ebp: 0xbfffc9d8 esp: 0xbfffc8e0
ss: 0x0000001f efl: 0x00010282 eip: 0x1772dc62 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0x00000000

also have tired the software on my old mac book pro and has the same message, must be a problem with the http part,

Wes

I have this exact same issue, very frustrating as Adium is my preferred messenger solution. Definitely an issue with 1.3.1, I am at 10.5.5 and this was an issue with the Adium upgrade not the OS X patch.

Process: Adium [456]
Path: /Applications/Adium.app/Contents/MacOS/Adium
Identifier: com.adiumX.adiumX
Version: 1.3.1 (1.3.1)
Code Type: PPC (Native)
Parent Process: launchd [131]

Date/Time: 2008-09-16 10:38:49.540 +0100
OS Version: Mac OS X 10.5.5 (9F33)
Report Version: 6

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 0

Thread 0 Crashed:
0 libpurple 0x17357608 read_impl + 428
1 libpurple 0x173549d0 pecan_node_read + 84
2 libpurple 0x1735675c read_cb + 204
3 libglib 0x17128a04 g_io_unix_dispatch + 196
4 libglib 0x170cfdfc g_main_dispatch + 676
5 libglib 0x170d1dbc g_main_context_dispatch + 212
6 libglib 0x170d2570 g_main_context_iterate + 1792
7 libglib 0x170d28dc g_main_context_iteration + 240
8 com.apple.CoreFoundation 0x951a7f74 __CFRunLoopDoObservers + 456
9 com.apple.CoreFoundation 0x951a912c CFRunLoopRunSpecific + 728
10 com.apple.HIToolbox 0x922c4d44 RunCurrentEventLoopInMode + 264
11 com.apple.HIToolbox 0x922c4ad0 ReceiveNextEventCommon + 260
12 com.apple.HIToolbox 0x922c49a8 BlockUntilNextEventMatchingListInMode + 84
13 com.apple.AppKit 0x961cfe18 _DPSNextEvent + 596
14 com.apple.AppKit 0x961cf7d0 -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] + 112
15 com.apple.AppKit 0x961c948c -[NSApplication run] + 736
16 com.apple.AppKit 0x96199e90 NSApplicationMain + 440
17 com.adiumX.adiumX 0x00003690 0x1000 + 9872
18 com.adiumX.adiumX 0x00003394 0x1000 + 9108

Thread 1:
0 libSystem.B.dylib 0x92ca84b8 semaphore_timedwait_signal_trap + 8
1 libSystem.B.dylib 0x92ceb8fc _pthread_cond_wait + 1320
2 ...apple.AddressBook.framework 0x95e5c570 -[ABRemoteImageLoader workLoop] + 184
3 com.apple.Foundation 0x94c2ab78 __NSThread__main__ + 1004
4 libSystem.B.dylib 0x92cea658 _pthread_start + 316

Thread 2:
0 libSystem.B.dylib 0x92d0cae4 select$DARWIN_EXTSN + 12
1 com.apple.CoreFoundation 0x951b49b0 __CFSocketManager + 764

Thread 0 crashed with PPC Thread State 32:
srr0: 0x17357608 srr1: 0x0200f030 dar: 0x00000000 dsisr: 0x40000000
r0: 0x00000000 r1: 0xbfffc220 r2: 0x00000000 r3: 0x00000000
r4: 0x00000003 r5: 0x00000008 r6: 0x0000524b r7: 0x00000007
r8: 0x004fc080 r9: 0xa04cd074 r10: 0x003f201c r11: 0xa0498898
r12: 0x92cb373c r13: 0x00000000 r14: 0xa08e6478 r15: 0x00000000
r16: 0x00000000 r17: 0xbfffe650 r18: 0xbfffe670 r19: 0x0040eb40
r20: 0x0040ec40 r21: 0x00000004 r22: 0x00000000 r23: 0x0040ec48
r24: 0xbfffe670 r25: 0x00000003 r26: 0x00000002 r27: 0xbfffe678
r28: 0x18059f98 r29: 0x175a4020 r30: 0xbfffc220 r31: 0x17357474
cr: 0x44042228 xer: 0x00000000 lr: 0x173575fc ctr: 0x92cb373c
vrsave: 0x00000000

So I had 1 MSN account that was set up to talk over HTTP. I opened Adium, went 'offline' and then reset the account to use my local SOCKS proxy instead. Adium now behaving again.

i dont have a socks proxy, i only use http, at work

Hi all -

Let me say to the 2 Adium Devs that replied to this issue: PLEASE read your TRAK issues list before telling someone to update their OS for a known, documented, accepted, and in progress bug.

I reported this the day 1.3.1 released, and as far as I can tell from reading through the bug trak, I'm one of MANY MANY MANY users experiencing a crash with Adium while using MSN over HTTP.

And hey lookit that - while I was typing this message, and without any intervention at all - Adium crashed out (TWICE!) while using MSN over HTTP -- which is the ONLY method available to MANY MANY users, like myself, who are locked down behind corporate firewalls that do not tunnel and only accept HTTP.

So ..

It crashes. It's not the OS. It's a bug with msn-pecan. 1.2.7 did not do this.

Check bug #11023 and related. (http://trac.adiumx.com/ticket/11023)

Sorry to be snippy, but I don't like seeing new users treated to the runaround on a known and documented issue like that.

P

Penumbra wrote:Hi all -

Let me say to the 2 Adium Devs that replied to this issue: PLEASE read your TRAK issues list before telling someone to update their OS for a known, documented, accepted, and in progress bug.

I reported this the day 1.3.1 released, and as far as I can tell from reading through the bug trak, I'm one of MANY MANY MANY users experiencing a crash with Adium while using MSN over HTTP.

And hey lookit that - while I was typing this message, and without any intervention at all - Adium crashed out (TWICE!) while using MSN over HTTP -- which is the ONLY method available to MANY MANY users, like myself, who are locked down behind corporate firewalls that do not tunnel and only accept HTTP.

So ..

It crashes. It's not the OS. It's a bug with msn-pecan. 1.2.7 did not do this.

Check bug #11023 and related. (http://trac.adiumx.com/ticket/11023)

Sorry to be snippy, but I don't like seeing new users treated to the runaround on a known and documented issue like that.

P

Obviously your reading comprehension is lacking.
has nothing to do with that ticket. Responses are not randomly placed throughout the thread.

zac wrote:

Penumbra wrote:Hi all -

Let me say to the 2 Adium Devs that replied to this issue: PLEASE read your TRAK issues list before telling someone to update their OS for a known, documented, accepted, and in progress bug.

I reported this the day 1.3.1 released, and as far as I can tell from reading through the bug trak, I'm one of MANY MANY MANY users experiencing a crash with Adium while using MSN over HTTP.

And hey lookit that - while I was typing this message, and without any intervention at all - Adium crashed out (TWICE!) while using MSN over HTTP -- which is the ONLY method available to MANY MANY users, like myself, who are locked down behind corporate firewalls that do not tunnel and only accept HTTP.

So ..

It crashes. It's not the OS. It's a bug with msn-pecan. 1.2.7 did not do this.

Check bug #11023 and related. (http://trac.adiumx.com/ticket/11023)

Sorry to be snippy, but I don't like seeing new users treated to the runaround on a known and documented issue like that.

P

Obviously your reading comprehension is lacking.

Code: Select all

Dyld Error Message:
Symbol not found: __CSAOSCopyStringForKey
Referenced from: /System/Library/Frameworks/AddressBook.framework/Versions/A/AddressBook
Expected in: /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices

has nothing to do with that ticket. Responses are not randomly placed throughout the thread.

True, when talking about the O.P. I skimmed to the full crash log, which isn't the same crash - so maybe we both lack reading comprehension skills? The above crash IS related - and thank you for editing down your quick-hit to Wes. I think that's what set me off.

P

Penumbra wrote:True, when talking about the O.P. I skimmed to the full crash log, which isn't the same crash - so maybe we both lack reading comprehension skills?

Code: Select all

Date/Time: 2008-09-16 10:38:49.540 +0100
OS Version: Mac OS X 10.5.5 (9F33)
Report Version: 6

Exception Type: EXC_BAD_ACCESS (SIGBUS)
Exception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000
Crashed Thread: 0

Thread 0 Crashed:
0 libpurple 0x17357608 read_impl + 428
1 libpurple 0x173549d0 pecan_node_read + 84

The above crash IS related - and thank you for editing down your quick-hit to Wes. I think that's what set me off.

P

Correct, and neither myself nor CFM have responded to that crash log being posted. Are you really unsure of the order of posts here? I edited that post—which was based on a very partial log—after I responded to you just now. It's definitely not what set you off.

I try to re-read the posts before I submit, especially when I've been accused of not paying attention so I saw your edit while I was posting - and made my thanks..

I mean.. It's just multi-tasking, right? lol

"KERN_PROTECTION_FAILURE" tells me it's something more messed up on your system than we have control over.

The above was what made me think "OMG.. Doesn't anyone read the Trak!?" -- Sorry for the miscommunication, wanna keep the sarcasm and bitterness going some more, or are we done?

P