/srv/irclogs.ubuntu.com/2016/05/02/#snappy.txt

=== zyga_ is now known as zyga
zygagood morning05:49
=== blr_ is now known as blr
=== JanC is now known as Guest37928
=== JanC_ is now known as JanC
morphiszyga: ping08:00
zygamorphis: hey, good morning08:00
morphiszyga: morning!08:00
morphiszyga: wondering if you tested the bluez interface changes at runtime as I am getting invalid apparmor profiles with those changes08:01
zygamorphis: hmm, no I did not08:01
morphisdoesn't seem to like peer=(label=snap.bluez.{bluez,obex}),08:01
zygamorphis: can you pastebin what you're getting?08:02
zygahmmm08:02
zygaI see, thanks, jdstrand suggested those nad I assumed it would be digested08:02
morphiszyga: https://paste.ubuntu.com/16186420/08:02
zygaok, let me look08:03
* zyga curses at 2fa08:03
zygawhy does it need to auth me for a f.... pastebin08:03
zygaPlain form not available for deep linking.08:04
zygamorphis: odd, for me it complains at line 24108:08
zygaAppArmor parser error for test.aa in test.aa at line 241: syntax error, unexpected TOK_ID, expecting TOK_CONDID or TOK_END_OF_RULE08:08
zygaand that is:   # for 'udevadm trigger --verbose --dry-run --tag-match=snappy-assign'$08:08
zyga??08:08
zygaI think line numbers are broken08:09
zygait really complains about   signal peer=snap.@{SNAP_NAME}.*,$08:09
* zyga experiments08:09
zygamorphis: it's clear that something is quite not right08:11
zygamorphis: can we wait till jdstrand or tyler shows up?08:11
morphissure08:14
morphiszyga: reworking the network-manager interface now08:14
slvnhello ! got some issue with my snap. Running "snap-review mysnap" says "checksums do not match.". I can't upload it to the store because of that. I have tested the "opencv" example and it worked.08:15
slvnI have also tested the command lines "snapcraft snap <DIR>" or "mksquashfs <dir> ..". But it failed also the checksum test.08:16
zygaslvn: we know that, at least on pi2, mksquashfs is not really deterministic08:20
zygamaybe it affects other arches08:20
zygaslvn: for now I'd report a bug and try to investigate08:21
slvnzyga, could you (quickly) double-check with the SDL2 package that it also fail on your side ? I am on amd64, and build for amd6408:24
zygaslvn: I'm somewhat busy but if you run it 100 times and collect the distribution of the hashes that would make a fantastic bug report08:24
zygaslvn: note, run mksquashfs only08:25
slvnok why not ...08:25
slvnhow can I get the hash ? checksun mysnap.snap ?08:25
zygaslvn: sha512sum08:26
* zyga explores how to refactor snapenv08:26
slvnand you say, I only need to re-do "snapcraft snap" ?08:26
zygaI'd just re-do the squashfs command but snapcraft snap is close enough08:27
slvnzyga, I get something like : http://paste.ubuntu.com/16186526/08:31
zygahmm08:31
zygaperhaps snapcraft snap is not enough08:31
zygaas in, it does changes to snap/ files08:32
zygakyrofa, sergiusens: ^^08:32
slvnzyga, something like "mksquashfs <dir> <snap> -noappend -comp xz -all-root -no-xattrs" ??08:33
zygayes08:33
slvnsame randomness ..08:36
zygaslvn: report that as a bug on squashfstools please08:36
zygadefinitely worth investigating08:36
slvnok08:37
zygaslvn: can you also check if it is the same if you use something to turn of paralell compression?08:37
slvnzyga, I was about to test that. But I haven't find the option08:37
slvnop yes -processors08:38
slvnI try08:38
zygaslvn: -processors 108:38
slvnalso failing :/08:39
slvnI will do the bug report !08:39
morphiszyga: I will most likely write the snap label replacement code you wrote for the plug side also for the slot side08:40
zygasure08:41
zygamorphis: if you figure out why apparmor doesn't accept the file you sent me feel free to fix the shared function too08:41
zygamorphis: and note that for me it also failed on line mid-file08:41
zygamorphis: on all-up-to-date xenial08:41
morphisok08:41
morphiszyga: https://github.com/ubuntu-core/snappy/pull/1036#discussion_r60144002 is what I am currently looking into08:42
morphisbut trying first to rework the rules a bit08:43
zygamorphis: keep this in mind: https://github.com/ubuntu-core/snappy/pull/1036#issuecomment-21584190408:43
zygamorphis: the 'works on the desktop' aspect08:44
morphiszyga: so how can I test that?08:44
zygamorphis: snap nmcli separately perhaps?08:44
morphisand how do I say that the ubuntu-core snap provides the interface?08:44
zygamorphis: you want to look at snap/implicit.go08:45
morphisok08:45
zygamorphis: but you'll have to bite the bullet and make it dependant on being on the desktop (say dpkg/info exists)08:45
morphishm08:45
zygabut don't worry08:45
zygathere's similar code in ubuntu-core-launcher08:46
pedroniszyga: we really need to talk (with mvo etc) about what's the official way to detect desktop vs not08:46
pedroniswe need an official helper somewhere for that08:46
morphiszyga: my only fear is this will bringup another lengthy discussion08:46
morphisso I would like to do that after the first PR08:46
morphisor let you guys do it properly08:46
zygamorphis: no worries, I'll help you out08:48
morphiszyga: sure but I want to get a first version merged soon, this is already pending for too long08:48
morphiszyga: also I am getting08:52
morphispeer=(label=snap.network-manager.networkmanager),08:52
morphisin the plug apparmor file08:52
morphiswith your method from utils.go, shouldn't that be snap.network-manager.nmcli?08:52
zygahmm08:53
zygayes, let's see what I did there08:53
zygais networkmanager an app name?08:55
slvnzyga, I haven't reported the bug yet because my testcase was passing the checksum test :)... so I found out something: adding a line "stage-packages: [ .. ]" solve the issue ...08:57
zygaslvn: curious08:59
slvnyep, I add a stage-package line in my "real" package, and it worked also. I will report that ...08:59
morphiszyga: it is09:00
zygamorphis: so that is correct, the plug can talk to the slot09:00
morphisok09:00
morphiszyga: however I am wondering if its ok to include the client app name in the permanent slot apparmor policy, propably not09:03
zygahmm, why?09:03
zygaclient app name in permanent slot?09:03
zygaisn't that what per-connection snippet should do09:04
morphiszyga: https://paste.ubuntu.com/16186665/09:04
zygamorphis: is nmcli connected to nm?09:05
zygamorphis: it seems to be the same as bluez and bluetoothctl09:05
morphisyes09:05
morphiszyga: see https://github.com/ubuntu-core/snappy/pull/1036#discussion_r6014400209:05
morphisthat is what I had before09:05
morphisbut jdstrand said we should use proper snap.* names too09:05
morphisfor bluez we didn't do that09:06
zygawasn't that what my earlier patch (now broken apparently) did?09:06
morphishttps://github.com/ubuntu-core/snappy/blob/master/interfaces/builtin/bluez.go#L7409:06
zygaah, I see09:07
zygaI'm somewhat confused though09:07
zygado we need this on both slot and plug ends?09:07
zygaif the slot side permission didn't exist09:08
zygawould the plug-side connection permission suffice?09:08
morphiszyga: not sure too09:08
morphisplaying a bit with more generic rules right now09:09
slvnhttps://bugs.launchpad.net/snapcraft/+bug/157733309:12
ubottuLaunchpad bug 1577333 in Snapcraft "snap-review failed with "checksums do not match"" [Undecided,New]09:12
morphiszyga: ok, I have a simpler version working now which pretty much looks the same as the bluez one09:27
ogra_mvo, looks like your latest u-d-f is broken, mind rolling it back (or do we need to update the gadgets ? ... looks more like squashfs-tools to me though)09:41
zygaogra_: see the bug reported by slvn above09:45
zygait seems that mksquashfs is the new willy wonka09:45
ogra_http://people.canonical.com/~ogra/snappy/all-snaps/ubuntu-device-flash is the last working one btw09:46
* ogra_ has backups ;)09:46
zygathe last one standing ;)09:46
ogra_:)09:46
morphiszyga: https://github.com/ubuntu-core/snappy/pull/1036#issuecomment-21618128409:50
zygamorphis: thanks09:51
morphiszyga: can you give this a last review round?09:51
morphisniemeyer, jdstrand: ^^09:51
zygamorphis: in a sec09:52
morphiszyga: btw. should I have AutoConnect() { return true }?09:52
zygamorphis: that won't do much on non-desktop09:54
zygaauto-connect only connects to stuff on the OS snap09:54
zyga(today009:54
morphisso you be false?09:54
zygayeah, leave it as false and add a note09:54
morphisok09:54
morphiszyga: btw. if you want to test the bluez snap we have prebuilt ones at https://code.launchpad.net/~snappy-hwe-team/+snap/bluez09:56
zygamorphis: oh, that's useful, thank you09:56
zygamorphis: I'll get to testing this shortly, I'm mid-way in another branch09:56
morphissure, take your time :-)09:57
=== ogra_` is now known as ogra_
zzarrhello! is there a snappy image for dragonboard 410c yet?10:40
ogra_zzarr, build one yourself ...10:42
ogra_http://people.canonical.com/~ogra/snappy/all-snaps/ubuntu-device-flash should be the last working ubuntu-device-flash10:42
zzarrnice, thanks ogra_10:43
ogra_http://people.canonical.com/~ogra/snappy/all-snaps/dragonboard/README has the runes you need10:43
zzarrthanks ogra_10:45
ogra_(do not use the mvo u-d-f, it is currently broken)10:47
zzarrmvo?10:48
ogra_the one mentioned in the readme10:48
zzarrokey10:48
mvoogra_: almost ready again10:48
ogra_good :)10:49
zzarrI use the one you have ogra_10:49
ogra_yeah, thats fine then10:49
zzarrit's done (it was quick)10:50
zzarr100/100 internet connection ssd and a quad core i7... I don't ever have to wait :)10:54
mvozzarr, ogra_: new u-d-f is up10:54
zzarrnice10:54
zzarrmvo, what are the benefits with it?10:55
zzarr(over ogra_'s binary?)10:55
mvozzarr: I don't know what ogra_ binary is doing, sorry so I can't answer10:56
zzarrokey, no problem, maybe ogra_ can tell10:56
=== pitti` is now known as pitti
zzarrthanks for helping me, both of you mvo and ogra_ :D10:57
zygamorphis: I'm adding some inline comments to n-m10:57
=== pitti is now known as Guest28148
morphiszyga: aye10:57
zygamorphis: quick side question: what's the dichotomy of apparmor doing some checks and dbus.xml doing what looks like the same checks again10:58
morphiszyga: a more fundamental question we could solve with snappy but for now we want to stick to what upstream does + apparmor on top10:59
zygamorphis: I see, thanks10:59
=== Guest28148 is now known as pitti
ogra_mvo: my binary is simply the one from brefore it broke :)11:28
ogra_*before11:28
mvoogra_: heh, clever!11:43
kyrofaGood morning12:12
zygajdstrand: around?12:25
jdstrandzyga: hey, I am now12:29
zygajdstrand: hey! :)12:29
zygajdstrand: I hope you had a good weekend12:30
zygajdstrand: we found some issues with apparmor and the {app1,app2} label syntax12:30
jdstrandyes, thank you12:30
jdstrandzyga: you too12:30
zygajdstrand: check the backlog with morphis above for details12:30
zygajdstrand: other than that there are some commends on the network-manager interface12:30
zygajdstrand: and otherwise we're looking good :)12:30
morphiszyga: looking at them now ..12:30
jdstrandzyga: can I see the generated policy?12:30
zygas/commends/comments/12:31
zygajdstrand: one sec12:31
zygajdstrand: https://paste.ubuntu.com/16186420/12:32
zygathat's the same pastebin as above12:32
zygaI tried it and I also had an error mid-file about signal and a glob there12:32
zyganot sure what to make of it12:32
jdstrandzyga: use peer=(label="snap.bluez.{bluez,obex}")12:33
jdstrandzyga: ie, put it in quotes12:34
zygaah, so just " "12:34
zygamorphis: ^^ :)12:34
jdstrandyeah12:34
zygathanks! :D12:34
zygajdstrand: did you try to compile it?12:34
jdstrandand you can do that for "snap.bluez.*"12:34
zygaI also got an error with signal mid way12:34
jdstrandzyga: yes12:34
zygaah ok12:34
jdstrandand "snap.bluez.app1"12:35
jdstrandzyga: as for signal, no issues here. are you compiling on an old kernel?12:36
zygajdstrand: on 4.4.0-2112:36
jdstrandit works fine here12:36
zygaif no issues let's disergard that, I'll re-check after this is patched12:36
zygadisregard*12:37
* zyga cannot type 12:37
morphisjdstrand: when you have some time, could you look at the reworked apparmor policy of the network-manager inteface?12:39
morphisjdstrand: tried to keep the same things as we already have in the bluez interface definition12:39
jdstrandyes12:39
morphisthanks12:40
jdstrandmorphis: as for question or client name in permanent slot, no, we should not do that. We could/should do that in connected slot though12:44
morphisjdstrand: ok12:44
jdstrands/or client/on client/12:44
kyrofazyga, `snapcraft snap` on its own will regenerate the meta/ directory. If you want to essentually only have it call mksquashfs you need to use `snapcraft snap <dir>`12:44
zygakyrofa: ah, thanks12:44
kyrofazyga, it does that so it picks up on YAML changes like changing the snap name, etc.12:45
urm8hello!12:52
urm8Hi people12:52
urm8where do I get newest info about Snappy, including forum discussions on building and stuff like that?12:53
zygaurm8: hey, right here is one spot, I know that many people also use ask ubuntu12:53
zygaurm8: I'd recommend snappy-app-devel maliling list as well12:54
urm8that mailing list looks like the one.12:54
urm8Thanks12:54
zygaurm8: there's also snappy-devel as well12:54
urm8I wanted to pack OpenFoam, but the learning curve to deb packing seem though, so I thought maybe giving the Snappy way a try!12:55
urm8brb12:55
=== pippo is now known as cdio
kgunnzyga: thot you'd be off today, but hey...after some discussion late friday with jdstrand, i think i really am stuck12:58
kgunni've got nil nil returning for everything but aa/seccomp on perm slot12:58
zygakgunn: hey? why is that?12:59
kgunnbut when i try to install my snap, it complains about dbus?12:59
kgunnand i don't even have dbus or any need for it12:59
zygacan you be more specific please?12:59
kgunnyep one sec12:59
ogra_asac, http://people.canonical.com/~ogra/snappy/all-snaps/canonical-pi2_3.3_all.snap in case you want to help testing :)13:01
kgunnzyga: will get back to you in a minute with some pastebins...first have to clean up an experiment i ran late friday13:06
zygakgunn: ok, I'm in a metting now, happy to work with you after13:07
urm8Hi people, is there a begginer guide to snappy too?13:16
sborovkovHello, which interface should I use to allow shared memory access? (peration="mknod" profile="snap.screenly-client.viewer" name="/dev/shm/WK2SharedMemory.907069164" pid=1006 comm="ld-linux-armhf." requested_mask="c" denied_mask="c" fsuid=0 ouid=0)13:18
zygasborovkov: ask jdstrand, perhaps none, in that case please file a bug on snappy (on launchpad)13:26
sborovkovzyga: ok, got it13:27
sborovkovjdstrand: Hello, is there an interface to allow shared memory access?13:27
zygasborovkov: to be clear, there's no specific interface, apps should have *some* shm access today13:27
zygaperhaps the some value needs tweaking13:27
jdstrandsborovkov: looking at your denial you need to adjust your app to use /{dev,run}/shm/snap/@{SNAP_NAME}/@{SNAP_REVISION}/13:28
jdstrandtbh, I never understood why that directory had revision in the path13:28
jdstrandI mean I sorta understood, but for what people use it for, it isn't needed imho13:29
zygajdstrand: the revision part is problematic, I think13:30
zygajdstrand: snaps hardly know that (they do but not really easy)13:30
jdstrandI'm totally fine to remove it13:30
sborovkovjdstrand: ok, understood, now just gotta find where it's used in webkit's code.13:30
zygajdstrand: if it's not a security issue I'd drop revision for sure13:30
jdstrandzyga: SNAP_REVISION is in the env13:30
zygajdstrand: yes, I know but hardly anyone patches code to use it13:30
jdstrandsborovkov: you might be interested in this historical bug: bug #119706013:33
ubottubug 1197060 in apparmor-easyprof-ubuntu (Ubuntu) "SDK webview applications should use an app-specific path for shared memory files" [Undecided,Fix released] https://launchpad.net/bugs/119706013:33
sborovkovjdstrand: Hmm, looks like this was resolved by using 0xide whatever that is. We are using our own build of webkit unfortunately for now so that won't help I guess. I don't understand if with new security I could still use apparmor to tweak this for my app somehow? Or should I just go the route of tweaking paths it accesses13:37
ogra_uh, webkit ... why do you get yourself into such a security nightmare ? :)13:38
sborovkovogra_: We had that part written long time ago to display web pages in QML. It also allows nice things like stopping animations, and some other low level stuff which is nice for performance on RPI. Now Qt moved to web engine but I have no idea if anyone even tried porting it to RPI13:41
ogra_well, oxide definitely runs on armhf devices ... and is well integrated with qml13:42
ogra_(and fully security maintained in ubuntu)13:42
sborovkovogra_: I will look at it, I was not aware about it before even. We are moving from raspbian to snappy currently. And have a beta soon, just need to port everything to new security (well once /dev/vchiq can be accessed with it). But need to get out beta for now :-)13:44
=== kissiel is now known as kissiel-afk
jdstrandsborovkov: is there a bug on /dev/vchiq? if not, can you file it describing what the device is and why you need it? please add the 'snapd-interface' bug tag13:56
kgunnzyga: hmmm....ok i made some progress, interesting stumbling block, i'd mod'd your refresh-bits to build off my fork of ubuntu-core/snappy (kgunnfront/snappy)...that seemed to be an issue13:57
kgunnat any rate.. i can install mir-snap now13:57
kgunnhttps://pastebin.canonical.com/155618/13:58
kgunnjdstrand: ^ i've not been so excited in quite a while ;)13:58
jdstrandslvn: is your issue one of bug #1576763 or bug #1555305 ?13:59
ubottubug 1576763 in click-reviewers-tools (Ubuntu) "pi2 images generate different checksums on repeated runs" [Undecided,New] https://launchpad.net/bugs/157676313:59
ubottubug 1555305 in click-reviewers-tools (Ubuntu) "resquashfs test fails if snap has symlinks" [High,Confirmed] https://launchpad.net/bugs/155530513:59
zygakgunn: hmm13:59
zygakgunn: you cannot change the package name13:59
zygakgunn: you have to move your fork of snappy into $GOROOT/src/github.com/ubuntu-core/snappy13:59
zygakgunn: otherwise it will never ever do anything13:59
sborovkovjdstrand: there is one, it has high priority now13:59
jdstrandslvn: if so, please comment in those bugs with any relevant info. otherwise, please file a new bug and let me know the bug number13:59
kgunnzyga: yep...i just copied over my mod'd files to ubuntu-core dir and it worked13:59
kgunnzyga: tools are getting too smart these days :)14:00
jdstrandsborovkov: what is the bug number?14:00
zygakgunn: glad to hear you are progressing :)14:00
sborovkovjdstrand: https://bugs.launchpad.net/snappy/+bug/153326514:00
ubottuLaunchpad bug 1533265 in Snappy "/dev/vchiq is inaccessible for unprivileged user" [High,Confirmed]14:00
jdstrandkgunn: woohoo! :)14:01
kgunni know minor victory14:01
ogra_jdstrand: we need the re-defined kernel snaps for thsi bug i fear14:02
ogra_*this14:02
zygaogra_: why?14:02
ogra_because we cant ship any udev roles today14:02
ogra_*rules14:02
zygaogra_: you can, via interfaces :)14:03
zygaogra_: interfaces create udev rules14:03
jdstrandit is more than just udev14:03
ogra_inside the kernel snap ?14:03
ogra_where would they end up ?14:03
zygaogra_: inside /lib/udev/rules.d14:03
ogra_there is no bind mounting or anything for the location they would need14:03
jdstrandzyga: those rules don't do DAC permissions14:03
ogra_zyga: that would just be ignored at snap install time14:03
jdstrandzyga: the interface udev rules are only for tagging14:03
zygaogra_: oh, I didn't knowthat14:03
jdstrandI suspect this is a device that won't be covered by the existing implementation14:04
jdstrandI asked for more information in the bug14:04
zygajdstrand: hmmm, it depends on what we need to do14:04
zygajdstrand: how is this different from /dev/ic2-114:04
zygajdstrand: (which worked okay)14:04
ogra_zyga: like you cant ship the kernel config in /boot/config-$uname today ...14:04
zyga(roughly 2/3 months ago)14:04
jdstrandbut I suspect /dev/vchiq is something like all the android specific devices on Touch and simply needs to be granted to all apps somehow. we'll see14:04
zygajdstrand: AFAIR /dev/vchiq is pi specific but perhaps I just know wrong14:05
ogra_jdstrand: it is a rpi only device afaik14:05
jdstrandzyga: if you read the bug, the bug says a) they used hw-assign (it is gone) and b) after using hw-assign, the perms are 60014:05
zygaogra_: I used interfaces to "hw-assign" /dev/i2c-1 to my snap14:05
jdstrand'a' would need to be solved with interfaces. 'b' cannot currently14:05
ogra_zyga: and thats fine14:05
sborovkovjdstrand: I am not sure what it does exactly, but it's needed for h/w decoding on RPI14:05
zygajdstrand: that's my earlier bug, remember when I said non-background apps should have a chmodded /dev/*14:06
zygajdstrand: it works if you are a service14:06
zygajdstrand: (you run as root, the tagging does the rest)14:06
* ogra_ still thinks that needs solving on a kernel level first14:06
jdstrandwe can't just chmod stuff14:06
zygajdstrand: I argued that we should chmod the device to 666 if it's tagged14:06
zyga(in the cgroup)14:06
jdstrandI know you did14:06
jdstrandthat isn't the right solution14:06
jdstrandit is too simple14:06
ogra_why not use udev-acl here ?14:06
ogra_and ship a udev rule for ti14:07
zygajdstrand: too simple and thus too open or what?14:07
jdstrandit might be ok for this device, but it might not be for another device14:07
ogra_*it14:07
zygajdstrand: if there's no tagging there's no cgroup, no chmod14:07
zygajdstrand: if there's tagging it is precisely because we want to allow access to the device14:07
jdstrandI know, but just because it is tagged doesn't mean non-root should have access14:07
jdstrandmaybe it should. maybe it shouldn't14:07
zygajdstrand: plus remember that we can always apparmor-away all bits we don't want14:07
zygajdstrand: I remember the discussion, I know it's still an open question14:07
zygajdstrand: but it somewhat feels like policykit discussion we had with gustavo a while aog14:08
zygaago*14:08
zygajdstrand: when it's granted, it should be just allowed14:08
zygajdstrand: still, that's my 0.0214:08
jdstrandand I maintain my objection to the simplistic approach14:08
jdstrandwe captured this in that doc a while ago. we can pick it up at another time14:09
zygajdstrand: given that if we say you cannot open without root, anyone can just ship a service that exposes it14:09
zygajdstrand: so I'd say it's not security but obfuscation at some level14:09
zygajdstrand: sounds good14:09
jdstrandonly if you assign it to the root service14:09
zygajdstrand: you assign it to a snap, what the snap author does is not something we control14:10
jdstrandthere's a lot of things to consider14:10
zygajdstrand: if it is assigned to a non-root cli tool then it's still under our control via the cgroup14:10
jdstrandI understand what you are saying14:10
jdstrandbut the security policy is something that uses DAC as well as our sandbox14:11
zygasorry, I'm not trying to convince you, I'm just arguing because I think there's no extra security in this mode and I'm hoping you will show me I'm wrong :)14:11
jdstrandwe need to be extremely careful14:11
zygaagreed14:11
jdstrandespecially when moving forward with multi-user, Ubuntu Personal and if we ever do opt-in per-app UIDs14:12
jdstrandthere is a lot to consider14:12
jdstrandanyway, I can't consider all of this right this second-- I have meetings to attend to and PRs to review14:12
jdstrand:)14:12
zygasure, no worries14:12
sborovkovAlright guys, I am gonna come back in few days and ask you again about this. If there is no solution in sight I can use custom kernel snap/whatever I guess - though it would be very nice if it's possible to upgrade in the future to stock ones without reflashing SD cards14:18
=== Aria22 is now known as Aria22|away
draglyHas there been any updates on accessing OpenGL in snaps? Last week I forgot to issue a bug report after I last talked on this channel about the trouble I had with Snapcraft+Qt+OpenGL on Nvidia hardware.14:32
draglyI tried the ubuntu-clock-app example now, and I still get the "Unrecognized OpenGL version" error when running it after installation. Should I file a bug report or is this already fixed in a newer version of snapcraft? I'm using 2.8.4.14:35
zygadragly: there were no changes on the desktop that are released yet, we are working on the first SRU now14:37
zygadragly: though I'm not sure if that particular bug is fixed there already (it might be)14:37
draglyanything in "proposed", or do I need to clone the repo to see if it has been fixed?14:39
kgunnhere's a bug link to track that14:42
kgunnhttps://bugs.launchpad.net/snappy/+bug/157485114:42
ubottuLaunchpad bug 1574851 in Snappy "libgl not found on nvidia machines (so far)" [Critical,Triaged]14:42
sergiusensjdstrand hello! Can I inject raw apparmor to test something out somehow? hint, relate to /dev/shm14:46
zygasergiusens: maybe14:46
zygasergiusens: I can help you out14:46
zygasergiusens: do the connection and all the other stuff you want14:46
zygasergiusens: then edit /var/lib/snapd/apparmor/profiles/*14:47
sergiusenszyga k, thanks14:47
zygasergiusens: then run apparmor_parser -r /path/to/that/file14:47
zygasergiusens: that should do the trick14:47
zygasergiusens: just keep in mind that various operations will erase that change14:47
sergiusenszyga do I need to run anything after editing?14:48
kgunnok, i'm stuck with https://pastebin.canonical.com/155621/14:49
zygasergiusens: apparmor_parser -r14:49
zygasergiusens: on the file14:49
zygasergiusens: to actually load it14:49
kgunnbasically says it can't find mir-server when it's clearly part of the smae14:49
kgunn*snap14:49
sergiusenszyga says already loaded, how do I unload?14:50
kgunnand this used to "just work"14:50
zygasergiusens: -r reloads it14:50
zygatechnically -r is replace14:51
zygaso just -r :)14:51
draglykgunn: Thanks! I'll subscribe to the bug.14:53
kgunnsergiusens: mvo i feel like this might be more in your wheelhouse, my mir-server.snap used to work & unchanged, i add mir i/f to builtin, mir snap installs...i see mir-server:mir in plug list14:55
kgunnbut then it fails with https://pastebin.canonical.com/155621/14:55
=== Aria22|away is now known as Aria
=== Aria is now known as Aria22
kgunnsaying it can't find mir-server which i can very well navigate to the current snap and see it there14:56
kgunndid some pathing assumptions possibly change?14:56
asacogra_: whats that image?14:57
morphisjdstrand: what about leaving the discussion to make that network-manager interface working on desktop up to another PR?14:58
ogra_asac, THATS A GADGET WITH WROKING SERIAL14:58
asacogra_: ah... well, i cant use udf still :/14:58
ogra_EEEK14:58
asacneed full blown images14:58
asachehe14:58
* ogra_ whacks his caps key14:58
jdstrandmorphis: I'm fine with that so long as there is a note in the PR about it (or even in the policy)14:58
* jdstrand was just going be what niemeyer asked for14:58
jdstrands/be/by/14:59
kgunnso, using $SNAP_APP_PATH in my files, is that correct? or did it change to something like $SNAP14:59
morphisjdstrand: yeah, commented for him on the PR about that14:59
jdstrandkgunn: those changed14:59
morphisniemeyer: would that be ok for you?14:59
jdstrandkgunn: SNAP is install, SNAP_DATA is /var, SNAP_USER_DATA is /home14:59
kgunnjdstrand: thanks14:59
jdstrandkgunn: I often find myself using 'hello-world.env|grep SNAP' :)15:00
kgunnjdstrand: i presume that's on a wiki somewhere and i just got lulled into previous glory/success :)15:00
sergiusenskgunn its just $SNAP15:00
kgunnthanks guys15:00
jdstrandkgunn: I'm not sure of that. the docs are in the process of being updated. dpm may have more details15:00
=== kissiel-afk is now known as kissiel
dpmjdstrand, kgunn, I'm missing some context on what you're trying to do, but that might help in the meantime: http://askubuntu.com/questions/762354/where-can-ubuntu-snaps-write-data/762405#76240515:04
kgunndpm: thanks...was just sharing i was lost :)15:04
kgunni was still using snap_app_path15:04
kgunndidn't realize it changed15:05
jdstranddpm: we were talking about the status of the docs wrt 16 changes (of which env vars is one part)15:05
asackgunn: hello-world.env is your friend :)15:05
asacoh that was already suggested15:06
asachehe15:06
kgunnasac: that's ok, it helps me to be told more than once :-P15:07
=== chihchunl is now known as chihchun
asaclol15:10
qenghokgunn: I wish the Lint tool warned about using deprecated environment variables.15:11
asackgunn: also hello-world.sh is neat... you end up in a shell inside the app sandbox, so you get a live feel what it means to live in a box :)15:11
* asac hopes kgunn learned at least something on top now :)15:11
mvokgunn: sorry, was in a meeting. I think the error you see is fixed in master but not yet in the distro, we want to sru this RSN but it is not done yet15:18
didrocks1ogra_: stupid questions, but where are the fresh vm images for ubuntu core series 16?15:19
=== cprov_ is now known as cprov
=== dragly_ is now known as dragly
=== clemensv__ is now known as clemensv
=== davidcalle_ is now known as davidcalle
=== Trevinho_ is now known as Trevinho
sergiusensjdstrand hey, I wrote an email to the list, mostly intended for you; maybe I am just too ignorant on many things I mention but wanted to get the ball rolling15:29
sergiusenskgunn I've been adding an app to my apps called "shell" with the same plugs as the ones I want to test15:30
didrocks1mvo: hey, do we have any equivalent of snappy list -u/-v ?15:32
mvodidrocks1: not yet, but please file a bug and we prioritize it15:33
=== didrocks1 is now known as didrocks
didrocksmvo: ok, I think it's the same for rollback and such, isn't it? (I remember there was a set-versions or whatsoever)15:34
mvodidrocks: yes15:35
didrocksricmm: that's going to make our script about rollback for FTF harder ^ :p15:36
didrocksmvo: bug #1577439 and bug #1577441 (trying to point the next important show we have in it, but I know the timeline is short)15:39
ubottubug 1577439 in Snappy "No more -u/-v options for "list"" [Undecided,New] https://launchpad.net/bugs/157743915:39
ubottubug 1577441 in Snappy "No way to rollback a snap since the move to snap command" [Undecided,New] https://launchpad.net/bugs/157744115:39
=== kissiel is now known as kissiel-afk
slvnjdstrand, the two bugs are https://bugs.launchpad.net/snapcraft/+bug/1575582 and https://bugs.launchpad.net/snapcraft/+bug/157733315:47
ubottuLaunchpad bug 1575582 in Snapcraft "Snap package, using SDL2, needs access to libGL.so and DRI dependencies" [Undecided,New]15:47
ubottuLaunchpad bug 1577333 in Snapcraft "snap-review failed with "checksums do not match"" [Undecided,New]15:47
=== pitti` is now known as pitti
=== pitti is now known as Guest25655
=== Guest25655 is now known as pitti
ogra_didrocks, onyl kvm currently (with the normal amd64 image) for vbox you would have to convert yourself ...15:54
didrocksogra_: do you have any link?15:58
didrocksI looked on cdimage, but only find the preinstalled file system15:58
didrocksno .img15:58
=== attente_ is now known as attente
ogra_didrocks, nothing beyond mvo's all-snaps dir, we still have no official 16.04 snappy alpha yet16:15
didrocksogra_: ok, that confirms it! Thanks :)16:15
zygare16:16
* zyga pushed a nice refactor branch https://github.com/ubuntu-core/snappy/pull/111417:27
zygamorphis: I'm done with my current track, I can now look at dbus and quoting what's required17:32
zygamorphis: anything else I can help you with?17:33
kyrofatyhicks, jdstrand https://code.launchpad.net/~kyrofa/ubuntu-core-launcher/create_user_common_data/+merge/293555 is ready for a look when you're able17:44
zygakyrofa: some of the error messages confuse allocating memory for filesystem operation failures17:50
zygaconfuse as in the error message might be confusing17:50
kyrofazyga, well remember it results in perror17:52
zyga+char *common_user_data = calloc(common_user_length, 1);17:52
zyga+if (common_user_data == NULL) {17:52
zyga+die("failed to create user common data directory");17:52
zyga+ }17:53
zygathat's clearly confusing IMHO17:53
zygathat's failed to allocate memory, not create anything17:53
kyrofazyga, the error message will actually say "failed to create user common data directory: out of memory" (or something similar)17:53
zygahmmm17:53
zygaI see17:53
kyrofazyga, I didn't want the message to say "unable to allocate memory: out of memory" :P17:53
ogra_needs to be prefixed with "success:"17:54
kyrofaHahaha17:54
* ogra_ sighs ... so it seems jdstrand made the german news with the ubuntu-core-launcher fix ...17:58
ogra_top story at heise.de today ... "another insecurity in snap packages"17:58
jdstrandthe joys of open source :)17:58
ogra_i wish i knew why they dislike us so much recently ...17:59
jdstrandhopefully they reported that it was discovered internally and fixed within a day of discovery17:59
ogra_nope17:59
ogra_wow, google translate makes it nearly unreadable ...18:01
ogra_https://translate.google.com/translate?sl=de&tl=en&js=y&prev=_t&hl=de&ie=UTF-8&u=http%3A%2F%2Fwww.heise.de%2Fnewsticker%2Fmeldung%2FErnste-Sicherheitsluecke-in-Ubuntus-neuem-Paketformat-Snap-geschlossen-3195532.html&edit-text=18:02
jdstrandheh18:04
jdstrandit was fairly even until the end. then there was an axe to gring18:04
jdstrandgrind18:04
ogra_Upon connection of mount points a clerical error resulted in the source code means that the launcher was placed with a correspondingly adapted package name to execute arbitrary code18:05
ogra_rrright18:05
jdstrandwell, I said even, not accurate :)18:07
ogra_heh18:07
jdstrandthey were pretty close18:07
ogra_yeah, the german sentence is fine there ...18:08
sergiusensjdstrand ok so I created #157751418:35
* sergiusens should probably reply to the ML as well18:36
=== Aria22 is now known as Aria22|away
=== Aria22|away is now known as Aria
=== Aria is now known as Aria22
=== Aria22 is now known as Aria
=== Aria is now known as Aria22
sergiusensjdstrand ok just to add to the bucket list I've expanded https://bugs.launchpad.net/snappy/+bugs?field.tag=snapd-interface by 418:57
* zyga soft-EODs19:11
jdstrandsergiusens: thanks19:36
jdstrandsergiusens: two of those are already fixed in trunk19:39
sergiusensjdstrand sounds good; just wanted to be torough19:40
jdstrandnp19:40
=== Aria22 is now known as Aria
=== Aria is now known as Aria22
=== peebles_ is now known as peebles
=== mjl_ is now known as mjl
=== kalikiana_ is now known as kalikiana
=== FourDollars_ is now known as FourDollars
=== rsalveti_ is now known as rsalveti
kgunnjdstrand: curious one, so i'm getting this denial https://pastebin.canonical.com/155642/ but i have "/run/udev/data/* r," in my slotAA20:34
sergiusenskgunn you might be hit by that snapd bug where you need to remove a snap before installing it again20:41
kgunnsergiusens: i am uninstalling my snap in between20:41
kgunnsnap remove mir-server20:41
kgunni installed with --devmode and it actually launched20:42
kgunnso now just trying to go through the aa/seccomp dance20:42
=== blr_ is now known as blr
paleriderwell, this looks popular...20:50
=== thibautr_ is now known as thibautr
sergiusenskgunn I don't know how to answer your problem except rinse and repeat20:53
kgunnright, sergiusens, i just thot that specifically having   "/run/udev/data/* r," in my slotAA would have taken care of the denials that appeared...20:54
kgunnalso i had that in my aa from the beginning20:55
kgunnso wasn't like i added it20:55
kgunnto suppress those20:55
=== Aria22 is now known as Aria22|away
=== Aria22|away is now known as Aria
=== Aria is now known as Aria22
jdstrandkgunn: that should be allowed by that rule. perhaps the slot didn't connect (ie, the policy isn't in the profile in /var/lib/snapd/apparmor/profiles/...)21:59
kgunnjdstrand: so i just grepped it22:02
kgunn/var/lib/snapd/apparmor/profiles/snap.mir-server.mir-server:246:  #   /run/udev/data/* r,22:02
kgunni presume the # is not a good sign22:02
jdstrandkgunn: no. there is a comment about it in the default policy. looks like your slot side didn't connect22:03
jdstrandfor your slot side udev apparmor rule22:03
jdstrand(ie, don't be confused be the comment-- your rules 'simply' didn't connect22:04
jdstrand)22:04
kgunnjdstrand: so what should i look at now?22:06
jdstrandkgunn: is the slot side configured to auto-connect?22:08
jdstrandI thihnk the bluez interface was set to autoconnect22:08
jdstrandlet me look22:08
kgunnjdstrand: no i'm not autoconnect22:08
jdstrandotherwise, you could snap remove mit and then install22:08
kgunn(i think)22:08
jdstrandno, bluez isn't22:11
kgunnjdstrand: but, just thinking about it... should mir be autoconnect?22:12
jdstrandwell, I'm not sure what the design is supposed to be here22:12
jdstrandI mean, to me it would make sense that the permanent slot policy would autoconnect22:13
jdstrandsince it is, well, permanent22:13
jdstrandkgunn: are you still using the trick I gave about putting it in the slot connection portion of the code or is it actually in the slot permanent part?22:14
jdstrandkgunn: regardless, to unblock yourself, you can look at built/opengl.go and set autoConnect: true in your NewMirInterface() which would hopefully unblock you until zyga is back22:15
kgunnjdstrand: right, so i'm actually permanent slot atm22:17
jdstrandkgunn: ok, that's good (in that that is what it should be)22:17
kgunnexactly22:17
jdstrandtry playing with autoConnect or moving it to connected slot and doing a manual connect to unblock yourself for the time being22:18
kgunnok np22:18
jdstrandbut we need zyga again22:18
kgunni mean i can run it with --devmode, so i'm really just wanting to work through doing it the "right way"22:18
kgunnthanks again :)22:18
* jdstrand nods22:19
jdstrandnp22:19
=== Aria22 is now known as Aria22|away
=== devil is now known as Guest7079
=== asac` is now known as asac
=== Aria22|away is now known as Aria
example6Hello everyone. I'm trying to make a _very_ basic snap consisting of nothing but a few shell scripts. I'm using just the 'copy' plugin to put everything in place, but it doesn't seem to be creating a .snap file OR moving any of the relevant files into snap/23:51
=== Aria is now known as Aria22

Generated by irclog2html.py 2.7 by Marius Gedminas - find it at mg.pov.lt!