[Bug 1945234] Re: Snapped apps are unable to trigger mate-notification-daemon
Brian Murray
1945234 at bugs.launchpad.net
Fri Nov 19 17:31:37 UTC 2021
Its not clear to me where this is Fix Committed and I don't want to just
upload this and undue any work Martin has on going, subsequently I'm
going to unsubscribe the Ubuntu Sponsors team. However, once this has
been fixed in jammy feel free to prepare some debdiffs and test cases
for Stable Releases.
--
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1945234
Title:
Snapped apps are unable to trigger mate-notification-daemon
Status in mate-notification-daemon package in Ubuntu:
Fix Committed
Bug description:
From https://forum.snapcraft.io/t/snapd-doesnt-allow-notification-
daemon-to-be-activatable/22912
Snapped applications are unable to trigger the mate-notification-
daemon due to the service file not specifying an assumed apparmor
label so apparmor does not know that it is unconfined and thus may
receive the dbus calls. Snapd specifies in the apparmor policy that
the label must be "unconfined".
I've filed an upstream PR to fix this at https://github.com/mate-
desktop/mate-notification-daemon/pull/201
ProblemType: Bug
DistroRelease: Ubuntu 21.10
Package: mate-notification-daemon 1.26.0-0ubuntu1
ProcVersionSignature: Ubuntu 5.13.0-16.16-generic 5.13.13
Uname: Linux 5.13.0-16-generic x86_64
ApportVersion: 2.20.11-0ubuntu69
Architecture: amd64
CasperMD5CheckResult: pass
CurrentDesktop: MATE
Date: Mon Sep 27 20:05:15 2021
InstallationDate: Installed on 2021-09-21 (6 days ago)
InstallationMedia: Ubuntu-MATE 21.10 "Impish Indri" - Beta amd64 (20210921)
SourcePackage: mate-notification-daemon
UpgradeStatus: No upgrade log present (probably fresh install)
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/mate-notification-daemon/+bug/1945234/+subscriptions
More information about the Ubuntu-sponsors
mailing list