That's true that if a program is sending too many notifications, it's the program's fault. However it makes sense to prevent this kind of things to happen because the notifications are system wide and there are bugs. I think that a notification system is quite different from a window manager. In fact your bug examples happen inside the bugged application while the notification are handled externally. What do you do with an app that opens 200 windows? kill -9 ... What do you do with an app that has sent 200 messages? Even if you kill it they'll be displayed, so the only solution is to kill Notify OSD. That's the reason because there must be some kind of control about how apps use Notify OSD.
-- design problem? infinite wait for long queue https://bugs.launchpad.net/bugs/334809 You received this bug notification because you are a member of Notify OSD Developers, which is subscribed to Notify OSD. Status in Notify OSD: Confirmed Status in “notify-osd” source package in Ubuntu: Confirmed Bug description: Binary package hint: notify-osd I'm using pidgin-libnotify and I discovered a problem in notify-osd (maybe a design problem, not sure). When a buddy writes me a lot of lines (say 25) all messages are queued and showed in the bubbles. Every bubble stays there for 7 seconds. 7*25=almost 3 minutes. What happens is that if any other contact writes to me, the bubbles are scheduled too! And also the notifies sent through "notify-send" are. (Instead volume notifies are displayed below.) This is a problem, because it seems that an application can bring the monopoly of the notification bubbles. ProblemType: Bug Architecture: i386 DistroRelease: Ubuntu 9.04 Package: notify-osd 0.8-0ubuntu4 ProcEnviron: PATH=(custom, user) LANG=it_IT.UTF-8 SHELL=/bin/bash SourcePackage: notify-osd Uname: Linux 2.6.28-8-generic i686 _______________________________________________ Mailing list: https://launchpad.net/~dx-team Post to : [email protected] Unsubscribe : https://launchpad.net/~dx-team More help : https://help.launchpad.net/ListHelp
