[01:51] <mup> PR snapd#3061 opened: Renamed thumbnailer interface to thumbnailer-service interface <Created by michihenning> <https://github.com/snapcore/snapd/pull/3061>
[02:23] <mwhudson> hm
[02:27] <mwhudson> hello
[02:27] <mwhudson> so on debian, if you install snapd then install (say) hello, the install of the core snap fails
[02:28] <mwhudson> (hangs at "run configure hook")
[02:34] <mwhudson> the configure hook has a defunct snapctl subprocess
[02:39] <mwhudson> running snap install core by itself works
[02:39] <mwhudson> ah well off to lp for this i think
[02:55] <mup> Bug #1674193 opened: core snap's configuration hangs on debian <Snappy:New> <https://launchpad.net/bugs/1674193>
[09:14] <zyga> o/
[12:13] <mup> PR snapd#3046 closed: many: merge release/2.23 into master <Created by zyga> <Closed by zyga> <https://github.com/snapcore/snapd/pull/3046>
[12:14] <mup> PR snapd#3062 opened: many: merge release/2.23 branch back to master <Created by zyga> <https://github.com/snapcore/snapd/pull/3062>
[12:30] <mup> PR snapd#3063 opened: tests: re-enable tests for /dev/pts on core <Created by zyga> <https://github.com/snapcore/snapd/pull/3063>
[12:32] <lool> jdstrand: hey!
[12:33] <lool> jdstrand: one partner snap was using sysctl -w net.ipv4.ip_forward=1
[12:34] <lool> jdstrand: oh actually sorry, I read wrong
[12:34] <lool> jdstrand: I was about to ask that sysctl be allowed to run
[12:34] <lool> but I see that's correctly already part of network-control
[12:38] <lool> jdstrand: (I thought writes to proc/sys were allowed but not running sysctl, but it is allowed - sorry for the bother)
[12:38] <lool> it's just that the snap was lacking network-control
[12:40] <lool> actually this might miss rw on forwarding
[13:22] <jdstrand> lool: use firewall-control for ip_forward. I agree this should also be in network-control and have added a todo for that
[13:22] <lool> jdstrand: I think it's actually in network-control
[13:22] <jdstrand> it isn't (I just checked)
[13:23] <lool> @{PROC}/sys/net/ipv{4,6}/** rw,
[13:23] <nothal> lool: No such command!
[13:23] <jdstrand> oh, yes, ok, good
[13:23] <jdstrand> I only grepped for ip_forward
[13:23]  * jdstrand removes todo
[13:24] <ogra_> jdstrand, do you remember if apparmor had issues with all overlay filesystem variants, or was that overlayfs specific
[13:24] <jdstrand> JamieBennett: hey, fyi, I drove the store reviews down such that the only things that are left are classic confinement snaps from non-Canonical employees
[13:24] <ogra_> (i remember that was discussed at some sprint)
[13:24] <lool> I had initially thought sysctl was missing because the ordering of the files wasn't the same (sysctl mentioned just before proc entries in https://github.com/snapcore/snapd/blob/master/interfaces/builtin/firewall_control.go but in separate listing in https://github.com/snapcore/snapd/blob/master/interfaces/builtin/network_control.go)
[13:25] <jdstrand> ogra_: it's mostly overlay and overlayfs. iirc, aufs is mediatable to a large extent (but our policy isn't written for it). I'm going to defer to tyhicks and jjohansen on the details
[13:29] <JamieBennett> jdstrand: OK, let me take a look, thanks
[13:30] <renat> Hi guys!
[13:31] <renat> I have two pull requests https://github.com/snapcore/snapd/pull/3045 and https://github.com/snapcore/snapd/pull/3051
[13:31] <mup> PR snapd#3045: interfaces: add random interface <Created by femdom> <https://github.com/snapcore/snapd/pull/3045>
[13:31] <mup> PR snapd#3051: interfaces: add consoles interface <Created by femdom> <https://github.com/snapcore/snapd/pull/3051>
[13:31] <renat> Unit tests pass for them, but other tests fail=(
[13:31] <renat> Could you, please, take a look?
[13:45] <ogra_> niemeyer, see above ... seems aufs could be made working for your ideas
[13:45] <niemeyer> ogra_: Problem is it's not in mainline, which means cross-distro headaches
[13:46] <ogra_> yeah, indeed
[13:46] <ogra_> same for ubuntu-core kernels etc ...
[13:55] <renat> niemeyer, hi=)
[13:57] <niemeyer> renat: Heya
[14:04] <renat> niemeyer, could you please look at my pull requests related to consoles an random interface. Test failed because of the timeout
[14:06] <ogra_> renat, uhm ... tty0 isnt always the system console ... you should better read it from /proc/cmdline
[14:06] <ogra_> (in fact tty0 is very rarely the system console on actual ubuntu-core images)
[14:11] <niemeyer> renat: Will do!  We've been rotating over the open PRs two or three times a week
[14:12] <renat> niemetyer, thanks!
[14:12] <renat> niemeyer, sorry
[14:12] <niemeyer> renat: np, pinging is fine as well
[14:13] <renat> ogra_, we need an interface to access that file)
[14:13] <ogra_> renat, even if it isnt your console device at all ?
[14:14] <ogra_> renat, i'd keep /dev/console and dynamically allow whatever is defined in console= from 7proc/cmdline
[14:14] <ogra_> */proc
[14:18] <tyhicks> ogra_: re overlay variants> I think aufs has an issue similar to ecryptfs (they're both stacked filesystems) where the policy has to grant permissions to two different filesystem paths
[14:19] <tyhicks> ogra_: that's something that can be worked around in policy
[14:21] <renat> ogra_ thanks. I need to read more about it)
[14:35] <mup> PR snapd#3056 closed: overlord: when shutting down assume errors might be due to cancellation so retry <Created by pedronis> <Merged by pedronis> <https://github.com/snapcore/snapd/pull/3056>
[14:39] <mup> PR snapd#3062 closed: many: merge release/2.23 branch back to master <Created by zyga> <Merged by niemeyer> <https://github.com/snapcore/snapd/pull/3062>
[15:08] <mup> PR snapd#3057 closed: systemd: mount the squashfs with nodev <Created by mvo5> <Merged by niemeyer> <https://github.com/snapcore/snapd/pull/3057>
[15:59] <kyrofa> mcphail, you asked me about the nextcloud snap notifying you. I'm not sure when you pinged me, but I was out last week
[16:00] <kyrofa> mcphail, from talking with oparoz, it sounds like there's an app I might be able to tie into for notifications (we have a bug for it), but I haven't had a chance to look into it yet
[16:10] <elopio> ogra_: ping, are you around? Could you please review https://github.com/snapcore/snapcraft/pull/1198/files ?
[16:10] <mup> PR snapcraft#1198: tests: add manual tests for the kernel snaps <Created by elopio> <https://github.com/snapcore/snapcraft/pull/1198>
[16:10] <ogra_> elopio, i looked yesterday already buit there wasnt much there ... checking againg
[16:10] <ogra_> -g
[16:12] <ogra_> elopio, i think sergiusens' comment still applies, i'm not sure where they maintain the Makefile tree nowadays, most likely not under lp:pc-kernel-snap anymore ... bjf would knwo
[16:13] <elopio> ogra_: I thought you maintained the make. This makes a lot of sense, because it's not booting :)
[16:13] <elopio> bjf: ping, where do you have the snapcraft.yaml for the pc kernel?
[16:13] <ogra_> elopio, i used to and then handed over to the kernel team ... since it is their realm after all
[16:14] <ogra_> elopio, the instructions look fine to me
[16:15] <ogra_> elopio, you dont need the --image-size 3G, that way you also test the auto-resize on first boot alongside ;)
[16:15] <ogra_> -image-size 3G is really only needed for kvm
[16:15] <elopio> I'll remove it. Thanks.
[16:16] <bjf> elopio, https://launchpad.net/~ubuntu-kernel/ubuntu/+source/linux-snap/+git/xenial
[16:18] <ogra_> oh, interesting, so master only has the makefile and the snapcraft.yaml's are in branches ... such a setup had never struck me
[16:18]  * ogra_ now knows why he handed it over ;)
[16:23] <elopio> bjf: thank you! If you have some minutes, it would be nice to also get a review from you: https://github.com/snapcore/snapcraft/pull/1198
[16:23] <mup> PR snapcraft#1198: tests: add manual tests for the kernel snaps <Created by elopio> <https://github.com/snapcore/snapcraft/pull/1198>
[16:24] <ogra_> i wonder if you cant actually force-sideload a kernel on an existing image to test ...
[16:25] <ogra_> (surely breaks the auth stuff in the end but probably a lot less work for a one-shot test to see if it still boots)
[16:28] <elopio> ogra_: this is not a lot of work, as we do it only if we change the kernel plugin, a couple of time before the release.
[16:30] <ogra_> elopio, hmm, so you test the kernel plugin by building a kernel that doesnt use the kernel plugin ?
[16:32] <elopio> ogra_: the 96boards example uses the kernel plugin. That's the test we wanted.
[16:33] <ogra_> elopio, right, then you dont want bjf's branch
[16:33] <elopio> I added pc only for completeness. I'm not yet sure what we win by running it, as we almost never change the make plugin these days, so I'm not yet sure when we should run it.
[16:33] <ogra_> since that uses binaries from the archive
[16:33] <ogra_> like all our offical kernel snaps do
[16:34] <ogra_> (to get the signing key for potential secure boot solutions)
[16:34] <elopio> yup. Ideally as we discussed some days ago, the signing could be done with scriptlets and we could use the kernel plugin for all our plugins.
[16:35] <elopio> but that's not something we are in a hurry to do, I think.
[16:35] <ogra_> elopio, i think ppisati has trees for all kernels that can use the kernel plugin directly
[16:35] <ogra_> the signing cant be done with scriplets ... because you dont have the secret key
[16:35] <elopio> ogra_: I'm trying to add those to our nightlies. https://github.com/elopio/snapcraft-de-noche/pull/21/files
[16:35] <mup> PR elopio/snapcraft-de-noche#21: Add the kernels <Created by elopio> <https://github.com/elopio/snapcraft-de-noche/pull/21>
[16:36] <elopio> with some errors there still to investigate.
[16:36] <ogra_> afaik the secret part of the archive key is spread across multiple people and split ... and parts of that live in a safe somewhere
[16:36] <ogra_> so signing something with it manually will be quite a challenge
[16:37] <ogra_> elopio, yeah, that one looks more correct for testing the plugin
[16:39] <ogra_> elopio, just ignore the Makefile stuff then and use https://github.com/elopio/snapcraft-de-noche/pull/21/files ... that will definitely test the right thing
[16:39] <mup> PR elopio/snapcraft-de-noche#21: Add the kernels <Created by elopio> <https://github.com/elopio/snapcraft-de-noche/pull/21>
[16:40] <ogra_> testing the Makefile side should simply be done by installing the latest official snap from edge ...
[16:41] <ogra_> (or beta ... or wherever brad lands this by default)
[16:41] <elopio> right, and that shouldn't be part of snapcraft's release process, that sounds good to me.
[16:41] <ogra_> yeah
[16:42] <ogra_> i'm not sure how well or how often the snapcraft.yaml based builds get tested at all though ... i knwo paolo recently tested dragoboard due to a mailing luist discussion ... but since we dont use these kernels by default i wouldnt count on regular testing
[16:43] <ogra_> so your results might vary
[16:43] <ogra_> (i.e. the kernel plugin might DTRT but the resulting kernel might not boot etc)
[17:13] <mcphail> kyrofa: cool! Was wondering if there was something built into snpad which can send notifications on updates? Would be a nice feature to have
[17:13] <kyrofa> mcphail, not that I know of anyway
[17:13] <kyrofa> mcphail, probably a better question for niemeyer
[17:13] <mcphail> kyrofa: ta. I'll maybe file a bug/feature request
[17:41] <pmcgowan> ogra_, its still not working right for me, date reports the correct time and zone, but timedatectl does not
[17:52] <ogra_> ogra@dragonboard:~$ date
[17:52] <ogra_> Sat Feb 18 13:09:41 UTC 2017
[17:52] <ogra_> ogra@dragonboard:~$ sudo timedatectl set-timezone Europe/Berlin
[17:52] <ogra_> ogra@dragonboard:~$ timedatectl
[17:52] <ogra_>       Local time: Sat 2017-02-18 14:10:08 CET
[17:52] <ogra_>   Universal time: Sat 2017-02-18 13:10:08 UTC
[17:52] <ogra_>         RTC time: Fri 1970-01-09 07:49:18
[17:52] <ogra_>        Time zone: Europe/Berlin (CET, +0100)
[17:52] <ogra_>  Network time on: no
[17:52] <ogra_> NTP synchronized: no
[17:52] <ogra_>  RTC in local TZ: no
[17:52] <ogra_> ogra@dragonboard:~$ date
[17:52] <ogra_> Sat Feb 18 14:10:12 CET 2017
[17:52] <ogra_> pmcgowan, works fine here
[17:52] <pmcgowan> ogra_, wait 5 mins
[17:53] <pmcgowan> or watch journalctl for when the daemon runs
[17:53] <pmcgowan> actually 2 mins should do
[17:54] <ogra_> pmcgowan, well, iu see the log warning, but thats just a warning ...
[17:54] <pmcgowan> ogra_, run timedatectl now
[17:54] <pmcgowan> to see whats set
[17:55] <ogra_> oh, you are right
[17:55] <ogra_> funny
[17:55] <pmcgowan> the problem I started with is snapweb calls that over dbus
[17:55] <pmcgowan> well its becuase of the logic I mentioed int he bug
[17:55] <pmcgowan> the daemon resolves the link and gets the wrong file
[17:55] <ogra_> why doers snapweb not use date
[17:55] <pmcgowan> it displays the tz
[17:55] <ogra_> there is no guarasntee we will even keep timedatectl around
[17:56] <ogra_> so does date
[17:56] <pmcgowan> date must get it from somewhere else
[17:56] <pmcgowan> we can change snapweb, now that we understand
[17:56] <ogra_> it just asks libc
[17:57] <ogra_> yeah, we migth decide to drop timedatectl and ship ntp or whatnot ... dont rely on any tools being here
[17:57] <pmcgowan> hmm ok
[17:57] <pmcgowan> let me repurpose the bug
[17:57] <ogra_> shell and libc (and recently a basic python interpreter) is the only stuff we guarantee
[17:57] <ogra_> everything else can always change
[17:58] <pmcgowan> understood
[17:58] <pmcgowan> ogra_, oh we also set time with that api
[17:58] <pmcgowan> will open a new bug
[17:58] <pmcgowan> the old one I guess can be marked fixed
[18:02] <mup> Bug #1650688 changed: timedatectl set-timezone fails on UC16 <Snappy:Fix Released by ogra> <https://launchpad.net/bugs/1650688>
[18:15] <bdmurray> If I have a simple daemon in a snap that sets some files in /proc, how I would unset those on removal?
[18:16] <bdmurray> stop-command doesn't seem right since its not a long running service
[18:24] <sergiusens> coreycb: from what I am seeing, the latest versions of pip and setuptools ignore entry_points in setup.cfg
[18:25] <sergiusens> we use 9 in our plugin, xenial in the distro has 8.1 and zesty has 9
[18:25] <coreycb> sergiusens, that's not very nice of them
[18:25] <sergiusens> coreycb: python distribution is a mess
[18:25] <sergiusens> coreycb: but I already ranted about this
[18:26] <coreycb> sergiusens, is that a bug upstream then with pip or setuptools?
[18:26] <sergiusens> still need to look into it a bit, but I might workaround the problem with a flag you can probably use
[18:26] <sergiusens> coreycb: haven't pin pointed it yet; elopio asked barry for some guidance
[18:26] <coreycb> sergiusens, ok cool
[18:26] <sergiusens> an attribute I mean, to seup the version of pip you need
[18:26] <coreycb> sergiusens, thanks
[18:27] <coreycb> sergiusens, that'd be a nice work around
[18:41] <mup> PR snapd#3064 opened: packaging: rename the file shipping snap-confine AA profile <Created by zyga> <https://github.com/snapcore/snapd/pull/3064>
[18:42] <zyga> jdstrand: hello
[18:42] <zyga> jdstrand: can you please review 3064
[18:42] <zyga> jdstrand: if possible we'd like to use that as the fix for all the issues (including those that block the kernel)
[18:43] <zyga> jdstrand: I just made it, didn't run any tests yet
[18:52] <zyga> jdstrand: thank!
[18:52] <zyga> thanks!
[18:54] <jdstrand> np
[19:02] <zyga> jdstrand: I'm considering _not_ removing the old conffile in this release
[19:02] <zyga> jdstrand: so that we can just relase it with minial risk
[19:02] <zyga> jdstrand: and unblock the kernel and snapd
[19:02] <zyga> jdstrand: and if this works we can remove it in 2.24
[19:03] <zyga> (the stale conffile)
[19:10] <jdstrand> zyga: there isn't really any more risk with removing it, and I'm pretty sure the sru team is going to require it (you don't ship the old one any more after all)
[19:10] <jdstrand> zyga: perhaps discuss it with them before you prepare an upload
[19:10] <zyga> jdstrand: are you sure? I don't have a way to test this (to see if this explodes dpkg)
[19:10] <jdstrand> ?
[19:10] <zyga> yes, that's very smart
[19:14] <zyga> gosh I hate dpkg
[19:15] <zyga> conf-file handling is just so annoying and hard to get right
[19:21] <zyga> jdstrand: is this sufficient?
[19:21] <zyga> http://paste.ubuntu.com/24216924/
[19:25] <Pharaoh_Atem> zyga: :P
[19:25] <zyga> Pharaoh_Atem: hey
[19:25] <Pharaoh_Atem> dpkg is kind of braindead with conffiles :)
[19:26] <Pharaoh_Atem> zyga: you know what I'm going to bug you about :)
[19:26] <zyga> Pharaoh_Atem: yes, I know
[19:26] <zyga> Pharaoh_Atem: I have some good news
[19:26] <zyga> Pharaoh_Atem: looks like I finally managed to reserve some time for !ubuntu work
[19:26] <Pharaoh_Atem> thank god
[19:26] <zyga> Pharaoh_Atem: details when I can release that :)
[19:27] <zyga> Pharaoh_Atem: but not tonight
[19:27] <Pharaoh_Atem> people are getting bitchy at me about it :(
[19:27] <zyga> I really undestand, I'm sorry about it
[19:27] <zyga> Pharaoh_Atem: I really wish we had less fires and less other things
[19:27] <Pharaoh_Atem> just get a fireman :)
[19:28] <zyga> well, don't look, here I come
[19:33] <Pharaoh_Atem> zyga: you can't be the only fireman...?
[19:34] <jdstrand> zyga: I've not done this for a while, but it should be, yes. you can perform an upgrade to 2.23.4 or higher and verify the removal. you should also run lintian on the deb
[19:35] <zyga> jdstrand: sounds like a plan, thank you
[19:35] <zyga> Pharaoh_Atem: the main fireman is on sick leave so I'm taking the honors
[19:35] <Pharaoh_Atem> ah
[19:38]  * davmor2 pictures zyga like this now https://en.wikipedia.org/wiki/Fireman_(steam_engine)#/media/File:Baureihe52Heizer.jpg what do you mean wrong fireman
[19:41] <zyga> davidcalle: wow, that guy is dressed better than me for the 99.9% of my life ;)
[19:41] <zyga> gee
[19:41] <zyga> I should have become a train driver
[19:41] <davmor2> zyga: wrong da<tab> ;)
[19:43] <zyga> ah, always
[19:44] <zyga> is there a way to tell irssi to do longest comon prefix and then stop?
[19:44] <zyga> like in vim
[19:44] <zyga> set wim=longest,list
[19:49] <davmor2> zyga: I think there is a way to set last replied or something like that can't remember how though
[19:49] <zyga> nah, I don't want last replied
[19:49] <zyga> I want consistency among differenet programs :/
[19:50] <davmor2> zyga: no idea then
[19:53] <zyga> jdstrand: I see /etc/apparmor.d/usr.lib.snapd.snap-confine.dpkg-old
[19:53] <zyga> ah but that file is ancient
[19:53] <zyga> ok, all good otherwise
[19:53] <zyga> I'm going to upload to the PPA now
[20:18] <mup> Bug #1674468 opened: More than 36% overhead running tests for dbus interface in snap <Snappy:New> <https://launchpad.net/bugs/1674468>
[20:27] <mwhudson> zyga: hi
[20:27] <mwhudson> zyga: did you see https://bugs.launchpad.net/snappy/+bug/1674193 ?
[20:27] <mup> Bug #1674193: core snap's configuration hangs on debian <Snappy:New> <https://launchpad.net/bugs/1674193>
[20:31] <dpb1_> hi guys -- what am I doing wrong?  http://paste.ubuntu.com/24217290/
[20:32] <kyrofa> dpb1_, what is the output of `snap --version`?
[20:33] <dpb1_> http://paste.ubuntu.com/24217297/
[20:33] <dpb1_> kernel update?
[20:34] <kyrofa> dpb1_, can we also see the output of `snap interfaces`, please?
[20:34] <dpb1_> error: no interfaces found
[20:35] <kyrofa> dpb1_, huh, that doesn't sound good. How about `snap list`?
[20:35] <dpb1_> No snaps are installed yet. Try "snap install hello-world".
[20:36] <dpb1_> I just cleared out all my snaps trying to get the 'ubuntu-core' snap upgraded to 'core'
[20:36] <kyrofa> dpb1_, ah, okay. Does the same thing happen if you just try to `snap install core`?
[20:36] <dpb1_> kyrofa: yes, both with and without sudo
[20:37] <kyrofa> dpb1_, not sure what's happening there. I'll refer you to zyga
[20:37] <dpb1_> kyrofa: I'm running apt-get dist-upgrade now just to remove uncertainty.
[20:37] <dpb1_> will reboot as well
[20:47] <mup> PR snapd#3065 opened: Allow seeding a snap with classic confinement <Created by cyphermox> <https://github.com/snapcore/snapd/pull/3065>
[20:48] <NicolinoCuralli> hi all i exchange some words with @pedronis and @mvo about a future feature for autoconnecting snap plug to core slot from gadget: is there some information more specific about the feature, the roadmap and chances to collaborate?
[20:51] <niemeyer> NicolinoCuralli: We don't have the feature in place yet, but it does make sense for it to exist
[20:51] <niemeyer> NicolinoCuralli: Gut feeling is that this should live in the model assertion, and be restricted to snaps present in the assertion as well
[20:52] <niemeyer> NicolinoCuralli: I need to catch up with pedronis to brainstorm on this, but I can see us extending the snap-declaration logic we have today to consider entries specified in the model
[20:53] <niemeyer> NicolinoCuralli: We have existing language today which is very flexible and defines when exactly to connect certain things automatically
[20:54] <popey> ogra_: gentle reminder that packageproxy still breaks if your pc reboots and leaves a stale lock around :)
[20:55] <NicolinoCuralli> So it is a one-shot enabling mechanism: is it possibile to extend during the lifetime of device this trust for other interface or snaps?
[20:55] <NicolinoCuralli> @niemeyer So it is a one-shot enabling mechanism: is it possibile to extend during the lifetime of device this trust for other interface or snaps?
[20:55] <nothal> NicolinoCuralli: No such command!
[20:56] <niemeyer> NicolinoCuralli: It's not one-shot.. declarations can be updated over time
[20:56] <niemeyer> NicolinoCuralli: Including the model one
[20:57] <niemeyer> NicolinoCuralli: As a first idea, we should probably restrict these declarations to snaps that are shipped with the model itself
[20:57] <niemeyer> NicolinoCuralli: Having them in one of the two ends (either as plug or slot)
[20:58] <niemeyer> We may lift that resitriction, but then we need to think about social consequences more broadly, and it's good to buy time before we take that sort of decision
[21:02] <niemeyer> NicolinoCuralli: e.g. developers would be pretty unhappy to find out that their snaps are broken because of custom declarations on particular devices
[21:03] <niemeyer> I need to step out for a moment.. back soon
[21:11] <zyga> mwhudson: hey
[21:11] <zyga> mwhudson: I saw that
[21:11] <mwhudson> zyga: that's a start :)
[21:11] <mwhudson> zyga: any ideas what's going on, or how to start debugging?
[21:12] <zyga> mwhudson: with so many things not working lately I don't have any ideas
[21:12] <zyga> mwhudson: I heard that mvo reproduced it by just installing anything
[21:12] <NicolinoCuralli> @niemeyer: I understand the danger for other snaps but in a contest where installed snap are from only one developer sounds very useful to have the changes to enabling trust between core and other snap in a more relaxed way
[21:12] <nothal> NicolinoCuralli: No such command!
[21:13] <zyga> mwhudson: I'm too tired with the constant fires to help with this tonight
[21:13] <mwhudson> zyga: eh, that's not very reassuring :/
[21:13] <mwhudson> zyga: fair enough
[21:13] <mwhudson> zyga: mvo reproduced it on debian? or on ubuntu?
[21:13] <NicolinoCuralli> niemeyer : the picture with the autoconnection built by model assertion seems good to me
[21:13] <zyga> mwhudson: on debian
[21:13] <mwhudson> ok
[21:13] <mwhudson> yes, that's my impression too
[21:14] <zyga> mwhudson: looks like snapctl or something like it explodes and doesn't die
[21:14] <zyga> (maybe one thread dies)
[21:14] <mwhudson> zyga: yeah, does it log anywhere?
[21:14] <zyga> never tried it though
[21:14] <zyga> nope, not that I know of
[21:14] <mwhudson> or i can hack it so it does i guess
[21:14] <mwhudson> i found a bug saying "the output of running hooks is not shown anywhere"
[21:14] <zyga> mwhudson: it's tricky as snapd consumes the output
[21:15] <zyga> mwhudson: but I think snapctl just explodes
[21:15] <zyga> no need for the hook logic
[21:15] <zyga> (maybe)
[21:15] <zyga> but also, I should shut this down and go to sleep
[21:15] <mwhudson> zyga: can i fake up the environment the hook runs in somehow?
[21:15] <mwhudson> zyga: tell me on the bug report tomorrow, sleep now :-)
[21:15] <zyga> mwhudson: maybe but I don't know how
[21:15] <zyga> mwhudson: I mean snapd verifies it
[21:16] <zyga> mwhudson: maybe some full system thing can look
[21:16] <zyga> mwhudson: or if you reproduce it just look at what's left of snapctl
[21:16] <zyga> mwhudson: this is especially odd if debian has no confinement
[21:16] <mwhudson> hm i wonder if i had confinement enabled
[21:16] <mwhudson> some of my debian vms do
[21:17] <zyga> check if it happens on vanilla
[21:17] <zyga> actually
[21:17] <zyga> my debian 9 system is ok
[21:17] <zyga> so perhaps confinement
[21:17] <zyga> if confinement we never probably expect that to work
[21:18] <mwhudson> so yeah this vm did have security=apparmor apparmor=1 on kernel command line
[21:18] <mwhudson> booting without that now
[21:18] <zyga> mwhudson: it's not worth debugging that case IMHO, it's not even meant to work, snap-confine doesn't work on debian-9 with apparmor
[21:19] <zyga> mwhudson: and the generated profile probably doesn't work really
[21:19] <zyga> mwhudson: all in all, good luck :)
[21:20] <mwhudson> oh ffs why is the vm fscking
[21:20] <mwhudson> zyga: thanks :)
[21:22] <mwhudson> er i have a godd running and i can't kill it with SIGKILL
[21:22] <mwhudson> maybe i should just give up on computers for today
[21:22] <zyga> haha, nice
[21:22] <kyrofa> mwhudson, haha, I hate days like that
[21:22] <zyga> mwhudson: probably it's apparmor preventing the signal to arrive
[21:22] <zyga> s/probably/maybe/
[21:24] <mwhudson> Mar 21 10:24:21 aeglos kernel: [ 1310.730799] Buffer I/O error on dev sdd, logical block 139859, lost async page write
[21:26] <mup> PR snapcraft#1201 opened: demos: make ROS demos support exiting after success <Created by kyrofa> <https://github.com/snapcore/snapcraft/pull/1201>
[21:26] <mwhudson> unplugging the card reader made godd die
[21:28] <mwhudson> maybe i just hate sd cards
[21:31] <mwhudson> yeah different sd card worked fine
[21:34] <mwhudson> and now libvirt has stopped working?
[21:35] <mwhudson> definitely a computers day
[21:55] <dpb1_> kyrofa: what appears to be failing on that sudo snap install core:  http://paste.ubuntu.com/24217781/
[21:56] <dpb1_> I'm not sure what those are signaling to me
[21:56] <kyrofa> dpb1_, indeed. Me neither
[21:57] <kyrofa> dpb1_, would you mind logging a bug?
[21:57] <kyrofa> (against snapd)
[21:57] <dpb1_> doing
[22:01] <pachulo> I'm having a problem with the keepassXC snap (but I think that it's not related to the application): I installed the snap with --classic confinment, but even then I can't access NFS mounted directories from the app, does anybody know why?
[22:01] <dpb1_> kyrofa: thx: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1674484
[22:01] <mup> Bug #1674484: snap install core failure: permission denied (apparmor) <amd64> <apport-bug> <third-party-packages> <xenial> <snapd (Ubuntu):New> <https://launchpad.net/bugs/1674484>
[23:43] <mup> Bug #1674505 opened: Error checking context: 'can't stat '/home/user/docker-project' when runing docker build <Snappy:New> <https://launchpad.net/bugs/1674505>