dx-packages team mailing list archive

[quequotion <390508@xxxxxxxxxxxxxxxxxx>]

>>mpt

It's pretty clear that the majority opinion is to have this fixed by
IMPLEMENTING the timeout parameter, not sweeping it under the rug.

The #1 reason people end up here is looking for some way to make Notify-
OSD's notifications go away faster.

-- 
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/390508

Title:
  notifyOSD ignores the expire timeout parameter

Status in One Hundred Papercuts:
  Invalid
Status in Message Web:
  New
Status in notify-osd package in Ubuntu:
  Won't Fix
Status in notify-osd package in Arch Linux:
  New

Bug description:
  Binary package hint: libnotify-bin

  adyroman@panther:~/libnotify-0.4.5/tools$ lsb_release -rd
  Description:	Ubuntu 9.04
  Release:	9.04
  adyroman@panther:~/libnotify-0.4.5/tools$ 

  adyroman@panther:~/libnotify-0.4.5/tools$ apt-cache policy libnotify-bin
  libnotify-bin:
    Installed: 0.4.5-0ubuntu1
    Candidate: 0.4.5-0ubuntu1
    Version table:
   *** 0.4.5-0ubuntu1 0
          500 http://ro.archive.ubuntu.com jaunty/universe Packages
          100 /var/lib/dpkg/status
  adyroman@panther:~/libnotify-0.4.5/tools$ 

  adyroman@panther:~/libnotify-0.4.5/tools$ cat notify-send.c | grep expire_timeout
  	static glong expire_timeout = NOTIFY_EXPIRES_DEFAULT;
  		{ "expire-time", 't', 0,G_OPTION_ARG_INT, &expire_timeout,
  	notify_notification_set_timeout(notify, expire_timeout);
  adyroman@panther:~/libnotify-0.4.5/tools$

To manage notifications about this bug go to:
https://bugs.launchpad.net/hundredpapercuts/+bug/390508/+subscriptions