Adium

Ticket #5404 (closed defect: duplicate)

Opened 4 years ago

Last modified 22 months ago

Group Chats remain disconnected when reconnecting jabber accounts

Reported by: michael@koziarski.com Owned by: nobody
Milestone: Component: Service/Jabber (XMPP)
Version: 1.0b9 Severity: normal
Keywords: Cc:
Patch Status:

Description

Steps to Reproduce

* Participate in a jabber group chat

* Disconnect your internet access or sleep the computer

* Reconnect / Wake the computer

Results

After the account is reconnected, the group chat window remains open and appears 'connected'. You can talk in the room, you can see other people who appear to be in there.

But you aren't actually connected to this group chat at all. Your messages go nowhere, and you miss what's actually happening

Expected Results

Ideally the group chats would reconnect when the account was reconnected.

Comments

While there's no crashing or data loss, it can be extremely frustrating when you suffer some network glitch, then miss all the traffic in the group chat. May affect other services/protocols, but I've only noticed with jabber.

Change History

Changed 4 years ago by yeled

do you think this is adium code or upstream?

Changed 4 years ago by edr1084

  • milestone set to Adium X 1.1

This may be resolved in Smack but that will not be included until 1.1 at the earliest. Is this a regression? (I'm assuming not so I'm putting it in the Smack milestone).

Changed 4 years ago by tick

  • milestone changed from Adium X 1.1 to Sometime after 1.0

We are no longer utilizing Smack, so we will need to rethink how to do this with libgaim.

Changed 3 years ago by irabinovitch

I'm seeing this behavior in 1.2svn as well. Would it be possible to at least show an error indicating a disconnect occurred? Often in this situation, I will not realize I have been disconnected and continue to send messages to the MUC room. Adium will show them as being sent, but since it never actually rejoined the chat those messages get lost in the ether.

Changed 3 years ago by irabinovitch

Searching trac I found #1880, which appears to cover this same issue with but all protocols, not just Jabber/XMPP.

Changed 3 years ago by edr1084

  • status changed from new to closed
  • patch_status set to None
  • resolution set to duplicate
  • pending set to 0
  • milestone changed from Good idea for "later" to zzzDuplicate tickets

Duping against #1880.

Changed 22 months ago by Robby

  • milestone zzzDuplicate tickets deleted
Note: See TracTickets for help on using tickets.