In my case, I just use this service inside the app. No other apps use it
but making the apparmor error gone away. My snapcraft.yaml is at:
https://github.com/liu-xiao-guo/xmradio/blob/master/snap/snapcraft.yaml
Thanks for your explanation.
On Thu, Mar 23, 2017 at 11:16 PM, Jamie Strandboge
wrot
On 10/06/16 06:36, Gustavo Niemeyer wrote:
> If it's a blank check, I don't see many advantages over asking for
> unity7 itself. Once we want to force the declaration, we can just
> introduce the actual interface.
My only reason for an orthogonal interface was so that we don't end up
duplicating t
Opinions! Always! How about 'session-dbus-bind' ? :)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1590679
Title:
Apps can't own session bus names (unity7 interface)
To manage notifications about t
Can we have an interface which is "bind to the user session dbus", and
then evolve it to add parameters, being a list of the names you want to
actually bind? That way we could start appropving those apps now with
"any" use dbus name, and evolve over time to require that they itemise
their interface
On 09/06/16 17:41, Sebastien Bacher wrote:
> That's something most of GNOME apps do nowadays ... Jamie, Tyler, do you
> know if it would be easy to allow that in the unity7 apparmor rules?
I bet we can make an interface which lets the snap own an explicit bus
name, yes.
I don't think we yet have
