Exposing dbus interface and using it inside the same snap
knitzsche
kyle.nitzsche at canonical.com
Tue Feb 14 00:57:28 UTC 2017
Hi Jamie,
Can you please point out the error in the below?
I believe he is getting an error like this (perhaps truncated):
Feb 13 19:33:07 ubuntu snap[3207]: GLib.Error: g-dbus-error-quark:
GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Connection ":1.49"
is not allowed to own the service "com.screenly.playlist" due to
security policies in the c
Feb 13 19:33:07 ubuntu snap[3207]: 0, timeout_to_glib(timeout),
None).unpack()
thanks,
kyleN
On 02/10/2017 12:35 PM, Sergey Borovkov wrote:
> Hi, I've been struggling with getting dbus interface exposed. I am
> getting this error during runtime:
> GLib.Error: g-dbus-error-quark:
> GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Connection
> ":1.1160" is not allowed to own the service "com.screenly.playlist" due
> to security policies in the configuration file (9)
>
> jdstrand helped me on IRC, and told me I need to have a slot and a plug
> in my snap. I am doing something wrong though, can someone help out with
> how it's correctly supposed to be used?
>
> apps:
> playlist:
> command: usr/bin/playlist-service.sh
> daemon: simple
> plugs: [network-bind, network, playlist-dbus]
>
> websocket:
> command: usr/bin/websocket-service.sh
> daemon: simple
> plugs: [network-bind, network, dbus]
> slots: [websocket-dbus]
>
> slots:
> playlist-dbus:
> interface: dbus
> name: com.screenly
> bus: system
>
> plugs:
> websocket-dbus:
> interface: dbus
> name: com.screenly
> bus: system
>
>
More information about the Snapcraft
mailing list