notify-send exit code doesn't match result

Bug #1970647 reported by Marco Trevisan (Treviño)
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libnotify (Ubuntu)
Fix Released
Medium
Marco Trevisan (Treviño)
Focal
Fix Released
Medium
Marco Trevisan (Treviño)
Jammy
Fix Released
Medium
Marco Trevisan (Treviño)

Bug Description

No error exit code is returned by notify-send on failure

[ Test case ]

1. Run:
   env DBUS_SESSION_BUS_ADDRESS= notify-send foo bar || echo error
2. In a terminal "error" should be printed

[ Regression potential ]

Programs relying on notify-send may have errors when they did not.

Jeremy Bícha (jbicha)
Changed in libnotify (Ubuntu Focal):
status: New → In Progress
importance: Undecided → Medium
Changed in libnotify (Ubuntu Jammy):
status: New → In Progress
importance: Undecided → Medium
assignee: nobody → Marco Trevisan (Treviño) (3v1n0)
Changed in libnotify (Ubuntu Focal):
assignee: nobody → Marco Trevisan (Treviño) (3v1n0)
Changed in libnotify (Ubuntu):
assignee: nobody → Marco Trevisan (Treviño) (3v1n0)
Revision history for this message
Launchpad Janitor (janitor) wrote :

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) <email address hidden> Wed, 27 Apr 2022 21:47:25 +0200

Changed in libnotify (Ubuntu):
status: In Progress → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote : Please test proposed package

Hello Marco, or anyone else affected,

Accepted libnotify into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libnotify/0.7.9-3ubuntu5.22.04.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in libnotify (Ubuntu Jammy):
status: In Progress → Fix Committed
tags: added: verification-needed verification-needed-jammy
Revision history for this message
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (libnotify/0.7.9-3ubuntu5.22.04.1)

All autopkgtests for the newly accepted libnotify (0.7.9-3ubuntu5.22.04.1) for jammy have finished running.
The following regressions have been reported in tests triggered by the package:

firewalld/1.1.1-1ubuntu1 (amd64)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/jammy/update_excuses.html#libnotify

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Revision history for this message
Brian Murray (brian-murray) wrote : Please test proposed package

Hello Marco, or anyone else affected,

Accepted libnotify into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/libnotify/0.7.9-1ubuntu3.20.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Changed in libnotify (Ubuntu Focal):
status: In Progress → Fix Committed
tags: added: verification-needed-focal
Revision history for this message
Ubuntu SRU Bot (ubuntu-sru-bot) wrote : Autopkgtest regression report (libnotify/0.7.9-1ubuntu3.20.04.2)

All autopkgtests for the newly accepted libnotify (0.7.9-1ubuntu3.20.04.2) for focal have finished running.
The following regressions have been reported in tests triggered by the package:

apparmor/2.13.3-7ubuntu5.1 (armhf)

Please visit the excuses page listed below and investigate the failures, proceeding afterwards as per the StableReleaseUpdates policy regarding autopkgtest regressions [1].

https://people.canonical.com/~ubuntu-archive/proposed-migration/focal/update_excuses.html#libnotify

[1] https://wiki.ubuntu.com/StableReleaseUpdates#Autopkgtest_Regressions

Thank you!

Revision history for this message
Marco Trevisan (Treviño) (3v1n0) wrote (last edit ):

On focal:

❯ apt-cache policy libnotify-bin
libnotify-bin:
  Installato: 0.7.9-1ubuntu3.20.04.2
  Candidato: 0.7.9-1ubuntu3.20.04.2
  Tabella versione:
 *** 0.7.9-1ubuntu3.20.04.2 400
        400 http://archive.ubuntu.com/ubuntu focal-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     0.7.9-1ubuntu2 500
        500 http://archive.ubuntu.com/ubuntu focal/main amd64 Packages

❯ env DBUS_SESSION_BUS_ADDRESS= notify-send foo bar || echo exit-error
L'indirizzo fornito è vuoto
exit-error

description: updated
tags: added: verification-done-focal
removed: verification-needed-focal
Revision history for this message
Marco Trevisan (Treviño) (3v1n0) wrote :

On Jammy:

❯ apt-cache policy libnotify4
libnotify4:
  Installato: 0.7.9-3ubuntu5.22.04.1
  Candidato: 0.7.9-3ubuntu5.22.04.1
  Tabella versione:
 *** 0.7.9-3ubuntu5.22.04.1 400
        400 http://archive.ubuntu.com/ubuntu jammy-proposed/main amd64 Packages
        100 /var/lib/dpkg/status
     0.7.9-3ubuntu5 400
        400 http://archive.ubuntu.com/ubuntu jammy/main amd64 Packages

❯ env DBUS_SESSION_BUS_ADDRESS= notify-send foo bar || echo exit-error
The given address is empty
exit-error

tags: added: verification-done verification-done-jammy
removed: verification-needed verification-needed-jammy
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libnotify - 0.7.9-3ubuntu5.22.04.1

---------------
libnotify (0.7.9-3ubuntu5.22.04.1) jammy; urgency=medium

  * debian: Update references as per ubuntu/jammy branching
  * debian/patches: Exit with an error if showing notification fails
    (LP: #1970647)
  * debian/patches: Handle file paths, uris and desktop-ID's in Snapped apps
    (LP: #1802483)

 -- Marco Trevisan (Treviño) <email address hidden> Wed, 27 Apr 2022 23:23:22 +0200

Changed in libnotify (Ubuntu Jammy):
status: Fix Committed → Fix Released
Revision history for this message
Łukasz Zemczak (sil2100) wrote : Update Released

The verification of the Stable Release Update for libnotify has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libnotify - 0.7.9-1ubuntu3.20.04.2

---------------
libnotify (0.7.9-1ubuntu3.20.04.2) focal; urgency=medium

  * debian: Update references as per ubuntu/focal branching
  * debian/patches: Exit with an error if showing notification fails
    (LP: #1970647)
  * debian/patches: Handle file paths, uris and desktop-ID's in Snapped apps
    (LP: #1802483)

 -- Marco Trevisan (Treviño) <email address hidden> Wed, 27 Apr 2022 23:42:13 +0200

Changed in libnotify (Ubuntu Focal):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.