As I understand the code, the "expire_timeout" variable is first initialized with a default, then the same value is used later to define an array and then to set the expiration timeout for the notification. I don't see any code that reads the notification timeout from the command line and sets the "expire_timeout" variable accordingly.
Anyway, regardless of where the problem lies, the expiration timeout can only be the default "5 seconds" - there's no way to change this value. DRM 'manages access' in the same way that jail 'manages freedom'. On Sat, Jun 27, 2009 at 6:39 AM, A. Walton <awal...@ubuntu.com> wrote: > Notify-Send is sending the timeout to the server correctly as your grep > shows, but Notify OSD does not support timeouts. > > ** Package changed: libnotify (Ubuntu) => notify-osd (Ubuntu) > > -- > notify-send ignores the expire timeout parameter > https://bugs.launchpad.net/bugs/390508 > You received this bug notification because you are a direct subscriber > of the bug. > -- notify-send ignores the expire timeout parameter https://bugs.launchpad.net/bugs/390508 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
