Hey Robert, the bluez plug and slot are now auto-connected as we put a snap-declaration for it on the store side in place. That assertion tells snapd that the bluez snap should get its slots/plugs automatically connected. But this only applies for the bluez snap coming from the store. If you install one you built locally you don't have the signed assertion from the store which would tell snapd to auto-connect the relevant plugs and slots.
However I am not sure why the interface connection is denied when you do it manually. @Samuele, Jamie: Any idea? regards, Simon On Thu, Oct 27, 2016 at 6:54 AM, Robert Liu <robert....@canonical.com> wrote: > Hi list, > > I have 2 questions about connecting bluez interface. > In Interfaces reference [1], it said the bluez is not auto-connected. But > after I installed the bluez snap, the bluez interface is connected. Do I > misunderstnad the definition? > > root@localhost:/tmp# snap install --edge bluez > bluez (edge) 5.37-2 from 'canonical' installed > root@localhost:/tmp# snap interfaces > Slot Plug > bluez:service bluez:client > > > The other question is that I cannot connect the interface when using my > own bluez snap. Should I sign my snap to make this work? > > root@localhost:/tmp# snap install --dangerous bluez_5.37-2_amd64.snap > bluez 5.37-2 installed > root@localhost:/tmp# snap interfaces > Slot Plug > bluez:service - > [snipped] > - bluez:client > root@localhost:/tmp# snap connect bluez:client bluez:service > error: cannot perform the following tasks: > - Connect bluez:client to bluez:service (connection denied by slot rule of > interface "bluez") > > [1] http://snapcraft.io/docs/reference/interfaces > > BR, > Robert > > -- > Snapcraft mailing list > Snapcraft@lists.snapcraft.io > Modify settings or unsubscribe at: https://lists.ubuntu.com/ > mailman/listinfo/snapcraft > >
-- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/snapcraft
