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: (unassigned) => Mirco Müller (macslow)
Status: New => Confirmed
--
Brightness notifications have a duration of 5000ms
https://bugs.launchpad.net/bugs/343553
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
