summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorDani Llewellyn <[email protected]>2021-09-27 19:43:59 +0100
committerraveit65 <[email protected]>2022-07-09 20:17:35 +0200
commitad27c3ccaffc5fd36189073a713f7536563ab816 (patch)
treeaf46968dd4177563a489c8e5ee9b52558969b446
parent911888b61678fb684d892452f8c2c941b80a0fcb (diff)
downloadmate-notification-daemon-ad27c3ccaffc5fd36189073a713f7536563ab816.tar.bz2
mate-notification-daemon-ad27c3ccaffc5fd36189073a713f7536563ab816.tar.xz
Add AssumedAppArmorLabel to dbus service file
Snap packages are unable to trigger the notification daemon in a fully confined package, because the snapd apparmor rules state that the target of the dbus call must specify that it is labelled `unconfined`. See https://forum.snapcraft.io/t/snapd-doesnt-allow-notification-daemon-to-be-activatable/22912/1 for the details. Signed-off-by: Dani Llewellyn <[email protected]>
-rw-r--r--data/org.freedesktop.mate.Notifications.service.in1
1 files changed, 1 insertions, 0 deletions
diff --git a/data/org.freedesktop.mate.Notifications.service.in b/data/org.freedesktop.mate.Notifications.service.in
index 343f57f..4ce7697 100644
--- a/data/org.freedesktop.mate.Notifications.service.in
+++ b/data/org.freedesktop.mate.Notifications.service.in
@@ -1,3 +1,4 @@
[D-BUS Service]
Name=org.freedesktop.Notifications
Exec=@LIBEXECDIR@/mate-notification-daemon
+AssumedAppArmorLabel=unconfined