cocoaforge

If I log out from an account, the account gets logged out but the menu option to login again always stays as "disconnect". Sometimes even the buddy list doesn't change even though I'm logged out. Same thing with the disconnect button in the accounts pane. Click disconnect, it never changed to connect. The only way to log back in is to quit adium.

Example: I have two AIM, 1 Jabber, and 1 Yahoo account. Connect to all. Select disconnect from the Jabber account, the buddy list cleared but there's no way to log back in as th emenu option still says disconnect. Same thing with other accounts. Once in a while it works, there's no pattern that I've found yet. The only way to deal with multiple accounts is to quit Adium and restart it. This is not acceptable even for a dot version release.

What version of Adium? What sort of internet connection? Does "disconnect all" work? Does this ALWAYS happen on ALL services?

dturley wrote: This is not acceptable even for a dot version release.

Be nice, please. This sort of comment only angers people, and doesn't help anyone.

This was first reported for 0.72, still there in .73.

To repeat:
Select File -> Connect All
connects to 2 AIM, 1 Jabber, 1 Yahoo account
Select File -> Disconnect All
buddy list empties. File menu still lists "disconnect option for Jabber and Yahoo accounts. No accounts can be reconnected unless Adium is quit and restarted.

Same results with cable connection at home, and T3 at work.

Consistent through 10.3.5, 10.3.6, and 10.3.7 upgrades.

What other info can I provide?

Truly bizarre! Try this: Go to ~/Library/Application Support/Adium 2.0/Users/Default/ and move the Accounts folder, and Accounts.plist, somewhere else (don't delete them). Reopen Adium -- you will have to re-add your accounts. Does the weirdness still happen? If no, you're set. If yes, move those files back where they were and post again.

I removed the entire Adium 2.0 folder and setup Adium again. Added jabber, aim, and yahoo accounts (1 each). Select connect all, they connect. Select disconnect all, jabber buddy list empties, aim buddies stay listed but can't be contacted. (no yahoo buddies listed as online) All menu options still say "disconnect" so I can't do anything further until I quit and restart Adium. Tried same accounts with Proteus and all works; I can disconnect and reconnect all or individually with no problems.

I guess there's no solution. :-(

Not that you care, but the issue still exists in .74

Adium has this bug, Proteus site has been offline since Dec. 24. IM situation for the Mac is pathetic.

That's one way to encourage help.

Nobody on our side of the fence can reproduce this issue.

What is your network setup? What's your computer?

dturley wrote:Not that you care, but the issue still exists in .74

Adium has this bug, Proteus site has been offline since Dec. 24. IM situation for the Mac is pathetic.

Your attitude is pathetic. Did you skip the day in school were they taught tact? Honestly.

"Fix my bug or I'll insult you." == (NOT) classy

dturley wrote:Adium has this bug, Proteus site has been offline since Dec. 24. IM situation for the Mac is pathetic.

I've used Adium for years and I don't have any problems with it at all. Obviously the IM situation on the Mac is not pathetic. Quit overreacting .

You could argue that it's better on the Mac than on Windows, but I've never used Trillian so that's not really fair to say.

I apologize for my lack of "tack". I was (am) frustrated at configuring numerous IM clients and finding yet another issue with each. In nine years, I don't recall having such an experience with Mac OS. (Anyone remember Open Transport with the first PPC Mac? Even that wasn't as frustrating.) No personal insult to the devs was intended.

I've moved across networks without a change in this issue. I'm curious, what version of jabber server is being used to test. I'm hitting a server that I believe was upgraded to the most recent release (query being made.) None of the the other clients have issues disconnecting.

I still keep playing with Adium to try and make it work. But I am concluding that it's an exercise in futility.

dturley wrote:I've moved across networks without a change in this issue. I'm curious, what version of jabber server is being used to test. I'm hitting a server that I believe was upgraded to the most recent release (query being made.) None of the the other clients have issues disconnecting.

It's not just a Jabber issue, though, eh? In any case, we generally test using jabber.org.

I still keep playing with Adium to try and make it work. But I am concluding that it's an exercise in futility.

It's frustrating over here, too, with a problem to which we can't propose a solution since we can't even reproduce it.

What I've discovered it that once I try to disconnect from jabber, any accounts listed after the jabber account in the account prefs hang as well. If I move the jabber account to last in the list, the rest will disconnect. Looking more and more like adium is not getting something it needs from the server to change the menu, and it hangs changing the menues of any further accounts. All the accounts actually get disconnected, but they can't be reconnected since all the menues and dialogues still show them as connected. I've also made inquiries to the jabber sys admin.

Once last post, then I'll go away :-)

I convinced the jabber server admin to reboot the jabber daemon. This seems to a have cured the hanging disconnect, as least for now. I'm a liitle cautious since I know the server has been bounced since I saw this issue with 0.73. No other clients for Mac, Linux, or Windows have had this problem.

I thank the devels for their patience thru my outrages. :-) As I said, I'm cautious, but hopeful to move away from Proteus. I'd like to have a solution as to the issue with Adium, but I don't see it coming, especially if it's working now. FWIW, the jabber version is 2.0s5.

dturley wrote:What I've discovered it that once I try to disconnect from jabber, any accounts listed after the jabber account in the account prefs hang as well. If I move the jabber account to last in the list, the rest will disconnect. Looking more and more like adium is not getting something it needs from the server to change the menu, and it hangs changing the menues of any further accounts. All the accounts actually get disconnected, but they can't be reconnected since all the menues and dialogues still show them as connected. I've also made inquiries to the jabber sys admin.

Now we're getting somewhere! That's bizarre; there really shouldn't be any order dependency, though clearly there is. My guess is that the account communication thread was hanging on the Jabber disconnect, so none of the others were able to be processed. At least that, along with your next post, explains why none of us were able to reproduce it -- it was an issue specific to your local Jabber server interacting with Adium for some reason, not an issue with all accounts.

I convinced the jabber server admin to reboot the jabber daemon. This seems to a have cured the hanging disconnect, as least for now. I'm a liitle cautious since I know the server has been bounced since I saw this issue with 0.73. No other clients for Mac, Linux, or Windows have had this problem ... As I said, I'm cautious, but hopeful to move away from Proteus.

So Proteus does work? They use the same libgaim protocol core as we do. Interesting. If it happens again, we'll get you a debug build to try to narrow down just what's going on with your Jabber connection.

Yes, Proteus and Psi would disconnect just fine during all this. Whatever the server issue is/was, it only affected Adium. Actually I was quite relieved when I discovered the account order issue. I've also setup a jabber account on a public server to eliminate anything specfic to my computer.

Right now I'm annoying my contacts because I am signing on and off frequently just to test. :-) If the situation arises again, I'll apply for the debug version.

dturley wrote:Yes, Proteus and Psi would disconnect just fine during all this. Whatever the server issue is/was, it only affected Adium. Actually I was quite relieved when I discovered the account order issue. I've also setup a jabber account on a public server to eliminate anything specfic to my computer.

For clarification: So it was happening on all Jabber servers, not just your local one? Or you're testing on a public server now?

I tested on a public server, it was working. So the issues was something that Adium didn't like from our server alone, BUT that the other clients did not have a problem with. At this point it's working so I can't debug further.