Stuck notifications (blue envolope remains after I've already read msg)

Bug #1113721 reported by bwat47
66
This bug affects 13 people
Affects Status Importance Assigned to Milestone
indicator-messages (Ubuntu)
Fix Released
Undecided
Unassigned
pidgin-libnotify (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Using clean install of raring with all updates. When i get an im in pidgin I get the blue envolope as expected, but if I read the message by alt tabbing to the pidgin conversation window or by using the launcher the blue envolope stays. The only way it goes away is if i access the message by clicking the message indicator and clicking the unread message from there. I did not have this problem in 12.10 with jconti's pidgin-libnotify ppa.

ProblemType: Bug
DistroRelease: Ubuntu 13.04
Package: pidgin-libnotify 0.14-9ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-4.8-generic 3.8.0-rc6
Uname: Linux 3.8.0-4-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
Date: Sat Feb 2 14:43:02 2013
InstallationDate: Installed on 2013-01-31 (2 days ago)
InstallationMedia: Ubuntu 13.04 "Raring Ringtail" - Alpha amd64 (20130129)
MarkForUpload: True
ProcEnviron:
 TERM=xterm
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: pidgin-libnotify
UpgradeStatus: No upgrade log present (probably fresh install)

Related branches

Revision history for this message
bwat47 (bwat47) wrote :
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in pidgin-libnotify (Ubuntu):
status: New → Confirmed
Revision history for this message
Xoimai (xoimai) wrote :

I am having the same problem with the gmail web app notifications in the latest version of 13.04. When the number of unread emails is 0 again, either by clicking the notification or opening the mail manually in the browser the indication stays blue.

Revision history for this message
Jason Conti (jconti) wrote :

Looking at the output of: pidgin -d; I see that when I focus the conversation, I get "REMOVING ATTENTION FOR (...)" so the plugin thinks it is doing the right thing anyway.

I am going to add indicator-messages to this bug, I'm not sure this is a pidgin-libnotify issue. I can reproduce the problem with a simple python app I've used for testing. It works on 12.10 but doesn't remove the attention on 13.04. I'll attach it to the bug as well.

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in indicator-messages (Ubuntu):
status: New → Confirmed
Revision history for this message
Jason Conti (jconti) wrote :

Guess I should have looked at the code immediately. There was a bit of refactoring in libmessaging-menu/messaging-menu.c and it seems the boolean for draws_attention was always set to TRUE mistakenly. Attached a branch that should fix it.

Changed in pidgin-libnotify (Ubuntu):
status: Confirmed → Invalid
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package indicator-messages - 12.10.6daily13.02.13-0ubuntu1

---------------
indicator-messages (12.10.6daily13.02.13-0ubuntu1) raring; urgency=low

  [ Jason Conti ]
  * Stuck notifications (blue envolope remains after I've already read
    msg) (LP: #1113721)

  [ Automatic PS uploader ]
  * Automatic snapshot from revision 337
 -- Automatic PS uploader <email address hidden> Wed, 13 Feb 2013 02:02:11 +0000

Changed in indicator-messages (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
dimovnike (dimovnike) wrote :

I upgraded via update-manager to 13.04 and the bug is still present.

Revision history for this message
dimovnike (dimovnike) wrote :

also the testing python app doesnt work at all, when i press "draw attention" button nothing happens.

Revision history for this message
Sebastien Bacher (seb128) wrote :

if you still have an issue please open a new bug

Revision history for this message
Hansen (moteprime) wrote :

I also have this bug. Are there a new bug opened?

Revision history for this message
dimovnike (dimovnike) wrote :

bug is still present.
nothing changed since status changed to "Fix Released"

Revision history for this message
lorty (lorty) wrote :

This bug still exists in updated 13.04, please reopen

Revision history for this message
Hansen (moteprime) wrote :

I opened a new Bug #1184291.
Please "This bug affects you" and subscribe, this bug is bothersome.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.