[Bug 476539] [NEW] Current notification policy based on last focus time is not reliable

TonyKnott tony_knott_666 at hotmail.com
Fri Nov 6 14:40:47 UTC 2009


Public bug reported:

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

** Affects: gwibber (Ubuntu)
     Importance: Undecided
         Status: New


** Tags: amd64 apport-bug

-- 
Current notification policy based on last focus time is not reliable
https://bugs.launchpad.net/bugs/476539
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs at lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs




More information about the universe-bugs mailing list