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 -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to libnotify in Ubuntu. https://bugs.launchpad.net/bugs/1802483 Title: Notifications emitted by a snap with local files or desktop files use wrong namespace Status in libnotify package in Ubuntu: Fix Released Status in libnotify source package in Focal: In Progress Status in libnotify source package in Jammy: Fix Committed Bug description: As can be tested using this example snap: - https://github.com/3v1n0/notify-send-test-snap Basically the icons are referenced using absolute paths in snap environment, while they should be readapted so that they depend on $SNAP location. As we do with appindicators and libunity emblems. ---- [ Impact ] Icons sonuds and desktop files referenced by a snapped app using notifications aren't exposed to the desktop in absolute paths [ Test case ] Build the test snap (or install it from the attached files to this bug): git clone https://github.com/3v1n0/notify-send-test-snap snapcraft prime snap try prime To use the pre-built snap (https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/comments/7) snap install --dangerous notify-send-test-snap_*.snap Check that icons are shown when launching: notify-send-test-snap notify-send-test-snap.image-path notify-send-test-snap.image-uri Ensure that desktop entry is correctly sent, monitoring the dbus session: In a terminal: dbus-monitor --session --monitor "interface='org.freedesktop.Notifications'" In the other: notify-send-test-snap.desktop-entry notify-send-test-snap.desktop-entry-explicit-id notify-send-test-snap.desktop-entry-explicit-file-name notify-send-test-snap.desktop-entry-explicit-path notify-send-test-snap.desktop-entry-explicit-uri notify-send-test-snap.desktop-entry-explicit-snapped-uri The `desktop-entry` value sent to dbus should be either: - A `notify-send-test-snap_`-prefixed desktop ID - A .desktop file path (readable from both inside and outside the snap) - A .desktop file uri (readable from both inside and outside the snap) [ Regression potential ] Normal applications that are run with a SNAP environment variable set, might use wrong paths for files or desktop file To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libnotify/+bug/1802483/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp