Notifications emitted by a snap with local files or desktop files use wrong namespace

Bug #1802483 reported by Marco Trevisan (Treviño) on 2018-11-09
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libnotify (Ubuntu)
Marco Trevisan (Treviño)
Nominated for Bionic by Marco Trevisan (Treviño)
Nominated for Xenial by Marco Trevisan (Treviño)

Bug Description

As can be tested using this example 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:
  git clone
  snapcraft prime
  snap try prime

Check that icons are shown when launching:

Running them with G_MESSAGES_DEBUG=all should provide translation logging

[ Regression potential ]

Normal applications that are run with a SNAP environment variable set, might use wrong paths for files or desktop file

Libnotify fix for xenial

Fix for bionic (and cosmic)

description: updated

The attachment "libnotify_0.7.7-3+snap-support.debdiff" seems to be a debdiff. The ubuntu-sponsors team has been subscribed to the bug report so that they can review and hopefully sponsor the debdiff. If the attachment isn't a patch, please remove the "patch" flag from the attachment, remove the "patch" tag, and if you are member of the ~ubuntu-sponsors, unsubscribe the team.

[This is an automated message performed by a Launchpad user owned by ~brian-murray, for any issue please contact him.]

tags: added: patch
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers