
** (process:39077): CRITICAL **: purple_eventloop_get_ui_ops: assertion `eventloop_ui_ops != NULL' failed It mostly works great, but ever since Leopard, Adium crashes about half the time on startup when the Skype plugin is installed:Įxception Codes: KERN_PROTECTION_FAILURE at 0x0000000000000000Ġ libpurple 0x07e0dfcf purple_blist_add_group + 130ġ libpurple 0x07f1a3b8 purple_ssi_parselist + 2383Ħ libpurple 0x07f09c04 flap_connection_recv_cb + 742ħ 0x92c12920 _CFSocketDoCallback + 640Ĩ 0x92c13f55 _CFSocketPerformV0 + 133ĩ 0x92c0960e CFRunLoopRunSpecific + 3166ġ0 0x92c09cf8 CFRunLoopRunInMode + 88ġ1 0x91822da4 RunCurrentEventLoopInMode + 283ġ2 0x9190d411 RunCurrentEventLoop + 65ġ3 0x011ddf8a IsSkypeAvailable + 90ġ4 0x011de0ac ConnectToSkype + 42ġ5 0x011e0d19 skype_login + 214 I think you should really concider getting rid of this absolutely unnecessary and annoying 'answer' window. when there are many calls, but it also one can really get cross when each time has to close the plug-in window because of the bug. Not only does it keep confusing and gets in your way esp. I think you should really get rid of that "answer the call" window. I must admit this is very annoying, especially when I get many calls. But here I get next unpleasant surprise: in addition to unnecessary multiple choice, there is a bug - even if I take the call the plug-in window stays on, still asking me if I want to answer. Because Skype bezel is really nice and faster I use it to answer the call.
#ADIUM CHAT LOGS WINDOWS#
The result is I have a call and I get 2 windows that let me answer it. But Skype shows the 'answer or reject' bezel in the first place. Whenether receive get a call via Skype, the plug-in shows the 'answer the call' window. Sorry I blamed your fantastic plug-in.Īnyway, there is one thing in the plug-in behaviour that I don't understand and I reckon it unnecessarily gets in one's way. And thanks for the explanation that it was not plug-in's fault, but Adium's. Thanks for the tip, it worked flawlessly. If the transfer issue could be solved, the plugin would be perfect! I have resorted to transfer by email again, as this plugin is too useful to want to disable it.

This is a shame as we can't actually tell which transfers are actually going through and if the one that just sits there will do so indefinitely and whether it is actually taking up bandwidth trying to transfer.

If you try to quite Adium - which is the only way to get rid of it as the x stop icon doesn't functiion - Adium will report that a file transfer is in progress and ask for confirmation of the quit. However, the first transfer item in the window just sits there saying that it's waiting to start. The Sype API Plugin is producing odd behaviour with file tranfers - both transfers in and out.Įach time we get two file transfers, the second of which seems to function normally - though Adium actually reports that the transfer was cancelled by the receiver even though they didn't. s/he referred to a Trac Adium ticket number, but I thought it might be helpful to pull the information into this list of comments.

Genba posted a reference to a problem which I am also experiencing.
