Adium

Ticket #6470 (closed defect: invalid)

Opened 3 years ago

Last modified 21 months ago

Adium hides GTalk contact from iChat

Reported by: hsivonen Owned by: nobody
Milestone: Component: Service/Google Talk
Version: 1.0.2 Severity: normal
Keywords: Cc:
Patch Status:

Description

Problem: When a GTalk user logs in using Adium, he disappears from my iChat contacts. When he is offline, iChat shows his buddy entry to me in iChat.

Unfortunately, I cannot figure out steps to reproduce.

Additional information:

  • This is not a problem with all GTalk users using Adium.
  • This is not a simple GTalk problem: everything works fine if we both use iChat.
  • This is specific to the Adium-iChat combination. The GTalk users shows up fine if we both use Adium or if he uses Adium and I use the Telepathy-based Jabber client of Nokia 770.
  • My Jabber account is not a GTalk account.
  • We have tried reauthorization with different client combinations and directions about a dozen times.
  • The GTalk user has tried creating a fresh account entry in Adium.

Change History

Changed 3 years ago by pausanias

I can fully verify all the claims of this bug. As long as the buddy is logged out, or logged into GTalk directly from gmail.com, the buddy appears in the iChat Jabber buddy list. As soon as the buddy logs into Adium, the buddy *fully disappears* from the iChat buddy list (i.e., is not even listed as unavailable; they just *poof* disappear).

More than likely this is an iChat bug. However, it may even be an iChat feature intended to discourage adoption of Adium. For this reason, I would recommend that you attempt to figure out why GTalk<->iChat works fine, whereas Adium<->iChat does not---simply so you can increase adoption of Adium.

Regards, P

Changed 3 years ago by dobunzli

Hello, I confirm the bug too. Here are some console log from the "iChat side"

2007-03-04 08:25:33.143 iChatAgent[182] WARNING: JConnection: Couldn't find target for IQ of type get containing 'jabber:iq:last*query' ID 'gaim95754279' 2007-03-04 09:56:54.055 iChatAgent[182] WARNING: JabberMessageNode: ignoring unknown child < http://jabber.org/protocol/chatstates*composing> 2007-03-04 09:56:54.056 iChatAgent[182] WARNING: JabberMessageNode: ignoring unknown child < http://jabber.org/protocol/archive*record>

...

2007-03-04 10:03:55.276 iChatAgent[182] WARNING: JabberMessageNode: ignoring unknown child < http://jabber.org/protocol/archive*record>

Changed 3 years ago by jas8522

  • patch_status set to None
  • milestone set to Needs feedback from users

Is this still a problem with 1.0.2? If so I'll have it changed to needs dev review.

Changed 3 years ago by dobunzli

Yes I can confirm that this is still a problem with 2 machines under Mac OS X 10.4.9, one with ichat and one with Adium 1.0.2.

This is the log of the computer with ichat:

2007-04-26 19:27:02.665 iChatAgent[184] WARNING: JConnection: Couldn't find target for IQ of type get containing 'jabber:iq:last*query' ID 'gaima63f15e9'
Workaround Bonjour: Unknown error: 0
2007-04-26 20:03:51.592 iChatAgent[184] WARNING: JabberMessageNode: ignoring unknown child <http://jabber.org/protocol/chatstates*composing>
2007-04-26 20:03:51.593 iChatAgent[184] WARNING: JabberMessageNode: ignoring unknown child <http://jabber.org/protocol/archive*record>
2007-04-26 20:03:53.254 iChatAgent[184] WARNING: JabberMessageNode: ignoring unknown child <http://jabber.org/protocol/chatstates*active>

Changed 3 years ago by jas8522

  • version changed from 1.0.1b to 1.0.2
  • milestone changed from Needs feedback from users to Needs dev review

Changed 2 years ago by zacw

  • status changed from new to closed
  • resolution set to invalid
  • pending set to 0

Adium 1.1.3 and iChat 4.0 have no problems seeing each other or communicating. Chalking this up as an iChat bug.

Changed 21 months ago by jas8522

  • milestone Needs dev review deleted
Note: See TracTickets for help on using tickets.