Adium

Adium 1.1 crash on launch

For many people, Adium 1.1 is crashing on launch (specifically, at the moment where it automatically updates). We’ve had a few reports of this happening to 1.0.5 people as well, but almost all the reports now are from people who are fresh off of 1.0.5, on their first launch of 1.1.

We have a ticket on this: it’s #7542. This bug is already confirmed. We do not need more tickets nor any statements that you have the bug too. What we do need is help tracking down the bug.

We know that the problem is with our automatic updater, but we need help from people who are able to reproduce this issue in order to track it down precisely.

Right now, as I write this, I’m compiling a debug version of Adium that we’ll distribute to a few people on the IRC channel. If you have programmer skills and a working installation of Xcode 2.4.x, we invite you to drop in and help us step up to the bug. We have no reason to believe that this version is fixed; this is a debugging version. If you don’t have programmer skills, using the debug version will not help anything—we certainly hope that it still has the bug, so that we can find the bug and fix it.

So if you fit the above criteria, please come by and help us out. We would appreciate it.

7 Responses to “Adium 1.1 crash on launch”

  1. Anonymous Says:

    For what it’s worth:

    Until the devs get this sorted out, you can still get Adium to work if you prevent it from contacting the host “duck.adiumx.com”

    I use Little Snitch, but an entry in the /etc/hosts should work just as well (point it at 127.0.0.1).

    When Adium fails to contact the update server, it will then be able to connect to your IM accounts.

    Hope this helps.

  2. raj Says:

    Ok, I downloaded this version and it still crashes on me. I can enter the debugger. What type of information would be helpful?
    Here’s a stack backtrace:
    #0 0x90a594c0 in objc_msgSend ()
    #1 0x00542fe0 in ?? ()
    #2 0x001e2881 in -[SUUpdater newVersionAvailable] ()
    #3 0x001e2c04 in -[SUUpdater appcastDidFinishLoading:] ()
    #4 0x9280e3fd in __NSFireMainThreadPerform ()
    #5 0×90860389 in __CFRunLoopPerformPerform ()
    #6 0x9082d05a in CFRunLoopRunSpecific ()
    #7 0x9082cace in CFRunLoopRunInMode ()
    #8 0x92ded8d8 in RunCurrentEventLoopInMode ()
    #9 0x92decfe2 in ReceiveNextEventCommon ()
    #10 0x92dece39 in BlockUntilNextEventMatchingListInMode ()
    #11 0×93293465 in _DPSNextEvent ()
    #12 0×93293056 in -[NSApplication nextEventMatchingMask:untilDate:inMode:dequeue:] ()
    #13 0x9328cddb in -[NSApplication run] ()
    #14 0x93280d2f in NSApplicationMain ()
    #15 0x000025ee in _start ()
    #16 0×00002515 in start ()

  3. Matt Wood Says:

    Adium was working fine. I updated OSX using the regular system updates, that occurred recently, and Adium stopped working.

  4. Mick Says:

    It stopped working for me today. I’m using 1.0.5 on Intel with OS 10.4.10.

  5. Anonymous Says:

    The /etc/host things works (after re-applying the network config), thanks! But only with 1.1. 1.0.4 still crashes.

    I also have the impression it’s something to do with a recent system update.

  6. Anonymous Says:

    running adium noticed me about an update. after it no response. console says
    dyld: /Applications/Adium.app/Contents/MacOS/Adium can’t open library: /System/Library/Frameworks/Quartz.framework/Versions/A/Quartz (No such file or directory, errno = 2)
    when i try to start adium.
    don’t know what that means, i’m new to mac.
    mac os x 10.3.9

  7. Anonymous Says:

    addition: adium version 1.1.1