Here's a log, not it goes from 0 to 2 messages with a WARNING in between it. This is where a message seemed to get dropped.
** (process:4132): DEBUG: Indicator Server Added: :1.29 messages.im ** (process:4132): DEBUG: Indicator Server Type: :1.29 messages.im ** (process:4132): DEBUG: Indicator Server Desktop: :1.29 /usr/share/applications/pidgin.desktop ** (process:4132): DEBUG: Indicator Server Added: :1.82 message.mail ** (process:4132): DEBUG: Indicator Server Type: :1.82 message.mail ** (process:4132): DEBUG: Indicator Server Desktop: :1.82 /usr/share/applications/evolution-mail.desktop ** (process:4132): DEBUG: Indicator Added: :1.82 0 message ** (process:4132): DEBUG: Indicator Removed: :1.82 0 message ** (process:4132): DEBUG: Indicator Added: :1.29 1 message ** (process:4132): DEBUG: Indicator Removed: :1.29 1 message ** (process:4132): DEBUG: Indicator Added: :1.82 0 message ** (process:4132): DEBUG: Indicator Removed: :1.82 0 message (process:4132): libindicate-WARNING **: No indicator 0 of type 'message' on ':1.82'. ** (process:4132): DEBUG: Indicator Added: :1.29 2 message ** (process:4132): DEBUG: Indicator Removed: :1.29 2 message ** (process:4132): DEBUG: Indicator Added: :1.82 0 message -- message indicator with pidgin seems to be flaky https://bugs.launchpad.net/bugs/334349 You received this bug notification because you are a member of Indicator Applet Developers, which is the registrant for Indicator Applet. Status in Indicator Applet: New Bug description: I am seeing some flaky behavior in the message indicator, specifically with pidgin messages. After starting pidgin, I do see messages that I receive in the indicator-applet. However, at some point after running for a while I stop seeing incoming messages in the indicator-applet. I do continue to see notifications via notify-osd, and the indicator-applet lists both "Pidgin Instant Messenger" and "Evolution", but not specific incoming messages. Restart pidgin makes it start behaving as expected again. I am filing this bug against indicator-applet because I have seen this happen once with evolution as well, where restarting evolution resolved it. _______________________________________________ Mailing list: https://launchpad.net/~dx-team Post to : [email protected] Unsubscribe : https://launchpad.net/~dx-team More help : https://help.launchpad.net/ListHelp
