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:
pio-9 -
- screenly-pi3:snapd-control
On 3 April 2017 at 16:58, Jamie Strandboge wrote:
> 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="D
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 getting this backtrace just
trying to obtain SystemBus in python:
Mar 31 12:44:02 localhost.localdomain snap[1
; # See the systemd.service manual on Restart for details.
> restart-condition: \
> on-failure | on-success | on-abnormal | on-abort | always | never
>
> Cheers.
>
> [1] https://snapcraft.io/docs/snaps/metadata
>
> On 16/03/17 09:41, Ara Pulido wrote:
> > On Thu,
Hello,
I am running service using daemon: simple in snapcraft. Is there any way to
configure how systemd handles restarting in the snapcraft.yaml? Current
behavior is that it restarts the service when it exits with non zero exit
code. But it does not get restarted otherwise. Can this be tweaked?
--
Nvm guys, I figured it out.
On 14 February 2017 at 09:44, Sergey Borovkov
wrote:
> Hi, I am using this code:
>
> apps:
> playlist:
> command: usr/bin/playlist-service.sh
> daemon: simple
> plugs: [network-bind, network]
> slots: [playlist-dbus
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-c
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 c
linux-raspi2 -e
> u-boot
>
>
> And you should get the package information like this comment
> https://bugs.launchpad.net/ubuntu/+source/linux-raspi2/+
> bug/1636838/comments/20
>
> Cheers,
> Taihsiang
>
> 2016-12-22 2:48 GMT+08:00 Sergey Borovkov :
>
>&
). Perhaps you could try the PPA listed in that
> bug? (Note that this is technically a bug for rpi2, but I *believe* they
> may share the same kernel)
>
> Thanks
> Chris
>
> On Wed, Dec 21, 2016 at 9:57 AM, Sergey Borovkov > wrote:
>
>> Hi. After I did apt upg
-raspi2/+bug/1636838
> (which should now be fixed). Perhaps you could try the PPA listed in that
> bug? (Note that this is technically a bug for rpi2, but I *believe* they
> may share the same kernel)
>
> Thanks
> Chris
>
> On Wed, Dec 21, 2016 at 9:57 AM, Sergey Borovko
Hi. After I did apt upgrade on classic image I can't boot my RPI anymore.
It's stuck on 'Starting kernel...'.
Tried different SD cards (on the second one I flashed out new classic image
and did upgrade as well) with the same result.
--
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify set
12 matches
Mail list logo
