Opened at 2013-05-04T15:37:16Z
Closed at 2014-07-16T03:35:19Z
#1053 closed defect (duplicate)
Bitlebee get kicked out of XMPP-MUCs when leaving the MUC from other Clients
Reported by: | anonymous | Owned by: | wilmer |
---|---|---|---|
Priority: | normal | Milestone: | |
Component: | Jabber | Version: | 3.0.5 |
Keywords: | Cc: | ||
IRC client+version: | Client-independent | Operating System: | Linux |
OS version/distro: |
Description
I get kicked out of Jabber MUC's when i connect with other Clients directly to the Server(Psi+, Xabber)
When i leave a MUC or disconnect with the other Clients bitlbee assume he has left the Channel. Auto-Rejoin via bitlebee is impossible and a reconnect to the server is necessary to solve the issue. (Tryed rejoins: bitlbee's auto-rejoin and ZNC's stickychans)
Bitlebee gaves me the Error Message "Already present in channel"
Attachments (0)
Change History (3)
comment:1 Changed at 2013-09-16T06:32:08Z by
comment:2 Changed at 2013-09-16T06:35:27Z by
Oh, and if it matters the server is prosody. I can look at the logs on the server if needed, but i suppose this is a presence issue.
comment:3 Changed at 2014-07-16T03:35:19Z by
Resolution: | → duplicate |
---|---|
Status: | new → closed |
#1027 seems to be a more general description of the same issue as this one.
I'm also seeing this with bitlbee 3.2 on OpenBSD.
If i'm connected to a muc in bitlbee, connect to the same xmpp account from another client (say, instantbird in thunderbird) and disconnect in that client, i'm disconnected from the muc channel in bitlbee with the message '17:35 * nick [user@localhost] has left #channel []'
I'm not disconnected from the xmpp server, but if i want to rejoin it i'm getting the 'Already present in channel' error message. The only workaround is to reconnect the account.