User1: good morning desktoppers
User2: good morning
User3: Morning oSoMoN and didrocks
User3: and jibel
User2: hey duflu
User1: salut didrocks
User1: hey duflu
User1: salut jibel
User2: salut oSoMoN
User4: Hi all
User3: Hi jibel
User2: hey jibel
User5: goooood morning desktopers
User5: Trevinho, jamesh, oSoMoN, weekly discourse summary!
User6: thanks for the reminder
User5: np :)
User3: Morning seb128
User5: jamesh,  weekly reminder aside, how are you doing? ;)
User5: hey duflu, how are you today?
User3: seb128, OK. I can build things again, thanks to Laney. How are you?
User5: I'm good thx!
User2: salut seb128
User5: I hope you didn't waste too much time after uninstalling your systems with proposed
User5: lut didrocks, en forme ?
User6: User5 good.  It feels like I've almost got a branch I started 1.5 years ago unblocked, and should be able to progress and get it landed
User6: I've also been experimenting with home brewing kombucha: started with a bottle from the supermarket, and have a decent culture growing after a bit over a week
User2: User5 Ã§a va, et toi ?
User5: jamesh, ah, nice for the branch, is that for dbus activation?
User6: User5 this is daemons running under the user mode instance of systemd, which is a prerequisite for dbus activation
User5: jamesh, I didn't know about kombucha, I just googled it, sounds interesting as a drink :p
User5: jamesh, ah! is that going in the snap source or is that a new component?
User6: User5 part of snapd.  This is a prereq for dbus activation on the session bus, since they want to be able to control lifetime of long running services
User3: seb128, it cost me an hour or two to rebuild the focal system from scratch. Just kept the same home
User6: e.g. kill service on snap removal, maybe restart on upgrade, etc
User6: for the kombucha, I started with a 300mL bottle from the store plus ~ 2 L of extra tea, and have culture about 2 mm thick floating on the top after a week
User5: duflu, k, sorry that focal failed you that well, good to see that it got sorted out quickly at the end though
User5: jamesh, I wonder if we can find kombucha here, I never saw the name before
User7: morning desktoppers
User5: is it popular in Australia?
User5: hey marcustomlinson, how are you?
User7: User5 good thanks, you?
User6: User5 I think it is growing in popularity as an import of US culture (TV, social media, etc).  There are a few brands distributed in the big supermarkets
User5: marcustomlinson, I'm good thanks!
User7: hey jamesh long time
User6: hi marcustomlinson
User7: User6 you well?
User6: yep.  No bush fires in sight :-)
User7: good to hear
User3: Morning marcustomlinson
User7: hey duflu, how's it going?
User3: marcustomlinson, so so. You?
User7: I guess a notch above so so
User7: why only so so?
User7: tuesday blues?
User3: marcustomlinson, just reiterating old branches to satisfy upstream blues
User7: ah those blues :P
User7: well good luck man
User8: hey
User2: hey marcustomlinson, Laney
User3: Morning Laney
User5: hey Laney, how are you today?
User8: hey didrocks duflu seb128
User1: seb128, done, and sorry for the late update
User5: oSoMoN, hey, no worry, thx!
User5: oSoMoN, how are you? made it back without issue? how is the baby/cold going?
User1: seb128, travelling back was uneventful, and the cold is not fully gone but everyone feels much better, so things are going in the right direction
User5: improvement :)
User8: User5 doing alright
User8: want spring now, bored of cold
User8: what about you?
User8: hey oSoMoN
User7: hey Laney didrocks oSoMoN
User5: spring would be nice! I saw the news on TV yesterday about south of France and how they have like 23Â°C atm
 * seb128 wants that
User5: it's freezing cold here this morning (would be better without the wind...)
User8: ð±
User7: the wind is a grumpy old bastard
User8: first couple of daffodils have come up in the garden though
User8: going in the right direction
User3: Ugh, we hit 43 or 44 today depending which suburb you are in
User8: eek
User1: hey Laney, marcustomlinson
User9: good morning desktopers
User1: good morning ricotz
User2: it was 19Â°C yesterday here
User2: hey ricotz
User9: hey oSoMoN didrocks seb128 marcustomlinson duflu
User9: hey Laney
User3: Hi ricotz
User8: moin ricotz
User5: did GNOME changed their process/started to stop building release tarballs?
User8: how's it going?
User8: no
User8: lots missing?
User5: https://ftp.gnome.org/pub/gnome/sources/file-roller/3.35/ doesn't have .90 which we have/jbicha uploaded to Debian
User5: same for https://ftp.gnome.org/pub/gnome/sources/nautilus/3.35/ but .90 was tagged on friday
User5: same https://ftp.gnome.org/pub/gnome/sources/gnome-control-center/3.35/ (where
User5: .90 was uploaded by Robert o focal)
User5: or maybe just that ftp is outdated and I'm looking at the wrong place?
User9: https://download.gnome.org/sources/gnome-control-center/3.35/gnome-control-center-3.35.90.tar.xz
User5: that's a "yes" to my previous question :)
User8: indeed, that server is the one linked from the ftp mails I think
User8: I'm not sure that ftp.gnome.org is meant to be out of date though
User8: would suggest asking in #sysadmin
User5: right, just saw that, I've been using ftp.gnome.org for ever ... I will ask there
User9: Your tarball will appear in the following location on ftp.gnome.org:
User9: https://download.gnome.org/sources/vala/0.47/
User9: haha ^
User9: output of "ftpadmin install ..."
User5: I've asked on #sysadmin, let's see
User8: covering all bases :>
User5: <av> seb128, you should *not* use anything that is not download.gnome.org
User5: <av> ftp.gnome.org is not maintained by GNOME and left as is for backwards compatility
User5: compatibility even
User5: k, that's clear
User8: TIL
 * seb128 updates his bookmarks (& versions' source)
User10: Hello, I need help. There were issues with drivers of video adapter [GeForce GTX 550 Ti]. After the system upgrade I have incorrect screen resolution. I can't set this because `nvidia-driver-390` does not work properly. How I can resolve this problem?
User2: cking: hey! Small question around a zfs patch. We are hit by bug https://github.com/zfsonlinux/zfs/issues/9381 which prevents us to list any history in the grub menu. We saw 2 patches that entered 0.8.3 and in particular https://github.com/zfsonlinux/zfs/commit/5a1bf9e8b17f8414d7bd30a833d4d2a26a1851a6. This one is in the 0.8.3-1ubuntu1. However, picking it from -proposed doesnât work. I
User11: zfsonlinux issue 9381 in zfs "Automount fails when accessing snapshots for root filesystem" [Type: Defect, Closed]
User2: wonder as we donât use a dkms module but a regular module if you copy the code to ther kernel and we need a newer kernel as well?
User2: (my guess and hope is that we are still running our tests with the old kernel having the unpatched zfs module copy)
User2: cking: ok, got it. Installed new kernel from -proposed which was built against the new zfs version and we can now see the snapshots content on root :)
User12: good morning desktopers!
User13: good morning
User1: good morning hellsworth, kenvandine
User12: hi oSoMoN and kenvandine :)
User7: morning hellsworth and kenvandine
User12: hi marcustomlinson !
User2: User5 mind subscribing desktop-packages to https://bugs.launchpad.net/ubuntu/+source/openjpeg2?
User5: didrocks, ah, movement there after years, are we the only ones needing it? (just wonder if it needs to fall on us only)
User5: also meeting time
User2: User5 apparently, we are the only ones, indeed
User5: #startmeeting Desktop Team Weekly Meeting - 2020-02-04
User14: Meeting started Tue Feb  4 14:31:20 2020 UTC.  The chair is seb128. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
User14: Available commands: action commands idea info link nick
* meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/mxaCZTVc | Desktop Team Weekly Meeting - 2020-02-04 | Current topic:
User5: Roll call:  didrocks, duflu (out), heather, jamesh (out), jibel, kenvandine, laney (out), marcustomlinson, oSoMoN, tkamppeter, trevinho, robert_ancell (out)
User12: o/
User1: \o
User7: \o
User15: o/
User2: hey again
User13: \o
User5: good, seems like we have quite some people around :)
User5: let's get started then
User5: #topic rls-bb-bug
* meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/mxaCZTVc | Desktop Team Weekly Meeting - 2020-02-04 | Current topic: rls-bb-bug
User5: no desktop item
User5: http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-tracking-bug-tasks.html
User5: only n-m there than we still didn't sort out
User5: #topic rls-dd-bug
* meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/mxaCZTVc | Desktop Team Weekly Meeting - 2020-02-04 | Current topic: rls-dd-bug
User5: http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-dd-incoming-bug-tasks.html
User8: no d!
User12: oh right!
User5: oh, uh, indeed
User5: #topic rls-ee-bug
* meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/mxaCZTVc | Desktop Team Weekly Meeting - 2020-02-04 | Current topic: rls-ee-bug
User5: thx :)
User5: http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ee-incoming-bug-tasks.html
User5: no desktop item
User5: http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ee-tracking-bug-tasks.html
User5: n-m is the only unassigned which isn't fix commited
User5: #topic rls-ff-bug
* meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/mxaCZTVc | Desktop Team Weekly Meeting - 2020-02-04 | Current topic: rls-ff-bug
User5: http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ff-incoming-bug-tasks.html
User5: bug #1861481
User16: bug 1861481 in accountsservice (Ubuntu) "language-options causes live CD sessions to be untranslated" [High,Confirmed] https://launchpad.net/bugs/1861481
User5: that's a bug leading to the live session not showing translated on some flavors with some locales
User5: I would vote -1 for rls tracking since it's not impacting Ubuntu Desktop itself and only live session/with some locales
User8: doesn't seem rls for our team but you tagged it so maybe can explain why
User5: Gunnar is looking at it and hopefully he gets it fixed though
User8: nod
User5: I think I did that at fosdem because I didn't read properly and though at the time it impact out live session :p
User5: sorry for the noise
User5: tagging -notfixing now
User5: http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-tracking-bug-tasks.html
User5: sorry
User5: http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ff-tracking-bug-tasks.html
User5: that seems buggy?
User7: hmm
User7: yeah looks odd
User8: no bugs \o/
User5: haha
User5: I will ping Brian about it, but let's skip that one for now then
User5: #topic champagne bugs?
* meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/mxaCZTVc | Desktop Team Weekly Meeting - 2020-02-04 | Current topic: champagne bugs?
User5: https://bugs.launchpad.net/ubuntu/+bugs?field.tag=champagne&orderby=-id&start=0
User5: it's still unclear to me how those are supposed to be handled and I feel like that needs to be sorted out before we team review them
User5: I've also tried to at least triage them as them come during the week
User17: o/
User5: hey Wimpress
User5: Wimpress, do you want to weight in about the champagne bugs thing?
User5: unsure what we are expected to be doing there
User5: should we review our set only as we do for other bugs?
User5: is the goal to triage and milestone/discard as we do for rls?
User17: Well, this is new ground. So I think we get to decide how we process this stuff.
User8: I made a proposal in an email but didn't get any feedback on it.
User17: I think it would be good to update which packages are affecvted if that information is not correct.
User17: Oh!
 * Wimpress david74@example.net...
User8: It'll probably be buried
User5: let's do that post meeting? doesn't feel like something we should block the team on atm
User8: But it's basically to treat it like rls-ff-incoming
User8: (1) we already have a process to handle that, and (2) it means the bugs go to the right teams
User8: yes good idea
User5: also as said I triaged the curent list so we don't really have a backlog to deal with, unless we want to do +1/-1 voting
User17: +1 on Laney's proposal
User7: +1
User12: +1
User1: +1
User17: Perhaps tag as rls-ff-incoming as appropriate too
User5: good, let's follow up with Brian/other teams then
User17: Yep
User2: seems we are voting, so +1 :p
User5: Wimpress, let's discuss it in our hangout a bit later?
User8: I was thinking modify the report to look at that tag
User8: yes ok
User17: OK
User5: k, sounds like enough for the topic for now then
User5: thx
User5: #topic update_excuses_by_team.html#desktop-packages
* meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/mxaCZTVc | Desktop Team Weekly Meeting - 2020-02-04 | Current topic: update_excuses_by_team.html#desktop-packages
User8: those LP lists of bugs aren't the best - the script's view is nicer I think
User5: indeed
User5: https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses_by_team.html#desktop-packages
User5: Laney, want to do that one this week or should I do it again since I've been keeping an eye on things recently?
User8: User5 probably you have a better view on this atm
User5: k
User8: I just know that python3 is screwing everything this time
User8: archive breakage of the week
User5: so lot of python3-defaults blocked items there
User17: Do we need any additional info from other teams to unblock that stuff Laney?
User5: a stack of gobject-introspection issues that are going to clear off now that L_aney landed a fixed version and that gcc has been fixed (need retries with right triggers which I'm doing)
User5: tjaalton, are we making any progress on openscad/s390x?
User5: I debugged the network-manager one and upstream has a PR fix up for review which I tested/is working so I expect that to clear off this week
User12: User7 wasn't a new libreoffice uploaded to proposed?
User5: e-d-s regressed on i386 due to an upload not pushed that got reverted, will be fixed
User7: libreoffice had an out-of-space issue crop up during the python3.8 rebuild that's fixed now AND looks like yesterdays build issue with g-i is fixed too, so hopefully that'll unblock a bit
User5: and I think that's basically it
User5: #topic AOB
* meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/mxaCZTVc | Desktop Team Weekly Meeting - 2020-02-04 | Current topic: AOB
User5: any other topic?
User8: User17 proposed? not in particular I don't think
User2: nothing for me
User17: Nothing else from me.
User17: Just to say we had a catch up with the Yaru team last night.
User5: k, just a reminder that ff is approching then
User17: All good there.
User17: In shape for 20.04.
User8: planning a release soon?
User17: Need to merge some upstream changes, then I think so.
User8: speaking of
User5: it looks like we didn't land much feature work yet so probably a good time to increase focus on getting things lined up
User8: User15 some gnome-shell/mutter verification still to do fyi
User5: Trevinho, and please start or 3.35.90 whenever you can
User15: ack
User5: I will do some of the apps/initial setup/etc in the next days
User18: User5 no, I'm not able to launch a s390x instance on canonistack, filed an issue but it's still open
User5: Wimpress, ^ are you maybe able to raise priority of that RT in the queue?
User15: User8 as per the SRU I'm waiting on feedback though (https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1845281/comments/18)
User16: Ubuntu bug 1845281 in mutter (Ubuntu Eoan) "gnome-shell crashed with SIGABRT in __GI_raise() from __GI_abort() from g_assertion_message() from g_assertion_message_expr() from meta_window_get_workspaces() [assertion failure "code should not be reached"]" [Medium,Fix committed]
User17: User18 Please forward me the RT details via email, and I'll see what I can do.
User5: Wimpress, thx
User5: ok, let's call it a wrap, those discussions can continue post meeting
User5: thanks team!
User5: #endmeeting
* meetingology changed the topic of #ubuntu-desktop to: Home of the Desktop Team, https://wiki.ubuntu.com/DesktopTeam | For help or questions, try #ubuntu | Work (read-only for non-developers): https://trello.com/b/mxaCZTVc
User14: Meeting ended Tue Feb  4 14:58:30 2020 UTC.
User14: Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2020/ubuntu-desktop.2020-02-04-14.31.moin.txt
User1: thanks
User13: thanks
User2: thx!
User18: User17 it's #123981, is that enough?
User7: thanks
User5: Laney, speaking of SRU, the new glib/eoan SRU is still having unhappy i386 tests :-(
User2: User17 User5 also, if you can get more detailed on a ETA on security review for zsys, that would be great. FF is approaching and no movement still
User18: User5 but I think we should just badtest that one, s390x is the only big-endian arch we have
User5: didrocks, @openjpeg, looks like recent nagers have been for imagemagick which is a foundation package :)
User17: User18 Thanks.
User8: User15 don't wait forever, also it's OK if it's not a regression
User5: tjaalton, talk to Laney, he wanted to see some evidence/understanding of the problem before skipping the test
User18: User5 I've pushed mesa 20.0-rc1 to experimental and enabled build-time tests, to see where they fail and how
User2: User5 I think it's not part of the MIR team to decide that, so I will let you and foundation discuss, but we need a team subscriber
User18: well, this should verify if llvmpipe tests fail on all BE archs
User5: didrocks, sure, I'm adding desktop for now, we can still trade/argue with them later
User2: yep :p
User17: User18 Have you spoken to xnox about s390?
User5: didrocks, done
User17: He maybe able to assist.
User2: but ofc security review still, so not close to be done
User2: thanks seb128
User17: User2 Has the zsys MIR review happened?
User2: User17 it was started said the card, but no result, no movement
User2: on the security side
User2: hence my request :p
User17: OK, added to my list of things to chase again.
User2: thx
User18: User17 yes
User2: User17 FTR, the security review was requested last August :p
User17: I know.
User8: User5 will look into that i386 thing tomorrow probably
User8: forgot about it so thx for the reminder
User8: laney@nightingale> openssl s_client -connect appstream.ubuntu.com:443 </dev/null 2>|/dev/null | openssl x509 -text | grep -A 1 'Subject Alternative Name'                                                                         ~
User8: X509v3 Subject Alternative Name:
User8: DNS:appstream.ubuntu.com
User8: can haz ssl
User8: IS gently spanked me for not having it set up
User19: I see your SSL and raise you a TLS
User8: YOLO: FOMO: LMAO!
User19: so, I managed to figure out what is happening with my stack overflow in Xorg, though not how to fix it or whether it is actually broken - https://paste.ubuntu.com/p/DFzpnysmfd/ `driBindContext` calls through to `dri2_drawable_get_buffers` which then calls Xorg's (not mesa's for some reason?) `dri2GetBuffersWithFormat` which then recalls
User19: `driBindContext` (it thinks the context is changed by `DRI2GetBuffersWithFormat` so it tries to reset the context and recall `DRI2GetBuffersWithFormat`) and the recursion continues until stack overflow
User19: tjaalton, possibly something you can help me with?
User19: reference for the offending logic that causes the recursion: https://gitlab.freedesktop.org/xorg/xserver/blob/master/glx/glxdri2.c#L710
User9: seb128, I guess syncing gexiv2 is possible now
User18: User19 best to file upstream
User19: thanks, tjaalton, I've filed it under Mesa, though I'm not sure whether it is Mesa or Xserver that the issue lies within: https://gitlab.freedesktop.org/mesa/mesa/issues/2469
User11: Mesa issue 2469 in mesa "Infinite recursion with xserver and Indirect GLX (specific to a single third-party library)" [Opened]
User20: seb128, do you know of an i386/budgie issue? Seems to be breaking the g-c-c autopkg tests.
User20: aha, we don't seem to build for i386 g-c-c in focal, perhaps that's the issue.
User5: robert_ancell, ask vorlon about it, I think it's a valid one to declare invalid on i386
User5: but Steve is the one who knows how to handle those
User20: seb128, thanks
ubuntu-desktop
Ubuntu IRC