I still get this issue with pidgin-libnotify 0.14-9ubuntu2~raring~ppa3
from ppa:jconti/gnome3
When I click on the chat window upon receiving a message, the blue mail
indicator does go away, but the list of names is still there. The
Clear menu item is also grayed out.
I am using a Jabber account
That version seems to work fine, I'm sponsoring it to saucy
** Changed in: pidgin-libnotify (Ubuntu)
Importance: Undecided = Low
** Changed in: pidgin-libnotify (Ubuntu)
Status: Triaged = Fix Committed
--
You received this bug notification because you are a member of Desktop
** Branch linked: lp:ubuntu/saucy-proposed/pidgin-libnotify
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pidgin-libnotify in Ubuntu.
https://bugs.launchpad.net/bugs/1175537
Title:
Stuck notifications (unable to clear them)
Status
This bug was fixed in the package pidgin-libnotify - 0.14-9ubuntu2
---
pidgin-libnotify (0.14-9ubuntu2) saucy; urgency=low
* debian/patches/messaging_menu.patch:
- Use purple_buddy_get_name() instead of sender in unique id if possible
(LP: #1175537)
- Associate a buddy
Ah, no, apparently it is in main (why?), so I can't upload there.
** Changed in: pidgin-libnotify (Ubuntu)
Status: Fix Committed = Triaged
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pidgin-libnotify in Ubuntu.
Uploaded pidgin-libnotify_use-buddy-name-v3.debdiff to saucy, thanks!
** Changed in: pidgin-libnotify (Ubuntu)
Status: Confirmed = Fix Committed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pidgin-libnotify in Ubuntu.
Yes, you are right - it was broken in ppa2 version. But now it works -
when I close conversation (even when there are unread messages), item
from menu is removed. And when envelope is blue because of unread
conversation I'm closing, it turns black as it should.
--
You received this bug
Thanks again for testing.
In my haste, I forgot to update the other location where
purple_conversation_get_name() was used, when deleting the conversation.
I pushed one last change out to ppa:jconti/gnome3, if you wouldn't mind
checking that closing a conversation window removes the associated
As far as I can say after short testing - when I receive more than 1
message from any contact, all notifications are working now (for all
contacts). Except notification bubble for new conversations (but
envelope turns blue so I know I have a new message). Problem #2 is
solved for me, thank you!
Great, I've installed deb file and it seems (partially) OK - now I can
see only one item for each conversation. It was a real pain for me :).
But there are four problems now:
1) Only notifications for the second message from the same contact are
displayed incl. notification bubble (I have to
@Jason: thanks for your work
I can confirm that the first message received doesn't trigger a
notification, that was happening before that update though. Testing the
patch the envelop still turns blue as it should, I was not able to
confirm the bug so I can't really confirm the fix but at least it
Thanks for testing. That buddy id was exactly what I was hoping to see,
so at least that part seems to be fixed.
Problem 1, as Sebastien mentioned, was unfortunately always there. I'm
not sure how to fix it. On my system at least, sometimes I will get the
first notification, sometimes not. I
Though now I'm concerned that the patch will break jabber users where it
previously worked because they didn't have random strings at the end,
but still don't have purple_buddy_get_name() matching
purple_conversation_get_name()...
--
You received this bug notification because you are a member of
After a few minutes thought, I realized if
purple_conversation_get_name() == sender, and I can get the buddy with
account and sender, then I should be able to do the same with the
conversation name. So I have pushed a new test package to
ppa:jconti/gnome3. Please test it out and let me know if it
There is an attempt in pidgin-libnotify to generate unique strings for
each buddy, where each string is the id of a menu item in the Messaging
Menu. If you are getting repeat entries, then for some reason it is
generating two different strings for the same buddy.
If someone experiencing this bug
Here are the lines you needed:
(22:24:03) pidgin-libnotify: SOURCE activated
'im:prpl-jabber:userone.recipient%40gmail.com%2Fdevoid:usertwo.sender%40gmail.com%2Fgemini2CEF0B0A'
(22:24:07) pidgin-libnotify: SOURCE activated
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
The attachment pidgin-libnotify_use-buddy-name.debdiff seems to be a
debdiff. The ubuntu-sponsors team has been subscribed to the bug report
so that they can review and hopefully sponsor the debdiff. If the
attachment isn't a patch, please remove the patch flag from the
attachment, remove the
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: pidgin-libnotify (Ubuntu)
Status: New = Confirmed
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pidgin-libnotify in Ubuntu.
also a lot of repetitions are there, the same contact may appear many
times.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to pidgin-libnotify in Ubuntu.
https://bugs.launchpad.net/bugs/1175537
Title:
Stuck notifications (unable to
20 matches
Mail list logo
