Thanks for the information, the random characters at the end of the buddy name seem to be what's hurting us here. It seems that sender may contain too much information, looks like where the message originated from. Originally it was using purple_buddy_get_name() instead of sender, but for all the protocols I tested, these were the same, so went with sender instead.
Attaching a debdiff with the minor change of using purple_buddy_get_name() if possible, and if not falling back to sender. But since I can't reproduce this easily, I don't know whether this will fix your issue or not (it works equivalently on the protocols I'm using). For ease of testing, I pushed the change to ppa:jconti/gnome3 , it should build in a few hours. You don't necessarily have to add the ppa to test it, just downloading the deb and installing will work (or rebuild with the attached debdiff if you prefer). If it doesn't fix the issue, I would be interested in seeing what the new buddy ids look like. ** Patch added: "pidgin-libnotify_use-buddy-name.debdiff" https://bugs.launchpad.net/ubuntu/+source/pidgin-libnotify/+bug/1175537/+attachment/3682414/+files/pidgin-libnotify_use-buddy-name.debdiff -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1175537 Title: Stuck notifications (unable to clear them) To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/pidgin-libnotify/+bug/1175537/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
