I expect the store sent an X-Oops-Id header with that; maybe snapcraft
should print it in these cases, to help with debugging?
On 6 April 2017 at 12:26, José Pekkarinen wrote:
> Hi list,
>
> I was trying to upload a clang snap to the ubuntu store today. To my
> surprise there seem
On 31 March 2017 at 21:52, Neal Gompa wrote:
> we
> definitely don't want to use less than SHA256 for snaps.
note snaps use sha3-384 currently; the above discussion is, as I
understand it, about snapcraft checking upstream checksums at build
time.
--
Snapcraft mailing list
Snapcraft@lists.snapc
On 28 March 2017 at 10:35, Simon Stürz wrote:
>
> I'm currently building an armhf system using live-build and running
> snapd on it. I wanted to pre-install snaps during the image build
> process and run into several problems.
> Using qemu-arm-static in the chroot I get following error:
the go de
Hi Sunny,
I don't understand what's going on with your system:
* snapd is running out of memory. snapd should be using about 20MB of
resident memory. How much was it trying to use when it ran out? How
much is available? What does dmesg say about this crash?
* snapd on a core system that doesn't li
I've filed https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1672819
and https://github.com/golang/go/issues/19546
(the latter more of an FYI than a bug)
On 14 March 2017 at 10:56, John Lenton wrote:
> As a followup, I added a mutex around pthread_create, and around the
> exec s
a look at this.
On 13 March 2017 at 23:33, Michael Hudson-Doyle
wrote:
> On 14 March 2017 at 12:21, John Lenton wrote:
>
>> On 13 March 2017 at 21:05, Michael Hudson-Doyle
>> wrote:
>> > If I add a
>> > time.Sleep(1*time.Millisecond) to a_go.go before th
On 13 March 2017 at 21:05, Michael Hudson-Doyle
wrote:
> If I add a
> time.Sleep(1*time.Millisecond) to a_go.go before the exec, the setuid bit
> is respected every time.
on my way to bed, I'll give your response a proper read in the
morning, but note that my reproducer causes the issue a lot mor
This one is slightly more interesting.
You need 1.8 (or patched <1.8 as per the previous thread) for this one
to make sense; without it you're just going to get drowned in warning
messages and not see the real issue.
This one is the real issue :-)
In go, when calling syscall.Exec to a setuid roo
Thank you Alfonso for that link (I didn't find that when I looked, so
kudos), and thank you Michael and Zyga for all your work on this!
On 12 March 2017 at 08:38, Michael Hudson-Doyle
wrote:
> PS: I guess I should back port that Go fix to all supported Go releases?
that would be very nice. Does
Hello!
We're seeing a weird issue with either go, pthreads, or the kernel. If
you're knowledgeable about one or more of those things, could you take
a look? Thank you.
The issue manifests as nasty warnings from the "snap run" command,
which is also the first step into a snapped app or service. It
note that in that log, snapd isn't running because
snapd[2217]: fatal error: runtime: out of memory
On 22 February 2017 at 07:52, Sunny Bhayani
wrote:
> Hi Ogra,
>
> Appreciate for your help.
>
>> hi,
>> Am Freitag, den 17.02.2017, 10:06 + schrieb Sunny Bhayani:
>> >
>> >
>> > You are correc
On 24 February 2017 at 13:08, Martin Winter
wrote:
> So not sure what’s going on.
Neither are we! But we've spotted some of these on errors.ubuntu.com.
Can you get get on IRC (#snappy on freenode)? We'd love to get our
hands on systems with this happening a we haven't been able to
reproduce it!
On 20 January 2017 at 18:24, Luke Williams wrote:
> Any ideas on this error?
what is your kernel snap called, and what is your /proc/cmdline?
--
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/snapcraft
09:30, Boris Rybalkin wrote:
> John,
>
> I am new to go language (coming from Java world) I want to debug with
> breakpoints from IDE (and I was able aftet adding socket creation code).
>
> Maybe I should run it with systemd and then attach to it from IDE?
>
> On 5 Dec 201
On 5 December 2016 at 08:58, Boris Rybalkin wrote:
>
> Is it possible to run snapd for debugging without systemd socket activation?
depends on what you mean. At the end of HACKING.md in the root of the
project there are instructions for how to run snapd by hand, using
systemd-activate:
https://g
On 14 October 2016 at 13:07, Sergio Schvezov
wrote:
> I hope you meant snapd/ubuntu-image here :-)
d'oh, yes.
--
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/snapcraft
On 14 October 2016 at 01:32, Luke Williams wrote:
> I’m getting http 500 errors when I try anything other than the stable
> channel….
those 500s come from the CDN; can you retry? (snapcraft should retry
500s on download; we'll get to that at some point...)
--
Snapcraft mailing list
Snapcraft@li
On 11 October 2016 at 15:23, Chris wrote:
> Not sure what I should be do now.
snap install snapweb?
--
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe at:
https://lists.ubuntu.com/mailman/listinfo/snapcraft
Eloy, Spencer, Otfried,
The xdg-open we ship in /usr/local in the snap-core snap failing like
that is a bug; it seems we weren't covering this use case in our
tests.
jdstrand has now addressed this, and although with his fix right now
you'll need to ask for the unity7 interface it is expected to
On 7 September 2016 at 17:32, Matthew Williams
wrote:
> one concrete example is shelling out to /usr/bin/sensible-browser.
note that sensible-browser will probably only work on debian and
derivatives. The better cross-distro way would be to call xdg-open,
and we already have that in place AFAIK.
On 18 August 2016 at 12:37, Jenny Murphy wrote:
> Is it possible that the ubuntu login on a Snappy Ubuntu Core platform can
> expire.
no (well, yes, but it's something you'd have to do yourself using the
usual pam tools, not something snappy would do for you).
What images are you using?
--
Sn
On 17 August 2016 at 03:24, Robert Ancell wrote:
> I've been trying to access snapd events using the REST API [1] and I'm not
> able to get it working.
I'm afraid the events work has fallen by the wayside. It was not
completed afaik, and obviously has no (or not enough) tests otherwise
this woul
On 5 August 2016 at 11:25, Dan Watkins wrote:
>
> The snapped program calls /usr/bin/awk at runtime, so I'd presumably
> need mawk to be installed in the host at runtime as well?
core has mawk, but not gawk. snaps run with the host's
/etc/alternatives but core's /usr.
--
Snapcraft mailing list
On 5 August 2016 at 10:20, Dan Watkins wrote:
> Something I'm snapping tries to run `awk`, which isn't included in the
> ubuntu-core snap
awk *is* in the ubuntu-core snap. What's happening is bug #1580018:
you've used update-alternatives on the host to switch to an awk that
is different to the on
On 29 July 2016 at 11:45, Dietmar Winkler wrote:
> ln: failed to create symbolic link
> '/home/dietmarw/snap/ipe/x22/.themes/themes': Read-only file system
that seems strange. What is read-only in that path?
--
Snapcraft mailing list
Snapcraft@lists.snapcraft.io
Modify settings or unsubscribe a
25 matches
Mail list logo
