On Mon, 2017-04-03 at 22:57 +0300, Sergey Borovkov wrote:
...
GLib.GError:
> g-dbus-error-quark: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: An
> AppArmor policy prevents this sender from sending this message to this
> recipient; type="
We worked through
So once the interfaces are connected the following happens:
1. In websocket service (the one that just calls methods over dbus) I can
get system bus without any issues.
2. In the second service, the one that exposes dbus interface I get
following exception when running this code:
try:
On Mon, 2017-04-03 at 17:57 +0300, Sergey Borovkov wrote:
> Hi, I manually connected interfaces. But the issue is that it can't even
> connect to system bus? Before trying to call any methods.
>
I'm slightly confused, so let's back up. It sounds like you are saying that you
install the snap and th
Hi, I manually connected interfaces. But the issue is that it can't even
connect to system bus? Before trying to call any methods.
root@localhost:/home/pi# snap interfaces
Slot Plug
:account-control -
:alsa -
:au
On Fri, 2017-03-31 at 17:55 +0300, Sergey Borovkov wrote:
...
> Mar 31 12:44:02 localhost.localdomain kernel: audit: type=1400
> audit(1490964242.523:72): apparmor="DENIED" operation="connect" profile=
> "snap.screenly-client.websocket" name="/run/dbus/system_bus_socket"
> pid=1466 comm="python3"
Hi Jamie,
Do you have any input on this issue?
thanks
On 03/31/2017 10:55 AM, Sergey Borovkov wrote:
Hi. I am running a couple of daemons (daemon: simple) and they interact
between each other using dbus. Unfortunately I've ran into the issue when
porting them from devmode to strict, I am getti
Hi folks, any tips here to unblock this critical issue? Thanks
On 03/31/2017 10:55 AM, Sergey Borovkov wrote:
Hi. I am running a couple of daemons (daemon: simple) and they interact
between each other using dbus. Unfortunately I've ran into the issue when
porting them from devmode to strict, I a
