#633 closed defect (obsolete)

Removal of buddies on oscar protocol does not remove buddy at server

Reported by: toba@… Owned by: Jelmer Vernooij
Priority: normal Milestone:
Component: OSCAR Version: 1.2.7
Keywords: Cc:
IRC client+version: Client-independent Operating System: Linux
OS version/distro: Gentoo


[21:45] >>> buddynick [] has joined &bitlbee 
[21:45] <@Toba_> remove buddynick SeanWaithe 
[21:45] >>> Signoff buddynick: &bitlbee (Leaving...)
[21:45] <@z> Buddy `buddynick' (nick buddynick) removed from contact list 
[21:46] <@z> oscar - imcb_buddy_status() for unknown handle buddynick:
[21:46] <@z> oscar - flags = 1, state = NULL, message = NULL 

This also happened on 1.2.3. I upgraded to 1.2.7 in hopes that it was fixed, but evidently it isn't.

Attachments (0)

Change History (9)

comment:1 Changed at 2010-06-17T01:48:24Z by toba@…

The string "SeanWaithe" in my description is spurious - I use a nick list in irssi and while I was cleaning out my copy-paste I missed that. It didn't appear on the lines in my irc client.

comment:2 Changed at 2010-06-17T21:50:40Z by Lakitu7

It goes away if you disconnect and reconnect the account, if you just want a workaround to silence the message.

comment:3 Changed at 2012-03-25T23:38:03Z by wilmer

Priority: majornormal

comment:4 Changed at 2012-03-26T00:05:12Z by toba@…

Thanks Lakitu7, I've been using that since you suggested it many moons ago. I see that you guys are doing a bug cleaning - yeah, this isn't a major issue.

comment:5 Changed at 2012-06-16T18:30:11Z by anonymous

this bug still exists

comment:6 Changed at 2012-08-28T09:22:55Z by anonymous

i love bitlbee, but changing the priority to normal on a bug that will let users have to reconnect an account in order to not get spammed every 45min with a message for an account that he just doesn't care for anymore (or even multiple ones) is, for a bug that exists since more than 2 years, a mess.

comment:7 Changed at 2012-08-28T09:57:32Z by wilmer

Only security bugs or completely broken modules are major. I can understand that you're annoyed, but there are no security concerns nor does this bug make it impossible to use the OSCAR module entirely.

Although this bug can be annoying, I have very little interest in fixing this. The OSCAR protocol is intentionally obfuscated, poorly documented and fixing bugs like this is not all that trivial. If I have to choose between spending hours on fixing this, or spending hours on adding new cool functionality to BitlBee, this bug just loses. :-/

OTOH if anyone knows why this is happening, I'd be more than happy to take patches, of course.

comment:8 Changed at 2012-09-05T18:38:29Z by bitlbee@…

I found this at

/ignore -regexp -pattern "oscar - imcb_buddy_status() for unknown handle" -network bitlbee root!root@localhost PUBLICS

It won't fix the problem, but it will hide it so you don't have to worry about it, or have it taking up your space in your log files.

comment:9 Changed at 2019-01-02T01:28:10Z by dx

Resolution: obsolete
Status: newclosed

Closing all OSCAR tickets, as ICQ switched to WIM which we don't support (the icyque purple plugin does)

Modify Ticket

as closed The owner will remain Jelmer Vernooij.
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.