Adium

Ticket #898 (closed defect: fixed)

Opened 3 years ago

Last modified 3 years ago

Jabber account does not automatically connect on launch.

Reported by: daved@tamu.edu Assigned to: evands
Priority: normal Milestone: Adium X 0.85
Component: Adium Core Version: 0.82
Severity: normal Keywords:
Cc: Patch:
Pending:

Description

I have selected 'Automatically connect on launch' for my Jabber account but the account does not connect when Adium is launched. Connecting manually works fine. All other accounts that have this option selected do connect on launch.

Change History

07/14/2005 07:40:49 AM changed by anonymous

My Adium doesn't connect to any of my accounts (AIM, Yabber, MSN, Yahoo, ICQ, Bonjour) since i have installed 0.83b1. I have to manually connect them. PowerBook G4, 768 MB Ram. Mac OS X 10.3.9

07/14/2005 06:02:08 PM changed by tedger

  • status changed from new to closed.
  • resolution set to duplicate.
  • component changed from Jabber to Adium Core.

Do a search this is a duplicate ticket it happens for all services not just jabber.

08/14/2005 12:27:11 AM changed by anonymous

I'm updating this one since a search on what I thought was obvious (the text from the config dialog "automatically connect on launch") did not show which one should be the original problem report and the number of the other report was not added to this one to make it explicit. Expanding the search terms results in many that complain of reconnecting after sleep/etc but I have not located the intended original of the dup.

I'm having the same problem. The last version that worked as expected was 0.80. I have checked both 0.81 and 0.82 and see the same problem with both.

08/24/2005 09:39:45 AM changed by daved@tamu.edu

  • status changed from closed to reopened.
  • resolution deleted.

I finally got back to dealing with this issue, sorry for the delay. I, as well, could not find the duplicate bug report(s). I looked very hard before submitting. I would be nice if one could point us at a ticket he was thinking so I could have confirmed that it was duplicate.

In any event, I have found workaround and hopefully this will show you guys where the problem is in the code. If you create an account for Jabber where the domain does not have an IP address, the account will not automatically connect on startup. In my case, that is tamu.edu. The actual server is jabber.tamu.edu. The workaround is to add the domain to your host file so it resolves to an IP and Adium will automatically connect on startup. I have confirmed that this is still in .83 as well.

08/27/2005 01:35:20 PM changed by evan@adiumx.com

How does your Jabber account connect at all if the server can't be resolved from the name?

08/27/2005 03:06:02 PM changed by daved@tamu.edu

The connect server is jabber.tamu.edu. The ids are daved@tamu.edu. The domain tamu.edu does not have an IP address.

08/27/2005 06:17:24 PM changed by evands

  • owner changed from nobody to evands.
  • status changed from reopened to new.
  • milestone set to Adium X 0.85.

Ah! Okay, then :)

Description of the fix: -[ESGaimJabberAccount host] should return the connect server if specified, otherwise should return the host as determined from the user ID.

08/29/2005 09:38:03 PM changed by evands

  • status changed from new to closed.
  • resolution set to fixed.

(In [13289]) Fixed -[ESGaimJabberAccount host] to return the connect host if applicable and otherwise to return the name determined from the jabber ID as before. This fixes issues with autoconnect of Jabber accounts and therefore fixes #898

08/29/2005 09:56:01 PM changed by evands

(In [13290]) Merged [13289]: Fixed -[ESGaimJabberAccount host] to return the connect host if applicable and otherwise to return the name determined from the jabber ID as before. This fixes issues with autoconnect of Jabber accounts and therefore fixes #898