-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Receiving duplicate messages #140
Comments
Try adding BITLBEE_DEBUG=1 to that (i guess that's an old bitlbee-libpurple?) |
Adding that to my env seems to stop bitlbee from segfaulting, so I'll see if get anything interesting when it happens again. I'm running my own compile of bitlbee 3.5.1, which is old, but I didn't configure with |
Here's a rough description of what I see in my logs:
But the next few time out or error:
At this point it relogs successfully. When it does a It does a So it is reconnecting, it just doesn't report it in the status channel. I don't see a way to match up the resent messages except by comparing the timestamp and text. I don't know if there's a way to respond to receiving them in the first place so they don't count as unread, but I know nothing of the protocol and it seems to not be documented? |
Seeing this too. |
Within the last couple weeks, I've sometimes been getting duplicates of received messages. In my IRC client, it looks like this:
Sometimes they involve multiple messages. It's never happened in a situation where I've replied, so a wild guess would be that it's Steam providing past messages for showing history. My bitlbee status channel doesn't say I reconnected to Steam between the duplicates, though. Maybe it has to do with my actual Steam client reconnecting to chat.
Running
BITLBEE_DEBUG_STEAM=1 bitlbee -Dn
seems to make bitlbee segfault for me, so I don't have any debug info.The text was updated successfully, but these errors were encountered: