Current notification policy based on last focus time is not reliable

Bug #476539 reported by TonyKnott
8
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Gwibber
Invalid
Undecided
Unassigned
gwibber (Ubuntu)
Invalid
Low
Unassigned

Bug Description

Binary package hint: gwibber

Consider the following use case:

1 - I set gwibber to refresh each 5 minutes
2 - gwibber refreshes
3 - after 2 minutes, someone sends me a message
4 - after 1 more minute, I open gwibber to post something or read a previous post
5 - I close gwibber

After 2 more minutes, gwibber refreshes, receives a new message and I am *not* notified because the last focus (step 4) happened *after* that message was sent. Gwibber should check if the new message was *received* and not *sent* after the last focus.

ProblemType: Bug
Architecture: amd64
Date: Fri Nov 6 14:30:23 2009
DistroRelease: Ubuntu 9.10
LiveMediaBuild: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
Package: gwibber 2.0.0~bzr476-0ubuntu3 [modified: usr/share/pyshared/gwibber/server.py usr/share/pyshared/gwibber/client.py]
PackageArchitecture: all
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SourcePackage: gwibber
Uname: Linux 2.6.31-14-generic x86_64

Revision history for this message
TonyKnott (tonyknott-deactivatedaccount) wrote :
Revision history for this message
TonyKnott (tonyknott-deactivatedaccount) wrote :

I noticed that there`s a "is_unread" property, but I don`t see this property being set to true anywhere.

Dario Panico (dariopnc-)
description: updated
Revision history for this message
Victor Vargas (kamus) wrote :

Please could you try to reproduce this issue in latest version of gwibber daily ppa (you can get from https://launchpad.net/~gwibber-daily/+archive/ppa) and check if this problem is still affecting you? Thanks in advance!

Changed in gwibber (Ubuntu):
importance: Undecided → Low
status: New → Incomplete
Revision history for this message
Victor Vargas (kamus) wrote :

We are closing this bug report because it lacks the information we need to investigate the problem. Please reopen it if you encounter that this issue is still occurring or even better if you can check in latest Ubuntu Lucid version. To reopen the bug report you can click under the Status column, and change the Status back to "New". Thanks again!

Changed in gwibber:
status: New → Invalid
Changed in gwibber (Ubuntu):
status: Incomplete → Invalid
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.