[05:32] <duflu> Trevinho, where in the world are you at the moment?
[05:33] <duflu> Trevinho[3v1n0], ^
[06:01]  * zyga opened https://gitlab.gnome.org/GNOME/gdm/issues/483 
[06:01] <gitbot> GNOME issue 483 in gdm "Ubuntu 19.04 login screen never appears when using the Nvidia driver" [Opened]
[06:03] <duflu> Thanks
[06:03] <duflu> ... zyga
[06:20] <didrocks> good morning
[06:20] <jibel> Hi didrocks
[06:21] <didrocks> salut jibel
[06:30] <duflu> Morning didrocks and jibel
[06:30] <duflu> biab
[06:36] <didrocks> hey duflu
[06:37] <pieq> zyga, I didn't witness this when testing 19.04, but I was using laptops with SSDs...
[06:37] <zyga> pieq: yeah, I bet this is a race and using a hdd is relevant
[06:38] <pieq> zyga, this doesn't happen with open source drivers (nouveau) instead of nvidia's?
[06:38] <zyga> I did not check
[06:39] <zyga> my whole point of using the hardware and nvidia is to work with snapping proprietary driver
[06:39] <zyga> I can check if that is someone wants to try to debug the core issue
[06:47] <jibel> OOC, are you reproducing this bug with the snapped version of the driver or the deb?
[06:47] <jibel> zyga, ^
[06:48] <zyga> jibel: with the deb
[06:48] <jibel> k
[06:48] <zyga> jibel: the snap is not a factor in this, it happened straight out of vanilla install
[06:51] <jibel> yeah, was just curious
[06:52] <jibel> pieq, would you have a workstation with an nvidia graphics card on which you could run lspci -n and paste the output?
[06:52] <jibel> eg not a laptop with intel+nvidia
[06:54] <oSoMoN> good morning desktoppers
[06:55] <Trevinho> duflu: Oaxaca, Mexico
[06:56] <oSoMoN> hey duflu, Trevinho
[07:01] <pieq> jibel, nothing around at the moment, let me check
[07:03] <oSoMoN> salut pieq, jibel
[07:03] <jibel> pieq, it is not urgent, I'd like to know the subclass of the card if it's 300 or 302
[07:04] <jibel> hi oSoMoN
[07:04] <pieq> salut oSoMoN
[07:04] <jibel> s/hi/bonjour/ :)
[07:08] <pieq> jibel, this is what I get on a workstation with Nvidia GV100 GPU: https://pastebin.ubuntu.com/p/jf4SQfjqRJ/
[07:10] <jibel> pieq, thanks
[07:10] <pieq> but I don't see the subclass (I took this out of a Checkbox session lspci attachment, not sure if it's -n)
[07:10] <pieq> (it's not)
[07:10] <pieq> :D
[07:10] <jibel> pieq, it's fine, it's 0300
[07:16] <didrocks> salut oSoMoN
[07:19] <oSoMoN> salut didrocks
[07:21] <GunnarHj> Laney: Thanks for sponsoring g-c-c!
[07:21] <GunnarHj> Laney: Yes, the current handling of modifiers isn't ideal, even if affected labels are distinguishable in Ubuntu. Any thoughts on approach/hack as regards translations of such strings? I suppose it should better be done upstream if at all.
[07:23] <seb128> good morning desktopers
[07:23] <oSoMoN> salut seb128
[07:23] <seb128> lut oSoMoN, en forme ?
[07:23] <oSoMoN> oui, et toi?
[07:25] <didrocks> salut seb128
[07:25] <seb128> oSoMoN, en forme :)
[07:25] <seb128> lut didrocks
[07:26] <GunnarHj> Good morning all!
[07:27] <duflu> Morning oSoMoN, seb128, GunnarHj
[07:28]  * duflu checks
[07:28] <duflu> And good morning Trevinho
[07:37] <seb128> trevinho, https://bileto.ubuntu.com/#/ticket/3704 ... can we just sync https://packages.qa.debian.org/g/gnome-shell-extension-appindicator/news/20190425T130319Z.html instead?
[07:38] <duflu> He's in Mexico so I assume might almost be bed time :)
[07:38] <Trevinho> it is :)
[07:38] <Trevinho> seb128: yes, now that it's released
[07:38] <Trevinho> syncing that is fine
[07:38] <Trevinho> for sru might still apply the other one though
[07:38] <seb128> right
[07:39] <seb128> thx trevinho
[07:39] <seb128> and good night :)
[07:39]  * Trevinho hides in bed :)
[07:39] <Trevinho> thanks
[07:39] <Trevinho> ah, someone could publish the shell stacks though
[07:40] <seb128> I will let Laney review those :)
[07:43] <seb128> andyrock, jamesh, tkamppeter, you need to post your weekly summary on the hub
[07:46] <didrocks> I think we should go back to everyone posting on Monday
[07:47] <didrocks> seems like people are slowly starting to post on Tuesday again
[07:49] <seb128> I don't think we ever moved from posting on monday?
[07:49] <didrocks> well, I mean encourage people to do it again
[07:49] <seb128> it's just post release and it was a week with holidays/long w.e for some etc
[07:49] <seb128> travelling for others as well
[07:50] <seb128> but yeah, that's why I pinged today, trying to remind people to go back on schedule :)
[07:50] <seb128> (me included :p)
[07:50] <didrocks> looks like it :p
[07:51] <didrocks> I should have pinged you like the only time in a year I didn't post on Monday :p
[07:51]  * didrocks writes to check every Tuesday morning now ;)
[07:51] <seb128> haha, fair enough :)
[08:02] <Laney> hi there
[08:02] <marcustomlinson> good morning
[08:02] <oSoMoN> hello Laney, marcustomlinson
[08:02] <didrocks> hey Laney, marcustomlinson
[08:03] <seb128> hey Laney marcustomlinson, how are you today?
[08:04] <marcustomlinson> Pretty good :) oSoMoN sponsored my first upload to archive yesterday
[08:04] <seb128> congrats! :)
[08:21] <Laney> hey oSoMoN didrocks seb128 marcustomlinson
[08:21] <Laney> doing alright, nice climbing session yesterday
[08:21] <Laney> how are you?!?!?!
[08:23] <seb128> I'm good!
[08:24] <seb128> didn't do anything fancy though, I wish I could play tennis this week but it's not likely, hopefully next
[08:26] <Laney> someone sick?
[08:28] <seb128> no, just in north of France this week (gf familly) and I don't have a club or someone to play with here...
[08:29] <Laney> ohhh
[08:34] <duflu> Morning Laney
[08:34] <duflu> and morning willcooke
[08:35] <willcooke> hihi
[08:35] <willcooke> marcustomlinson, good news!  You should now be a member of the Canonical group in Trello
[08:35] <willcooke> mad times ahead
[08:36] <marcustomlinson> indeed I am :)
[08:36] <marcustomlinson> weird though that kenvandine and jamesh are not :P
[08:37] <Laney> please escort them off the premises
[08:37]  * Laney nods gravely towards duflu 
[08:38] <duflu> gravely?
[08:38] <Laney> It was that or sagely
[08:38] <Laney> and I did briefly consider savagely but it's too early for that
[08:38] <Laney> solemnly would also work, but I'll save that treat for another day
[08:39] <Laney> vigorously after I've had an espresso
[08:39] <Laney> etc
[08:39] <duflu> Careful with your neck
[08:39] <duflu> Presumably you only have one
[08:40]  * duflu waves instead
[08:44] <Laney> zyga: want to try something? (maybe in #gdm / gimpnet so that upstream can see?)
[08:44] <zyga> Laney: hold on, let me join that network
[08:45] <Laney> thx
[08:47] <zyga> Laney: I'm there
[09:42] <andyrock> good morning!
[09:43] <Laney> 😭 hi andyrock 😭
[09:44] <andyrock> 😭
[09:51] <seb128> hey andyrock
[09:51]  * seb128 hugs andyrock
[09:52]  * andyrock hugs the desktop team and all the ubuntu friends
[10:01] <duflu> Morning andyrock
[10:01] <duflu> 🤗
[10:02] <duflu> The hug emoji is somewhat confusing
[10:02] <duflu> 😭
[10:11] <seb128> duflu, do you have a special way to triage/keep track of gnome-shell bugs that might be worth a SRU to bionic? e.g bug #1825547
[10:11] <ubot5`> bug 1825547 in gnome-shell (Ubuntu) "incorrect vpn status" [Low,Fix released] https://launchpad.net/bugs/1825547
[10:11] <duflu> seb128, no I wait for a bionic bug report unless it is critical
[10:12] <duflu> If there are none then there may be a reason for that you have overlooked
[10:12] <duflu> so targeting an SRU might not be needed
[10:13] <seb128> inf act that is fixed in the SRU that recently landed
[10:29] <tkamppeter> seb128, weekly summary is posted now.
[10:30] <seb128> tkamppeter, thx, please try to remember to post on monday (or earlier)
[10:43] <tkamppeter> seb128, I have all the time done it "before the meeting", when is the typical reading time by you or whover chairs the meeting?
[11:32] <seb128> tkamppeter, no, we said (in Malta or was it the one before?) that they need to posted by monday evening so team members in australia or new zealand can read them before the meeting and post comments/questions if they have some
[11:33] <seb128> tkamppeter, if you post them on 10am european time on tuesday it's like 9pm for Robert and he hasn't a chance to comment before the meeting
[11:33] <seb128> since he's already done with work for the day
[11:39] <seb128> xnox, thx for that community hub e-cycle plans post, it's useful!
[11:39] <xnox> seb128, well, also awaiting for my ubuntu-devel-announce post to be published to the mailing list
[11:40] <xnox> seb128, as one wise man once said (willcooke) we get better engagement with emojis!
[11:40] <seb128> :-)
[11:40] <willcooke> :D
[11:41] <didrocks> ￼️ golang updated to 1.12. \o/
[11:41] <didrocks> phew, having 1.10 in the archive starts to be annoying
[11:41] <didrocks> (/me secretly hope 1.13 is released before FF and we can update to it)
[12:00] <xnox> didrocks, pester mwhudson about that =)
[12:01] <didrocks> xnox: I'll gladly do it :)
[13:29] <willcooke> bah
[13:29] <willcooke> as I knew would happen, the calendar didnt remind me and so now I am unprepared for this meeting.
[13:29]  * willcooke wings it
[13:30] <willcooke> #startmeeting Desktop Team Meeting - 2019-04-30
[13:30] <meetingology> Meeting started Tue Apr 30 13:30:04 2019 UTC.  The chair is willcooke. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[13:30] <meetingology> Available commands: action commands idea info link nick
[13:30] <didrocks> hey
[13:30] <Trevinho> hello
[13:30] <willcooke> Roll call: andyrock, didrocks, duflu (out), jamesh (out), jibel, kenvandine, laney, marcustomlinson, oSoMoN, seb128, tkamppeter, trevinho, robert_ancell (out)
[13:30] <seb128> hey
[13:31] <andyrock> o/
[13:31] <kenvandine> o/
[13:31] <marcustomlinson> \o
[13:31] <willcooke> Bad times:  Last meeting with andyrock 😭
[13:32]  * kenvandine cries
[13:32] <Trevinho> 😭😭😭😭😭
[13:32] <andyrock> 😭
[13:32] <willcooke> Bye andyrock, we will all miss you.  We got you this cake:  🎂
[13:32] <kenvandine> cake!
[13:32] <andyrock> I'll miss you all too :D
[13:32] <willcooke> and we all clubbed together and bought you a helicopter:  🚁
[13:33] <marcustomlinson> I already missed you andyrock
[13:33] <seb128> :(
[13:33] <oSoMoN> come back soon!
[13:33] <willcooke> Good times:  My first meeting with marcustomlinson 🚀🚀🚀
[13:33] <Trevinho> no the helicopter is what he has to buy us...
[13:33] <willcooke> :d
[13:33] <willcooke> D
[13:33] <didrocks> we are going to miss you andyrock
[13:34] <willcooke> ok, lets whizz through the bugs
[13:34] <willcooke> I have some AOB which might be interesting
[13:35] <willcooke> #topic Bionic bugs
[13:35] <willcooke> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-incoming-bug-tasks.html
[13:35] <willcooke> incoming is clear
[13:35] <seb128> willcooke, there is one listed here
[13:35] <willcooke> oh boy
[13:36] <willcooke> thanks seb128
[13:36] <seb128> :)
[13:36] <seb128> looks like it's assigned to Trevinho/being handled, so probably just a matter of untagging
[13:36] <willcooke> donr
[13:36] <willcooke> e
[13:36] <Trevinho> yeah added to know weather was the case to consider is rls
[13:36] <willcooke> for tracking there is this one:
[13:36] <willcooke> https://bugs.launchpad.net/ubuntu/+source/libnfs/+bug/1746598
[13:36] <ubot5`> Ubuntu bug 1746598 in libnfs (Ubuntu Cosmic) "[MIR] libnfs" [High,In progress]
[13:37] <willcooke> Trevinho, +1, its important as it can lock up the shell, useful to fix
[13:37] <willcooke> plus andyrock did all hard work
[13:37] <willcooke> ;)
[13:37] <seb128> willcooke, I've assigned the libnfs one to Eric who was driving that conversation
[13:37] <willcooke> ah thx
[13:38] <willcooke> #topic Cosmic Bugs
[13:38] <willcooke> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-cc-incoming-bug-tasks.html
[13:38] <willcooke> Really is clear (even ctrl-f desktop this time)
[13:38] <seb128> :)
[13:39] <willcooke> There's this one which is unassigned: https://bugs.launchpad.net/ubuntu/+source/saaj/+bug/1814133
[13:39] <ubot5`> Ubuntu bug 1814133 in virtualbox-hwe (Ubuntu Cosmic) "update to openjdk 11 in 18.04 LTS" [Undecided,New]
[13:39] <willcooke> which is probably in our list for LO
[13:39] <willcooke> and that looks like its in hand/done
[13:40] <oSoMoN> yeah, the LO part is done
[13:40] <willcooke> Oh, we have libnfs and fonts-liberation2
[13:40] <willcooke> seb128 - do I remember you were looking at the nfsone?
[13:41] <oSoMoN> not sure where the fonts-liberation task comes from…
[13:41] <oSoMoN> I'll ask do_ko after the meeting
[13:41] <willcooke> thx
[13:42] <willcooke> and then there's this one:
[13:42] <willcooke> https://bugs.launchpad.net/ubuntu/+source/cups/+bug/1822062
[13:42] <ubot5`> Ubuntu bug 1822062 in cups (Ubuntu Eoan) "Race condition on boot between cups and sssd" [Medium,In progress]
[13:42] <willcooke> which looks like a cups issue?
[13:42] <seb128> willcooke, that one was also in the bionic report
[13:42] <seb128> it looks like it's being handled by the sustain team already
[13:42] <seb128> I would just assign all the lines to Victor
[13:43] <seb128> or Eric
[13:43] <willcooke> ok, I will do that after the meeting
[13:43] <seb128> willcooke, nfs is fix commited or are you talking about another line?
[13:43] <seb128> (we skip over those usually since that's = handled already)
[13:43] <tkamppeter> This one is already assigned to Victor.
[13:43] <willcooke> I was talking about the Eric one
[13:43] <willcooke> my bad
[13:43] <willcooke> oki, so that all looks ok then
[13:43] <willcooke> #topic Disco Bugs
[13:43] <seb128> the libnfs one is the same as bionic, right
[13:44] <willcooke> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-dd-incoming-bug-tasks.html
[13:44] <willcooke> All already assigned.  Except that we should reassign the tracker-miners one probably
[13:45] <seb128> we need to +1/-1 serie nominations though
[13:45] <tdaitx> willcooke: sorry to intrude, 1814133 is a bug that we used to track the openjdk-11 transition to bionic, please don't reuse it, create a new bug instead, thanks ;-)
[13:45] <andyrock> the fix is already upstream
[13:45] <andyrock> for tracker-miners
[13:45] <seb128> I vote +1 for the tracker one
[13:45] <seb128> it's fine to have andy assigned, he did the work, I can do the uploading
[13:45] <andyrock> iirc I linked the fix in the bug report
[13:45] <willcooke> ok
[13:46] <willcooke> next:
[13:46] <andyrock> seb128: let me know if you need some help with that, the fix targeted tracker 2.2 but it should apply without problems in 2.1.8
[13:46] <seb128> bug #1823464 looks like it just needs untagging since it got accepted in a previous meeting
[13:46] <ubot5`> bug 1823464 in gnome-keyring (Ubuntu Disco) "gnome-keyring ftbfs in disco (s390x only)" [High,New] https://launchpad.net/bugs/1823464
[13:46] <willcooke> done
[13:46] <seb128> willcooke, we still didn't review the list to accept/reject the items
[13:47] <seb128> the list is still going to be in that state next week if we don't do that...
[13:47] <willcooke> that's what we're doing now?
[13:47] <seb128> incoming is about ack/nack
[13:47] <willcooke> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1813716
[13:47] <ubot5`> Ubuntu bug 1813716 in gnome-shell (Ubuntu) "gnome-shell crashed with SIGSEGV in meta_x11_display_get_xdisplay → detach_pixmap → meta_surface_actor_x11_dispose → g_object_unref → ObjectInstance → → release_native_object" [High,In progress]
[13:47] <Trevinho> compositore crash is instead something happening in restart but is our top in errors.u.c. However not upstreamed yet. But got a +1 review so far.
[13:47] <seb128> ah, I though your next was another item
[13:47] <willcooke> +1 for that shell crash
[13:47] <seb128> +1 for rls
[13:48] <willcooke> motion carried
[13:49] <willcooke> +1 for ee too then
[13:49] <seb128> (still about bug #1823464, kenvandine can you talk to jamesh about it, he seems to have been ignoring him, I wouldn't be surprised he overlooked the bug assignement/launchpad email)
[13:49] <ubot5`> bug 1823464 in gnome-keyring (Ubuntu Disco) "gnome-keyring ftbfs in disco (s390x only)" [High,New] https://launchpad.net/bugs/1823464
[13:49] <seb128> willcooke, +1
[13:49] <kenvandine> i emailed him about it and never heard back
[13:49] <kenvandine> it's on my list for our 1:1 this week
[13:50] <Laney> Trevinho: get that merged now, we can include it in this upload I am doing atm
[13:50] <seb128> kenvandine, thx
[13:50] <willcooke> next: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1826933
[13:50] <ubot5`> Ubuntu bug 1826933 in gnome-shell (Ubuntu) "gnome-shell crashes in meta_monitor_mode_get_resolution -> calculate_scale -> meta_monitor_calculate_mode_scale derive_calculated_global_scale -> meta_monitor_manager_rebuild_logical_monitors_derived" [Medium,In progress]
[13:50] <willcooke> Not sure how that manifests itself
[13:51] <Trevinho> Laney: no maintainer ack yet, I expect can involve some more time then
[13:51] <Laney> ask
[13:51] <Laney> (you got a comment from Carlos)
[13:52] <willcooke> Trevinho, re: #1826933 are you +1 on rls tagging that?  Is it a big deal?
[13:52] <willcooke> shell crash, sounds like it is
[13:53] <willcooke> anyone got any feelings about it?
[13:53] <willcooke> +1 from me
[13:53] <seb128> +1, sounds like worth fixing
[13:53] <Laney> it's going to be in the upload
[13:54] <Laney> just nominate it, that is needed for the SRU anyway
[13:54]  * Laney wouldn't have tagged that one
[13:54] <Trevinho> willcooke: yes, I've already proposed the fix in the merge Laney is handling
[13:54] <willcooke> k, thx
[13:55] <willcooke> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-dd-tracking-bug-tasks.html
[13:55] <willcooke> DD tracking is actually all up to date, the report is just a little old
[13:56] <seb128> willcooke, bug #1826182 has no assignee for disco?
[13:56] <willcooke> #topic Eoan bugs
[13:56] <ubot5`> bug 1826182 in mutter (Ubuntu Eoan) "[DisplayLink][fixed upstream] GNOME libmutter crash on hotplugging a dock with a monitor" [High,In progress] https://launchpad.net/bugs/1826182
[13:56] <willcooke> Trevinho, can you take that one>? ^
[13:57] <Trevinho> willcooke: already taken too
[13:57] <seb128> trevinho, no you didn't, or launchpad disagreed
[13:57] <willcooke> he did now
[13:57] <seb128> ah, now
[13:57] <willcooke> since I updated it
[13:57] <willcooke> :)
[13:57] <seb128> when he said so it was still not commited :;p
[13:57] <seb128> thx
[13:57] <Trevinho> seb128: I meant it's in the upload IIRC.
[13:57] <willcooke> Looks like the ee reports are missing, anyone know who I should ask to fix that?
[13:58] <seb128> let me ask bdmurray
[13:58] <Trevinho> willcooke: I was about asking the same
[13:58] <willcooke> thanks seb128
[13:58] <willcooke> Is there another way to see them easily?
[13:58] <willcooke> them = bugs
[13:58] <jibel> launchpad advanced search
[13:58] <seb128> https://bugs.launchpad.net/ubuntu/+bugs?field.tag=rls-ee-incoming
[13:59] <Trevinho> also andyrock had an issue when they were added to incoming but... (can't remember all the conditions)
[13:59] <willcooke> https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1798790
[13:59] <ubot5`> Ubuntu bug 1798790 in mutter (Ubuntu) "Ubuntu login screen never appears when using the Nvidia driver (and setting WaylandEnable=false fixes it)" [High,Confirmed]
[13:59] <andyrock> if the bug if fix-released for every target and you tag rls-xx-incoming
[13:59] <andyrock> the bug will not be added to the list
[14:00] <seb128> willcooke, +1 to accept, Laney redirected zyga to upstream earlier
[14:00] <andyrock> I think this would be useful to target as rls-bug something we want to sru
[14:00] <Laney> dunno that the first follows on from the second
[14:01] <willcooke> Seems like an important one to fix, so I'd be +1
[14:01] <didrocks> I need to find if that's the same bug I raised a cycle ago upstream
[14:02] <willcooke> so do we pass that one for now?
[14:02] <seb128> I vote +1 to nominate it
[14:02] <seb128> dunno about others
[14:02] <didrocks> no, that was a different bug
[14:02] <seb128> it seems an important issue, especially as we get closer from the next LTS
[14:02] <didrocks> +1 for me
[14:02] <willcooke> ok, done
[14:02] <seb128> Laney, you hinted zyga toward upstream, can you maybe own it? you also have some gdm experience
[14:03] <Laney> shrug
[14:03] <seb128> the other one would probably be Trevinho who is quite loaded with other bugs atm
[14:03] <Laney> guess so
[14:03] <willcooke> https://bugs.launchpad.net/ubuntu/+source/duplicity/+bug/1440372
[14:03] <ubot5`> Ubuntu bug 1440372 in duplicity (Ubuntu) "please port duplicity to Python3" [Medium,In progress]
[14:03] <seb128> sorry...
[14:03] <seb128> thx!
[14:03] <seb128> willcooke, +1 to accept, I can own it
[14:03] <Laney> I was helping to triage, don't like that this leads to owning in the end
[14:03] <Laney> but maybe it makes separate sense
[14:03] <seb128> Laney, I was going to ask you anyway, I put that on my notes yesterday
[14:03] <seb128> so don't feel like the triaging help is what hinted the outcome
[14:04] <seb128> I think we have you and, Trevinho basically who understand gdm's code atm
[14:04] <seb128> and Trevinho is too busy
[14:04]  * Laney isn't busy?
[14:04] <seb128> too
[14:04] <Laney> anyway, seems fine
[14:04] <seb128> well, I try to balance
[14:04] <willcooke> https://bugs.launchpad.net/ubuntu/+source/thunderbird/+bug/1801383
[14:04] <ubot5`> Ubuntu bug 1801383 in linux (Ubuntu) "the WifiSyslog apport hook (used in firefox/tb) includes SSID informations" [Undecided,Confirmed]
[14:04] <seb128> thx
[14:04] <willcooke> oSoMoN, you did the ffox part for that ^
[14:04] <oSoMoN> that one is for me
[14:05] <willcooke> for tbird too?
[14:05] <oSoMoN> yes
[14:05] <seb128> thxc oSoMoN
[14:05] <willcooke> thx
[14:05] <willcooke> ok, afaict thats it for us
[14:06] <jibel> there is bug 1826844 I'd like to have fixed
[14:06] <ubot5`> bug 1826844 in nvidia-graphics-drivers-390 (Ubuntu) "nvidia-drivers-* are not on the ISO" [Undecided,New] https://launchpad.net/bugs/1826844
[14:06] <jibel> it's a matter of adding them to ship-live but I'd like to sure there is no issue with the license
[14:06] <willcooke> jibel, you want me to work on the licensing question?
[14:07] <jibel> willcooke, if you want, sure
[14:07] <seb128> trello card material rather than rls bug?
[14:07] <jibel> they would be on the pool of the iso not in the squashfs
[14:07] <jibel> k, I'll add a card too
[14:07] <willcooke> yeah, +1 for trello
[14:07] <willcooke> and to untag
[14:07] <jibel> can I have both
[14:07] <jibel> ? :)
[14:08] <jibel> I love bugs
[14:08] <willcooke> you can, but should you?
[14:08] <willcooke> all Im talking about here is untagging it from e
[14:08] <willcooke> the bug can and should still exist
[14:08] <jibel> target it
[14:08] <seb128> well we don't even know if it's valid
[14:08] <seb128> until we resolve the license question
[14:09] <willcooke> not sure about this one, doesnt seem like a release blocker to me
[14:09] <willcooke> it's been broken for ages
[14:09] <willcooke> I totally think we should fix it though
[14:10] <seb128> I don't know enough to understand how new the issue is and if it's a regression and when it started
[14:10] <seb128> yeah, same
[14:10] <Laney> not everything has to be a release bug
[14:10] <Laney> NEXTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTTT
[14:10] <seb128> I would vote -1 for rls
[14:10] <willcooke> that ^
[14:10] <seb128> assign + trello
[14:10] <seb128> imho
[14:10] <willcooke> I'm taking it
[14:10] <willcooke> Right, I propose that's the end of the bugs
[14:11] <willcooke> seb128, did I miss anything
[14:11] <seb128> not that I can see
[14:11] <willcooke> ok
[14:11] <willcooke> thx
[14:11] <willcooke> #topic AOB
[14:11] <willcooke> I have a topic
[14:11] <willcooke> More bugs!!!
[14:11] <seb128> btw bdmurray replied, he's doing the changes to get the rls-ee reports
[14:11] <willcooke> woot
[14:11] <seb128> :)
[14:12] <seb128> more bugs? :-
[14:12] <seb128> :-(
[14:12] <willcooke> So, off the back of the OEM meetings last week we will have some more bugs coming our way via the OEM team
[14:12] <willcooke> at the moment, I meet with the OEM team once every two weeks.  Thats been going fine, but can be a bottle neck and the bus factor
[14:13] <willcooke> so as well as that meeting, they will also start tagging bugs that they think are important
[14:13] <willcooke> I think we should do the same process as for rls bugs
[14:13] <willcooke> so next week, or maybe the week after, I'll add a new section to the meeting where we can look at the OEM bugs and assign them as needed
[14:13] <Trevinho> can't just they use the same tagging and assign to oem project too?
[14:14] <seb128> ?
[14:14] <seb128> I don't understand, I though we asked them to use the rls-nn-incoming process a while ago when we discussed oem bugs
[14:14] <seb128> wouldn't it make more sense to just use the same process rather than inventing a new one?
[14:15] <willcooke> quite possibly
[14:15] <willcooke> I'm going to do a few dummy runs with them, so I'll try and do it with rls bugs as normal and see how it goes
[14:16] <didrocks> shouldn't there be a way to know it's coming from oem?
[14:16] <didrocks> (so maybe an additional tag + rls- ones)
[14:16] <didrocks> or oem-priority
[14:16] <Trevinho> yeah indeed adding the oem project or a tag and then underline it in the rls page would be nice
[14:17] <willcooke> ok, lets try that and see how it goes, we can tweak as we go
[14:17] <seb128> oem has way to let us know
[14:17] <seb128> description
[14:18] <seb128> oem-priority
[14:18] <seb128> comments
[14:18] <seb128> I don't think that's going to be a problem
[14:18] <seb128> but yeah, let's iterate and see if we have practical issues
[14:18] <willcooke> yeah
[14:18] <willcooke> good
[14:18] <willcooke> ok, that's all I got for now
[14:18] <willcooke> Anyone else?
[14:19] <seb128> not really
[14:19] <willcooke> going once
[14:19] <seb128> I wonder if we should start gettting organized for next cycle
[14:19] <seb128> but that's probably good via email/next meeting
[14:19] <willcooke> seb128, yeah you and I should talk this week
[14:19] <willcooke> I was planning to do it in the meeting on Weds, but...
[14:19] <seb128> I did email my team asking people to start thinking about that
[14:20] <willcooke> so Thursday will have to be the day
[14:20] <seb128> and try to deal with SRU/look at tech debt and how to reduce it meanwhile
[14:20] <seb128> but yeah
[14:20] <seb128> sry :)
[14:20] <kenvandine> +1
[14:20] <willcooke> we picked up some small work from Taipei, nothing major
[14:20] <seb128> worker day, celebrated by not working! :)
[14:20] <willcooke> typical French
[14:20] <willcooke> XD
[14:20] <willcooke> ok, lets wrap.
[14:20] <willcooke> longest meeting ever
[14:21] <willcooke> #endmeeting
[14:21] <meetingology> Meeting ended Tue Apr 30 14:21:01 2019 UTC.
[14:21] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2019/ubuntu-desktop.2019-04-30-13.30.moin.txt
[14:21] <willcooke> thanks all
[14:21] <Trevinho> thanks
[14:21] <didrocks> thx
[14:21] <oSoMoN> thanks
[14:21] <andyrock> thx! and thx again for everything!
[14:22] <seb128> thx
[14:22] <didrocks> thanks andyrock, don't be a stranger
[14:22] <andyrock> sure! :D
[14:42] <oSoMoN> doko, tdaitx: why is there a fonts-liberation2 task on bug #1814133 ?
[14:42] <ubot5`> bug 1814133 in virtualbox-hwe (Ubuntu Cosmic) "update to openjdk 11 in 18.04 LTS" [Undecided,New] https://launchpad.net/bugs/1814133
[15:14] <seb128> trevinho, could you look at bug #1826797?
[15:14] <ubot5`> bug 1826797 in gnome-shell (Ubuntu) "[regression] gnome-shell crashes if booted with the monitor off ["JS ERROR: TypeError: monitor is null" from _updateContentScale@resource:///org/gnome/shell/ui/magnifier.js:174:9]" [Medium,Triaged] https://launchpad.net/bugs/1826797
[15:38] <tdaitx> oSoMoN: because it was one of the packages we updated, probably libreoffice
[15:39] <tdaitx> *probably a dependency of libreoffice
[15:45] <oSoMoN> tdaitx, libreoffice and libreoffice-common both recommend fonts-liberation2, but that doesn't imply that fonts-liberation2 should be rebuilt, right?
[15:46] <tdaitx> oSoMoN: I don't know, I haven't look into that (doko worked on those packages), bionic had fonts-liberation2 2.00.1-5 and it was updated to 2.00.1-7~18.04.2 during the transition
[15:49] <oSoMoN> it was apparently only a no-change upload targetting the security pocket
[15:50] <oSoMoN> tdaitx, do you know why there are cosmic tasks for some of the packages in that bug report?
[15:50] <tdaitx> oSoMoN: because we had to update packages on Cosmic as well, since a few versions on bionic ended up being higher than cosmic
[15:52] <tdaitx> and when the approval to -proposed happens a task is created for each "bug fixed" in the changelog for that release
[15:58] <oSoMoN> ack, that makes sense
[15:59] <oSoMoN> that's not the case for fonts-liberation2 though, cosmic already had 2.00.1-7
[16:15] <tdaitx> oSoMoN: oh, you are asking about the cosmic task for fonts-liberation2, weird, it should not have that... in fact, since the changelog does not mention 1814133 it shouldn't be there at all
[16:19] <oSoMoN> yeah
[16:24] <tdaitx> oSoMoN: feel free to remove it and any other tasks that are not mentioned on the changelog, specially for cosmic tasks
[16:24] <tdaitx> I will run through that bug again later on this week to make sure it is sane
[16:34] <Trevinho> seb128: ok looking that too
[16:42] <seb128> trevinho, thx, seems an issue with one of your PRs
[16:42] <Trevinho> yep
[16:50] <oSoMoN> tdaitx, ok, will do (at least for fonts-liberation2)
[17:21] <willcooke> night all
[18:56] <oSoMoN> good night all, see ya on Thursday