QNetworkManagerInterface error when launching a snap

[Jamie Strandboge]

On Thu, 2017-01-05 at 11:32 -0600, Leo Arias wrote:
> Hello,
> 
> When launching the shadow snap, these errors are printed to the terminal:
> 
You aren't plugging the network-manager interface. Once you do, you'll need to
connect it after install.

> QNetworkManagerInterface::QNetworkManagerInterface(QObject*)
> propsReply "An AppArmor policy prevents this sender from sending this
> message to this recipient; type=\"method_call\", sender=\":1.138\"
> (uid=1000 pid=7546 comm=\"/snap/shadow/x2/usr/local/bin/umbra \")
> interface=\"org.freedesktop.DBus.Properties\" member=\"GetAll\" error
> name=\"(unset)\" requested_reply=\"0\"
> destination=\"org.freedesktop.NetworkManager\" (uid=0 pid=864
> comm=\"/usr/sbin/NetworkManager --no-daemon \")"
> QNetworkManagerInterface::QNetworkManagerInterface(QObject*) nmReply
> "An AppArmor policy prevents this sender from sending this message to
> this recipient; type=\"method_call\", sender=\":1.138\" (uid=1000
> pid=7546 comm=\"/snap/shadow/x2/usr/local/bin/umbra \")
> interface=\"org.freedesktop.NetworkManager\" member=\"GetDevices\"
> error name=\"(unset)\" requested_reply=\"0\"
> destination=\"org.freedesktop.NetworkManager\" (uid=0 pid=864
> comm=\"/usr/sbin/NetworkManager --no-daemon \")"
> 
> snappy-debug doesn't mention anything about it. How can we fix that?

snappy-debug doesn't support dbus denials yet. This is planned. You need to
'grep DEN /var/log/syslog' for dbus denials when debugging for now.

> Here is the snapcraft.yaml:
> https://github.com/shadowproject/shadow/blob/master/snapcraft.yaml
> -- 
> ¡paz y baile!
> http://www.ubuntu.com
> 
-- 
Jamie Strandboge             | http://www.canonical.com

-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: This is a digitally signed message part
URL: <https://lists.ubuntu.com/archives/snapcraft/attachments/20170105/86bd335c/attachment.sig>