Maybe there should be a party for the imminent second anniversary of this report.
The foregoing feedback should suggest that there is no basis for determining how best to hard-wire the expiration time of pop-up notifications. Attempting to do so arbitrarily limits the usefulness of the service, since its behaviour will often be inappropriate to the context. Just one concrete example: A popular use of notify-send among programmers is to present pass/fail results from automated tests that are invoked when a changed source file is detected. A notification that is welcome and useful when it appears for 2 or 3 seconds becomes annoying and intrusive when it insists on hovering for 10 seconds. Moreover, it seems to happen for no apparent reason because many people are relying on documentation for notify-send. Thus they encounter behaviour that's unexpected, resulting in confusion and wasted time. I'm just the latest in a long line of people who had to research this issue, eventually finding my way here to protest. One wonders how many man- hours have been similarly squandered. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/390508 Title: notifyOSD ignores the expire timeout parameter -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
