After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 638291 - Successive notify-send notifications stack up in the gnome-shell message bar
Successive notify-send notifications stack up in the gnome-shell message bar
Status: RESOLVED OBSOLETE
Product: libnotify
Classification: Platform
Component: general
git master
Other Linux
: Normal normal
: ---
Assigned To: libnotify-maint
libnotify-maint
Depends on:
Blocks:
 
 
Reported: 2010-12-29 17:25 UTC by Travis Reitter
Modified: 2020-11-26 15:31 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Travis Reitter 2010-12-29 17:25:40 UTC 
Each time jhbuild hits an error, it ends up adding a new notification message to the gnome-shell notification queue. In Gnome 2.x, only the last error would be displayed in the notification area. But in Gnome 3.x (with gnome-shell), the number is unbounded.

This is particularly frustrating since errors pile up quickly when working through build errors, leaving the user with several clicks' worth of work.

(There may be at least partly a gnome-shell bug)
Comment 1 Frederic Peters 2010-12-29 17:27:14 UTC 
It looks like GNOME Shell reacts that way on tooltip changes.
Comment 2 Travis Reitter 2011-06-29 21:15:24 UTC 
I've managed to completely fill up my message tray with these errors today.

Does anyone have suggestions for fixing this? Is it something that should be fixed in jhbuild?
Comment 3 Jasper St. Pierre (not reading bugmail) 2011-06-29 22:04:18 UTC 
It's because we use PID to track sources when there's nothing better, and jhbuild uses notify-send to send notifications. See bug 650533 for a bit of a better fix.
Comment 4 Milan Bouchet-Valat 2011-06-30 07:36:15 UTC 
It would be good to fix notify-send itself, because many small apps and scripts will suffer from this problem if they use it. Maybe notify-send could just pass the PID of it's parent?
Comment 5 Matthias Clasen 2011-07-06 12:11:01 UTC 
Or maybe add a --pid argument to notify-send ?
Comment 6 Dan Winship 2011-07-06 12:42:17 UTC 
(In reply to comment #5)
> Or maybe add a --pid argument to notify-send ?

yeah, that works better in the double-fork-to-avoid-zombies case
Comment 7 Matthias Clasen 2011-07-08 15:54:51 UTC 
Moving this to libnotify, then
Comment 8 André Klapper 2012-04-04 10:39:43 UTC 
Mass-fixing incorrect Default Assignee and QA contact scheme for libnotify so interested people can follow its development. (See 606365#c1 for ref.)
Comment 9 André Klapper 2020-11-26 15:31:13 UTC 
bugzilla.gnome.org is being replaced by gitlab.gnome.org. We are closing all
older bug reports and feature requests in GNOME Bugzilla which have not seen
updates for a while.

If you still use libnotify and if you still see this bug / want this feature in a recent and currently supported version, then please feel free to report it at
https://gitlab.gnome.org/GNOME/libnotify/-/issues/
by following the guidelines at
https://wiki.gnome.org/Community/GettingInTouch/BugReportingGuidelines

Thank you for creating this report and we are sorry it could not be implemented
so far (volunteer workforce and time is limited).