[06:21] <oSoMoN> good morning desktoppers
[06:25] <duflu> Hi oSoMoN
[06:37] <jibel> morning tout le monde
[06:39] <oSoMoN> hey duflu
[06:39] <oSoMoN> salut jibel
[06:40] <duflu> Morning jibel
[07:16] <didrocks> good morning
[07:18] <duflu> Hi didrocks
[07:24] <didrocks> hey duflu
[07:31] <oSoMoN> salut didrocks
[07:34] <didrocks> salut oSoMoN, ça va mieux ?
[09:03] <Laney> lut
[09:05] <duflu> lo Laney
[09:07] <seb128> hey Laney, how are you today?
[09:07] <marcustomlinson> morning all
[09:09] <oSoMoN> didrocks, bien mieux, merci! et toi, ça va?
[09:09] <oSoMoN> hey Laney
[09:09] <oSoMoN> morning marcustomlinson
[09:09] <oSoMoN> salut seb128
[09:09] <duflu> Hi marcustomlinson
[09:10] <didrocks> oSoMoN: ça va oui, merci :)
[09:10] <seb128> lut oSoMoN, ça va mieux ?
[09:10] <seb128> oSoMoN, Lukaz was looking for you yesterday asking if the tb SRU is meant to go through security again
[09:11] <seb128> oSoMoN, and popey was asking what's the status of firefox 71 for 19.10/stable series
[09:12] <oSoMoN> seb128, beaucoup mieux, merci
[09:12] <seb128> super!
[09:13] <oSoMoN> seb128, I'll talk to them, thanks. the TB SRU isn't meant to go through security, and firefox 71 is up in -security and -updates since last night, except for xenial, but I'm working on it
[09:13] <Laney> hey duflu seb128 marcustomlinson oSoMoN
[09:14] <Laney> seb128: doing alright! you?
[09:16] <seb128> doing good!
[09:21] <oSoMoN> seb128, before you ask, I'm working on my weekly status update
[09:26] <seb128> oSoMoN, :-)
[09:49] <oSoMoN> ricotz, good morning! you probably noticed that I re-enabled unity-menubar.patch in the xenial build in firefox-next, but when testing I found that the menubar gets duplicated when opening any menu
[09:50] <oSoMoN> I need to investigate this further, I won't re-enable the patch in the other series until I figure it out
[09:50] <oSoMoN> also, I'm tempted to remove the patch altogether in focal, so that we don't have to maintain it forever
[09:53] <Laney> +++++
[10:13] <seb128> popey, hey, in case you didn't see, https://launchpad.net/ubuntu/+source/firefox/71.0+build5-0ubuntu0.19.10.1
[10:13] <popey> \o/ thanks!
[10:13] <seb128> np!
[10:15] <seb128> Trevinho, kenvandine, jamesh, monday weekly summary (if you are off on monday we said it should be posted on friday)
[10:15] <oSoMoN> popey, I'm still working on the 71.0 update for xenial, in case anyone asks
[10:15] <oSoMoN> s/asks/complains/
[10:56] <dupondje> oSoMoN: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=946249 and https://bugzilla.mozilla.org/show_bug.cgi?id=1601707
[10:56] <dupondje> and https://github.com/vector-im/riot-web/issues/11606#issuecomment-563944612
[10:56] <gitbot> vector-im issue 11606 in riot-web "Riot Web stop receiving new messages after Firefox 71 update" [Bug, Upstream-Issue, 🔥 Fire 🔥, Open]
[10:56] <dupondje> might want to put it on your radar :) My first tests show that ubuntu is also affected
[11:08] <Laney> just installed a VM to test the new gtk
[11:08] <Laney> and it's completely broken /o\
[11:09] <Laney> can't get to gdm, even systemd.unit=rescue.target doesn't give me a shell to do anything at
[11:09] <oSoMoN> dupondje, ack, those issues are caused by gcc miscompilation, firefox in ubuntu is now built with clang, so in theory it shouldn't be affected
[11:10] <oSoMoN> dupondje, what tests exhibit a problem?
[11:11] <seb128> Laney, :-(
[11:15] <Laney> seb128: for your gtk2 upload, I think you need ${CROSS_COMPILE} in the pkg-config call too
[11:17] <seb128> Laney, yeah, thx, I was just fixing that now
[11:17] <Laney> cool
[11:47] <dupondje> oSoMoN: well tested riot, but seems like it was just some delay, and finally worked. So guess we're unaffected on ubuntu indeed. Didn't notice other issues at least :)
[11:48] <oSoMoN> dupondje, good :) keep me posted if you do find issues!
[13:37] <Laney> tjaalton: hey, can you take a look at this log and see if you know why it's going south please? https://paste.debian.net/1120491/
[13:38] <Laney> this is a VM and I can't log into a session
[13:40] <Laney> GDM/Wayland fails like this: https://paste.debian.net/1120492/
[13:41] <Laney> is this some udev thing?
[13:41] <Laney> just wanted to test my gtk update - two broken projects later and I'm still not there :)
[13:41] <Laney> nicely shaven yak though
[13:41]  * Laney goes to eat lunch
[13:44] <tjaalton> Laney: looks like xserver starts before the kms driver is ready
[13:45] <tjaalton> restart gdm and it should be fine
[14:05] <seb128> shrug, why is canonistack so sloooow :(
[14:10] <kenvandine> jdstrand: did you see the autoconnect request for gnome-firmware?  https://forum.snapcraft.io/t/gnome-firmware-auto-connect-to-fwupd-interface/14444
[14:11] <jdstrand> kenvandine: yes, I plan to run through the rest of the store requests today (it is what I am currently doing)
[14:11] <kenvandine> jdstrand: great!
[14:28] <Wimpress> Hello desktoppers.
[14:28] <marcustomlinson> yo Wimpress
[14:28] <oSoMoN> hi Wimpress
[14:29] <seb128> hey
[14:29] <hellsworth> good morning everyone
[14:30] <oSoMoN> good morning hellsworth
[14:31] <hellsworth> o/
[14:31] <Wimpress> Right, lets do this thing :-)
[14:31] <Wimpress> #startmeeting Desktop Team Weekly Meeting - 2019-12-10
[14:31] <meetingology> Meeting started Tue Dec 10 14:31:26 2019 UTC.  The chair is Wimpress. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[14:31] <meetingology> Available commands: action commands idea info link nick
[14:31] <Wimpress> Roll call:  didrocks, duflu, hellsworth, jamesh, jibel, kenvandine, laney, marcustomlinson, oSoMoN, seb128 , tkamppeter, trevinho, robert_ancel
[14:31] <marcustomlinson> \o
[14:31] <hellsworth> o/
[14:31] <kenvandine> o/
[14:32] <oSoMoN> 🐵/
[14:32] <seb128> _o/
[14:32] <Wimpress> Well, shall we make a start?
[14:33] <Wimpress> #topic rls-bb-bugs
[14:33] <Wimpress> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-incoming-bug-tasks.html
[14:34] <Wimpress> Nothing for desktop there.
[14:34] <Wimpress> Nothing in unknown we should I own IMO.
[14:35] <seb128> +1
[14:35] <Wimpress> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-tracking-bug-tasks.html
[14:36] <Wimpress> Everything in desktop is assigned.
[14:37] <Wimpress> Quick scan of unknown doesn't appear to have anything we should own.
[14:38] <Wimpress> Move on to dd?
[14:38] <Wimpress> #topic rls-dd-bugs
[14:38] <Wimpress> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-dd-incoming-bug-tasks.html
[14:38] <Wimpress> Nothing for desktop in there.
[14:38] <Wimpress> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-dd-tracking-bug-tasks.html
[14:39] <Wimpress> desktop-packages bugs are assigned.
[14:39] <hellsworth> but #1733321
[14:40] <Wimpress> hellsworth: Well spotted. I missed that.
[14:40] <hellsworth> wow it's 2 years old
[14:41] <Wimpress> Yep, just reading...
[14:41] <seb128> I don't think it's rls material
[14:41] <seb128> but it has a workaround patch and might be worth reviewing
[14:41] <seb128> but that's rather for the sponsoring queue imho;..
[14:41] <Wimpress> Hmm, patch looks like a bodge.
[14:42] <Wimpress> `sleep 2`
[14:44] <Wimpress> seb128: You want it in the sponsoring queue?
[14:44] <seb128> Wimpress, well, it has a patch that didn't get reviewed, even if it's not correct 1- the contributor deserves a reply 2- it might give a clue of the issue and of a better fix
[14:45] <seb128> just need to subscribe ubuntu-sponsors for that
[14:45] <seb128> but in the meeting we usually focus on +1/-1 to rls nominate
[14:45] <Wimpress> I've subscribe ubuntu-sponsors
[14:45] <seb128> as I said I would -1, it's a flacky test, not an user facing problem
[14:45] <seb128> thx
[14:45] <oSoMoN> agreed, -1 for rls
[14:45] <Wimpress> Move on to ee?
[14:46] <seb128> +1
[14:46] <Wimpress> #topic rls-ee-bugs
[14:46] <Wimpress> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ee-incoming-bug-tasks.html
[14:47] <Wimpress> http://launchpad.net/bugs/1855593
[14:48] <seb128> Wimpress, that's a duplicate and I while it's a frequently reported issue I don't think we should rls target it
[14:48] <Wimpress> OK. I'll drop the tag.
[14:48] <seb128> it's also already being worked on upstream (I provided them a db from a system which has the issue, looks like it happens on corrupted sqlite dbs)
[14:50] <Wimpress> Left a comment on the bug.
[14:50] <Wimpress> So Brian knows why I removed the tag he placed.
[14:51] <Wimpress> Nothing in unknown that looks like it belongs to us.
[14:51] <Wimpress> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ee-tracking-bug-tasks.html
[14:51] <Wimpress> http://launchpad.net/bugs/1845801
[14:53] <Wimpress> Seems to be affecting a reasonable number of people.
[14:55] <seb128> tseliot was on it, we should check with him (but probably outside of the meeting, no need to make the meeting longer over that)
[14:55] <Wimpress> OK
[14:56] <Wimpress> Everything else looks in order for the desktop.
[14:56] <Wimpress> Time for focal?
[14:56] <seb128> \o/
[14:56] <Wimpress> #topic rls-ff-bugs
[14:56] <Wimpress> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ff-incoming-bug-tasks.html
[14:57] <Wimpress> Look good to me.
[14:57] <Wimpress> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ff-tracking-bug-tasks.html
[14:58] <Wimpress> Looks in hand too.
[14:58] <Wimpress> #topic update_excuses_by_team.html#desktop-packages
[14:58] <Wimpress> https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses_by_team.html#desktop-packages
[14:59] <Wimpress> That has grown.
[14:59] <Laney> Think seb128 is more on it than me atm
[14:59] <seb128> right
[15:00] <hellsworth> i can poke the security folks on libmail-dkim-perl today
[15:00] <hellsworth> seb128: is there anything on this list i can help with?
[15:00] <seb128> thx, that would be useful
[15:00] <seb128> I think the list is mostly i386 removal fallouts
[15:00] <seb128> which are being handled
[15:00] <hellsworth> oki
[15:01] <Wimpress> Suspiciously high number of build failures on armhf
[15:01] <seb128> https://lists.ubuntu.com/archives/ubuntu-devel/2019-December/040859.html
[15:01] <seb128> for those who didn't see that / want context
[15:01] <seb128> Wimpress, oh?
[15:01] <seb128> anyway, outside of i386
[15:01] <seb128> oSoMoN, I think we should consider badtest firefox/armhf
[15:01] <seb128> rather than keep retrying a long job with poor success
[15:01] <oSoMoN> yeah, agreed
[15:02] <Wimpress> +1
[15:02] <oSoMoN> it's gotten worse lately
[15:02] <Laney> what made it start failing and why wouldn't it be more appropriate to fix that?
[15:02] <seb128> can you mp a britney hint for it?
[15:02] <oSoMoN> Laney, I don't know what made it start failing, there's a bug open to investigate it but I haven't had time for it
[15:03] <seb128> Laney, we should fix it, but realistically armhf isn't high enough the priority list that I can see it fixes before holidays
[15:03] <seb128> so I suggest we skip that version instead of hammering retry which we currently do
[15:03] <seb128> I will card the task to properly fix it though
[15:03] <seb128> Laney, sounds an acceptable compromise?
[15:04] <seb128> otherwise cyrus-imapd needs to be fixed, but that's not especially us since it's universe
[15:05] <seb128> and I think that's it
[15:05] <didrocks> I think related to this, there are 2 MIRs that needs investigations (if needed), and if so, filed: xorg/xterm, libnotify/sugar (https://people.canonical.com/~ubuntu-archive/component-mismatches-proposed.svg)
[15:05] <seb128> hellsworth, thx for asking if you could help, but I think we should be good for this round (if you want to poke at cyrus-imapd feel free though)
[15:05] <Laney> I don't particularly suggest "hammering retry" is ever the right thing to do
[15:06] <Laney> if we don't care about a working firefox on armhf, stop building it
[15:06] <seb128> didrocks, thx
[15:06] <seb128> Laney, yeah, I was thinking about that, we should probably have that discussion
[15:06] <seb128> oSoMoN, ^
[15:06] <seb128> firefox on amd64 only
[15:06] <seb128> but not today :)
[15:07] <seb128> Wimpress, I think that's enough for that section of the meeting
[15:07] <oSoMoN> I would certainly welcome dropping architectures that almost no-one uses anyway
[15:07] <Laney> I don't think armhf (or arm64) falls into that category though, they are certainly used for desktop stuff
[15:07] <oSoMoN> the most obvious one being s390x, which we know builds but segfaults at startup
[15:07] <Laney> I'm certainly happy for an armhf build of firefox on my raspberry pi
[15:07] <Wimpress> I agree with Laney
[15:08] <marcustomlinson> yep
[15:08] <marcustomlinson> desktop != amd64
[15:08] <oSoMoN> yeah
[15:08] <kenvandine> s390 though... that should be a candidate to drop
[15:08] <seb128> well, but also n% of our capacity spent for 0.01% users...
[15:09] <seb128> but anyway
[15:09] <seb128> not a topic for here/now I think
[15:09] <oSoMoN> I'm not aware of reports that firefox doesn't work on armhf though, it seems it's just that one test when run in the autopkgtest infrastructure
[15:10] <Laney> we control what tests the package executes, and if it's not doing a good job of testing if firefox actually works then it could be altered to do so
[15:11] <Wimpress> Are we all done with that topic?
[15:11] <seb128> I think so
[15:11] <oSoMoN> Laney, let's continue the discussion just after the meeting
[15:11] <Wimpress> Good idea.
[15:11] <Laney> if the firefox in focal release is already broken then we could badtest this version I guess
[15:11] <Wimpress> #topic AOB
[15:12] <Laney> :( poor tests :(
[15:12] <Wimpress> ANyone have anything they want to discuss?
[15:13] <seb128> not me
[15:13] <Wimpress> me either
[15:13] <hellsworth> nothing from me
[15:13] <didrocks> nothing for me
[15:14] <Wimpress> OK.
[15:14] <Wimpress> Going in 3...
[15:14] <Wimpress> 2...
[15:14] <hellsworth> wow those are slow seconds..
[15:14] <hellsworth> :)
[15:14] <didrocks> big ones ;)
[15:14] <Wimpress> Country time ;-)
[15:14] <hellsworth> lol
[15:14] <Wimpress> 1...
[15:15] <Wimpress> #endmeeting
[15:15] <meetingology> Meeting ended Tue Dec 10 15:15:02 2019 UTC.
[15:15] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2019/ubuntu-desktop.2019-12-10-14.31.moin.txt
[15:15] <didrocks> thx!
[15:15] <Wimpress> Thanks everyone
[15:15] <oSoMoN> thanks
[15:15] <hellsworth> thanks!
[15:15] <marcustomlinson> dankie
[15:15] <jibel> thx
[15:15] <oSoMoN> Laney, so the firefox/focal/armhf hang is tracked by bug #1853571
[15:16] <oSoMoN> it appears that what hangs is geckodriver, i.e. the executable used for driving the selenium tests, not firefox itself
[15:16] <oSoMoN> which would explain why I haven't seen any reports of firefox actually not working on armhf
[15:17] <oSoMoN> this is of course something that needs to be investigated and fixed, but realistically I won't get around to it before the holidays
[15:17] <oSoMoN> what's the least bad course of action?
[15:18] <seb128> thx
[15:18] <Laney> is the version already in focal broken in the same way do you know?
[15:18] <oSoMoN> yes
[15:18] <oSoMoN> It migrated after a few retries
[15:19] <Laney> probably means it is ok-ish to add a badtest hint then, since the package in proposed doesn't change the situation
[15:19] <oSoMoN> (I know retrying is almost never the right answer, but it appears that if the test infrastructure isn't under load there's a much higher probability for the test to pass)
[15:20] <oSoMoN> see http://autopkgtest.ubuntu.com/packages/firefox/focal/armhf
[15:20] <Laney> if it's a fails on slow systems thing then stress-ng might help you :-)
[15:20] <oSoMoN> it started failing more reliably on 2019-11-07
[15:23] <oSoMoN> nothing really stands out in the versions of the test dependencies
[15:27] <Laney> yeah I guess it'll take some poking
[15:27] <Laney> you can see the testbed deps too if you download the artifacts
[15:27] <oSoMoN> yeah, I did that
[15:29] <oSoMoN> Laney, there's already a badtest hint for it, the version just needs updating: https://bazaar.launchpad.net/~ubuntu-release/britney/hints-ubuntu/revision/4089
[15:29] <oSoMoN> do you want me to submit a MR for it, or can you go ahead and push it yourself?
[15:30] <oSoMoN> the version in -proposed is 71.0+build5-0ubuntu1
[15:32] <Laney> ok, I can do that
[15:33] <oSoMoN> thanks