I think this is related to an issue with intentionally ignoring the timeout argument, there is a long discussion about the issue/bug #390508 here: https://bugs.launchpad.net/ubuntu/+source/notify-osd/+bug/390508
-- You received this bug notification because you are a member of DX Packages, which is subscribed to notify-osd in Ubuntu. Matching subscriptions: dx-packages https://bugs.launchpad.net/bugs/1176365 Title: Support for ADHD accessibility Status in Notify OSD: New Status in “notify-osd” package in Ubuntu: Triaged Bug description: Apologies if I'm submitting my concerns to the wrong place. I've been unable to find any mention of accessibility in relation to notifyOSD anywhere on the web. As someone with ADHD, I find an unskippable 10 second timeout to be extremely disruptive. This is especially true when there are many notification fading in and out in the corner of my eye. The notifications might as well take up my whole screen. That's not an exaggeration and it's not meant to be a snarky insult. I'm being honest and sincere when I say that the default behavior makes my computer nearly unusable . . . *for me*. I acknowledge that I am not the most common user example, but there are accommodations in Ubuntu for other disabilities. Those accommodation are generally far more effort to implement than click-to-close behavior or a configurable time-out. As things are now, I am relying on kludgey, third party solutions to make my computer usable. To manage notifications about this bug go to: https://bugs.launchpad.net/notify-osd/+bug/1176365/+subscriptions -- Mailing list: https://launchpad.net/~dx-packages Post to : dx-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~dx-packages More help : https://help.launchpad.net/ListHelp
