This bug was fixed in the package libnotify - 0.7.11-1
---------------
libnotify (0.7.11-1) unstable; urgency=medium
* New upstream release:
- notify-send: Support for replacing an existing notification (LP: #257135,
Closes: #559544)
- notify-send: Support commas in icon filenames (LP: #674642)
- notify-send: Give failing exit code if showing notification fails
(LP: #1970647, Closes: #609556, Closes: #679653)
- notify-send: Add support for notification actions and responses
(Closes: #571181)
- notify-send: Add option to wait until notification has been closed
- notify-send: Add support for boolean hints (Closes: #636343)
- docs/notify-send: Add missing --app-name to manpage (Closes: #756151)
* debian/rules: Use DPKG_GENSYMBOLS_CHECK_LEVEL instead of override
* debian: Use debhelper 13, and remove explicit --fail-missing
* debian/control: Update Standards-Version, no change needed
* debian/libnotify4.symbols: Add new symbols
* debian/patches: Add transient option to man
-- Marco Trevisan (Treviño) <ma...@ubuntu.com> Wed, 27 Apr 2022
21:47:25 +0200
** Changed in: libnotify (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/257135
Title:
notify-send(1) can't replace an existing notification
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/257135/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
