Re: content interface, DENIED mounting $SNAP/mydir

Hey Kyle, If this is of help, you can check how I did it in the case of Collabora Office snap [1] using Nextcloud [2] docs in write mode. I created the target folder into "snap/" and then I referred it in snapcraft.yaml plug skipping "snap" parent, like this: target: though the folder was indee

Re: content interface, DENIED mounting $SNAP/mydir

On 03.03.2017 08:37, XiaoGuo Liu wrote: > Can we use the configure hook to create the directory at installation? No, as it runs after the automatic connection of plugs/slots defined in the snap-declaration. regards, Simon -- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings o

Re: content interface, DENIED mounting $SNAP/mydir

hi, Am Donnerstag, den 02.03.2017, 13:33 -0500 schrieb knitzsche: > > It is DENIED (see below) when I try to use a $SNAP directory. the $SNAP directory is root owned and readonly (it is the mounted squashfs), the $SNAP_DATA dir is likewise root owned (but indeed writable). even if you have a dir

First Snap ktouch - no success

Hi all, According to the site https://www.ubuntu.com/desktop/snappy I just installed my first snap - which was ktouch - simply with sudo snap install ktouch The I just run the application ("which ktouch" informs me that the path is /snap/bin/ktouch), but it immediately aborts with ktouch: erro

Re: First Snap ktouch - no success

hi, Am Freitag, den 03.03.2017, 12:33 +0100 schrieb Harald Nikolisin: > Hi all, > > According to the site  https://www.ubuntu.com/desktop/snappy > I just installed my first snap - which was ktouch - simply with > sudo snap install ktouch > > The I just run the application  ("which ktouch" informs

Re: First Snap ktouch - no success

hi, Am Freitag, den 03.03.2017, 12:53 +0100 schrieb Oliver Grawert: > hi, > Am Freitag, den 03.03.2017, 12:33 +0100 schrieb Harald Nikolisin: > >  > > According to the site  https://www.ubuntu.com/desktop/snappy > > I just installed my first snap - which was ktouch - simply with > > sudo snap insta

Re: First Snap ktouch - no success

@oli: Thx for the link! you said "looks rather like you did not add libqt5sql5 to your stage-packages in snapcraft.yaml ..." That is a task for the creator/maintainer of the snap, or is it a task for the user? Harald Am 03.03.2017 um 12:53 schrieb Oliver Grawert: > hi, > Am Freitag, den 03.03.2

plugins in snap?

Hi, Maybe one silly question: I've moved plugins to be in snap/plugins path. All works fine, but I see them included in the snap package. Is there any way to avoid this?. I don't want the plugins there. Thanks. -- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify settings or unsubscrib

Running xdg-open

Hi all! Currently the xdg-open tool is provided by the core snap, which has it located in its /usr/local/bin/ path. Unfortunately, this means that other snaps cannot run it, unless they have /usr/local/bin in their PATH. Consequently, I filed a bug against the desktop helpers script [1] requestin

Re: Running xdg-open

On 03/03/17 15:02, Alberto Mardegan wrote: > Currently the xdg-open tool is provided by the core snap, which has it > located in its /usr/local/bin/ path. Will it not always be available at /snap/core/current/usr/local/bin/ ? Mark -- Snapcraft mailing list Snapcraft@lists.snapcraft.io Modify

Re: Running xdg-open

hi, Am Freitag, den 03.03.2017, 17:02 +0300 schrieb Alberto Mardegan: > Hi all! >   Currently the xdg-open tool is provided by the core snap, which has > it > located in its /usr/local/bin/ path. > Unfortunately, this means that other snaps cannot run it, unless they > have /usr/local/bin in their

Re: First Snap ktouch - no success

I believe there is a KDE snap that has all the libraries needed by KDE apps. Something like frameworks. On Mar 3, 2017 7:04 AM, "Harald Nikolisin" wrote: > @oli: Thx for the link! > > you said "looks rather like you did not add libqt5sql5 to > your stage-packages in snapcraft.yaml ..." > > That

Re: Running xdg-open

hi, Am Freitag, den 03.03.2017, 15:22 +0100 schrieb Mark Shuttleworth: > On 03/03/17 15:02, Alberto Mardegan wrote: > > > >   Currently the xdg-open tool is provided by the core snap, which > > has it > > located in its /usr/local/bin/ path. > Will it not always be available at /snap/core/current/

Re: Running xdg-open

Le 03/03/2017 à 15:54, Oliver Grawert a écrit : hi, Am Freitag, den 03.03.2017, 15:22 +0100 schrieb Mark Shuttleworth: On 03/03/17 15:02, Alberto Mardegan wrote: Currently the xdg-open tool is provided by the core snap, which has it located in its /usr/local/bin/ path. Will it not always be

Re: First Snap ktouch - no success

Ok, I searched and found kde-frameworks-5 and installed it. But still the same problem. However - my naive expectation on snaps is that I install only(!) the application without bothering which other SW is needed to run it. Am I wrong with that? Am 03.03.2017 um 15:25 schrieb Aaron Honeycutt: > I

Re: First Snap ktouch - no success

On 03/03/17 16:56, Harald Nikolisin wrote: > However - my naive expectation on snaps is that I install only(!) the > application without bothering which other SW is needed to run it. Am I > wrong with that? Snaps allow for completely self-contained apps, yes. But they also allow the publisher of t

Re: First Snap ktouch - no success

On Fri, 2017-03-03 at 16:56 +0100, Harald Nikolisin wrote: > Ok, I searched and found kde-frameworks-5 and installed it. > But still the same problem. > You likely are now experiencing a different bug where the snap is not connected and/or the mount namespace is not properly set up because you ins

New snapd 2.23 release

Hi, The snappy team is happy to announce the new snapd 2.23 release! The new release is available in the "core" (and "ubuntu-core") snap on the "candidate" channel and also in the Ubuntu 14.04, 16.04, 16.10 "proposed" pockets and in 17.04. To install this new release you need to run the followin

Snaps and the latest 16.04 kernel (problem?)

Hi, one of my snaps stopped to work properly today [1]. Trying to debug it, I find out that: - If I boot using the previous 4.4.0-64 kernel, I can successfully run the snap. - If I let GRUB do its job (kernel 4.4.0-65), the snap cannot start properly and I can see new apparmor="DENIED" on logs. -

Re: plugins in snap?

Hello Roberto, On Fri, Mar 3, 2017 at 6:37 AM, Roberto Mier Escandón  wrote: > Maybe one silly question: I've moved plugins to be in snap/plugins path. > All works fine, but I see them included in the snap package. Is there > any way to avoid this?. I don't want the plugins there. We are trying

Re: Snaps and the latest 16.04 kernel (problem?)

On Fri, 2017-03-03 at 16:32 -0300, Claudio André wrote: > Hi, one of my snaps stopped to work properly today [1]. Trying to debug it, > I find out that: > > - If I boot using the previous 4.4.0-64 kernel, I can successfully run the > snap. > - If I let GRUB do its job (kernel 4.4.0-65), the snap c

auto-import of system-user assertion on vm

I'm attempting to run a virtual machine with an ubuntu core image and an additional image containing a system-user assertion attached as a usb device. The auto-import mechanism appears to find the assertion, but does not seem actually succeed at creating the user. To verify this, I'm creating a use

Re: plugins in snap?

Thanks Leo, I didn't know about that discussion. I'll take a look. On 03/03/17 20:41, Leo Arias wrote: > Hello Roberto, > > On Fri, Mar 3, 2017 at 6:37 AM, Roberto Mier Escandón  > wrote: >> Maybe one silly question: I've moved plugins to be in snap/plugins path. >> All works fine, but I see th

Re: sosreport and snaps

Hello Louis! On Fri, Feb 17, 2017 at 11:35 AM, Louis Bouchard wrote: > If you have to diagnose a bug in the snappy ecosystem, what information will > you > be asking for ? If some information is sensible, it can be obfuscated at > run-time so it is not included in the produced tarball. snap ver

Re: GEM/Ruby snapcraft plugin?

Hey Justin! On Wed, Feb 15, 2017 at 12:45 AM, Justin McPherson wrote: > I had a chance to take a quick look at this; see here > > > The plugin works in this case, with gist. But is not good enough to be a > general solution - no native extensions, probably