[02:28] stokachu: np [04:18] Bug # changed: 1627893, 1632124, 1632306, 1642257 [07:18] PR snapd#2740 closed: releasing snapd version 2.22 [07:29] PR snapd#2738 closed: spread: remove state tar on project restore [07:35] PR snapd#2691 closed: tests: allow to install snapd debs from a ppa instead of building them [08:17] PR snapd#2693 closed: cmd: rename mountinfo to sc_mountinfo [08:39] PR snapd#2742 opened: tests: fix typo in systems name [09:59] PR snapd#2676 closed: cmd: collect string utilities in one module, add missing tests [10:11] good morning [10:11] sorry for joinling late, forgot I turned my server off [10:12] http://askubuntu.com/questions/877850/error-cannot-deliver-device-serial-request-unexpected-status-400 <- any snappy people can help this person out? [10:13] popey: hey [10:13] popey: most of the time when this happens is when people build their own model [10:13] popey: or use a board outside of the supported set [10:20] PR snapd#2742 closed: tests: fix typo in systems name [10:25] PR snapd#2713 closed: cmd: fix issues uncovered by valgrind [10:26] PR snapd#2416 closed: cmd/snap-confine: add snap-confine command line parser module [10:26] PR snapd#2739 closed: tests: remove (some) garbage files found by restore cleanup analysis [11:00] PR snapd#2698 closed: asserts,interfaces/policy: add support for $SLOT()/$PLUG()/$MISSING in *-attributes constraints [11:02] PR snapd#2743 opened: debian: move the snap-confine packaging into snapd === hikiko is now known as hikiko|ln [12:15] Bug #1648777 changed: writing a (3GB sized) x86 image to a 3GB SD card makes the filesystem resizing being skipped === hikiko|ln is now known as hikiko [12:44] PR snapd#2658 closed: cmd: add mount / unmount helpers [13:01] Hrm [13:01] Cannot find the definition for part 'desktop-ubuntu-app-platform'. [13:01] It may be a remote part, run snapcraft update to refresh the remote parts cache. [13:02] ^^ This seems to be a regression? Cloud parts used to be pulled in automatically [13:02] I was quite confused and it took me a bit to realize the part name wasn't wrong [13:04] ogra_: hey! what do you think about adding a configure/install hook on the classic snap running apt update to initialize the apt database for the user? [13:05] didrocks, not much since that forces you to be online [13:06] didrocks, well, we could add it with an online check i guess ... but the whole thing is designed so that you can also use it witouth being online at all [13:10] ogra_: well, when you install the snap, you are online already, correct? :) [13:10] true indeed [13:11] and it we can try to make it ran only at that time? [13:11] I'm happy to have a shot at it [13:11] (not today) [13:11] but just wanted to know if you were +1 first on it [13:11] sure, the script that gets executed is actually shipped in the core snap [13:11] and is only executed the first time you run "sudo classic" [13:11] seems like a snap installed app can't read from the keyboard? [13:12] ah, I was more thinking as a hook in the classic snap itself [13:12] also, can't click on a link in the snapped app and open it in the system browser [13:12] "read from the keyboard" ? [13:12] do you have a camera attached ? :P [13:12] didrocks, nah, it should just become part of the setup script ... the classic snap only calls this [13:13] ogra_: ok, do you have the repo reference handy? If not, no worry, I'll have a shot later anyway [13:13] no repo ... it is part of the livecd-rootfs package in the image PPA [13:13] ogra_: copying text into a snapped app is weird [13:14] ogra_: ok, which ppa? (if you prefer to do it yourself, feel free ;)) [13:14] didrocks, http://paste.ubuntu.com/23893526/ [13:15] didrocks, from https://launchpad.net/~snappy-dev/+archive/ubuntu/image/+packages?field.name_filter=&field.status_filter=published&field.series_filter=xenial [13:15] ogra_: excellent! Thanks a lot :) [13:15] (note that the pasted one is outdated, use the actual one from the PPA) [13:17] yeah, I'll be able to find it, I'm sure :) [13:35] davidcalle: ping re security whitepaper (I asked a question probably after your eod on friday) [14:11] jdstrand: hey [14:11] zyga: hey :) [14:12] jdstrand: I'm working on the kernel bug and also on the string changes you suggested [14:12] jdstrand: I think the outcome will be much safer, thanks for that! [14:13] zyga: gret! :) [14:13] great even! [14:19] jdstrand: I'm on it today, pdf is live already [14:26] davidcalle: hi! :) ok, so is https://developer.ubuntu.com/en/snappy/guides/security-whitepaper/ the correct url for the whitepaper? it is out of date, but the pdf it links to is up to date [14:28] jdstrand: indeed, I've uploaded the new pdf, updating the page as we speak (will be live in a short moment) [14:28] davidcalle: ah, I see. ok, thanks! :) [14:46] what should I do if I want some feedback from the user once a snap is installed ? I am working on a selenium based twitter bot that is going to run on xvfb. For twitter login I need to request username/password from the user to login. [14:46] is there probably a way to run a script once a snap is installed ? [14:53] PR snapd#2558 closed: snapstate: move refresh from a systemd timer to the inernal snapstate Ensure() [14:59] sergiusens: is that perhaps why my snap isn't showing up in the store? because it's classicly confined? [15:01] PR snapd#2744 opened: move configstate.Transaction stuff into configstate.transaction [15:04] kirkland, snap find conjure-up works though it returns a bunch of results [15:04] stokachu: can you "snap find hollywood"? [15:05] snap find hollywood [15:05] The search "hollywood" returned 0 snaps [15:05] kirkland, is our snap published/public in the webui? [15:05] your* [15:06] stokachu: yes, it looks like it [15:11] kirkland, not sure if this helps but here is what mine looks like from the webui: http://imgur.com/a/pEiEp [15:12] kirkland, oh do you have a stable snap published? [15:12] i have at least one stable [15:13] stokachu: ah, maybe that's it? [15:14] stokachu: so, I need to change "grade: devel" to "grade: stable" in snapcraft.yaml? [15:14] stokachu: rebuild, reupload? [15:15] kirkland, try just releasing it to stable channel from the webui [15:27] jdstrand, is kirkland's hollywood snap not showing up in the snap search results b/c it hasn't been approved? [15:28] 00:40:01> kirkland: done. approved but you'll need to release it [15:28] I got that on Friday [15:28] and then I did release it [15:38] kirkland, ah ok [15:38] stokachu: it is in beta and edge. 'stable' is the only channel 'snap find' will give results for [15:39] kirkland: fyi, I see 1.12 is uploaded but not released anywhere [15:39] 1 kirkland@x250:/tmp/sandbox.hwgfBlQv/hollywood/snapāŸ« snapcraft release hollywood 1 stable [15:39] Revision 1 (classic) cannot target a stable channel (stable, grade: devel) [15:39] aha! [15:39] now that worked [15:39] (bumped the rev) [15:40] kirkland, \o/ [15:40] kirkland: you seem to have specified 'grade: devel' which means it will never go to stable [15:40] kirkland: ah, you fixed that in 1.12 [15:41] and snap find now finds it [15:42] kirkland, haha nice snap [15:50] What does hollywood do, kirkland? [15:50] qengho: https://www.youtube.com/watch?v=rVMn3xk5mcY [15:50] Ah! I remember this. [15:55] This reminds me of a tool I remember from my early unix days, when I was just an egg. Our auditory processing is as good or better than visual attention. An app would convert network traffic into sound. You'd start it and maybe hear that something seems a little off today. [15:55] what's the trick to create a desktop launcher with snap? i have desktop: entry in app: but no icon appears in menu [15:56] a working example would be nice [16:04] cos-: it's tricky, ask sergiusens [16:04] also having a desktop in setup/gui doesn't seem to work, as examplified here https://github.com/ubuntu-core/snapcraft-examples/blob/master/03-hello-world-desktop-devmode/setup/gui/hello-world-desktop.desktop [16:04] cjwatson, hey ... we need some expert opinion ... in the core images we used to use a profile.d snippet to extend the PATH with /snap/bin (we do that in classic still), for remote ssh commands without login shell that didnt work, so we moved the /snap/bin to the global PATH in /etc/environment ... now it turned out that some tests actually use su ... [16:05] PR snapd#2745 opened: cmd: add sc_must_stpcpy [16:05] jdstrand: hey, could you please have a look at this pull request: ^^ this is the safe stpcpy we've discussed. [16:06] cjwatson, i remember you being opposed to change ENV_SUPATH (and i'm slightly reluctant to touch login.defs at all) ... should we or should we not change it there ? [16:06] jdstrand: my only comment was to perhaps use memmove just to be super paranoid safe [16:06] cjwatson, or rather ... what would be the drawbacks [16:06] ogra_: just /etc/environment is supposed to work for su as well; this is basically https://wiki.ubuntu.com/OneTruePath [16:07] stokachu: okay, we're there now :-) [16:07] ah, i didnt find the wikipage [16:07] and for qt5 app should i have after: desktop/qt5, desktop-qt5 or qt5conf? all are used in different examples [16:07] ogra_: I don't think you should change it there, but rather you should chase down why su's use of pam_env apparently isn't working? [16:07] kirkland, cool man [16:07] cjwatson, well, it seems it doesnt [16:07] stokachu: thanks for your help [16:07] ogra_: I'm not arguing with that, but from the config file on my system it seems that it should [16:07] np anytime [16:07] ogra_: so that seems worth tracking down rather than working around and forgetting [16:07] ok, thanks [16:18] PR snapcraft#1092 opened: meta: properly get the icon extension from splitted name [16:24] sergiusens: i'd appreciate any help with creating a .desktop launcher. my current code is here https://github.com/vranki/siilihai-client [16:26] cjwatson, hmm, are you actually sure su should use pam_env for PATH ? the manpage sounds like some vars wont be read from there http://paste.ubuntu.com/23894355/ [16:26] hmm, maybe the used files should be in the git repository and having them in the build directory isn't enough.. i'll try recreating the package with files in git [16:26] cjwatson, note the "Other" in there [16:28] ogra_: see /etc/pam.d/su [16:29] I see no reason to assume the manual page is up to date with the intended PAM configuration :-) [16:29] lol [16:29] ok [16:54] PR snapcraft#1093 opened: python plugin: do the right thing with classic === petevg is now known as petevg_noms [17:17] sergiusens, ^ will that fix classic install on trusty? [17:18] ogra_: you are scheduled for the linaro open hours on feb 23th, 8am pacific time. [17:18] elopio, ok, i'll add that to my calendar [17:18] Chipaca: zyga: would you like to join them for an episode and talk about ubuntu core 101? it would be feb 16th. [17:19] ogra_: thanks. Robert will send you an email with the details. [17:19] great [17:19] elopio, can i think about it? [17:19] elopio: yes, gladly [17:19] Chipaca: yes, and you can also say no :) This is the thing: http://www.96boards.org/OpenHours/ [17:19] elopio: can you please send me an invite? I forget everything otherwise :) [17:20] thanks zyga. [17:20] elopio, huh, saying no is an option ?!? [17:20] :P [17:20] ogra_: it was an option for you last week. Not anymore :p [17:20] haha [17:21] kgunn: are you around now? I'm not sure if you got my ping, maybe email is better. [17:22] jamiebennett: and this is the thing you signed up for: https://www.youtube.com/watch?v=P1_HjzcnJ-s [17:22] elopio: what's up [17:22] you will be the main panelist on the march 9th. [17:22] about to go for a run....but at least i got your most recent ping [17:23] elopio: I did ;) [17:23] ogra_: is also going so maybe we can tag team [17:23] kgunn: hello! go and run. I'm sending you an email to see if you want to show the kiosk on linaro openhours and ubuntu testing days. [17:23] ah, elopio ok.... cc AlbertA ;) [17:24] will do. [17:25] jamiebennett: ogra_: Robert said rsalveti will be in the panel too. I can only imagine the party afterwards :D [17:25] elopio, lol [17:25] and i know in which bar it will happen ! [17:27] elopio: my pleasure :-) [17:27] elopio: lol :) [17:27] o/ [17:28] hah, the lurker ! [17:28] rsalveti: hey :) [17:28] rsalveti: how are you doing? [17:28] good :-) [17:29] who are going to be at connect? [17:29] o/ [17:29] rsalveti: I think only ogra_ [17:30] how are things at the snappy land :-) [17:30] connect is in US so I cannot go :/ [17:30] ogra_: oh! that would be awesome [17:30] rsalveti, it will !!! [17:30] zyga, huh ? budapest i thought ... [17:30] rsalveti: reliable little by little [17:30] ogra_: oh [17:30] ogra_: the vegas thing confused me [17:30] then I could go [17:30] (if someone would want me there) [17:30] i guess the US is dead territory for conferences for the next 4 years [17:31] hahah, indeed [17:31] ogra_: going to drive there? [17:31] nah [17:31] don't remember if you did that last time [17:32] i did [17:32] right, I had some good memories :-) [17:32] ogra_: or 16 [17:32] but i largely gave up on cars ... so it would be rental or train ... [17:32] ogra_: 4 + 4 then after the war with canada and mexico is over ;) [17:32] its a lovely ride thogh ... [17:32] zyga, if it is only canada and mexico, yeah [17:32] get a new porsche [17:33] nah, i still need to get rid of the three others :P [17:33] ogra_: then china invades and all connects will be in china ;-) [17:33] you mean "berlin - china" or "paris -china" ? [17:33] :) [17:33] ogra_: just bejning east, west, central, etc... [17:34] lol ... [17:34] ogra_: on the upside, aliexpres will ship locally [17:34] everywhere [17:34] from the moon :D [17:35] apart from UK though ... because of brexit [17:35] I still wait fo brexit for electricity, to stop the immigration of electrons from mainland [17:35] haha [17:35] UK could switch to 100VCD === petevg_noms is now known as petevg [18:41] PR snapd#2712 closed: interfaces/builtin: refine the content interface rules using $SLOT [19:16] sergiusens [19:17] sorry my bad. was search the responses in the irc term [19:17] was searching* [19:19] was looking for hints as to why "service snap" namespace in trusty doesn't seem to map to a given snap running snap. For example, "sudo service snapd status" works on xenial, but not on trusty [20:10] PR snapd#2746 opened: interfaces: remove some syscalls already in the default policy plus comment cleanups [20:33] PR snapd#2747 opened: interfaces/mount-observe: add quotactl with arg filtering (LP: #1626359) [20:38] PR snapd#2748 opened: seccomp-support.c: add PF_* domains which can be used instead of AF_* [20:46] jdstrand: hey, still around? [20:48] wtf, i think i've found a glibc bug [20:49] mwhudson: hey [20:49] mwhudson: long time, how are you? [20:49] zyga: ok! [20:49] zyga: well right now i am in a rabbit hole but otherwise :) [20:50] mwhudson: what are you up to? do you need a garden elf assistant? :) [20:50] zyga: i'll have a bug comment in a minute [20:51] zyga: i hope you didn't say 'elf' there by accident [20:51] hehehe [20:51] such a versatile word :) works both ways [20:53] oh heh i commented by email so i can't show it to you yet [20:54] zyga: it will be here in a few minutes: https://bugs.launchpad.net/snapd/+bug/1657504/comments/18 [20:54] Bug #1657504: asciinema 1.3.0 snap is segfaulting on 14.04 [20:55] I could never get dlopen() to work in a snap I was making [20:56] zyga: it's there now [20:56] mcphail: a classic or strict snap? [20:56] mwhudson: strict [20:57] mcphail: probably something a bit different from this then, i think [20:57] mwhudson: aah, OK [20:57] mwhudson: oh, intereting [20:57] mwhudson: looking [20:58] I was working on that part so very keen to get to the bottom ofthat [20:59] zyga: the code in glibc is around here https://sourceware.org/git/?p=glibc.git;a=blob;f=elf/dl-load.c;h=a5318f9c8d1d42745a254479cf6bb1cd2acd516f;hb=HEAD#l2035 [20:59] zyga: DT_RUNPATH is only like 15 years old, of course there are still loads of obscure bugs when you try to use it [20:59] mwhudson: do you know if nss works by loading modules into the process or by doing IPC to something that loads the modules? [21:00] zyga: it just calls dlopen [21:00] this is one of the reasons static linking with glibc don't work good [21:01] zyga: https://sourceware.org/git/?p=glibc.git;a=blob;f=nss/nsswitch.c;h=0a65f6ad0c640ae144cbe9d7c2edf9d67e67a245;hb=HEAD#l358 [21:01] mwhudson: that makes sense, I recall a warrning from the linker when one does that to name resolution functions [21:02] mwhudson: so what should we do to have libc load the nss modules from the core snap? [21:02] zyga: fix glibc to look at DT_RUNPATH in the executable, i think [21:02] zyga: which is of course going to be loads of fun [21:03] zyga: you could also try turning off the flags that make ld emit RUNPATH vs RPATH [21:03] mwhudson: and good fun of work [21:03] fun kind of work :) [21:03] well at least you don't have to argue with mr drepper any more [21:03] mwhudson: actually I don't know why I suggested to use the newer version of those flags [21:03] mwhudson: for the initial experiment rpath worked just as well [21:04] zyga: if you use RPATH, LD_LIBRARY_FLAGS is ignored [21:04] mwhudson: but AFAIK we don't need LD_LIBRARY_FLAGS for classic snaps [21:04] mwhudson: (for those that are linked properly) [21:04] oh heh this dude found the same thing as me http://blog.qt.io/blog/2011/10/28/rpath-and-runpath/ [21:05] (and i'd read that post before too) [21:05] mwhudson: question: would it be possible to invoke the dnyamic linker to ask it to load an executable without rpath/dtrunpath? [21:05] mwhudson: e.g. to load /bin/true from the core snap that is just vanilla /bin/true in an odd location [21:07] zyga: i don't understand, sorry [21:08] zyga: you don't feel like writing something that adds DT_RUNPATH (and edits the ELF interpreter) to all binaries in the core snap? :) [21:09] (i presume in strict snaps the core snap is available at both / and /snap/core/current ?) [21:09] mwhudson: that's the problem actually, it's not [21:09] mwhudson: and we want one core snap, not two (one for classic and one for strict confinement) [21:09] mwhudson: in strict confinement core snap is / and you cannot read /snap/core/* [21:09] zyga: ah [21:09] zyga: fun times [21:09] mwhudson: in classic confinememt core snap is /snap/core/* and you can read anything [21:10] mwhudson: goal: make it possible to run stuff from the core snap in both cases [21:10] mwhudson: I was thinking about having snap-exec run the dynamic linker (even patched one since it's the one from the core snap) [21:10] zyga: don't see how that's possible [21:10] mwhudson: and load the application with some fancy defaults [21:10] oh [21:10] something like that might work [21:10] mwhudson: but that breaks down when we exec something from the core snap (e.g. we run bin/sh but then we run bin/ls) [21:11] mwhudson: because then the system (wrong) linker gets used [21:11] yeah [21:11] mwhudson: I don't know of a way to force "gimme that linker" somehow [21:11] mwhudson: unless [21:11] mwhudson: we do some hackery around exec in the libc that ships in the core snap [21:11] mwhudson: then it might just work allright [21:11] mwhudson: it'd be a simple case of path comparison, if starts with /snap -> use fancy linker mode [21:12] mwhudson: crazy? certainly! possible? maybe [21:12] can you bind mount something over /lib/ld-linux.so.2? [21:12] uh not that one [21:12] mwhudson: no, because in confinement: classic mode we don't have a mount namespace so everything in the system would sere that [21:12] mwhudson: we can but that's hurt us [21:12] yeah [21:12] mwhudson: and distros would be looking at us carefully if we bind mount over /lib for eveyone to see just to run [21:13] mwhudson: I think we need some linker work to make this play ball [21:13] PR snapd#2749 opened: interfaces/default: allow mknod for regular files, pipes and sockets [21:13] i think so too [21:13] mwhudson: at the very least to fix nss issue [21:14] well also this running /snap/core/bin/ls uses the host elf interp thing [21:14] mwhudson: hmmm [21:14] no? [21:14] mwhudson: yes [21:14] mwhudson: that's true [21:14] this is all very confusing [21:14] mwhudson: unless we never allow that to happen [21:14] mwhudson: remember that we control all entry points [21:14] zyga: you mean, just don't let classic snaps exec things from the core snap? [21:14] mwhudson: snap-run -> snap-exec: we can run a patched dynamic linker at that stage [21:15] mwhudson: exec: we can use a patched glibc that uses an alternate linker if the target is in the core snap [21:15] mwhudson: I think we should not restrict what classic confinement snaps can run [21:15] mwhudson: it would limit their usefunless heavily IMHO [21:15] yeah it's a pretty blunt instrument [21:16] zyga: hey, yes [21:16] mwhudson: do you see any alternative ideas? [21:16] jdstrand: hey :) [21:16] jdstrand: I just commented on your PR :) [21:16] zyga: seccomp-bpf? :) [21:17] zyga: anyway, i think the nss issue is easier than the interpreter issue [21:17] mwhudson: hmmm, curious [21:17] zyga: "just" patch libc (well libdl) in the core snap to respect RUNPATH in the executable, like the docs say [21:17] mwhudson: how would that work? we'd attach a seccomp profile that patches exec? [21:17] zyga: yeah [21:18] zyga: i have no idea if that's easily possible [21:18] er -easily [21:18] zyga: i worry about statically linked go binaries :) [21:18] mwhudson: but taht profile carries across exec right? would it not clash if someone wanted to run something that already uses seccomp for other things? [21:18] mwhudson: oh, interesting [21:18] mwhudson: don't those use their own name resolver stack? [21:19] zyga: for the elf interpreter stuff i mean [21:19] jdstrand: if you could give me some feedback on the sc_must_stpcpy branch I would really appreciate it [21:19] mwhudson: mmmm [21:19] mwhudson: wait, what's the problem there? there are no libaries to cause issues [21:19] mwhudson: and and golang's dlopen just needs to be fixed somehow (if broken) [21:20] I must be missing something [21:20] jdstrand: is that branch changing our dependency on base seccomp version in any way? (both in kernel and in the userspace) [21:20] zyga: it's possible i am [21:21] zyga: this is all very confusing, and you've spent longer thinking about it than i [21:21] mwhudson: (offtopic, I find it funny that I just opened IRC by accident and joked about "garden elf" and here we are talking about this issue that's currently also close to my heart as I was working with sergiusens earlier trying to figure out what's going on) [21:22] mwhudson: (any) statically compiled binary will work OK (or not) but is beyond our control, if it includes a dynamic linker inside we also have no way to influence it [21:23] mwhudson: I was thinking about extending the auxilliary vector to set a bit that indicates a given process uses classic confinement [21:23] mwhudson: and that would change how linker behaves [21:24] hi folks, question out of left field. I'm on trusty, how do I check the status of the snapd process and my snaps. I was accustomed to using systemd w/ "service snapd status" and "service snap. status" on xenial. [21:24] zyga: and what behaviour would it change ? [21:24] mwhudson: I think we could use it to change default search path [21:25] mwhudson: my goal would be to leverage that to have pre-compiled software (e.g. debs) work as classic confinement snaps [21:25] I see snapd package on trusty pulls in systemd as a dependency, I'm just not sure how that shakes out as far as checking ths snap processes via tools like services, initctl etc. I *could* check ps easily enough, but I wondered what expected behavior is. [21:25] zyga: oh, so you wouldn't need to set DT_RUNPATH in the binaries in a classic snap? [21:25] blackboxsw: on 14.04 we have a deputy systemd [21:25] zyga: just the elf interpreter ? [21:25] mwhudson: exactly [21:26] mwhudson: because we probably cannot just (not sure) easily rewrite a random executable to have it "gain" runpath and a different dynamic linker path [21:26] well not even the elf interpreter, because you jam a custom interperter in via snap-exec [21:26] mwhudson: the dynamic linker path is also problematic but if we do it upstream it could work elsewhere too [21:26] mwhudson: yes, that's true [21:27] blackboxsw: and you should be able to use regular systemd commands to control services [21:27] and you'd also have a hook in exec that does if exe_path.startswith("/snap/core"): jam_custom_interp_in() [21:27] blackboxsw: there might be some bits missing; I don't know if journald is wired, for example [21:28] mwhudson: yes [21:28] zyga: well sounds crazy, and not inherently impossible [21:28] mwhudson: the idea with the extra bit in auxv is to have clean transitions from snaps to classic world [21:28] mwhudson: but perhaps we can do that with snap-exec each time and this is not required [21:29] mwhudson: (all transitions are out of snap world, snap-exec brings us back) [21:29] zyga: not if the classic snap just invokes /snap/core/bin/python3 directly? [21:30] mwhudson: that's true, I forgot about side-stepping the apps system [21:30] mwhudson: then we need patched glibc [21:30] mwhudson: or seccomp-bfp [21:30] mwhudson: I think that we will either 1) spec this and JFDI or 2) reconsider classic confinement [21:31] mwhudson: as right now the edges feel pretty sharp :/ [21:31] zyga, thanks for the suggestion. yeah, what I'm seeing from trusty-proposed seems like it's missing a little bit of glue. I'll try digging a bit more, but running "service snapd status" errors with "unrecognized service" though I see /lib/systemd/system/snapd.service defined [21:32] blackboxsw: I think you want to talk to tvoss, he was working on this feature [21:32] zyga: yeah, in some ways the "mixed world" of classic snaps is trickier than isolated snaps [21:33] mwhudson: if we do the magic right it will seem easier [21:33] mwhudson: but I totally agree with what it is today [21:34] good reference zyga thanks will continue the conversation with him. [21:35] blackboxsw: o/ [21:36] tvoss, isn't it 22:35? [21:36] mwhudson: zyga well I fixed all env var leaking for classic snaps (even PATH), use a little shebang trick to chose the right interp and added a way to provide your own python in stage for the plugin to use [21:36] blackboxsw: so for snapd itself and services from snaps, systemctl should do the right thing [21:36] blackboxsw: yup, it's 22:35 [21:36] yowsa. [21:37] blackboxsw: so systemd is not running as pid 1 on trusty, upstart is still the init system [21:37] blackboxsw: so using sudo service will end up querying upstart, instead of systemd [21:37] tvoss, ahh got it! thanks, looks like I needed "sudo" on trusty too [21:37] without sudo it gives things like "No such interface" etc. [21:38] hmmm, I can give that a spin tomorrow my morning, on my tablet right now [21:38] I'll take a note, thanks for testing it out [21:39] thanks for the response. tvoss. solved my initial hurdle [21:39] blackboxsw: cool, later then :) [21:39] o/ [21:39] \o [21:40] mwhudson: if it helps http://paste.ubuntu.com/23895943/ [22:16] PR snapd#2750 opened: interfaces/default: don't allow TIOCSTI ioctl [22:34] PR snapcraft#1091 closed: tests: add ubuntu user to sudoers on every adt platform