Brightness notifications have a duration of 5000ms

Bug #343553 reported by Ara Pulido
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
notify-osd (Ubuntu)
Fix Released
Undecided
Mirco Müller
Nominated for Jaunty by Mat Tomaszewski

Bug Description

Binary package hint: notify-osd

Brightness notifications are confirmation notifications and, therefore, they should last only 2000ms.

Volume notifications are lasting 2000ms, but brightness ones are lasting for 5000ms since the last updates.

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 9.04
NonfreeKernelModules: nvidia
Package: notify-osd 0.9.3-0ubuntu1
ProcEnviron:
 PATH=(custom, user)
 LANG=en_NZ.UTF-8
 SHELL=/bin/bash
SourcePackage: notify-osd
Uname: Linux 2.6.28-9-generic i686

Revision history for this message
Ara Pulido (ara) wrote :
Revision history for this message
Mat Tomaszewski (mat.t.) wrote :

Affects me, too

Revision history for this message
Mirco Müller (macslow) wrote :

That's very likely been introduced by revision http://bazaar.launchpad.net/~notify-osd-developers/notify-osd/main/revision/224 where I fixed bug https://bugs.edge.launchpad.net/ubuntu/+source/notify-osd/+bug/341565. I'll add "compatibility"-checks to ease the transition-phase for patched apps.
What happens is that, right now, checks in notify-osd are only done for the correct capability- and hint-names (e.g. "x-canonical-private-synchronous"). But all patched apps still use the old (and non-spec compliant) ones (e.g. "synchronous"). Thus for the example of synchronous notifications/bubbles these now are handled as asynchronous ones and are treated with the 5000ms timeout instead of the 2000 ms one.

Changed in notify-osd (Ubuntu):
assignee: nobody → macslow
status: New → Confirmed
Revision history for this message
Mat Tomaszewski (mat.t.) wrote :

Just noticed that volume and brightness display simultaneously, seems like the brightness behaves just like an asynchronous notification.

Revision history for this message
David Barth (dbarth) wrote :

That's gpm/gsd patches. I'm on that.

Changed in notify-osd:
assignee: macslow → dbarth
Revision history for this message
Mirco Müller (macslow) wrote :

I just added compatibility-checks to notify-osd, which also check for the old hint-names (in addition to the new ones) and also exposes the old capability-names (in additionn to the new ones too). So this should ease the flood of bug-reports from users. Still our patches to applications need to be updated... rather sooner than later.

Changed in notify-osd (Ubuntu):
assignee: dbarth → macslow
status: Confirmed → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package notify-osd - 0.9.6-0ubuntu1

---------------
notify-osd (0.9.6-0ubuntu1) jaunty; urgency=low

  * New upstream release 0.9.6:
    - Detect screensaver inhibition for do-not-disturb mode.
    - Add compatibility checks to ease transition period for applications to
      pick up the capability and hint name changes. (LP: #343553)
    - Correctly exit if registering on DBus failed. (LP: #331150)
    - Fix filtering of HTML.
    - Basic accessibility support.

 -- Martin Pitt <email address hidden> Thu, 19 Mar 2009 13:39:13 +0100

Changed in notify-osd:
status: Fix Committed → Fix Released
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.