[06:34] <didrocks> good morning
[06:39] <duflu> Good Thursday
[06:41] <jibel> Good morning
[06:42] <didrocks> salut jibel, hey duflu!
[06:42] <duflu> Hi jibel
[06:42] <duflu> So today is the day.... :)  http://cdimages.ubuntu.com/daily-live/current/
[07:15] <oSoMoN> good morning desktoppers
[07:21] <didrocks> hey oSoMoN
[07:22] <oSoMoN> salut didrocks
[07:22] <oSoMoN> ça va?
[07:23] <didrocks> ça va, le soleil est revenu ce matin
[07:23] <didrocks> et toi ?
[07:26] <oSoMoN> très bien, pas de rush pour aller à l’école ce matin, ma fille est partie en classe verte pour 3 jours, c’est étrangement calme (et il fait beau)!
[07:27] <didrocks> ah, en effet :)
[07:30] <seb128> good morning desktopers
[07:30] <didrocks> salut seb128
[07:37] <oSoMoN> salut seb128
[07:37] <seb128> lut didrocks oSoMoN, en forme ?
[07:37] <oSoMoN> oui, et toi?
[07:37] <seb128> nickel
[07:58] <willcooke> word
[08:01] <didrocks> hello
[08:01] <didrocks> bad FIFO implementation :)
[08:01] <Laney> ey up
[08:02] <didrocks> and broken keyboard for Laney :p
[08:02] <didrocks> or too much hairs under the "h"
[08:02] <Laney> nope
[08:02] <Laney> just teaching you the nottingham dialect
[08:02] <didrocks> this is like "how mouch?"
[08:03] <Laney> https://www.youtube.com/watch?v=NQTGkO5GjD8
[08:04] <didrocks> ok, remind me to never get there or I'll get lost and cry :)
[08:05] <Laney> :D
[08:05] <Laney> don't actually hear people talking like that very often sadly :(
[08:05] <didrocks> is it consider as slang or a local dialect?
[08:05] <didrocks> considered*
[08:05] <Laney> well I guess I mostly know people that aren't from here originally
[08:06] <Laney> not many of the local old people :P
[08:06] <seb128> good morning U.K
[08:06] <seb128> willcooke, Laney, how are you?
[08:06] <Laney> hmm, probably a dialect?
[08:06] <Laney> hey seb128
[08:06] <Laney> feeling GOOOOOOOOOOOOOOOOOOD
[08:06] <Laney> went to bed at 2230
[08:06] <Laney> what about you?
[08:06] <willcooke> alright me ducks?
[08:08] <Laney> wotcha geeza
[08:08] <seb128> I'm doing great
[08:08] <seb128> yesterday was tennis night!
[08:08] <didrocks> Laney: that's my daily routine to go to bed at that time now :)
[08:08] <seb128> it was quite windy and I'm out of shape, didn't play much during the winter between weather/us being sick in turn/weather
[08:08] <seb128> but it was still good fun :)
[08:09] <Laney> :>
[08:10] <seb128> same here, 2230 is our normal bed time now :/
[08:10] <willcooke> heh. Rock and roll in the channel today
[08:11]  * willcooke complains that his knees hurt
[08:11] <didrocks> for dancing Rock and roll? :)
[08:13] <duflu> Morning willcooke, Laney (I just saw words that didn't immediately translate, but they do aurally)
[08:19] <duflu> And morning seb128
[08:20] <seb128> hey duflu, how are you today?
[08:20] <duflu> and oSoMoN
[08:20] <Laney> greetings duflu
[08:20] <duflu> seb128, doing OK. I finished a rework of a mutter branch for the Gnome guys just now that I expected to take at least all day.
[08:20] <duflu> You?
[08:21] <Laney> couple of months ago one of the lights in the kitchen started making the fuse trip
[08:21] <seb128> nice
[08:21] <seb128> I'm good thanks
[08:21] <Laney> unscrewed it to have a look at the wiring
[08:21] <Laney> face and body covered in water /o\
[08:21] <seb128> urg
[08:21] <willcooke> oof
[08:21] <duflu> Presumably with electricity off
[08:21] <Laney> the push pipe fitting from the bath had come loose
[08:21] <Laney> yes
[08:29] <oSoMoN> hi duflu
[08:41] <Nafallo> o/
[08:50] <duflu> Hi Nafallo
[08:55] <Nafallo> duflu: hey! how's thing going with that annoying purple screen and mouse bug? :-)
[08:56] <duflu> Nafallo, I think I saw Laney land an upstream fix last night
[08:56] <Nafallo> oooh. nice :-)
[08:58] <Nafallo> just need to wait for packages to test then :-)
[08:59] <Nafallo> right. I need to go collect medicine and get the bus home. bbl.
[09:10] <seb128> Laney, Trevinho, you managed to land the gdm fix/refactoring for the refcount issue from what I see, well done! :)
[09:11] <Laney> thx
[09:12] <Trevinho> seb128: yeah... Who cherry picks it? I can do it later if you want or I just point the commits if in rush
[09:13] <Laney> don't worry about it, I can handle it
[09:14] <Laney> quite a lot of pings about this one...
[09:21] <seb128> thx Laney, sorry about the pings
[09:22] <Laney> no worries
[10:29] <Nafallo> willcooke: bug #1730765 still on your radar, right? :-)
[10:30] <willcooke> Nafallo, it'll get reviewed when we go through the cc list.  So once 18.04.1 is out the door, or thereabouts
[10:30] <willcooke> No promises though, we've already got a full schedule.
[10:31] <Nafallo> willcooke: hmm. I was hoping for 18.04.1 actually ;-)
[10:31] <willcooke> Worth seeing if anyone upstream and/or in the community wants to work on it.  I've zero clue about how much work it would be, but I think it's probably non-trivial
[10:33] <Nafallo> hmm. let me check the release schedule. I might be able to find time for working on it as long as I get some handholding from time to time.
[10:33] <willcooke> woot!
[10:34] <Nafallo> well, we need it for 18.04.1 I think :-)
[10:34] <Nafallo> would make sense to get time allocated.
[10:35] <Nafallo> wow. 18.04.1 week 30 and 16.04.5 week 31 :-P
[12:08] <didrocks> There is some work being done on it upstream
[12:08] <didrocks> I don't think it's realistic for 18.04.1
[12:08] <didrocks> Nafallo: sounds like you volunteer to help them? :)
[12:09] <didrocks> as you feel that's crucial (knowing that we didn't huge feedback about the necessity on 17.10…)
[12:10] <didrocks> Nafallo: willcooke: https://github.com/micheleg/dash-to-dock/pull/677 FYI. Note that we need some nautilus API as well, this is why I pointed them to talk to upstream about it
[12:10] <ubot5-ng> micheleg bug (Pull request) 677 in dash-to-dock "Trash and Removable Device Icons" (comments: 12) [Open]
[12:11] <Nafallo> didrocks: as soon as I can land my new role, I've already negotiated doing upstream work :-)
[12:11] <didrocks> nice!
[12:12] <Nafallo> Laney: should be fine running the cosmic proposed builds on bionic still, right? :-)
[12:26] <Nafallo> didrocks: I like that the patches Philip did takes the trash can into consideration as well. I've got a separate extension for that at the moment :-P
[12:32]  * didrocks really never use the trash that much…
[12:32] <didrocks> remember that dnd isn't supported
[12:32] <didrocks> though
[12:36] <Nafallo> didrocks: yeah, me neither. no idea if my users do either :-)
[13:04] <oSoMoN> Laney, the chromium-browser autopkgtest run for armhf appears to be stuck (http://autopkgtest.ubuntu.com/running#pkg-chromium-browser , been running for >5hrs), is there a way to cancel and re-run?
[13:09] <Laney> oSoMoN: all I can do is kill the process, no user facing way
[13:10] <Laney> it will time out eventually
[13:10] <Laney> and the container is still running fine, smells like the test itself has hung to me
[13:11] <Laney> Nafallo: dunno, sounds like you get to keep both halves if it breaks
[13:12] <Nafallo> Laney: :-D
[13:12] <Nafallo> Laney: I'll try it out in a bit.
[13:12] <Laney> if it were me I'd build the package myself
[13:13]  * Nafallo notice Laney is trying to get him to write an ansible role for setting up a schroot environment ;-)
[13:14]  * Laney sounds the sysadmin siren and runs away
[13:14] <Nafallo> awesome... lastpass-cli just became completely unusable because Lastpass changed certificate and upstream of the client requires new upstream versions for that... :-(
[13:16] <Nafallo> ehrm. upstream is Lastpass themselves...
[13:16] <Nafallo> gah
[13:25] <andyrock> good morning all!
[13:26] <Nafallo> morning andyrock :-)
[13:26] <willcooke> hey andyrock
[13:30] <oSoMoN> Laney, ack, thanks
[13:31] <oSoMoN> too much load on my machine, it almost grinded to a halt, I hoped to restore it by jumping to a tty and killing a few processes, but even that was too much, had to do a hard reboot :/
[13:35] <didrocks> hey andyrock
[13:40] <kenvandine> didrocks, any idea why i can't request a review from oSoMoN for the helpers?
[13:42] <didrocks> kenvandine: good question, there is no special team or anything, maybe he needs to start a first review to get in the review list then?
[13:43] <oSoMoN> I just went through every possible setting at https://github.com/settings/, and nothing appears to be explicitly disallowing review assignment
[13:44] <oSoMoN> I already reviewed some of Ken's changes
[13:44] <didrocks> as part of the team?
[13:44] <didrocks> well, org group member?
[13:45] <seb128> hey andyrock
[13:45] <didrocks> oh
[13:45] <didrocks> I know I think
[13:45] <didrocks> you are in private mode
[13:45] <didrocks> let me see if I can switch you to public
[13:45] <didrocks> oh no, you are public…
[13:46] <didrocks> let me grand you explicitely access to that repo
[13:47] <didrocks> oSoMoN: you probably received an email
[13:48] <oSoMoN> didrocks, yep, and I accepted the invitation
[13:48] <oSoMoN> github says "You now have push access to the ubuntu/snapcraft-desktop-helpers repository."
[13:48] <oSoMoN> kenvandine, can you assign me a review now?
[13:48] <didrocks> and you are on the list!
[13:48] <didrocks> oSoMoN: you couldn't push before, just being part of the org?
[13:48] <oSoMoN> didrocks, dunno, I didn't try in that timeframe
[13:49] <didrocks> maybe it's better to add directly people to repos thus…
[13:49] <oSoMoN> I was added to the org yesterday or the day before, can't remember exactly
[13:49] <didrocks> I thought I added you to the org last week
[13:52] <oSoMoN> it could be last week, my memory is failing me
[13:53] <oSoMoN> according to my inbox, it was the 14th
[13:53] <oSoMoN> so neither yesterday, nor the day before, nor last week :)
[13:55] <didrocks> we were both wrong!
[13:56] <didrocks> what, it's not Friday? Felt already like a week :p
[13:57] <oSoMoN> you wish :)
[14:03] <kenvandine> oSoMoN, yes
[14:03] <kenvandine> oSoMoN, what did you do?
[14:04] <didrocks> I added him to the repo explicitely
[14:04] <kenvandine> ah
[14:04] <kenvandine> ok
[14:04] <kenvandine> thx
[14:05] <didrocks> yw
[14:07] <andyrock> seb128: livepatch guys say we just need to check if we're in a LTS or not
[14:08] <andyrock> seb128: in order to understand if we need to show the UI or not
[14:09] <didrocks> andyrock: what's their answer to people installing the snap on non LTS?
[14:09] <seb128> what didrocks said
[14:09] <didrocks> confusing for them to install non working services…
[14:10] <andyrock> didrocks: well if you install it you still need to enable it
[14:10] <andyrock> once you enable it you get an error message
[14:11] <didrocks> still seems unnice while we have an existing mecanism to prevent this
[14:11] <didrocks> any reason for them to not use per-release track?
[14:12] <andyrock> but the per-release track will not prevent people to install the snap
[14:13] <didrocks> I don't know if it's only a naming convention or something backed in into snapd, would need to reach out the snapd people
[14:13] <didrocks> at least, it would give you a clear hint that's purposed for one release
[14:14] <seb128> andyrock, checking if we are on a LTS is probably going to give us the right user experience, but yeah it would be nice if they handled that better...
[14:15] <seb128> we should still communicate that to them
[14:15] <seb128> but I think it's fine to do the lts check meanwhile on our side
[14:15] <andyrock> the question is how we do the lts check? 😂
[14:16] <andyrock> seb128: python has some nice libraries to do that
[14:16] <seb128> what is the livepatch snap doing?
[14:16] <seb128> can you see their code?
[14:16] <andyrock> they're checking the kernel
[14:16] <seb128> you mean?
[14:17] <andyrock> the kernel version
[14:17] <seb128> shouldn't we do the same thing then?
[14:17] <seb128> but do they have a mapping table?
[14:17] <seb128> or do they ask the server if it's supported?
[14:17] <andyrock> let me check
[14:18] <seb128> andyrock, otherwise you could parse /etc/os-release and see if VERSION contains "LTS"
[14:18] <andyrock> I would go with the /etc/os-release thing
[14:18] <seb128> or use the ID and see if it's an <even number>.04
[14:18]  * didrocks would think "LTS" is safer
[14:18] <andyrock> it feels less likely to change in the future
[14:19] <didrocks> btw, with .1 .2 release, do anyone of you know if the ID change as well?
[14:19]  * didrocks was wondering that for ubuntu-report
[14:19] <didrocks> (VERSION_ID)
[14:19] <kenvandine> willcooke, seb128: oSoMoN and I are talking about how important is it to build chromium snaps for armhf/arm64
[14:20] <kenvandine> thoughts?
[14:20] <seb128> not?
[14:20] <kenvandine> since we don't have arm desktop images
[14:20] <kenvandine> doesn't seem useful
[14:20] <seb128> didrocks,
[14:20] <seb128> VERSION="16.04.4 LTS (Xenial Xerus)"
[14:20] <seb128> VERSION_ID="16.04"
[14:20] <seb128> seems not
[14:20] <didrocks> seb128: thx for confirming :)
[14:20] <seb128> np!
[14:20] <oSoMoN> not sure if there's a way of getting snap usage statistics per architecture?
[14:21] <didrocks> and for having old vm/install around ;)
[14:21] <willcooke> kenvandine, ah - flavours do have, e.g. mate - but not sure if that means we are obliged or not.
[14:21] <seb128> :)
[14:22] <seb128> willcooke, do they care enough to contribute some work to help with it?
[14:22] <seb128> I would say it depends of the cost
[14:22] <seb128> but it's not trivial and just to help a flavor so I think it's fair to ask for shared cost
[14:22] <oSoMoN> the problem is not so much an extra maintenance cost (armhf is unsupported upstream so it requires a patch to keep building every now and then, but it's not too bad), but rather that it takes forever to build chromium on arm (typically more than 20 hours)
[14:24] <willcooke> oSoMoN, what's the knock on effect of slow building?  Like, can you kick it off and just leave it until its done?
[14:24] <willcooke> or do you need to keep checking back on it
[14:27] <oSoMoN> willcooke, yeah, I can totally kick it off and wait for it to be done, it's just very asynchronous
[14:27] <willcooke> oSoMoN, My 0.02USD, if it's not a big burden to keep it building, it will be useful to people, but when that changes I think we reconsider
[14:27] <oSoMoN> it's not even something that I can kick off before going to bed and expect to have it done when I wake up, so it makes for very slow iterations, but I can live with it
[14:28] <willcooke> oSoMoN, now, if we can get the snap building, then we can get an idea of user numbers
[14:28] <willcooke> and then that makes a case for or against pretty easy
[14:28] <oSoMoN> willcooke, do we get snap stats per architecture?
[14:28] <willcooke> oh
[14:28] <willcooke> hm
[14:28] <willcooke> I just assumed we did
[14:29] <willcooke> upload it as a new snap if not ;)
[14:29] <oSoMoN> I couldn't figure out how to extract that info from the dashboard, but maybe there's a way
[14:29] <didrocks> you can: https://dashboard.snapcraft.io/docs/api/snap.html#fetch-metrics-for-snaps
[14:29] <didrocks> but you have to poke the API manually
[14:30] <oSoMoN> aha
[14:30] <didrocks> and you need to request per arch
[14:30] <oSoMoN> perfect, thanks didrocks
[14:32] <didrocks> oSoMoN: hold on, actually, I'm unsure, as I thought you can filter by revision, and getting the revision from another API call…
[14:32] <didrocks> (for each arch)
[14:32] <kenvandine> Laney, i have a question about seeded snaps in my desktop-preinstalled image
[14:32] <didrocks> but it seems it doesn't return the revision :/
[14:32] <didrocks> (on the metrics filter)
[14:33] <kenvandine> Laney, the snaps are in /var/lib/snapd/seed/snaps/
[14:33] <kenvandine> but snap list doesn't show them as installed
[14:33] <Laney> do you get the seed.yaml?
[14:33] <Laney> livecd-rootfs makes that
[14:33] <kenvandine> yes
[14:33] <kenvandine> and it has them
[14:33] <Laney> then snapd is supposed to do a thing to install them
[14:33] <Laney> on the first boot
[14:34] <didrocks> oSoMoN: the only way would be to hardcode to arch in the "Version" field from what I see :/
[14:34] <kenvandine> http://paste.ubuntu.com/p/NN4Ph3hhr5/
[14:34] <kenvandine> Laney, snapd is running :(
[14:34] <kenvandine> nothing in /snap
[14:35] <Laney> I don't know how that part is supposed to work, sorry
[14:35] <Laney> try #snappy ?
[14:35] <kenvandine> Laney, no worries
[14:35] <kenvandine> will do
[14:36] <Laney> as far as I was concerned our job ended at writing seed.yaml, snapd is supposed to arrange for that to work
[14:38] <kenvandine> oh... snapd.seeded service was still marked as "starting"
[14:38] <kenvandine> since yesterday
[14:53] <Laney> /o\
[15:06] <Nafallo> Laney: followed your advice and built them in an lxd guest. debs for amd64 if someone needs to test on bionic is at http://people.ubuntu.com/~nafallo/gdm3/
[15:11] <Laney> phat
[15:44] <Trevinho> Laney: as per reading the email / telegram, it might be already too late, but to get better gdm development experience, and want to run it from jhbuild, I can help...
[15:45] <Laney> oh yeah, show me IRL?
[15:45] <Laney> I was using a testing laptop and making debs
[15:45] <Laney> or ... write a wiki page :-o
[15:45] <Trevinho> Laney: I generally do such things in a VM (things which supprot mesa drivers, as vmware or maybe kvm are better)
[15:46] <Trevinho> but yeah... I wanted to write down something
[15:47] <Laney> nice
[15:47] <Trevinho> anyway the basic trick is just create an alternative .service file, stripped of the pre/post-exec and the dbusbusname
[15:47] <Trevinho> then setting the exect to a script that sets proper PATH, LD_LIBRARY_PATH and GI_TYPELIB_PATH and runs the actual gdm... Then you've to symlink something too
[15:48] <Laney> haha
[15:48] <Laney> easy!
[15:48] <Trevinho> but that's mostly for xorg stuff as you might not want to run it from your jhbuild (i did, but still)...
[15:48] <Trevinho> well it's quite easy, just need to check a bit the logs for erros, but eventually it works (once you use upstream gdm with my patches)
[15:48] <Laney> I never even ran the shell from jhbuild
[15:49] <Trevinho> noooo?!
[15:49] <Trevinho> How can you!
[15:49] <Laney> symlink the binaries to /usr/bin
[15:49] <Trevinho> -_-
[15:49] <Trevinho> you can also run funny stuff such as `jhbuild run gdb gnome-shell -batch -ex "set logging on" -ex "run --replace" -ex "bt full" -ex "call gjs_dumpstack()"   -ex quit
[15:49] <Trevinho> `
[15:50] <Trevinho> which bsicallty gives you the traces (gjs and c) when it crashes
[16:23]  * oSoMoN is done for today, have a good evening
[17:50] <willcooke> night
[18:15] <ricotz> chrisccoulson, please push your packaging branches!