[03:56] <murthy> how to know the details of a .snap file?
[05:54] <mborzecki> morning
[06:49] <zyga> good morning
[06:49] <zyga> I need to figure out how to wake up at 6 and start the work at 7
[06:49] <zyga> kids leaving at all random moments is not helping
[06:49] <zyga> murthy: hello
[06:49] <zyga> murthy: can you please be more specific, what is it that you would like to know?
[06:50] <murthy> zyga: https://www.phoronix.com/scan.php?page=news_item&px=Ubuntu-Snaps-Chromium-VA-API
[06:51] <murthy> zyga: cant wait till it gets published..
[06:51] <murthy> zyga: I have downloaded the .snap file from launchpad website
[06:51] <murthy> zyga: I would like to run the snap file
[06:51] <murthy> zyga: good morning btw
[06:52] <zyga> murthy: do this please:
[06:52] <zyga> murthy: on a system with snapd installed
[06:52] <murthy> zyga: I just saw a video and it spoiled my day already
[06:53] <murthy> I am on ubuntu 18.10
[06:53] <zyga> run "snap install chromium --channel=candidate/vaapi"
[06:53] <murthy> zyga: so snap search wont display from candidate?
[06:53] <zyga> this will install the snap from a given "channel", like a lane of development
[06:53] <zyga> murthy: that's correct AFAIK
[06:54] <murthy> zyga: ok, I knew about channels, but didn't know search is not done on candidate, let me try that
[06:54] <murthy> zyga: full confinment means sandboxed?
[06:54] <zyga> yes
[06:56] <mborzecki> zyga: hey
[06:56] <murthy> zyga: it says it cant find that package. shall I do sudo snap install --candidate chromium-snap-from-source-enable-vaapi   ?
[06:56] <murthy> zyga: https://code.launchpad.net/~osomon/+snap/chromium-snap-from-source-enable-vaapi?_ga=2.8470321.583249682.1548065371-1544747127.1545400671
[06:57] <zyga> no no
[06:57] <zyga> try --channel="..."
[06:57] <zyga> full name there
[06:59] <murthy> zyga: can you check the above link and tell me the exact full command
[07:00] <murthy> I am yet to learn stuff about snap
[07:00] <zyga> sure, just hold on
[07:00] <zyga> doing a few things in parallel here
[07:00] <murthy> zyga: sure no problem
[07:03] <mborzecki> murthy: i just installed chromium using
[07:04] <mborzecki> snap install --channel=candidate/vaapi chromium
[07:04] <mborzecki> murthy: what error are you getting exactly?
[07:05] <murthy> mborzecki: Its installing now
[07:06] <murthy> mborzecki: I tried the following earlier as suggested by zyga "snap install chromium --channel=candidate/vaapi"
[07:07] <murthy> mborzecki: That gave me an error of some thing not found
[07:08] <mborzecki> murthy: what was not found?
[07:08] <zyga> paste the error you got
[07:08] <zyga> that helps
[07:13] <mborzecki> zyga: btw. connecting interfaces for chromium takes a longer while, iirc we had a pr that would bundle all apparmor updates to one, did it land?
[07:13] <murthy> zyga: I think I mistyped
[07:14] <murthy> mborzecki: hardware acceleration works for you with chromium?
[07:15] <mborzecki> murthy: where can i test it?
[07:17] <murthy> with what you installed just now and goto youtube, search for a 4k video and play it in 4k'
[07:18] <murthy> mborzecki: then type  in the address bar "chrome://media-internals"
[07:19] <murthy> mborzecki: you should see some thing like this "blob:https://....."
[07:19] <mborzecki> murthy: mhm, it's there
[07:20] <murthy> mborzecki: click that and then tell me what do you see as value for "video_decoder"
[07:20] <mborzecki> murthy: VpxVideoDecoder
[07:21] <murthy> mborzecki: that means no hardware acceleration
[07:22] <mborzecki> maybe it's somethign about amdgpu & vaapi then
[07:22] <zyga> re
[07:22] <murthy> mborzecki: goto "chrome://gpu/"
[07:22] <murthy> mborzecki: see whats in for video decode
[07:23] <mborzecki> murthy: heh, hardware accelerated
[07:23] <mborzecki> wonder if that covers vp9 too
[07:23] <murthy> brb
[07:26] <zyga> good morning mvo
[07:42] <zyga> mvo_: so, we have a +1 from mwhudson but we must remove transitional packages as they would get axed through NEW
[07:45] <zyga> I'll do that now
[08:00] <mvo_> zyga: hi
[08:00] <mvo_> zyga: sorry wwas not registered earlier
[08:14] <r3r57> Hello, I've got http://paste.debian.net/1062047/ with several snaps (chromium, etc.). Does anyone know if this is a distribution related issue or an issue with the snap itself? Thank you in advance.
[08:21] <murthy> mborzecki: I think It specifically means hardware acceleration of vp9
[08:29] <murthy> Are the intel's latest drivers packaged with the chromium browser or the drivers are synced from 16.04?
[08:30] <mborzecki> murthy: chromium seems to be based on core18, so it's at least the version that shipped with 18.04
[08:34] <murthy> Hardware acceleration is not working for me. I even tried after enabling overide gpu blacklist flag, no good.
[08:37] <mup> PR snapcraft#2440 closed: meta: make hooks executable instead of complaining they're not <Created by Saviq> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/2440>
[08:37] <mup> PR snapcraft#2441 closed: legacy/meta: make hooks executable instead of complaining they're not <Created by Saviq> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/2441>
[08:38] <murthy> bbl
[09:07] <Chipaca> moin moin
[09:07] <mup> PR snapcraft#2447 opened: build providers: remove SIGUSR1 signal ignore workaround for multipass <Created by sergiusens> <https://github.com/snapcore/snapcraft/pull/2447>
[09:13] <mup> PR snapd#6396 closed: packaging: import debian salsa packaging work and use in spead <Created by mvo5> <Closed by mvo5> <https://github.com/snapcore/snapd/pull/6396>
[09:15] <mup> PR snapd#6413 opened: packaging: import debian salsa packaging work and use in spead <Created by mvo5> <https://github.com/snapcore/snapd/pull/6413>
[09:16] <zyga> hello Chipaca :)
[09:26] <pedronis> mborzecki: hi,  the maybe my forum post was confusing but the plan is really to change behavior only if there's pinned tracked for the moment, so it cannot be done in the client. Later we will have default tracks but that is something the store will report for snaps. Either way is not about the "current" track
[09:27] <mborzecki> pedronis: quick HO?
[09:27] <pedronis> mborzecki: can do, one sec
[09:29] <pedronis> mborzecki: I'm in the standup
[09:34] <Chipaca> mborzecki: thank you for the review
[09:57] <mborzecki> Chipaca: yw, hopefully haven't missed anything when iterating over this on paper :)
[09:57] <Chipaca> mborzecki: on... paper?
[09:57] <Chipaca> pedronis: welcome back
[09:58] <mborzecki> Chipaca: making sure the counts add up
[09:58] <Chipaca> ah
[09:59] <pedronis> Chipaca: hi
[10:00] <Chipaca> pedronis: I was wondering if I should delve into a further refactoring of cmd_info, or if I should wait for a review from you today
[10:07] <pedronis> Chipaca: you are talking about #6389?
[10:07] <mup> PR #6389: cmd/snap: small refactor of cmd_info's channel handling <Created by chipaca> <https://github.com/snapcore/snapd/pull/6389>
[10:07] <Chipaca> pedronis: the review I'd ask for is the epochs one, if I could only ask for one :-)
[10:08] <Chipaca> I mean, yes 6389 needs a review, and I tagged you for it, but #6356 is the roadmap item
[10:08] <mup> PR #6356: overlord/snapstate: during refresh, re-refresh on epoch bump <Created by chipaca> <https://github.com/snapcore/snapd/pull/6356>
[10:12] <zyga> hey pedronis :)
[10:12] <pedronis> Chipaca: ah
[10:21] <mup> PR snapd#6414 opened: daemon: try to tidy up the icon stuff a little <Created by chipaca> <https://github.com/snapcore/snapd/pull/6414>
[10:22] <Chipaca> pedronis: fwiw 6389 doesn't _need_ a review from you, but you had Opinions :-)
[10:24] <cjwatson> sergiusens: Is there a plan to SRU snapcraft 3.x?  (Re improved core18 support, sort of)
[10:24] <cjwatson> sergiusens: Or indeed to have it as a .deb in Ubuntu at all
[10:27] <sergiusens> cjwatson: no, we have no plans to SRU 3.x as a deb. There is a plan to SRU a 2.44 as a deb with bug fixes but that does not have the proper support for bases
[10:27] <cjwatson> sergiusens: OK, so we should be looking at automatically defaulting snapcraft to the stable channel at least for core18
[10:28] <cjwatson> sergiusens: Weren't you going to do a systematic build comparison to test safety of switching to the stable channel by default across the board?
[10:28] <sergiusens> my proposal sent over email was to keep using the deb when not using a base and to switch to the snap when using a base so no one would break
[10:29] <cjwatson> I must have missed that, since I just reinvented the same idea independently :)
[10:30] <cjwatson> I think that's reasonable; the other thing we need to do in LP is to map bases to series and automatically dispatch the right one
[10:43] <cjwatson> sergiusens: https://bugs.launchpad.net/launchpad/+bug/1812985 FWIW
[10:43] <mup> Bug #1812985: Support snapcraft base snaps <feature> <lp-snappy> <Launchpad itself:Triaged> <https://launchpad.net/bugs/1812985>
[10:54] <dot-tobias> I have a question re: interface hooks, happy for any pointers: https://forum.snapcraft.io/t/apparmor-denial-in-interface-hook/9625
[11:05] <Chipaca> zyga: do I remember right that we had a bug where hooks wouldn't always get the right interface connections?
[11:05] <zyga> Chipaca: yes
[11:05] <zyga> I saw that question
[11:05] <Chipaca> zyga: do you remember when we fixed it?
[11:05] <zyga> I think that's fixed in 2.37 but not sure
[11:05] <zyga> recently
[11:06] <Chipaca> zyga: this was only about inheritance, ie it could be worked around?
[11:06] <zyga> Chipaca: I don't remember
[11:06] <zyga> today the focus is on some other topics
[11:06] <Chipaca> zyga: 🐀
[11:10] <Chipaca> dot-tobias: I'm going afk for a while, but meanwhile you could try 2.37 in case the issue is fixed there
[11:10] <Chipaca> dot-tobias: it's already in candidate :-)
[11:11] <dot-tobias> Chipaca: Thanks, will do! Answering to your forum reply just now.
[11:11] <Chipaca> yeah, please do, at least for posterity
[11:11] <Chipaca> :-)
[11:11]  * Chipaca ⇝ physio or 'the gym'
[11:38] <ackk> hi, I'm having this weird issue (not the first time I hit it): https://paste.ubuntu.com/p/9Bz2YjhDkG/
[11:38] <ackk> the snap is devmode,try if it matters
[11:39] <ackk> anyone has a suggestion on how to debug it ?
[11:39] <popey> ackk: what does "snap version" say?
[11:40] <ackk> popey, https://paste.ubuntu.com/p/DDtKbbhpvB/
[11:41] <popey> is that a snap that's in the store?
[11:41] <popey> snappy-debug.security scanlog
[11:41] <popey> run that in a terminal, do you get output while running the snap?
[11:41] <ackk> popey, not really, it's a local build
[11:42] <ackk> installing snappy-debug
[11:42] <ackk> popey, do I run it as root?
[11:42] <popey> why do you need to?
[11:43] <popey> oh, misread, sorry. No.
[11:43] <popey> :)
[11:43] <ackk> popey, https://paste.ubuntu.com/p/sNMfxptp68/
[11:43] <popey> is this a core device?
[11:44] <ackk> no, a bionic LXD container
[11:44] <popey> ok, do you get any output when running your snap?
[11:44] <ackk> popey, it was working earlier, I just updated some files in the prime/ dir (as said it's a snap try)
[11:46] <ackk> popey, other snaps work fine fwiw
[11:47] <popey> perhaps strace it to see what its failing on?
[11:47] <ackk> $ snap run --strace maas
[11:47] <ackk> error: exit status 1
[11:48] <popey> wtf
[11:50] <popey> can you wormhole me the snap so i can take a look?
[11:50] <popey> or the yaml
[11:50] <ackk> popey, I can tarball the prime dir, not sure if you'll have the issue though
[11:51] <popey> I'd rather have the snap or yaml
[11:51] <popey> nothing in dmesg?
[11:51] <ackk> popey, you mean the snap.yaml or the snapcraft.yaml ?
[11:52] <popey> snapcraft.yaml
[11:53] <ackk> popey, https://git.launchpad.net/maas/tree/snap/snapcraft.yaml
[11:53] <popey> you said this works in devmode?
[11:54] <ackk> yeah, it only works in --devmode
[11:54] <ackk> popey, nothing in dmesg except the usal apparmor messages, but no error that I can see
[11:57] <popey> are you building this in 18.04?
[11:57] <ackk> yes
[11:57] <popey> with the snapcraft snap
[11:58] <ackk> no, with the bionic snapcraft deb
[11:58] <popey> ah
[11:58] <popey> you should probably move to using the snapcraft snap
[11:58] <popey> the deb is ye olde and crusty
[12:01] <ackk> yeah, I'll take a look at that then
[12:01] <ackk> I'll also try to reinstall the snap, that usually works
[12:01] <ackk> popey, thanks
[12:12] <mup> PR snapd#6415 opened: snapstate, snap: allow update/switch requests with risk only channel to DTRT <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/6415>
[12:12] <mborzecki> pedronis: the change is fairly confined ^^
[12:58] <Chipaca> mborzecki: the move from "stable means latest/stable" to "stable means <current>/stable" is not minor, and will break / surprise people that have learned the old behaviour
[13:01] <mborzecki> Chipaca: yeah, went over it with pedronis, the PR is limited only to cover pinned (kerne & gadget) tracks only
[13:02] <Chipaca> mborzecki: ah :-)
[13:02] <mborzecki> Chipaca: while at it, could you take a look at #6415?
[13:02] <mup> PR #6415: snapstate, snap: allow update/switch requests with risk only channel to DTRT <Created by bboozzoo> <https://github.com/snapcore/snapd/pull/6415>
[13:02] <Chipaca> mborzecki: me? review stuff? madness
[13:02]  * Chipaca reviews while his food cooks
[13:03] <mborzecki> Chipaca: thanks
[13:03] <mborzecki> off to pick up the kids
[13:04] <Chipaca> hmmmm
[13:05]  * Chipaca IRL hmms
[13:45] <mup> PR snapd#5822 closed: wrappers: allow user mode systemd daemons <Created by jhenstridge> <Closed by pedronis> <https://github.com/snapcore/snapd/pull/5822>
[13:46] <pedronis> Chipaca: did you have a chance to look again at 6034 ?
[13:46] <pedronis> should we close it until you do?
[13:46] <Chipaca> pedronis: I was going to and then I doubted myself so I stopped
[13:47] <Chipaca> pedronis: probably need a refresher of what needs changing, as all I remembered was "make it clearer that it's only per-snap not per-revision"
[13:47] <pedronis> Chipaca: no new tasks as well (if possible)
[13:47] <Chipaca> ah, forgot about that. I'll look now after the standup.
[13:47] <Chipaca> thank you
[13:48] <pedronis> Chipaca: also think what we would do if we grew per revision stuff like thus
[13:50] <Chipaca> pedronis: and add a note about it?
[13:50] <pedronis> Chipaca: yes
[13:51] <Chipaca> pedronis: one thing I wondered was whether this and sequence aren't the same thing
[13:51] <pedronis> Chipaca: this?  you mean that?
[13:51] <pedronis> this is about per-snap
[13:52] <Chipaca> pedronis: but sequence is per revision, so that's that half of it
[13:52] <Chipaca> :)
[13:52] <Chipaca> pedronis: I mean SnapSeqDir
[13:52] <Chipaca> yeh
[13:53] <Chipaca> it's a weird thing :)
[13:53] <pedronis> I forgot about that
[13:54] <pedronis> Chipaca: it's used only for rollback in the new core18 bootstrap support, no?
[13:54] <Chipaca> pedronis: I mean, snap seq dir, is essentially a cache of per-revision side info
[13:55] <Chipaca> except each json has the whole sequence of sideinfos
[13:56] <Chipaca> e.g. https://pastebin.ubuntu.com/p/pnRbYThvHp/
[13:56] <Chipaca> that's probably more  than is needed for that feature
[13:56] <Chipaca> anyway. Standup coming up.
[14:40] <cjwatson> sergiusens: quick question for you in https://bugs.launchpad.net/launchpad/+bug/1812985, since I see you aren't subscribed to it
[14:41] <mup> Bug #1812985: Support snapcraft base snaps <feature> <lp-snappy> <Launchpad itself:Triaged> <https://launchpad.net/bugs/1812985>
[14:44] <mup> PR snapcraft#2447 closed: build providers: remove SIGUSR1 signal ignore workaround for multipass <Created by sergiusens> <Merged by sergiusens> <https://github.com/snapcore/snapcraft/pull/2447>
[15:02] <zyga> I'll do something about the room, it's too cold here
[15:14] <mup> PR snapcraft#2448 opened: Swap yaml schema document with json equivalent <Created by diddledan> <https://github.com/snapcore/snapcraft/pull/2448>
[15:16]  * zyga -> lunch
[15:37] <mup> PR snapd#6416 opened: snap: really run the RunSuite <Simple 😃> <Created by mvo5> <https://github.com/snapcore/snapd/pull/6416>
[15:39] <diddledan> I love commit messages like that
[15:40] <diddledan> other messages that are fun are "fix the tests so they don't fail"
[15:41] <cwayne> Best ones are "I don't know what this does"
[15:41] <diddledan> there totally needs to be a way to test testsuites without the program you're testing because without being sure your test suite is sane you can't be sure that the problem is in your project or the project's tests
[15:42] <diddledan> "I have no idea what these changes are.. I made them ages ago and didn't commit them. they must be important or I wouldn't have left them in the source"
[15:43]  * diddledan reboobs to Winders
[16:22] <mup> PR snapd#6417 opened: snap: fix reexec from the snapd snap for classic snaps <Created by mvo5> <https://github.com/snapcore/snapd/pull/6417>
[16:36] <mup> PR snapd#6418 opened: many: allow core as a fallback for core16  <Created by mvo5> <https://github.com/snapcore/snapd/pull/6418>
[16:38] <sergiusens> \o/
[16:38] <sergiusens> mvo: 🧐 🎆
[16:39] <mvo> sergiusens: :)
[16:40] <mvo> sergiusens: I had hoped you would like it
[16:54] <Chipaca> I'm going to EOD in a few minutes; a little early, and I might be back later tonight. Need to say goodbye to a friend.
[17:37] <sergiusens> Chipaca: good bye!
[17:37]  * sergiusens assumes that _a_ friend could be _any_ friend
[19:06] <sergiusens> mvo: I took a quick glance at the PR, this does not solve `snap install core16` installing `core`, correct?
[19:12] <mvo> sergiusens: if you "snap install core16" you still get that, that seems to be ok, no?
[21:00] <mup> PR pc-amd64-gadget#10 closed: Add mmx64.efi (MokManager) to support mokutil <Created by tsunghanliu> <https://github.com/snapcore/pc-amd64-gadget/pull/10>
[21:00] <mup> PR pc-amd64-gadget#11 closed: Add mmx64.efi (MokManager) to support mokutil <Created by tsunghanliu> <https://github.com/snapcore/pc-amd64-gadget/pull/11>
[21:01] <mup> PR pc-amd64-gadget#10 opened: Add mmx64.efi (MokManager) to support mokutil <Created by tsunghanliu> <https://github.com/snapcore/pc-amd64-gadget/pull/10>
[21:01] <mup> PR pc-amd64-gadget#11 opened: Add mmx64.efi (MokManager) to support mokutil <Created by tsunghanliu> <https://github.com/snapcore/pc-amd64-gadget/pull/11>
[22:23] <SlidingHorn> anyone else having an issue with the icon in Discord missing within the past few days or so?
[22:23] <SlidingHorn> (snap version, obviously)
[22:45] <mup> PR snapd#6419 opened: miscellaneous policy updates <Created by jdstrand> <https://github.com/snapcore/snapd/pull/6419>
[22:50] <mup> PR snapd#6420 opened: miscellaneous policy updates - 2.37 <Created by jdstrand> <https://github.com/snapcore/snapd/pull/6420>
[22:50] <mwhudson> um i wonder what happened here https://launchpadlibrarian.net/407843985/buildlog_snap_ubuntu_xenial_amd64_go110_BUILDING.txt.gz
[22:57] <mwhudson> does snapcraft.BasePlugin.run invoke things via sh?
[22:57] <mwhudson>         self.run(['./make.bash'], cwd=os.path.join(self.builddir, 'src'), env=env)
[22:57] <mwhudson> is failing with
[22:58] <mwhudson> /bin/sh: 24: exec: ./make.bash: not found
[22:58] <mwhudson> ./make.bash
[22:58] <mwhudson> Failed to run './make.bash' for 'built': Exited with code 127.
[22:58] <mwhudson> this worked yesterday :)
[23:01] <mwhudson> same snapcraft version