#718 closed defect (fixed)

Users never leave

Reported by: augmentedfourth Owned by:
Priority: normal Milestone:
Component: BitlBee Version: 3.0
Keywords: Cc: bitlbee@…
IRC client+version: irssi/lenny 0.8.12-7 Operating System: Linux
OS version/distro: Debian 5 (Lenny) i686


I'm running 3.0 compiled on Debian 5 with the default configuration. I'm only using it for Google Chat over XMPP, so I can't tell the full extent of this problem, but contacts *never* quit the channel once they've appeared. I've been using 3.0 for almost a week, and according to my logs no users have left the channel for any reason.

If I turn off the account, it looks like a netsplit rather than actually quitting users (like it used to in 1.2.8).

Attachments (0)

Change History (11)

comment:1 Changed at 2010-11-10T19:13:23Z by wilmer

Priority: blockernormal

Yes, known issue. Fixed in bzr and in the 3.0.1 that will hopefully come out soon.

Since this is not in any way related to security this obviously can't be priority=blocker.

comment:2 Changed at 2010-11-10T19:19:57Z by augmentedfourth

I was probably too hasty in assigning priority. I just jumped as high as I could since it felt like it was breaking one of the main points of IM communication (i.e. presence notification).

In any case, glad to see it's been fixed already. I'll just go back to 1.2.8 until 3.0.1 is officially available. Out of curiosity, what was the scope of this problem? Was it all of bitlbee, just Jabber, only Google Jabber connections... ?

comment:3 Changed at 2010-11-10T19:22:48Z by wilmer

Only XMPP. The bug was pretty stupid and if I waited a few more days before releasing 3.0 I may have found it in time. Then again, putting a "stable" stamp on something always releases a herd of testers who find all kinds of bugs. :>

But yeah, I reserve priorities above major for security-related things, and major for things like "doesn't log in at all".

comment:4 Changed at 2010-11-12T22:53:50Z by wilmer

Resolution: fixed
Status: newclosed

Oops. So of course I should've closed this.

comment:5 Changed at 2011-03-23T00:12:33Z by augmentedfourth

Resolution: fixed
Status: closedreopened

It's baaaack...

Some users are showing as logging on and off just fine, but today one particular user never showed as logged off (despite leaving and returning several times during the day, I later learned) until I turned my Jabber account off then back on.

comment:6 Changed at 2011-03-23T00:17:55Z by Wilmer van der Gaast <wilmer@…>

I assume this is GTalk?

comment:7 Changed at 2011-03-23T00:29:46Z by augmentedfourth <a4@…>

Yep. And I'm up to 3.0.2 as of a week or so ago. So the user that displayed improperly *did* show correctly for at least a few days. And flipping the account off & on ended up with significantly fewer online contacts after reconnection.

comment:8 Changed at 2011-03-26T16:54:13Z by wilmer

Resolution: fixed
Status: reopenedclosed

This is an issue with GTalk. I've seen it myself with xmlconsole turned on, there simply were no <presence type="unavailable"/> stanzas sent for people who did go offline. If you're sure you see this with BitlBee only, an xmlconsole dump would be useful.

comment:9 Changed at 2011-03-26T22:19:27Z by augmentedfourth <a4@…>

This wasn't a problem until I upgraded to 3.0.2, though... 3.0.1 seemed fine, so my temporary solution was to just downgrade.

I'm back at 3.0.2 and keeping an xmlconsole dump; I'll send it over if this happens again.

comment:10 Changed at 2011-03-26T22:27:09Z by augmentedfourth <a4@…>

By the way; would his be affected by the fact that my IRC client (irssi) changes my /nick when I set Away? I know bitlbee now allows nick changes, and I'm not sure if there are any other ramifications to that.

comment:11 Changed at 2011-03-27T14:05:29Z by wilmer

I don't think anything changed in 3.0.2 that could cause this so this is probably unrelated. Please let me know if you find something in the xmlconsole logs.

Modify Ticket

as closed The ticket will remain with no owner.
The resolution will be deleted.

Add Comment

E-mail address and name can be saved in the Preferences.

Note: See TracTickets for help on using tickets.