Exposing dbus interface and using it inside the same snap
Sergey Borovkov
serge.borovkov at gmail.com
Tue Feb 14 09:40:19 UTC 2017
Nvm guys, I figured it out.
On 14 February 2017 at 09:44, Sergey Borovkov <serge.borovkov at gmail.com>
wrote:
> Hi, I am using this code:
>
> apps:
> playlist:
> command: usr/bin/playlist-service.sh
> daemon: simple
> plugs: [network-bind, network]
> slots: [playlist-dbus-server]
>
> websocket:
> command: usr/bin/websocket-service.sh
> daemon: simple
> plugs: [network-bind, network, playlist-dbus-client]
>
> slots:
> playlist-dbus-server:
> interface: dbus
> name: com.screenly.playlist
> bus: system
>
> plugs:
> playlist-dbus-client:
> interface: dbus
> name: com.screenly.playlist
> bus: system
>
> After doing snap installl --devmode screenly.snap snapd prints out this
> error:
> 2017-02-13T21:48:28Z INFO snap "screenly-client" has bad plugs or slots:
> dbus (cannot find attribute 'bus')
>
> All of this happens with snapd from the proposed repository:
>
> root at ubuntu:/home/ubuntu# snap --version
> snap 2.22.2
> snapd 2.22.2
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.ubuntu.com/archives/snapcraft/attachments/20170214/c13c3f21/attachment.html>
More information about the Snapcraft
mailing list