[05:29] <jibel> morning everyone
[07:12] <didrocks> good morning
[07:19] <oSoMoN> good morning desktoppers
[07:19] <oSoMoN> salut didrocks
[07:45] <didrocks> salut oSoMoN
[07:55] <jibel> fidencio, Hey, could you send me your preseed again? The paste expired
[08:09] <seb128> gooood morning desktopers!
[08:33] <didrocks> salut seb128
[08:36] <seb128> lut didrocks, comment va aujourd'hui ?
[08:43] <marcustomlinson> morning desktoppers
[08:45] <seb128> hey marcustomlinson, how are you?
[08:45] <marcustomlinson> seb128: I'm good thanks, you?
[08:46] <seb128> I'm good thanks!
[08:46] <seb128> I got proposed migration items a bit sorted out, we need you/libreoffice at this point to clear off items that are otherwise ready
[08:50] <didrocks> seb128: la gorge qui gratte, mais ça va
[08:50] <seb128> k, cool que ça aille un peu mieux
[08:51] <seb128> brb, relocating
[08:56] <oSoMoN> good morning marcustomlinson
[09:02] <Laney> hey hey
[09:04] <didrocks> hey Laney, marcustomlinson
[09:06] <Laney> hey didrocks
[09:07] <seb128> hey Laney
[09:07] <Laney> moin seb128
[09:14] <oSoMoN> hey Laney, salut seb128
[09:15] <seb128> lut oSoMoN
[09:15] <seb128> Laney, oSoMoN, how are you today?
[09:15] <oSoMoN> I'm doing quite alright, despite a rough night (baby waking up every 30mins)
[09:23] <Laney> 😵
[09:23]  * Laney is good
[09:31] <seb128> oSoMoN, :-(
[09:32] <didrocks> waow :(
[09:33] <seb128> Laney, I did try to get on top of proposed-migrations issues and created card/tried to get things moved, I hope I didn't step on your toes too much while doing that
[09:33] <Laney> thx
[09:33] <Laney> no I didn't work on that too much
[09:35] <seb128> cool
[10:23] <Laney> google are killing cloud print :-o
[10:25] <tkamppeter> Laney, did you read this somewhere?
[10:25] <Laney> yes
[10:26] <tkamppeter> Laney, where?
[10:26] <Laney> but it's on that -> machine
[10:26] <Laney> so I suggest searching for it :P
[10:26] <tkamppeter> Laney, so I do not need to pu effort on supporting it any more, nore promote it.
[10:27] <Laney> https://www.techradar.com/news/google-is-shutting-down-its-cloud-printing-service
[10:27] <tkamppeter> Laney, seems that no one sends a print job to a printer which is far away from him.
[10:28] <tkamppeter> Printing from a phone seems to be done nowadays by being close to a modern printer with driverless IPP support.
[10:32] <jibel> sending a print job to a printer far away used to be called a fax, isn't it? ;)
[10:33] <tkamppeter> Laney, "it was particularly useful for Chrome OS users whose existing printers may not have been compatible with their Chromebooks or Chromeboxes.". This use case is now covered by driverless IPP printing.
[10:33] <Laney> for their existing printers?
[10:33] <tkamppeter> Laney, and the Google Chrome guys were on the last 2 or 3 OpenPrinting/PWG Summits and picked up all of our nice driverless stuff.
[10:34] <tkamppeter> Laney, at least for modern printers, and modern can mean something like up to 5 years old. I do not exactly know for how long there is AirPrint (the first driverless IPP standard) now.
[10:35] <Laney> Right
[10:35] <Laney> I'm saying "you don't need this thing, because you can get yourself some new hardware which works better" isn't that great
[10:37] <tkamppeter> Only if you try with these stone-old, never-breaing HP printers with toner from eBay you are probably out of luck (if there is no generic PCL 5e support).
[10:39] <tkamppeter> Laney, and perhaps (I do not have confirmation) Chrome OS already supports or will support Snap and so they have access to future printer drivers (Printer Applications).
[11:24] <fidencio> jibel: https://paste.fedoraproject.org/paste/3b-XEPKLeVT~utEHATuQOg
[11:26] <jibel> fidencio, thanks. looking now
[12:51] <tkamppeter> seb128, Wimpress, kenvandine, I am not able to make it to the meeting today, but my weekly summary is up.
[12:51] <fidencio> jibel: let me know if you are able to, at least, reproduce the very same issue :-)
[13:07] <jibel> fidencio, yes, I will.
[13:50] <jibel> fidencio, where does it stop for you?
[13:57] <fidencio> jibel: https://fidencio.fedorapeople.org/ubuntu_1910_issue.png
[14:05] <fidencio> jibel: btw, happens when using the following media: http://releases.ubuntu.com/19.10/ubuntu-19.10-desktop-amd64.iso
[14:09] <jibel> fidencio, I'm testing on focal, but there shouldn't be much difference
[14:13] <fidencio> jibel: interesting thing (at least for me) is that I haven't seen this issue before, and the issues doesn't happen with other medias or when doing a net-based installation
[14:16] <seb128> marcustomlinson, do you think you will have a chance to look at the libreoffice libiximion thing today? or maybe I can help and give it a try if you prefer?.
[14:17] <marcustomlinson> seb128: I am busy with it. You think you could help nudge libixion and liborcus through from proposed to main?
[14:17] <marcustomlinson> seb128: I assume those will need to be in main before I can have libreoffice depend on the,
[14:17] <marcustomlinson> them
[14:19] <seb128> they are available/ready
[14:19] <seb128> just stuck in proposed waiting on libreoffice
[14:19] <seb128> they can't move before/without it
[14:19] <marcustomlinson> oh ok, I'll have libreoffice pushed in a few
[14:21] <marcustomlinson> I've just had amd64 finish building in my ppa and manual testing looks good
[14:22] <seb128> thx
[14:26] <Wimpress> tkamppeter: Thanks.
[14:26] <Wimpress> Afternoon desktoppers. I'll debut driving the meeting this afternoon :-)
[14:27] <kenvandine> Wimpress: woot
[14:27] <marcustomlinson> :)
[14:27] <Wimpress> Let's not get carried away just yet ;-)
[14:28] <didrocks> heh
[14:29] <seb128> kenvandine, Trevinho, tkamppeter, it was posted a bit late yesterday, but please update your bugs status on https://discourse.ubuntu.com/t/release-bugs-for-week-commencing-monday-25th-november-2019/13474
[14:29] <Trevinho> o/
[14:30] <Wimpress> #startmeeting Desktop Team Weekly Meeting - 2019-11-26
[14:30] <meetingology> Meeting started Tue Nov 26 14:30:03 2019 UTC.  The chair is Wimpress. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[14:30] <meetingology> Available commands: action commands idea info link nick
[14:30] <Wimpress> Roll call:  didrocks, duflu (out), hellsworth, jamesh, jibel, kenvandine, laney, marcustomlinson, oSoMoN, seb128 , tkamppeter (out), trevinho, robert_ancell
[14:30] <seb128> _o/
[14:30] <kenvandine> \o
[14:30] <oSoMoN> hey there
[14:30] <marcustomlinson> o/
[14:30] <didrocks> hey
[14:30] <Wimpress> Hello team o/
[14:31] <jibel> \o
[14:31] <Wimpress> Right, let's push on
[14:31] <Wimpress> #topic rls-bb-bugs
[14:31] <Wimpress> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-incoming-bug-tasks.html
[14:32] <Wimpress> Does look like any thing in there for us, right?
[14:32] <marcustomlinson> nope
[14:32] <Wimpress> *Does not
[14:32] <oSoMoN> nope
[14:32] <seb128> looks like not
[14:32] <Wimpress> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-tracking-bug-tasks.html
[14:33] <hellsworth> here
[14:33] <Wimpress> Hi hellsworth :-)
[14:34] <Wimpress> Not seeing anything obvious unassisgned in the above.
[14:34] <hellsworth> 1852315 ?
[14:34] <seb128> Wimpress, I usually sort by assigneed for that section and look at anything which is "unassigned" and !fix-commited|!incomplete
[14:34] <Wimpress> Although, embarrsingly, MATE Desktop stuff.
[14:34] <hellsworth> it's unasigned and not fix committed
[14:35] <seb128> Wimpress, don't look to unknown section but to desktop one
[14:36]  * seb128 encourage Wimpress, you can do it :)
[14:36] <Wimpress> tseliot_: What is the status of https://pad.lv/1852315
[14:36] <Wimpress> seb128: I'm looking at the desktop stuff now :-)
[14:37] <seb128> Wimpress, that one does look like it make sense, should just be assigned to tseliot_
[14:37] <seb128> so we can probably move to -dd bugs
[14:39] <Wimpress> OK. Everything else for Binonic looks good.
[14:39] <seb128> +1 :)
[14:39] <hellsworth> woot
[14:39] <Laney> yeh, looking at -tracking is really only to find ones that people directly nominated without going through the process
[14:39] <Wimpress> Skip dd completely seb128 or just look at bug tracking tasks?
[14:40] <Laney> all the rest will have been assigned already
[14:40] <hellsworth> why add it to dd and not ee or ff?
[14:40] <seb128> Wimpress, I looked at dd reports, nothing on incoming nor tracking so you can skip it
[14:41] <Wimpress> OK
[14:41] <Wimpress> #topic rls-ee-bugs
[14:41] <Wimpress> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ee-incoming-bug-tasks.html
[14:41] <seb128> and yeah, usually bugs are also on new serie (but sometime not and users nominate only for the one they care about/use)
[14:41] <Wimpress> Looks to be in hand ^
[14:41] <seb128> +1
[14:41] <Wimpress> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ee-tracking-bug-tasks.html
[14:42] <Laney> wait
[14:42]  * Wimpress waits...
[14:42] <Laney> we still need to either nominate it and assign to Till, or tag that as notfixing to not track it
[14:42] <Laney> otherwise we'll see it in incoming next week
[14:43] <seb128> it's assigned
[14:43] <Laney> not nominated
[14:43] <seb128> I don't think it looks a rls issue at this point
[14:43] <seb128> right
[14:43] <Laney> then notfixing
[14:43] <seb128> I was typing :p
[14:43] <seb128> yeah, -1 from me
[14:43] <Laney> I'm just saying you need to do one or the other to get it off the list
[14:44] <seb128> right, I agree
[14:44] <Laney> no opinion on which
[14:44] <seb128> I hit enter too soon
[14:44] <seb128> read my 2 lines as one :p
[14:44] <seb128> sorry if that was confusing
[14:44] <seb128> so my vote is -notficing
[14:44] <seb128> fixing
[14:44] <seb128> others?
[14:45] <seb128> (only 129 reports total on 19.10 from the error tracker, which is low)
[14:45] <marcustomlinson> ±0
[14:45] <Laney> sounds ok to me, not sure Till acknowledged the assignment though so it might get missed
[14:45] <hellsworth> idk if this package is broken, we should fix it for ff since it would be a lts - or remove the package
[14:45] <hellsworth> so i would vote for fixing it
[14:46] <seb128> kenvandine, can you make sure tkamppeter saw it being filed/assigned to him?
[14:46] <kenvandine> yeah
[14:46] <seb128> thx
[14:46] <Wimpress> OK to move on to ff?
[14:47] <didrocks> yeah ;)
[14:47] <seb128> Wimpress, I think you have team input, so your call to either nominate for $series or to change to tag to rls-ee-notfixing
[14:47] <Wimpress> #topic rls-ff-bugs
[14:47] <Wimpress> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ff-incoming-bug-tasks.html
[14:47] <seb128> Wimpress, ^ you need to do one of those actions on the previous bug
[14:48] <seb128> -notfixing doesn't mean we are not going to fix it, just that we don't accept it to be tracked as a release issue and will use the standard process
[14:48] <Wimpress> seb128: OK, what is the mechanism for doing that?
[14:48] <seb128> if you accept it you click "target to series" under the bugs table
[14:48] <seb128> and select the series you want to track it for
[14:49] <seb128> if you think it doesn't need special rls tracking, as said change the tag to rls-ee-notfixing
[14:49] <seb128> rls-ee-incoming -> rls-ee-notfixing
[14:50] <Wimpress> Which bug nuber are you referring to?
[14:50] <hellsworth> the till one
[14:51] <hellsworth> 1851918
[14:52] <Wimpress> OK, that should be updated accordingly.
[14:52] <kenvandine> hellsworth: i've pinged tkamppeter about that one
[14:52] <seb128> Wimpress, thx, we can move to ff then :)
[14:53] <Wimpress> OK.
[14:53] <Wimpress> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1853112
[14:53] <seb128> I think it's worth nominating
[14:53] <seb128> and from this week summary, Laney started looking at it
[14:53] <Laney> sounds good, that can be assigned to me
[14:53] <Wimpress> OK
[14:53] <Laney> but I would be shocked if that bug wasn't a duplicate
[14:53] <didrocks> \o/
[14:54] <didrocks> Laney: I didn't find any other
[14:54] <Laney> ok
[14:54] <Wimpress> Laney wins a bug.
[14:54] <seb128> :-)
[14:54] <Wimpress> NOthing else there that isn't in hand already.
[14:54] <Wimpress> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ff-tracking-bug-tasks.html
[14:54] <seb128> the MIR one there needs to be nominated or tagged -notfixing
[14:55] <seb128> either would work, it's the MIR team queue
[14:56] <Wimpress> So, is libmail-authenticationresults-perl not in main right now?
[14:56] <hellsworth> correct
[14:56] <Wimpress> But on the 19.10 image?
[14:56] <seb128> no
[14:56] <seb128> it blocks a libmail-dkim-perl update in focal-proposed
[14:56] <Laney> that bug is assigned already
[14:56] <Laney> nomin8 it
[14:57] <Laney> imho
[14:57] <seb128> that works yes
[14:57] <Wimpress> I agree. What is the mechanism to nominate something?
[14:57] <hellsworth> i'm happy to keep on with this mir
[14:57] <Laney> target to series, focal, assign to hellsworth
[14:57] <Wimpress> It is nominated for ff.
[14:57] <Laney> delete the incoming tag
[14:58] <didrocks> Wimpress: it can't be on official image if not in main (technically speaking, it will be an iso build failure with "unknown package")
[14:58] <Wimpress> OK, should be correctly nominated for ff now.
[14:58]  * marcustomlinson reads: It is nominated ffs.
[14:59] <Laney> cool
[14:59] <Wimpress> Move on to the next topic?
[14:59] <Laney> ff-tracking looks good, so yeah
[14:59] <seb128> +1
[14:59] <Wimpress> #topic update_excuses_by_team.html#desktop-packages
[15:00] <Wimpress> https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses_by_team.html#desktop-packages
[15:00] <Laney> yeah
[15:01] <Laney> dunno what happened last week
[15:01] <Laney> did these get assigned?
[15:01] <marcustomlinson> there's a few of those that should be cleared out with the libreoffice upload I just did
[15:01] <seb128> Laney, I think everything in the list is being handled
[15:01] <seb128> half of it should unblock with libreoffice
[15:01] <Laney> ok
[15:02] <didrocks> (xorg-server waiting list is scary, probably autopkgtests running ;))
[15:02] <seb128> the other one are a MIR waiting review, librsvg which is being worked on and a few issue from Debian being discussed there
[15:02] <Wimpress> oSoMoN: Are you still fighting with librsvg?
[15:02] <oSoMoN> it's bug #1853657, I'll update to 2.46
[15:02] <seb128> Laney, in fact I lied about one, libxml is blocked by postgresql-12 ... do you know if anyone is looking at that?
[15:03] <Laney> nope
[15:03] <seb128> it's not for out team though and I would expect it's being handled, unsure who to ping though
[15:03] <Laney> maybe need to check with server team
[15:03]  * seb128 wants p_iti :)
[15:03] <Laney> probably in ubuntu-devel
[15:03] <seb128> +t
[15:03] <seb128> right
[15:03] <Laney> what is glm?
[15:03] <Laney> why do we own all this weird stuff ._.
[15:03] <Wimpress> GL maths library.
[15:04] <didrocks> https://bugs.launchpad.net/ubuntu/+source/glm/+bug/1176083
[15:04] <didrocks> Robert! :)
[15:04] <didrocks> (Mir requirement)
[15:04] <seb128> Mirrrr
[15:05] <seb128> we should reassign that to Saviq
[15:05] <didrocks> yeah, I think that should be their team
[15:05] <Laney> are they a main owning team these days?
[15:05] <Laney> would be good if so
[15:05] <seb128> we should talk about that
[15:05] <Laney> looks like it
[15:05]  * seb128 takes a note to discuss it in the manager meeting later
[15:05] <Laney> http://reqorts.qa.ubuntu.com/reports/m-r-package-team-mapping.html#mir-team
[15:06] <Wimpress> Seems reasonable.
[15:06] <Laney> so we can probably move that one after asking
[15:06] <Laney> \o/
[15:06] <didrocks> yep ;)
[15:06] <Laney> so I guess that's it
[15:06] <seb128> :-)
[15:06] <hellsworth> why does that mir-team not have libmail-authenticationresults-perl?
[15:06] <Wimpress> ANything else in there we need to assign or find another owner for?
[15:06] <seb128> Saviq, can you subscribe the mir team to glm?
[15:06] <Wimpress> Nicve try hellsworth ;-)
[15:07] <Laney> ha
[15:07] <hellsworth> im serious
[15:07] <didrocks> I suggest all -perl -> other teams ;)
[15:07] <hellsworth> isn't the mir team supposed to review the mirs?
[15:07] <Wimpress> +1 :-)
[15:07] <Laney> it's Mir not MIR
[15:07] <hellsworth> must be a newbie question
[15:07] <didrocks> ah yeah puzzling
[15:07] <Laney> as in ...
[15:07] <Wimpress> #namingthingsishard
[15:07] <hellsworth> mir as in the os?
[15:07] <didrocks> hellsworth: Mir is a display server, like xorg, not MIR (Main Inclusion Request)
[15:07] <Laney> https://mir-server.io/
[15:07] <hellsworth> right
[15:07] <Laney> that thing
[15:08] <oSoMoN> lucky there isn't a mIR team
[15:08] <hellsworth> ok that mir is the only mir i was aware of before joining the team :)
[15:08] <hellsworth> ok
[15:08] <hellsworth> two mirs
[15:08] <Wimpress> oSoMoN: Give it time.
[15:08] <Laney> still only two
[15:08] <didrocks> or a MiR or mIr or… :)
[15:08] <Laney> not as many as we've had autopilots
[15:08] <Wimpress> Time for AOB?
[15:08] <didrocks> Laney: heh ;)
[15:08] <didrocks> yeah, looks like time for AOB
[15:08] <Wimpress> #topic AOB
[15:08] <Wimpress> Anyone have anything else they want to discuss?
[15:09] <seb128> not from me
[15:09] <didrocks> anope
[15:09] <Trevinho> neither
[15:09] <oSoMoN> nothing here
[15:09] <Saviq> seb128: what am I doing again?
[15:09] <Wimpress> You just agree to own the glm package in main Saviq :-)
[15:10] <seb128> Saviq, https://launchpad.net/ubuntu/+source/glm/+subscribe
[15:10] <seb128> Saviq, and subscribe the mir team, so the package mapping is showing the correct owner
[15:10] <seb128> since it seems the only reason it is in main is mir
[15:10] <Saviq> ETOOMANYTEAMS
[15:10] <seb128> indeed
[15:11] <seb128> the subscribe dialog could use filtering or keyboard completion
[15:11] <Saviq> seb128: but subscribed
[15:11] <seb128> Saviq, thx!
[15:11] <Saviq> ofc
[15:11] <Wimpress> Saviq: Thanks.
[15:11] <Laney> now, it's stuck in -proposed, go fix it :p
[15:11] <seb128> lol
[15:11] <didrocks> "btw…" ;)
[15:11] <Saviq> sneaky b…
[15:11] <seb128> Saviq, it's being handled in Debian don't worry
[15:11] <Wimpress> Well played team.
[15:12] <Laney> haha
[15:12] <Saviq> Wimpress: that's how you run them, eh?
[15:12] <Wimpress> :-)
[15:12] <Wimpress> I have an AOB topic, if noone else has anything.
[15:13] <Laney> dunno about don't worry, still good to keep an eye, no guarantees there
[15:13] <Laney> go
[15:13] <seb128> Saviq, https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=940906 for reference, the autopkgtest got broken by the removal of the cmake file which looks like upstream is bringing back, so probably just wait for upstream/debian and it will automagically resolve
[15:13] <seb128> but yeah, still keep an eye in case it needs some nagging
[15:13] <seb128> Wimpress, go!
[15:14] <Wimpress> Wanted to discuss the idea have this meeting at alternating times every other week.
[15:14] <seb128> what times?
[15:14] <Wimpress> Basically, so we can do this with the team members from down under.
[15:14] <Wimpress> I have given the time much thought yet.
[15:14] <seb128> we used to do that but 1am meeting wasn't really working
[15:15] <seb128> it cost to the team more than it's worth imho
[15:15] <Wimpress> Just wanted to see if it has been tried before or what you all think about the idea.
[15:15] <didrocks> that would mean early morning, without US but with NZ/AU?
[15:15] <didrocks> or just US/NZ/AU?
[15:15] <Laney> don't think we have any working day overlap with robert_ancell
[15:15] <Laney> maybe the US does
[15:15] <hellsworth> yep we do
[15:15] <seb128> or everyone in turn with every n weeks some people up at 1am for an IRC meeting (we had that at some point in the past)
[15:15] <hellsworth> but between US/EU/AU pick 2
[15:15] <Wimpress> I have meetings with RObert at 8pm UK time regarding snap store.
[15:16] <seb128> which is like 6am for James?
[15:16] <seb128> there is still like 3 hours between Robert and James
[15:17] <Wimpress> Yeah, I know this isn't easy.
[15:17] <Wimpress> I don't think asking anyone to have a meeting at 1am is reasonable.
[15:17] <kenvandine> it's really tough
[15:17] <hellsworth> i think kenvandine and i are the only us ones. i'm happy to meet in the evening if it helps
[15:18] <Wimpress> So, the idea is OK. Just needs some actual thought regarding logistics?
[15:18] <seb128> it's still going to be inconvenient for people, either earlier or conflciting with familly life, dinner, activities...
[15:18] <seb128> I don't think it's worth the cost
[15:19] <kenvandine> i agree
[15:19] <seb128> but just my opinion
[15:19] <Wimpress> OK.
[15:19] <seb128> if we don't want to exclude half the team maybe think about fully go async?
[15:19] <didrocks> or we make the attendance optional, and have rolling time, so, it can be once US/AU, once US/EU, (and maybe EU/AU?)
[15:19] <seb128> e.g drop the meeting and just use discourse...
[15:19] <marcustomlinson> I do think it's a nice idea to have US/AU community around for a meeting time
[15:19] <seb128> or what didrocks says could also worth
[15:20] <seb128> maybe change the meeting purpose
[15:20] <Laney> feels like a chat for a retrospective in a sprint at this point
[15:20] <seb128> we have bugs & activity on discourse
[15:20] <Laney> to me anyway
[15:20] <seb128> make it a sync point/office hour slot
[15:20] <Wimpress> Laney: Good idea!
[15:20] <seb128> +1
[15:20] <Laney> personally I don't agree that the rls stuff would be good on discourse, that works nicely in real time I think
[15:20] <Laney> but time zones do sucks
[15:20] <Laney> -s
[15:21] <Wimpress> Right, I'll think on that some more and we can chat about it together.
[15:21] <Laney> ta
[15:21] <Wimpress> I'm done. Anything else?
[15:21] <kenvandine> nothing from me
[15:21] <Wimpress> 3...
[15:21] <hellsworth> travel
[15:22] <hellsworth> folks should do that real quick
[15:22] <hellsworth> that is all
[15:22] <kenvandine> indeed
[15:22] <Wimpress> Good point hellsworth
[15:22] <seb128> not from me
[15:22]  * didrocks is dealing with atpi, sounds train is complex for them :)
[15:22] <seb128> oh, as we do reminders
[15:22] <seb128> @online training :)
[15:22] <hellsworth> is there an official due date for the online training?
[15:22] <marcustomlinson> deadline is next Wednesday I beleive
[15:22] <hellsworth> ah ok
[15:23] <seb128> they said end of the month
[15:23] <marcustomlinson> well it was said 1 month from access which was 4 Nov
[15:23] <seb128> but I emailed saying it was not possible for some people who were in holidays and they replied "do you best then"
[15:23] <seb128> your*
[15:23] <Wimpress> End of this week is the target I believe.
[15:23] <seb128> so I think it's not an well defined line, they just wanted to push people to get it done
[15:24] <hellsworth> sure ok thanks
[15:24] <Wimpress> And, I also heard there is some wiggle room.
[15:24] <Wimpress> lulz
[15:24] <kenvandine> :)
[15:24] <Wimpress> All finished?
[15:24] <Laney> wonder if that'll break meetingology
[15:24] <didrocks> yep ;)
[15:24] <seb128> yep
[15:24] <Laney> or if meetingology will break it
[15:25] <seb128> should not, I think the bot is mart
[15:25] <seb128> smart
[15:25] <Wimpress> Thanks everyone.
[15:25] <hellsworth> thanks!
[15:25] <Wimpress> 2...
[15:25] <oSoMoN> a smart bot? there is no such thing
[15:25] <seb128> Wimpress, thx, well done handling your first meeting :)
[15:25] <Wimpress> 1...
[15:25] <Wimpress> Thanks seb128
[15:25] <Wimpress> #endmeeting
[15:25] <meetingology> Meeting ended Tue Nov 26 15:25:41 2019 UTC.
[15:25] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2019/ubuntu-desktop.2019-11-26-14.30.moin.txt
[15:25] <Laney> HA
[15:25] <didrocks> thx!
[15:25] <marcustomlinson> Thanks Wimpress
[15:25] <Laney> KNEW IT
[15:25] <seb128> meetingology, you s.... bot :p
[15:26] <Wimpress> #botfail
[15:26] <oSoMoN> told you
[15:26] <seb128> pfiou
[15:26] <seb128> not today that the bot get us out of having a job then!
[15:26] <oSoMoN> not that one anyway :)
[15:26] <hellsworth> lol
[15:33] <kenvandine> Wimpress: joining?
[15:36] <jibel> fidencio, I can do an automated installation with your preseed and find nothing wrong with it.
[15:37] <jibel> fidencio, then only thing I can imagine at the moment is that you set disk and bootdev to vda and if your VM is configured with a SATA interface instead of Virtio then the disk won't exist
[15:38] <jibel> but I suspect the error would be different than stopping on the guided partitioning step
[15:38] <jibel> it would likely be an error from partman saying it cannot find the root device
[15:40] <fidencio> jibel: you tried with the mentioned ISO? if you tried with focus, would you mind pointing me to the ISO you used?
[15:40] <fidencio> jibel: we do set the disk and bootdev to vda, but it's recognised and I can finish the installation without any issue, manually, still using vda
[15:41] <jibel> fidencio, I tried focal and I'm verifying on eaon now
[15:42] <jibel> fidencio, http://cdimage.ubuntu.com/daily-live/pending/focal-desktop-amd64.iso
[15:43] <fidencio> jibel: let me try with focal here as well
[15:45] <seb128> https://trello.com/b/mxaCZTVc/ubuntu-desktop-common
[15:45] <seb128> new board
[15:46] <seb128> the other board is "Ubuntu Desktop Snap" so I used "Common" there
[15:48] <Laney> beautiful
[15:51] <fidencio> jibel: same error here
[15:51] <fidencio> jibel: I wonder whether it may be related to the init_automatically_partition string passed to partman-auto
[15:55] <jibel> fidencio, another difference is that I put the seed in the preseed directory of the iso not the initrd
[15:56] <fidencio> jibel: can ubuntu generate a preseed file by the end of a normal installation?
[15:57] <fidencio> jibel: what's really fishy for me is that it only broke when using initrd injection with this specific ISO (and now with focal as well)
[15:58] <seb128> grrr, moving column between boards lost the people :/
[16:00] <Laney> do they come back once they re join the board?
[16:01] <fidencio> jibel: what I can see here is: ubiquity: Partman: state = [['', None, None]]
[16:01] <jibel> fidencio, no it cannot, you could do a debconf-get-selections but there would be lot of noise
[16:01] <seb128> Laney, no :(
[16:01] <Laney> :<
[16:01] <fidencio> jibel: Partman: auto_state [0, 'Guided - use entire disk']
[16:01] <fidencio> so, seems that partman is not getting the state passed
[16:01] <jibel> yeah
[16:02] <fidencio> jibel: what are the possible values to be passed?
[16:02] <seb128> I'm adding people back to the board as I see fit but please review and add yourself to card if I missed some
[16:02] <seb128> sorry for the noise :/
[16:05] <jibel> fidencio, partman auto supports the following values
[16:05] <jibel> Guided - use the largest continuous free space
[16:05] <jibel>  Guided - use entire disk
[16:05] <jibel>  Guided - resize ${PARTITION} and use freed space
[16:05] <jibel>  Guided - reuse partition, ${PARTITION}
[16:05] <jibel>  Guided - use entire partition, ${PARTITION}
[16:23] <fidencio> jibel: how can I be sure the preseed file was found?
[16:36] <fidencio> when taking a look at casper.log, I can see something like "Begin: Loading preseed file... ... grep: /root/preseed.cfg: No such file or directory"
[16:41] <fidencio> nah, doesn't seem to be the issue as the same is shown when trying to install 18.10 and it just works
[16:52] <ricotz> oSoMoN, hi, remember ff71 on xenial needs to be built against patch llvm-6 or llvm-8+
[16:53] <oSoMoN> ricotz, I know, and it's high on my to-do list, but I wanted to get the builds going in the PPA anyway
[17:00] <ricotz> oSoMoN, ok
[17:00] <ricotz> with llvm-9 in bionic now it seems a good backport candidate as well
[17:07] <oSoMoN> indeed
[17:08] <oSoMoN> ricotz, with our conditional code, once llvm-9 is out of proposed it should be picked up automatically by firefox builds, right?
[17:08] <oSoMoN> i.e. nothing to change in the packaging
[17:09] <ricotz> oSoMoN, yes
[17:13] <fidencio> jibel: hmm. Interesting thing .... on 19.10, I can see on dmesg: "Trying to unpack rootfs image as initramfs..." and "Initramfs unpacking failed: Decoding failed"
[17:41] <jibel> fidencio, how to you inject the preseed and rebuild the initrd?
[18:02] <bittin_> Hello! Any Ubuntu Desktop Meeting today? i did my duties and reported a Totem bug atleast
[18:03] <bittin_> https://gitlab.gnome.org/GNOME/totem/issues/377
[18:03] <gitbot> GNOME issue 377 in totem "Totem SegFaults on Ubuntu 20.04 Daily Image" [Opened]
[18:03] <bittin_> https://bugs.launchpad.net/ubuntu/+source/totem/+bug/1854085
[18:06] <oSoMoN> hi bittin_ ! the weekly desktop meeting was 3 hours ago
[18:06] <oSoMoN> thanks for that bug report
[18:06] <bittin_> oSoMoN: alright, any meetings log file ?
[18:07] <oSoMoN> bittin_, https://irclogs.ubuntu.com/2019/11/26/%23ubuntu-desktop.html
[18:07] <bittin_> thx
[18:14]  * bittin_ reads up
[18:24] <bittin_> btw anyone knows something about Force Feedback Wheels on Ubuntu 18 or 19? a friend is wondering
[18:33] <bittin_> done reading thanks
[18:38] <bittin_> Anyone know how to create a stack trace with Debug Symbols?
[18:40] <oSoMoN> bittin_, install debug symbols with instructions at https://wiki.ubuntu.com/Debug%20Symbol%20Packages, then run whichever app that crashes in gdb, and when it breaks at the gdb prompt type "t a a bt" followed by return
[18:41] <bittin_> oSoMoN: thanks the Totem guys wanted a strace but never did this before
[18:47] <bittin_> oSoMoN: (gdb) "t a a bt"
[18:47] <bittin_> Undefined command: "".  Try "help".
[18:54] <bittin_> https://gitlab.gnome.org/GNOME/totem/issues/377#note_656651
[18:54] <gitbot> GNOME issue 377 in totem "Totem SegFaults on Ubuntu 20.04 Daily Image" [1. Crash, 2. Needs Information, Opened]
[18:54] <bittin_> @ oSoMoN
[19:09] <bittin_> oSoMoN: so if you know how gdb works, could you help with that? that would be nice
[19:45] <oSoMoN> bittin_, gbd totem, then when you get the first prompt "run" and return
[19:45] <oSoMoN> then make the app crash, and "t a a bt"
[19:46] <bittin_> oSoMoN: thanks
[19:47] <bittin_> oSoMoN: https://gitlab.gnome.org/GNOME/totem/issues/377
[19:47] <gitbot> GNOME issue 377 in totem "Totem SegFaults on Ubuntu 20.04 Daily Image" [1. Crash, 3. Not Gnome, Closed]
[20:03] <oSoMoN> bittin_, note that if you have a crash file for totem under /var/crash, apport should have uploaded it automatically to errors.ubuntu.com
[20:08] <robert_ancell> sergiusens, hi
[20:08] <oSoMoN> bittin_, that's https://errors.ubuntu.com/problem/55095074fb3c3335c19f63f3c91d3a8231be2034
[20:09] <oSoMoN> (you might not be able to see this, but that means the crash is known and being tracked)
[20:17] <seb128> robert_ancell, hey
[20:17] <robert_ancell> seb128, hi
[20:20] <seb128> oSoMoN, bittin_, looks like a valid one to send upstream to gitlab
[20:23] <oSoMoN> hey robert_ancell
[20:24] <robert_ancell> oSoMoN, hi! Actually I had a questions for you... Can you set the common-id for the 0ad snap?
[20:24] <oSoMoN> robert_ancell, sure, how do I do that?
[20:25] <robert_ancell> oSoMoN, https://github.com/microsoft/vscode/pull/76432
[20:25] <gitbot> microsoft issue (Pull request) 76432 in vscode "snapcaft.yaml: Set the AppStream ID in the Snap metadata" [Closed]
[20:26] <robert_ancell> Something like that. If that app doesn't have an ID then you use the .desktop file name
[20:27] <robert_ancell> oSoMoN, according to the .deb version in the YAML the ID should be com.play0ad.zeroad
[20:28] <fidencio> jibel: I just use virt-install to do so. Let me check the code.
[20:28] <oSoMoN> robert_ancell, so that's the value of the <id> field in the appdata.xml, right?
[20:29] <robert_ancell> oSoMoN, Yes.
[20:29] <oSoMoN> ack
[20:29] <robert_ancell> Bonus points for pulling it out automatically :)
[20:29] <robert_ancell> I'm trying to work out with sergiusens if we can get snapcraft to make this easier.
[20:30] <fidencio> jibel: https://github.com/virt-manager/virt-manager/blob/master/virtinst/install/installerinject.py#L15
[20:32] <marcustomlinson> Hey robert_ancell
[20:32] <robert_ancell> o/
[20:36] <oSoMoN> robert_ancell, appdata.xml is in the source tarball, so I could extract the id from there, but I don't suppose there's a "snapcraftctl set-common-id <ID>" command that can be used in scriptlets, is there?
[20:37] <robert_ancell> oSoMoN, I don't have enough snapcraft experience to say.
[20:38] <oSoMoN> sergiusens, can you confirm ^ ?
[20:39] <robert_ancell> oSoMoN, the common-id is per-app, so I guess it would have to be "snapcraftctl set-common-id <APP> <ID>" ?
[20:39] <marcustomlinson> robert_ancell: you may want to join #snapcraft
[20:40] <oSoMoN> right
[20:46] <oSoMoN> robert_ancell, https://bazaar.launchpad.net/~osomon/+junk/0ad-snap/revision/34 , and snaps rebuilding on launchpad
[20:46] <robert_ancell> oSoMoN, thanks!
[20:49] <oSoMoN> ok, I'm off for today, have a good rest of the day everyone
[20:50] <marcustomlinson> me too. bye!
[20:54] <mwhudson> hm hm rustc builds ok on xenial/armhf when built with gcc 7...
[21:06] <fidencio> jibel: Aha! https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1835660
[21:07] <fidencio> jibel: not exactly the same issue, but similar / same error message
[21:09] <fidencio> and https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840945
[21:51] <fidencio> jibel: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1840945 is the root cause. it *is* a regression as gzip stopped working. Preferring lz4 is totally understandable, dropping gzip support, tho, is a big regression as it does affect virt-manager / gnome-boxes / and pretty much a bunch of users relying on old scripts using gzip
[21:51] <fidencio> jibel: I've patched virt-manager to do the test, and used `lz4 -9 -l` and it just worked
[21:52] <fidencio> jibel: but patching virt-manager for dealing with this specific ISO is not the way to go
[22:12] <fidencio> robert_ancell: heya! are you running 19.10?
[22:13] <robert_ancell> fidencio, yes
[22:14] <fidencio> robert_ancell: mind pasting the output of `zgrep CONFIG_RD_ /usr/src/<path/to/latest/kernel>/.config`?
[22:14] <robert_ancell> $ zgrep CONFIG_RD_ /usr/src/linux-headers-5.3.0-23-generic/.config
[22:14] <robert_ancell> CONFIG_RD_GZIP=y
[22:14] <robert_ancell> CONFIG_RD_BZIP2=y
[22:14] <robert_ancell> CONFIG_RD_LZMA=y
[22:14] <robert_ancell> CONFIG_RD_XZ=y
[22:14] <robert_ancell> CONFIG_RD_LZO=y
[22:14] <robert_ancell> CONFIG_RD_LZ4=y
[22:15] <fidencio> robert_ancell: hmm. interesting. not a kernel change then.
[22:15] <fidencio> robert_ancell: thanks a lot!