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 790636 - Multiple redundant and/or contradictory 'NotificationClosed' signals from the GNOME desktop notification server
Multiple redundant and/or contradictory 'NotificationClosed' signals from the...
Status: RESOLVED OBSOLETE
Product: gnome-shell
Classification: Core
Component: message-tray
3.26.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2017-11-20 21:49 UTC by Jason Gray
Modified: 2021-07-05 14:26 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Jason Gray 2017-11-20 21:49:24 UTC 
The title pretty much says it all.

The GNOME notification server sends multiple redundant and/or contradictory 'NotificationClosed' signals for the same notification. A notification ofc should have only one 'NotificationClosed' signal.

Here is a little app I wrote in PyGObject to test notifications. It uses Gio.DBusProxy to interact with the notification server(not LibNotify).

https://gist.github.com/JasonLG1979/935a66eff58eb72ab25f876ce5cc05d9
Comment 1 GNOME Infrastructure Team 2021-07-05 14:26:17 UTC 
GNOME is going to shut down bugzilla.gnome.org in favor of  gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/

Thank you for your understanding and your help.