Re: Semaphores and access to /dev/shm

[Alberto Mardegan]

On 09/02/2017 02:22, Jamie Strandboge wrote:
> I confirmed this works fine under confinement (return code checking omitted 
> for
> clarity):
> 
>char *name = "/dev/shm/sem.snap.foo.bar";
>open(name, O_CREAT | O_EXCL | O_RDRW, S_IRUSR | S_IWUSR);
>sem_open("snap.foo.bar", 0);
> 
> As such, sem_open() can work under confinement, but the application needs to 
> be
> written to work within it.

Thanks Jamie, this is helpful!

> Sergio put together snapcraft-preload:
> https://github.com/sergiusens/snapcraft-preload
> 
> It doesn't seem to have sem_open() support yet, but it certainly could.

Cool, I didn't know about this project. I submitted

https://github.com/sergiusens/snapcraft-preload/issues/2

Ciao,
  Alberto



signature.asc
Description: OpenPGP digital signature
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: [System Enablement] New releases Feb 2017

[Simon Fels]

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
> * Aliases for all exported commands are available
> * Set of automated and manual test cases guarantee quality of each release
> 
> network-manager 1.2.2-11:
> 
> * Wake-on-WLAN can be configured via snap confiration / nmcli
> * Automatic reconfiguration of network devices when devices wakes up
> * Alias support for nmcli command
> * WiFi powersave is now configurable via snap configuration
> * Network-Manager tests are using tests-extras repository to fetch the
> image creating scripts rather than embed them.
> 
> upower 0.99.4-2:
> 
> * First release
> * Integration with systemd to suspend the system on low battery events

We found a problem with upower which causes its plugs/slots not
correctly connected/specified. This is now fixed and new revisions are
uploaded into the candidate channel. The following revisions are now
available for testing:

22 (amd64)
25 (arm64)
24 (armhf)
23 (i386)

regards,
Simon


-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

[Dragonboard410c] Ubuntu OS Build Issues, and Support

[Sunny Bhayani]

Hi Oliver / Paolo,

Thank you for your time.

> the work is going on here:
>
> https://github.com/snapcore/snapcraft/pull/1115

Is there a way, that we can come to know about an official fix, apart from the
above link that you mentioned.

Also, how did the build for the Dragonboard410C succeed for the pre-built
Ubuntu Core OS image ?

Since that is working properly, /lib/modules have the kernel modules and
/lib/firmware has the firmware binaries.

Also, the wifi interface (wlan0) is working.

Sorry, but I was just curious to know this.


Thanks,
Sunny
*
 eInfochips Business Disclaimer: This e-mail message and all attachments 
transmitted with it are intended solely for the use of the addressee and may 
contain legally privileged and confidential information. If the reader of this 
message is not the intended recipient, or an employee or agent responsible for 
delivering this message to the intended recipient, you are hereby notified that 
any dissemination, distribution, copying, or other use of this message or its 
attachments is strictly prohibited. If you have received this message in error, 
please notify the sender immediately by replying to this message and please 
delete it from your computer. Any views expressed in this message are those of 
the individual sender unless otherwise stated. Company has taken enough 
precautions to prevent the spread of viruses. However the company accepts no 
liability for any damage caused by any virus transmitted by this email. 
*
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: ubuntu-app-platform updated to Qt 5.6.2

[XiaoGuo Liu]

Hi James,

Thanks for your reply. Yeah, it could be reason for it. I used to have a Qt
project, and the app was launched by desktop-launch:

https://github.com/liu-xiao-guo/rssreader_platform

For my case, it is a html5 app. I do not know what is the correct way to
launch the app. Do you know what should be set up correctly? I may have my
own script to set them up.

Thanks & best regards,
XiaoGuo

On Thu, Feb 9, 2017 at 12:02 PM, James Henstridge <
james.henstri...@canonical.com> wrote:

> On 9 February 2017 at 10:43, XiaoGuo Liu 
> wrote:
> > I am now trying to snap a html5 webapp. My source code is here at:
> >
> > https://github.com/liu-xiao-guo/wuziqi
>
> Looking at the snapcraft.yaml file, you don't seem to be using the
> launcher shell script provided by the part.  Without that,
> LD_LIBRARY_PATH and other environment variables won't be set up
> correctly to use libraries provided by ubuntu-app-platform.
>
> James.
>
> --
> Snapcraft mailing list
> Snapcraft@lists.snapcraft.io
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/snapcraft
>



-- 
XiaoGuo, Liu
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: ubuntu-app-platform updated to Qt 5.6.2

[James Henstridge]

On 9 February 2017 at 10:43, XiaoGuo Liu  wrote:
> I am now trying to snap a html5 webapp. My source code is here at:
>
> https://github.com/liu-xiao-guo/wuziqi

Looking at the snapcraft.yaml file, you don't seem to be using the
launcher shell script provided by the part.  Without that,
LD_LIBRARY_PATH and other environment variables won't be set up
correctly to use libraries provided by ubuntu-app-platform.

James.

-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: ubuntu-app-platform updated to Qt 5.6.2

[XiaoGuo Liu]

These days, I tried to make use of ubuntu-app-platform. I have upgraded the
snap to the latest version 34 from the edge channel. Still I get an error
like:

This application failed to start because it could not find or load the Qt
platform plugin "xcb"
in "".

Reinstalling the application may fix this problem.
Aborted (core dumped)

What could be the problem for it?

Thanks & best regards,
XiaoGuo

On Wed, Feb 8, 2017 at 11:54 PM, Florian Boucault <
florian.bouca...@canonical.com> wrote:

> Indeed, sorry about that. The latest version with no Qt bundled is
> released now.
>
> Florian
>
> Le mer. 8 févr. 2017 à 14:20, Timo Jyrinki  a
> écrit :
>
>> 2017-02-07 17:00 GMT+02:00 Florian Boucault > com>:
>> > I thought I fixed the terminal last week. At least the terminal
>> available on
>> > the edge channel now is working for me. Does it work for you?
>> > I made sure that the stage-packages only contain packages that are not
>> in
>> > ubuntu-app-platform and also used  build-attributes:
>> [no-system-libraries]
>>
>> It does not work if I upgrade to the edge version of
>> ubuntu-app-platform (and uninstall and reinstall ubuntu-terminal-app).
>>
>> So yes you fixed it, and I tested the fix but the fixed version needs
>> to be uploaded to the store by someone with rights. Maybe Bill?
>>
>> The current 33 version in the store still has the bundled Qt libraries
>> - see $ ls /snap/ubuntu-terminal-app/33/usr/lib/x86_64-linux-gnu/
>>
>> -Timo
>>
>> --
>> Snapcraft mailing list
>> Snapcraft@lists.snapcraft.io
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/
>> mailman/listinfo/snapcraft
>>
>
> --
> Snapcraft mailing list
> Snapcraft@lists.snapcraft.io
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/snapcraft
>
>


-- 
XiaoGuo, Liu
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Semaphores and access to /dev/shm

[Jamie Strandboge]

On Thu, 2017-02-09 at 00:31 +0300, Alberto Mardegan wrote:
> Hi all!
>   I'm working on a snap of a python2 utility which is using the Pool
> class from the multiprocessing module. But this gets blocked by apparmor:
> 
> Log: apparmor="DENIED" operation="mknod"
> profile="snap.bundler-mardy.bundler-py" name="/dev/shm/8sszOM" pid=17782
> comm="python2" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
> File: /dev/shm/8sszOM (write)
> Suggestion:
> * adjust program to create files and directories in
> /dev/shm/snap.$SNAP_NAME.*
> 
> 
> Unfortunately, the suggestion is not really helpful, because the
> filename is not decided by the client code. But even if somehow we fixed
> the python implementation to generate a proper name, it looks like
> sem_open() is behaving in a very peculiar way: please have a look at
> this strace log, obtained on an *unconfined* process:
> 
> =
> statfs("/dev/shm/", {...}) = 0
> futex(0x7f1b658f9310, FUTEX_WAKE_PRIVATE, 2147483647) = 0
> lstat("/dev/shm/ApjbNj", 0x7ffe9cefff20) = -1 ENOENT
> open("/dev/shm/ApjbNj", O_RDWR|O_CREAT|O_EXCL, 0600) = 6
> write(6,
> "\1\0\0\0\0\0\0\0\200\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
> 32) = 32
> mmap(NULL, 32, PROT_READ|PROT_WRITE, MAP_SHARED, 6, 0) = 0x7f1b65a5d000
> link("/dev/shm/ApjbNj", "/dev/shm/sem.mp18207-15353487325820441356") = 0
> fstat(6, {st_mode=S_IFREG|0600, st_size=32, ...}) = 0
> unlink("/dev/shm/ApjbNj")   = 0
> close(6)= 0
> =
> 
> That is, it looks like sem_open() is first creating a temporary file,
> and then linking it to a file with the proper name (the python code is
> using "/mp%ld-%lu" as semaphore filename). This also seems confirmed by
> a quick look at glibc's source code:
> 
> http://sourceware.org/git/?p=glibc.git;a=blob;f=nptl/sem_open.c;h=a80e5b8e9b15
> 090c2ecacb1c1e587c501cf20ffb;hb=HEAD#l277
> 
> So, it looks like sem_open() can't possibly work under confinement, or
> am I missing something here?
> 

sem_open() is https://bugs.launchpad.net/snappy/+bug/1653955 and snapd 2.21
added support to allow /{dev,run}/shm/sem.snap.@{SNAP_NAME}.*. This is
sufficient to make use of sem_open() possible.

The python code is, as you've indicated, is choosing to use "/mp%ld-%lu" instead
of '"/snap.%s.%ld-%lu" % os.getenv("SNAP_NAME")'. However, reading the
shm_open() implementation in glibc you gave, if O_CREAT or O_EXCL are specified
then a temporary file is created that doesn't conform to the name, but if the
file exists you can use it.

I confirmed this works fine under confinement (return code checking omitted for
clarity):

   char *name = "/dev/shm/sem.snap.foo.bar";
   open(name, O_CREAT | O_EXCL | O_RDRW, S_IRUSR | S_IWUSR);
   sem_open("snap.foo.bar", 0);

As such, sem_open() can work under confinement, but the application needs to be
written to work within it.

Sergio put together snapcraft-preload:
https://github.com/sergiusens/snapcraft-preload

It doesn't seem to have sem_open() support yet, but it certainly could.

-- 
Jamie Strandboge | http://www.canonical.com



signature.asc
Description: This is a digitally signed message part
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Semaphores and access to /dev/shm

[Alberto Mardegan]

Hi all!
  I'm working on a snap of a python2 utility which is using the Pool
class from the multiprocessing module. But this gets blocked by apparmor:

Log: apparmor="DENIED" operation="mknod"
profile="snap.bundler-mardy.bundler-py" name="/dev/shm/8sszOM" pid=17782
comm="python2" requested_mask="c" denied_mask="c" fsuid=1000 ouid=1000
File: /dev/shm/8sszOM (write)
Suggestion:
* adjust program to create files and directories in
/dev/shm/snap.$SNAP_NAME.*


Unfortunately, the suggestion is not really helpful, because the
filename is not decided by the client code. But even if somehow we fixed
the python implementation to generate a proper name, it looks like
sem_open() is behaving in a very peculiar way: please have a look at
this strace log, obtained on an *unconfined* process:

=
statfs("/dev/shm/", {...}) = 0
futex(0x7f1b658f9310, FUTEX_WAKE_PRIVATE, 2147483647) = 0
lstat("/dev/shm/ApjbNj", 0x7ffe9cefff20) = -1 ENOENT
open("/dev/shm/ApjbNj", O_RDWR|O_CREAT|O_EXCL, 0600) = 6
write(6,
"\1\0\0\0\0\0\0\0\200\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0",
32) = 32
mmap(NULL, 32, PROT_READ|PROT_WRITE, MAP_SHARED, 6, 0) = 0x7f1b65a5d000
link("/dev/shm/ApjbNj", "/dev/shm/sem.mp18207-15353487325820441356") = 0
fstat(6, {st_mode=S_IFREG|0600, st_size=32, ...}) = 0
unlink("/dev/shm/ApjbNj")   = 0
close(6)= 0
=

That is, it looks like sem_open() is first creating a temporary file,
and then linking it to a file with the proper name (the python code is
using "/mp%ld-%lu" as semaphore filename). This also seems confirmed by
a quick look at glibc's source code:

http://sourceware.org/git/?p=glibc.git;a=blob;f=nptl/sem_open.c;h=a80e5b8e9b15090c2ecacb1c1e587c501cf20ffb;hb=HEAD#l277

So, it looks like sem_open() can't possibly work under confinement, or
am I missing something here?

Ciao,
  Alberto

-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Spread Tests with proxy (mostly go get)

[Max Brustkern]

I was able to get most of the tests working by configuring the classic
environment to use the proxy. I think long-term the correct solution is
still system-wide proxy support on ubuntu core, and there's already a bug
open for that, so I'll keep working with the current methods and propose
changes for the tests if those are reasonable to make without affecting
other functionality. Since the VMs are all in the lab, getting full network
connections for them would be difficult to get approved by IS, and I think
having most of the testing working behind the proxy is a pretty good state
for now.

On Tue, Feb 7, 2017 at 1:55 PM, Gustavo Niemeyer <
gustavo.nieme...@canonical.com> wrote:

> Hi Max,
>
> The problem isn't spread itself, as it won't try to communicate out of the
> host by itself. The problem is that snapd's test suite expects to be able
> to talk to the network.
>
> Someone would have to go through and fix all such cases to go through the
> proxy, which is perhaps more troubling than connecting the VM itself into
> the network?
>
> On Mon, Jan 23, 2017 at 8:01 PM, Max Brustkern <
> max.brustk...@canonical.com> wrote:
>
>> I'm trying to run spread tests on an ubuntu core VM in a lab that needs
>> to use a proxy for web access. The mirrors are redirected, so the package
>> installations work as expected, but I run into problems with go get:
>>
>> ++ classic 'GOPATH=/home/gopath go get ../../home/gopath/src/github.c
>> om/snapcore/snapd/tests/lib/snapbuild'
>> Cannot determine calling user, logging into classic as root
>> mount: devpts is already mounted or /dev/pts busy
>>devpts is already mounted on /dev/pts
>> package gopkg.in/yaml.v2: unrecognized import path "gopkg.in/yaml.v2"
>> (https fetch: Get https://gopkg.in/yaml.v2?go-get=1: dial tcp
>> 45.33.69.124:443: i/o timeout)
>> package gopkg.in/check.v1: unrecognized import path "gopkg.in/check.v1"
>> (https fetch: Get https://gopkg.in/check.v1?go-get=1: dial tcp
>> 45.33.69.124:443: i/o timeout)
>> ++ sysctl -w net.ipv6.conf.all.disable_ipv6=0
>> net.ipv6.conf.all.disable_ipv6 = 0
>> -
>> 2017/01/23 16:46:54 Restoring project on external:ubuntu-core-16-64...
>> 2017/01/23 16:46:55 Successful tasks: 0
>> 2017/01/23 16:46:55 Aborted tasks: 107
>> 2017/01/23 16:46:55 Failed project prepare: 1
>> - external:ubuntu-core-16-64:project
>> 2017/01/23 16:46:55 Keeping external:ubuntu-core-16-64 at 127.0.0.1:54323
>> error: unsuccessful run
>>
>> I'm using the following spread commands to run on the local VM:
>> export SPREAD_EXTERNAL_ADDRESS=127.0.0.1:$PORT
>> ./tests/lib/external/prepare-ssh.sh 127.0.0.1 $PORT $USER
>> spread -v -reuse external:ubuntu-core-16-64 | tee $WORKSPACE/spread-output
>>
>> How should I configure spread to make go aware of the proxy?
>>
>> Thanks,
>> Max
>>
>> --
>> Snapcraft mailing list
>> Snapcraft@lists.snapcraft.io
>> Modify settings or unsubscribe at: https://lists.ubuntu.com/mailm
>> an/listinfo/snapcraft
>>
>>
>
>
> --
> gustavo @ http://niemeyer.net
>
> --
> Snapcraft mailing list
> Snapcraft@lists.snapcraft.io
> Modify settings or unsubscribe at: https://lists.ubuntu.com/
> mailman/listinfo/snapcraft
>
>
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: connecting a non-auto interface, automatically

[Claudio André]

2017-02-08 14:37 GMT-02:00 Olivier Tilloy :

> On Tue, Feb 7, 2017 at 3:43 PM, Simon Fels 
> wrote:
> Where can this be requested?
>
>
+1.

Sorry, this is a hijack.

I would like to see an interfaces revamp/discussion. E. g.:
- my snap is useless without process-control, but works without home [1].
The previous is mandatory, the later is optional [2].
- why not document if an non-auto interface is mandatory? And, as Olivier
said, a mechanism to say: a required interface isn't connected.

I am, as an user, interested in using **some** snaps as 1st class software:
a 'turbo' text editor, a better archiver, GIMP, ...
- No alien "home", no need to copy files around to open them.

Claudio

[1] it is ok if the user wants to copy files from/to $SNAP_DIRs.
[2] In fact, auto-connecting home might be a bad idea.

PS:
- extending this, what about a filesystem interface:
  - a text editor snap (or an archiver) can run confined without problems.
But, the user might want to open /etc/fstab or a file in a removable media.

Sorry if this is offensive, I REALLY apologize. Recently in planet GNOME we
was able to read about flatpak "FileChooser portal". To me, it seems to be
the needed solution.
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: license.txt and snap/ directory

[Joseph Rushton Wakeling]

On 08/02/17 17:52, Gustavo Niemeyer wrote:

The discussion above felt like painting an incorrect picture of what we're
aiming at. We *definitely* want to track license information inside the snap
format in a proper location. We want to support both basic cases such as just
listing a well known name, custom licenses, and all the way up to requiring an
explicit agreement with the provided text.

We're not there yet, but this is in our short to medium term roadmap for sure.


Sounds good!  Thanks for the clarification :-)


--
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: ubuntu-app-platform updated to Qt 5.6.2

[Florian Boucault]

Indeed, sorry about that. The latest version with no Qt bundled is released
now.

Florian

Le mer. 8 févr. 2017 à 14:20, Timo Jyrinki  a
écrit :

> 2017-02-07 17:00 GMT+02:00 Florian Boucault <
> florian.bouca...@canonical.com>:
> > I thought I fixed the terminal last week. At least the terminal
> available on
> > the edge channel now is working for me. Does it work for you?
> > I made sure that the stage-packages only contain packages that are not in
> > ubuntu-app-platform and also used  build-attributes:
> [no-system-libraries]
>
> It does not work if I upgrade to the edge version of
> ubuntu-app-platform (and uninstall and reinstall ubuntu-terminal-app).
>
> So yes you fixed it, and I tested the fix but the fixed version needs
> to be uploaded to the store by someone with rights. Maybe Bill?
>
> The current 33 version in the store still has the bundled Qt libraries
> - see $ ls /snap/ubuntu-terminal-app/33/usr/lib/x86_64-linux-gnu/
>
> -Timo
>
> --
> Snapcraft mailing list
> Snapcraft@lists.snapcraft.io
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/snapcraft
>
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

chroot into a snap

[Roberto Mier Escandón ]

Hey engineers,

I need some ideas to solve this: I'm trying to snap collaboraoffice
online but that's not being easy at all. FYI: this is a kind of Google
Drive stuff so that when you request in your browser certain document,
it is rendered and can be edit by many at the same time, etc..

Though I've been able to build from sources a snap package, that is only
working in classic confinement but not in devmode or strict.

The reason is because the way it works:
- There is a server listening for documents requests
- for every new document requested an instance of a document manager is
started in a chrooted environment
- If requested n documents there will be n different chroot jails based
in same certain template
- document manager has certain linux capabilities to create the needed
roots (cap_fowner,cap_mknod,cap_sys_chroot...)
- the way of packaging the snap, currently, is by setting those caps and
call mksquashfs skipping -no-attrs option set by default by snapcraft

I thought about a solution of having server in a snap and document
manager in another, but still there would be needed calling chroot for
every new document... ideas?

BR.

-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: [Dragonboard410c] Ubuntu OS Build Issues, and Support

[Oliver Grawert]

hi,
Am Mittwoch, den 08.02.2017, 15:40 +0100 schrieb Paolo Pisati:
> On Wed, Feb 08, 2017 at 01:07:34PM +0100, Oliver Grawert wrote:
> > 
> > 
> > yes, i belive the snapcraft team together with the kernel team are
> > working on a fix for this [1], the snapcraft kernel plugin seems to
> > put
> > the modules and firmware in a /lib subdir in the snap package which
> > is
> > wrong [2] and will not make them end up in the final place on the
> > filesystem.
> I hit [1] too when rebuilding an image for the dragonboard410c
> yesterday, and i
> wrote a snapcraft patch that creates symlinks from /lib/modules to
> /modules and
> from /lib/firmware to /firmware but it wasn't enough, because during
> the staging
> phase, snapcraft complains that:
> 
> ...
> IsADirectoryError: [Errno 21] Is a directory:
> '/home/flag/canonical/snapcraft/demos/96boards-
> kernel/snap/stage/modules'
> 
> And that is problably because symlinks are not maintained from build
> to stage
> (and afterward).

the work is going on here:

https://github.com/snapcore/snapcraft/pull/1115

ciao
oli

signature.asc
Description: This is a digitally signed message part
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: [Dragonboard410c] Ubuntu OS Build Issues, and Support

[Paolo Pisati]

On Wed, Feb 08, 2017 at 01:07:34PM +0100, Oliver Grawert wrote:
> 
> yes, i belive the snapcraft team together with the kernel team are
> working on a fix for this [1], the snapcraft kernel plugin seems to put
> the modules and firmware in a /lib subdir in the snap package which is
> wrong [2] and will not make them end up in the final place on the
> filesystem.

I hit [1] too when rebuilding an image for the dragonboard410c yesterday, and i
wrote a snapcraft patch that creates symlinks from /lib/modules to /modules and
from /lib/firmware to /firmware but it wasn't enough, because during the staging
phase, snapcraft complains that:

...
IsADirectoryError: [Errno 21] Is a directory:
'/home/flag/canonical/snapcraft/demos/96boards-kernel/snap/stage/modules'

And that is problably because symlinks are not maintained from build to stage
(and afterward).

Here is the python call trace and full log:
http://pastebin.ubuntu.com/23954641/

1: https://bugs.launchpad.net/snapcraft/+bug/1658177
-- 
bye,
p.

-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Anyone seen this? Snap fails to mount as /run fills up

[Martin Winter]

So I’ve noticed something unusual on my CI system (which 
installs/uninstalls debian packages and snap packages

all the time as part of testing):

I couldn’t install snap’s anymore - (only had the ubuntu-core loaded 
at this time)


dut:~# snap install --force-dangerous 
./frr_2.1-dev-20170207.191620-git.03bf19b_amd64.snap

error: cannot perform the following tasks:
- Mount snap "frr" (unset) ([start snap-frr-x1.mount] failed with exit 
status 1: Warning: snap-frr-x1.mount changed on disk. Run 'systemctl 
daemon-reload' to reload units.
A dependency job for snap-frr-x1.mount failed. See 'journalctl -xe' for 
details.)

root@ci-comp19-dut:~#

and looking at “journalctl -xe”

-- The start-up result is done.
Feb 07 06:26:18 ci-comp19-dut systemd-logind[1561]: New session 3160 of 
user root.

-- Subject: A new session 3160 has been created for user root
-- Defined-By: systemd
-- Support: http://lists.freedesktop.org/mailman/listinfo/systemd-devel
-- Documentation: 
http://www.freedesktop.org/wiki/Software/systemd/multiseat

--
-- A new session with the ID 3160 has been created for the user root.
--
-- The leading process of the session is 17387.
Feb 07 06:26:18 ci-comp19-dut systemd-logind[1561]: Failed to save user 
data /run/systemd/users/0: No space l
Feb 07 06:26:18 ci-comp19-dut systemd-udevd[17397]: failed to create db 
file '/run/udev/data/+cgroup:task_str
Feb 07 06:26:18 ci-comp19-dut systemd-udevd[17396]: failed to create db 
file '/run/udev/data/+cgroup:proc_ino
Feb 07 06:26:18 ci-comp19-dut systemd-udevd[17401]: failed to create db 
file '/run/udev/data/+cgroup:sighand_
Feb 07 06:26:18 ci-comp19-dut systemd-udevd[17402]: failed to create db 
file '/run/udev/data/+cgroup:signal_c
Feb 07 06:26:18 ci-comp19-dut systemd-udevd[17403]: failed to create db 
file '/run/udev/data/+cgroup:mm_struc
Feb 07 06:26:18 ci-comp19-dut systemd-udevd[17404]: failed to create db 
file '/run/udev/data/+cgroup:anon_vma
Feb 07 06:26:18 ci-comp19-dut systemd-udevd[17395]: failed to create db 
file '/run/udev/data/+cgroup:dentry(4
Feb 07 06:26:18 ci-comp19-dut systemd-udevd[17399]: failed to create db 
file '/run/udev/data/+cgroup:anon_vma
Feb 07 06:26:18 ci-comp19-dut systemd-udevd[17394]: failed to create db 
file '/run/udev/data/+cgroup:cred_jar
Feb 07 06:26:18 ci-comp19-dut systemd-udevd[17400]: failed to create db 
file '/run/udev/data/+cgroup:files_ca
Feb 07 06:26:18 ci-comp19-dut systemd-udevd[17397]: failed to create db 
file '/run/udev/data/+cgroup:pid(4365
Feb 07 06:26:18 ci-comp19-dut systemd-udevd[17403]: failed to create db 
file '/run/udev/data/+cgroup:kmalloc-


—> /run filesystem full!

dut:~# df
Filesystem 1K-blocksUsed Available Use% Mounted on
udev 1003440   0   1003440   0% /dev
tmpfs 204812  204812 0 100% /run
/dev/vda16060608 3362132   2367572  59% /
tmpfs1024048   0   1024048   0% /dev/shm
tmpfs   5120   0  5120   0% /run/lock
tmpfs1024048   0   1024048   0% /sys/fs/cgroup
/dev/loop0 78080   78080 0 100% /snap/ubuntu-core/1411
/dev/loop1 76800   76800 0 100% /snap/ubuntu-core/423
tmpfs 204812   0204812   0% /run/user/0


These are my versions:
dut:~# snap --version
snap2.21
snapd   2.21
series  16
ubuntu  16.04

Anyone seen this before? This is a basic Ubuntu 16.04 (server) install

After a reboot I don’t seem to have more space, so not sure if I 
should reconfig something to add more space to

/run or if this is some bug.

Thoughts?

- Martin Winter

--
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: snapd available in Trusty Tahr

[Andrew Mason]

Awesome, i am going to give this a try!

On 8 February 2017 8:01:30 am ACDT, Manik Taneja  wrote:
>On Tue, Feb 7, 2017 at 12:36 PM, Mark Shuttleworth 
>wrote:
>
>> On 07/02/17 20:17, Thomas Voß wrote:
>> > https://bugs.launchpad.net/ubuntu/+source/xorg-server-
>> lts-xenial/+bug/1655724
>> > was released to the updates pocket today.
>>
>> Congrats! Quick feedback from folks with Trusty (14.04 LTS) systems,
>> cloud or desktop, would be welcome. Pick a favorite snap and take it
>for
>> a spin.
>>
>The experience is very clean now. I just tried on AWS and have
>RocketChat
>up and
>running-
>
>[image: Inline image 1]
>Kudos to everyone involved in delivering this!
>
>Cheers,
>Manik

-- 
Sent from my mobile device.-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: ubuntu-app-platform updated to Qt 5.6.2

[Timo Jyrinki]

2017-02-07 17:00 GMT+02:00 Florian Boucault :
> I thought I fixed the terminal last week. At least the terminal available on
> the edge channel now is working for me. Does it work for you?
> I made sure that the stage-packages only contain packages that are not in
> ubuntu-app-platform and also used  build-attributes: [no-system-libraries]

It does not work if I upgrade to the edge version of
ubuntu-app-platform (and uninstall and reinstall ubuntu-terminal-app).

So yes you fixed it, and I tested the fix but the fixed version needs
to be uploaded to the store by someone with rights. Maybe Bill?

The current 33 version in the store still has the bundled Qt libraries
- see $ ls /snap/ubuntu-terminal-app/33/usr/lib/x86_64-linux-gnu/

-Timo

-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft

Re: Is there any way to list all of the configure options for a snap application?

[Oliver Grawert]

hi,
Am Mittwoch, den 08.02.2017, 15:00 +0800 schrieb XiaoGuo Liu:
> Yeah, I think this is much needed. For example, I really want to know
> what are the configuration options for the core snap. One use case
> could be that I want to stop the autopilot upgrade feature..
> 
https://docs.ubuntu.com/core/en/reference/core-configuration

there isnt much fully done yet, the the core snap in the edge channel
has additionally:

snap set core service.rsyslog.disable=true/false
snap set core service.systemd-timesyncd.disable=true/false

in the works are:

options to set timeserver and remote syslog server, support for
sysctl.d, forced module loading, module options and management of some
power features of logind (configurable power button behaviour)

the auto-upgrade feature is currently being completely re-worked to be
handled in snapd itself, until this is fully done we wont have a config
option for it.

all config options will be listed on the above page before they hit the
stable channel.

ciao
oli

signature.asc
Description: This is a digitally signed message part
-- 
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at: 
https://lists.ubuntu.com/mailman/listinfo/snapcraft