Comment 23 for bug 332600

Matthew Paul Thomas [2009-02-27 12:46 -0000]:
> This is not because it has any non-default timeout, and it's not because
> the notifications are queued. It's almost cerainly because gnome-mount
> sets expire_timeout to 0

Right, that's what I meant. It's used as an _indefinite_ timeout, not
an _infinite_ one.

> ** Changed in: notify-osd
> Status: Confirmed => Invalid

I strongly object to this, though. While we'll see to fix gnome-mount,
we can't possibly fix the entire software world by Jaunty, so at least
for Jaunty itself, notify-osd should respect different timeouts,
including indefinite ones. Otherwise I'm afraid we'll get a lot of bad
press and spoil the story of notify-osd.

Please NB that I am not complaining against disregarding timeouts
_eventually_, just for a transition period (well, I still question
that a fixed 10 second timeout is always the right thing, because I
feel that it's not; but that's a separate issue).

Did you mark this bug as invalid because you insist on disregarding
timeouts for Jaunty, or because it should be tracked in a separate
bug?