Re: Desktop snaps are not working in KDE

On 29.03.2017 18:40, Simon Fels wrote: > Hey everyone, > > we currently see bug reports (e.g. > https://bugzilla.opensuse.org/show_bug.cgi?id=1031501) that certain > snaps are not working in KDE on openSUSE (42.2 / Tumbleweed). On the > same distribution, when I run the

Desktop snaps are not working in KDE

Hey everyone, we currently see bug reports (e.g. https://bugzilla.opensuse.org/show_bug.cgi?id=1031501) that certain snaps are not working in KDE on openSUSE (42.2 / Tumbleweed). On the same distribution, when I run the snaps within Gnome, everything works as it should and the applications are

Re: content interface, DENIED mounting $SNAP/mydir

On 03.03.2017 01:06, Michi Henning wrote: > >> On 3 Mar 2017, at 4:33 , knitzsche > > wrote: >> >> Hi, >> >> I am trying to use the wifi-ap content sharing interface. >> >> It is DENIED (see below) when I try to use a $SNAP

Re: chroot into a snap

On 09.02.2017 17:08, Thomas Voß wrote: > On Thu, Feb 9, 2017 at 2:38 PM, Roberto Mier Escandón  > wrote: >> Because this will use nextcloud documents, and they are internal to >> nextcloud snap >> > > In that case, content-sharing would help, yes. Is that always

Re: a little script: snapdiff

On 10.02.2017 01:44, Michael Hudson-Doyle wrote: > Very much inspired by debdiff, I wrote a little script to compare two > snaps. It looks like this: > > (master)mwhudson@aeglos:/opt/opensource/snaps/go$ snapdiff > go-17-mwhudson_1.snap go-17-mwhudson_2.snap > Only in second snap,

Re: IPC between snaps

On 09.02.2017 11:36, Roberto Mier Escandón  wrote: > Thanks Löic. > I'll take a look > > On 09/02/17 11:18, Loïc Minier wrote: >> Hi, >> >> Yes, this is typically how you allow a snap to talk to snapd or docker >> daemon or lxd. You need a new interface to grant access to this socket >> path. If

Re: [System Enablement] New releases Feb 2017

On 07.02.2017 15:40, Simon Fels wrote: > Hey everyone, > > new releases of the alsa-utils, network-manager, upower and wifi-ap > snaps were pushed into the candidate channel. > > alsa-utils 1.1.2-2: > > * First official release supported by Canonical > * Aliase

[System Enablement] New releases Feb 2017

Hey everyone, new releases of the alsa-utils, network-manager, upower and wifi-ap snaps were pushed into the candidate channel. alsa-utils 1.1.2-2: * First official release supported by Canonical * Aliases for all exported commands are available * Set of automated and manual test cases

Re: the ppp interface (and general renaming/transitioning of interfaces)

On 06.02.2017 15:48, Simon Fels wrote: > On 06.02.2017 14:36, Oliver Grawert wrote: >> hi, >> >> on the core images we currently provide a ppp interface that used to be >> used for pppd access in 15.04 images and also gives access to >> /dev/tty[0-9]. >

Re: the ppp interface (and general renaming/transitioning of interfaces)

On 06.02.2017 14:36, Oliver Grawert wrote: > hi, > > on the core images we currently provide a ppp interface that used to be > used for pppd access in 15.04 images and also gives access to > /dev/tty[0-9]. > > with series 16 the pppd binary was dropped from the core snap and a > pppd snap was

Re: Which snap interface allows accessing /dev/rfkill?

On 19.01.2017 10:41, Tonny Tzeng wrote: > Hi, > > I'd like to unblock the Bluetooth interface on Ubuntu Core, so I use > 'stage-packages' keyword to install 'rfkill' package to my snap. If I > install the snap in devmode, the rfkill command works as expected. But > if the snap is installed in

Re: DHCP and /etc/resolv.conf

:snapcraft-boun...@lists.snapcraft.io] On Behalf Of Simon Fels > Sent: Tuesday, January 17, 2017 11:05 AM > To: snapcraft@lists.snapcraft.io > Subject: Re: DHCP and /etc/resolv.conf > > On 17.01.2017 14:18, Zygmunt Krynicki wrote: >> Quick grep tells me that no interface curren

Re: DHCP and /etc/resolv.conf

On 17.01.2017 14:18, Zygmunt Krynicki wrote: > Quick grep tells me that no interface currently relates to "resolv.conf" file Actually you shouldn't allow access to /etc/resolv.conf but to /run/resolvconf/ which the network-manager interface allows as the only one so far. regards, Simon > On

Re: [System Enablement] New releases: wifi-ap=10 pulseaudio=8.0-3

As both platform and commercial QA have approved the new snaps I would like to go ahead with both snaps earlier than waiting for next Wednesday and publishing them to stable. Any objections from anyone? regards, Simon On Wed, Jan 4, 2017 at 2:51 PM, Simon Fels <simon.f...@canonical.com>

Re: Serial Port Plug/Interface issue with Ubuntu-core 16.04 (#2557)

You can add a serial port slot to a gadget snap.yaml like this: ttyS4: interface: serial-port path: /dev/ttyS4 This only applies to static serial port nodes. If you have one provided by an USB device you have to user a slightly different slot definition which refers the USB product/vendor id

Re: [System Enablement] New releases: wifi-ap=10 pulseaudio=8.0-3

On 04.01.2017 17:10, Jon Melamut wrote: > > > On Wednesday, January 4, 2017, Simon Fels <simon.f...@canonical.com > <mailto:simon.f...@canonical.com>> wrote: > > Hey everyone, > > A new release of the wifi-ap and pulseaudio snaps were pus

Re: [System Enablement] New releases: wifi-ap=10 pulseaudio=8.0-3

On 04.01.2017 15:16, Jamie Bennett wrote: > On Wed, Jan 4, 2017 at 1:51 PM, Simon Fels <simon.f...@canonical.com> wrote: >> Hey everyone, >> >> A new release of the wifi-ap and pulseaudio snaps were pushed into the >> candidate channel. This release includes sever

[System Enablement] New releases: wifi-ap=10 pulseaudio=8.0-3

Hey everyone, A new release of the wifi-ap and pulseaudio snaps were pushed into the candidate channel. This release includes several improvements for both snaps. wifi-ap: * Switched to a unix domain socket instead of a local TCP endpoint to provide secure access to the management service REST

Re: Source of ssh key for first login

Take https://git.launchpad.net/~snappy-hwe-team/snappy-hwe-snaps/+git/network-manager/tree/tests/image as an example of how to generate such an image which includes a predefined user (user: test, password: test in this case). This comes with some implications (like if you're not the brand the

Re: Wifi setup problem on Bubblegum 96board ubuntu core snappy

Why are you calling $ sudo netplan ifupdown-migrate ? The correct steps to apply the netplan configuration is $ sudo netplan generate $ sudo netplan apply regards, Simon On Tue, Nov 29, 2016 at 9:08 AM, Zechao Wang wrote: > hello, luo > > The yaml file is set as

Re: Is there any guidance/document about how to write App-provided slots

On 14.11.2016 11:56, Enwei Zhang wrote: > Thanks David. Did you forget to add Morphis and Zyga? :) > Loop Simon. > Simon told me here is the latest bluez snap, > https://code.launchpad.net/~snappy-hwe-team/snappy-hwe-snaps/+git/bluez >

Re: Snap hangs when accessing a special /dev/file (/dev/vcio) [ubuntu-core 16 / RaspberryPi2]

On 09.11.2016 21:25, Jacques Supcik wrote: > Thank you Oliver for your constructive feedback. > > I like the idea of a "mailbox-device" and I will open a bug in the > whishlist of snappy. > > My snap needs also write access to "/dev/mem": > > = AppArmor = > Time: Nov 9 19:09:52 > Log:

Re: questions about connecting bluez interface

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

Re: CLI UX for plugs with parameters?

You wont set the attribute of the slot/plug in the command line you use to connect slot and plug. Every attribute as to be set in the definition of the plug/slot. Like plugs: my-plug: interface: really-awesome-interface attribute1: value1 ... Then you simply connect via $ snap

Re: Access denied to /dev/ttyUSB0

On 07.09.2016 15:05, Loïc Minier wrote: > Hi, > > You need to use: > > plugs: [serial-port] > > In your snapcraft.yaml; then you also have to connect your snap to that > interface manually as it's not autoconnected; check "snap interfaces" to > see which plugs and slots are connected. That

Re: Snappy on OpenSwitch

Hey Mike, >> I'm very interested in adding Snappy support to OpenSwitch >> (www.openswitch.net ). >> >> OpenSwitch is a Network Operating System for network switches build upon >> OpenEmbedded/Yocto/Poky. > > Pretty nice idea! > >> I'm using a branch of OpenSwitch in

Re: Need LXD for Ubuntu Core 16 image

On 02.09.2016 11:43, Omer Akram wrote: > Hi! > > I am working with Ubuntu Core 16 image[1] on a Raspberry Pi. I am > wondering if I there is a LXD snap that I can install on that image ? I > found this snap[2] but it seems its not available for Ubuntu Core 16. > > Is there a place where I can

Re: New ubuntu-device-flash cannot use own gadget snap?

B/s 0 > > Unmounting... > > New image complete > > Summary: > > Output: snappy.img > > Architecture: amd64 > > Channel: edge > > Version: 0 > > > On Wed, Aug 31, 2016 at 11:11 AM, Yann Sionneau > <yann.sionn...@parrot.com <mailto:yann.sionn...

Re: New ubuntu-device-flash cannot use own gadget snap?

On 31.08.2016 10:49, Yann Sionneau wrote: > Hello, > > It seems the new (snapp'ed) ubuntu-device-flash cannot use my own gadget > snap anymore. > > yann@imperium$ sudo -E /snap/bin/ubuntu-device-flash --verbose core 16 > -o snappy.img --channel edge --gadget $PWD/../../../xxx_2.0_all.snap >

Re: Snappy on OpenSwitch

Hey Mike, > I'm very interested in adding Snappy support to OpenSwitch > (www.openswitch.net ). > > OpenSwitch is a Network Operating System for network switches build upon > OpenEmbedded/Yocto/Poky. Pretty nice idea! > I'm using a branch of OpenSwitch in which

Re: Using sudo from within a snap

On 06.08.2016 15:54, Chris Wayne wrote: > Hi guys, > > I seem to be having some issues while running anything as sudo from within a > snap (namely bug > https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1610292). If you package sudo within your snap snapcraft will strip the necessary suid

Snaps on Yocto/OpenEmbedded

Hey everyone, after an idea during the sprint in Heidelberg I've quickly created a meta-snappy layer for Yocto/OpenEmbedded which now brings snaps to any Yocto/OpenEmbedded based operating system (assuming it runs systemd). The relevant git repository and instructions how to get started are

Re: Overriding seccomp policy: shm_open

On 01.08.2016 06:55, Jacob Zimmermann wrote: > Hi > > I'm trying to get my hands on snapcraft by building a snap of "Hatari" > (Atari ST emulator). I got it working nicely in devmode but it won't run > under strict confinement, specifically it gets killed when attempting to > execute shm_open().