14:30 <seb128> #startmeeting Desktop Team Meeting 2019-02-26 14:30 <meetingology> Meeting started Tue Feb 26 14:30:36 2019 UTC. The chair is seb128. Information about MeetBot at http://wiki.ubuntu.com/meetingology. 14:30 <meetingology> 14:30 <meetingology> Available commands: action commands idea info link nick 14:30 <andyrock> o/ 14:31 <seb128> Roll call: andyrock, didrocks, duflu (out), jbicha (out), jamesh (out), jibel, kenvandine (out), laney (late?), oSoMoN, tkamppeter (out), trevinho, robert_ancell (out) 14:31 <oSoMoN> o/ 14:31 <Trevinho> O/ 14:32 <didrocks> hey 14:32 <seb128> quite some people out today, let's get started anyway 14:32 <jibel> hi 14:32 <seb128> #topic rls-bugs-review 14:32 <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-incoming-bug-tasks.html 14:33 <seb128> no desktop section for -bb but bug #1803136 sounds like it should be owned by desktop 14:33 <ubot5> bug 1803136 in vala (Ubuntu) "[SRU] Update to vala 0.40.13 in bionic" [Low,New] https://launchpad.net/bugs/1803136 14:33 <seb128> though that it's in universe 14:34 <didrocks> it impacts potential rebuilds in main, though? 14:34 <seb128> I vote rls-bb-notfixing, it's a valid request and we should SRU it but it's not worth rls tracking 14:34 <seb128> well, it might 14:34 * didrocks always feels uneasy with vala update 14:34 <seb128> but it shouldn't? it's a bugfix update 14:34 <Trevinho> not sure... 14:35 <seb128> no reason we need to rebuild thing, though it could lead to ftbfs-es 14:35 <didrocks> yeah, but bugfixing means doing a mass rebuild anyway, so… +1 on -notfixing 14:35 <seb128> anyway 14:35 <didrocks> (or segfaults at runtime :p) 14:35 <seb128> k, let's not argue if (test) rebuilds are required on not, it's not useful if we rls-bb-notfixing 14:35 * seb128 updates the bug 14:36 <Trevinho> does it need rebuilding the vala world all the times? 14:37 <didrocks> Trevinho: well, generated C code will get the fixes, no? 14:38 <seb128> fixing the toolchain and updating our packages to benefit of the fixes are different things 14:38 <seb128> we can update the toolchain first and then evaluates what would benefit from a rebuild 14:38 <seb128> but that's a conversation for post meeting :) 14:38 <Trevinho> yep, depends on the fixes... Could also be just on the compiler itself. then bugs depend on specific cases I think 14:38 <seb128> that was the one bionic incoming 14:38 <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-cc-incoming-bug-tasks.html 14:39 <didrocks> (but it means that a security update later can have more troubles than needed due to untested rebuild first, but agreed, discussion for later) 14:39 <seb128> same vala situation there 14:39 <didrocks> yep 14:40 <seb128> and that's the one one for cosmic 14:40 <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-dd-incoming-bug-tasks.html 14:40 <seb128> that is more interesting 14:41 <seb128> bug #1817020 14:41 <ubot5> bug 1817020 in gnome-shell-extension-ubuntu-dock (Ubuntu) "Touching and dragging an icon on the dock blocks input to other apps" [High,Confirmed] https://launchpad.net/bugs/1817020 14:41 <seb128> that basically screws your session 14:41 <andyrock> I can take this 14:41 <seb128> but most of our users don't use touch 14:41 <seb128> k, so I vote +1 and assignee andyrock :) 14:41 <Trevinho> andyrock ❤️ 14:41 <seb128> others agree on nominating? 14:41 <seb128> andyrock, thx! 14:41 <andyrock> np 14:41 <didrocks> hard to argue against :p 14:42 <seb128> done 14:42 <andyrock> thx 14:42 <seb128> bug #1817546 14:42 <ubot5> bug 1817546 in gnome-shell (Ubuntu Disco) "Changing the volume (with the mouse wheel over icon) locks up gnome-shell" [High,Confirmed] https://launchpad.net/bugs/1817546 14:43 <seb128> +1 for me for nominating 14:43 <seb128> trevinho, you want to own that one? 14:43 <andyrock> +1 14:43 <Trevinho> yep 14:43 <seb128> thx 14:43 <seb128> next 14:43 <seb128> bug #1817128 14:43 <ubot5> bug 1817128 in gnome-keyring (Ubuntu) "gnome-keyring not automatically unlocked on login" [High,Triaged] https://launchpad.net/bugs/1817128 14:43 <seb128> I vote +1, I'm ok to own it 14:44 <seb128> (I hope GNOME fixes it for .0 but otherwise we know what commit to revert) 14:45 <seb128> k, no other vote, let's do that and move on 14:45 <seb128> bug #1817490 14:45 <ubot5> bug 1817490 in gnome-shell-extension-appindicator (Ubuntu) "gnome-shell-extension-appindicator 23-1 is busted -- no appindicators are displayed" [High,Fix committed] https://launchpad.net/bugs/1817490 14:45 <seb128> that has already been handled, the new version just needed to be locked to the same gnome-shell serie 14:45 <seb128> L_aney uploaded that earlier 14:45 <seb128> bug #1440372 14:45 <ubot5> bug 1440372 in duplicity (Ubuntu) "please port duplicity to Python3" [Medium,Triaged] https://launchpad.net/bugs/1440372 14:45 <seb128> I vote -1 / notfixing 14:46 <didrocks> yeah, same as well 14:46 <Trevinho> Wasn't there a branch already? 14:46 <Trevinho> IIRC... 14:46 <seb128> unsure why it has been tagged, that's nothing new nor urgent 14:46 <seb128> not that I know 14:47 <didrocks> well, there is a branch from 2015, from mterry, but tested? Why not merged? unsure 14:47 <seb128> yeah, no reason it needs to be important not for disco in any case 14:47 <seb128> bug #1816945 14:47 <ubot5> bug 1816945 in xdiagnose (Ubuntu) "failsafeXServer does not parse Xorg.failsafe.log correctly" [Undecided,New] https://launchpad.net/bugs/1816945 14:48 <seb128> that has a patch and looks like worth fixing (I don't know what's the status of failsafe nowadays, I think I read comments saying it didn't work (well) with gdm/recent Ubuntu versions) 14:48 <seb128> I vote +1 14:48 <seb128> tjaalton, can you review the patch/test that? 14:49 <seb128> k, no other opinion? :( 14:50 <seb128> I do accept/assign & let's move to next one 14:50 <didrocks> I'm unsure it even works TBH 14:50 <Laney> back 14:50 <seb128> right 14:50 <seb128> wb Laney 14:50 <seb128> you got saved by a long list of dd-incoming, we didn't reach your section yet :) 14:51 <seb128> bug #1817073 14:51 <ubot5> bug 1817073 in gnome-shell-extension-appindicator (Ubuntu) "GNOME Shell crash when an asset is not found (due to too many logs spawn by appindicator extension)" [Undecided,Confirmed] https://launchpad.net/bugs/1817073 14:51 <seb128> brb, door bell 14:51 <seb128> please discuss ^ 14:51 <didrocks> I'm on +1 fixing it, this is a bad behavior which can crash the shell by $whatever_app 14:51 <didrocks> I can have a look if Trevinho or andyrock don't have time for it, I will be less effective though as they know more the code than I do 14:52 <andyrock> I took a look during the sprint (forget to put it in the weekly report) but was unable to reproduce the problem 14:52 <didrocks> (I guess there are 2 parts: 1. printing the asset name so that app authors can see that on the log and 2. prevent the infinite loop) 14:52 <seb128> I agree that it would be nice to fix it 14:52 <didrocks> andyrock: with a simple app and no asset? 14:52 <didrocks> like simple app publishing an indicator (do you have any handy?) 14:52 <seb128> we didn't seem to have much report and seems specific to a not-used-a-lot software 14:53 <andyrock> didrocks: with their app 14:53 <didrocks> ahhh, interesting 14:53 <Trevinho> I expect the shell not to crash more than the extension though 14:53 <didrocks> anyway, I can havae a try to reproduce 14:53 <seb128> let's discuss details after the meeting 14:53 <andyrock> if no one wants to take this feel free to assign it to me 14:53 <seb128> I think I -1 tracking it as -rls because it's obviously not something lot of users have been hitting 14:53 * Laney thinks assign but not rls personally 14:53 <seb128> agreed 14:53 <andyrock> makes sense 14:54 <didrocks> (was twitter-popular for a while, this is why it got my attention btw) 14:54 <didrocks> (and blaming ubuntu, blablabla) 14:54 <seb128> didrocks, I assign to you to find a reproducer then feel free to reassign to andy 14:54 <didrocks> sure 14:55 <seb128> bug #1772811 14:55 <ubot5> bug 1772811 in OEM Priority Project "different behaviors for switch display mode between xenial and bionic" [Critical,Triaged] https://launchpad.net/bugs/1772811 14:55 <seb128> I think that's fixed in proposed 14:55 <seb128> trevinho, correct? 14:55 <Trevinho> yeah it should 14:55 <seb128> if so can you update the status? 14:55 <seb128> thx 14:56 <Trevinho> yep. Forgot to add it in the changelog it seems 14:56 <seb128> k 14:56 <seb128> so, tracking list 14:56 <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-dd-tracking-bug-tasks.html all owned 14:57 <seb128> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-cc-tracking-bug-tasks.html 14:57 <seb128> bug #1796622 14:57 <ubot5> bug 1796622 in network-manager (Ubuntu Cosmic) "NetworkManager IPv6 DAD lifetime behavior introduce security risk" [High,New] https://launchpad.net/bugs/1796622 14:57 <seb128> cosmic needs fixing/SRU to the current version 14:57 <seb128> let's assign to Till 14:58 <Laney> Till mentioned that on his report 14:58 <seb128> right 14:58 <seb128> bug #1815708 14:58 <ubot5> bug 1815708 in gnome-software (Ubuntu Cosmic) "Use ODRS for reviews" [Medium,New] https://launchpad.net/bugs/1815708 14:59 <seb128> I assign that one to robert since he uploaded the change to cosmic https://launchpadlibrarian.net/411242971/gnome-software_3.30.2-0ubuntu10_source.changes 15:00 <seb128> or I will later if launchpad stops timeouting on me :/ 15:00 <seb128> that's it for cosmic 15:00 <andyrock> regarding this https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1799293 15:00 <ubot5> Launchpad bug 1799293 in gnome-shell-extension-dashtodock (Ubuntu Disco) "Locking the screen once leaves screen contents visible but not interactive. Locking the screen a second time works." [Undecided,Incomplete] 15:00 <andyrock> do we really care about gnome-shell-extension-dashtodock 15:00 <andyrock> it's fixed in gnome-shell-extension-ubuntudock 15:00 <andyrock> and upstream 15:00 <seb128> it would be nicer to fix it there, but it's not a priority 15:01 <seb128> don't spend time on it 15:01 <Laney> IMO not as a team, but you can use ~ubuntu-sponsors and someone might pick it up 15:01 <Laney> ...if you want... 15:01 <seb128> +1 15:01 <didrocks> sounds good 15:01 <andyrock> kk 15:01 <seb128> ok, moving on 15:01 <seb128> bb-tracking 15:02 <seb128> bug #1763892 15:02 <ubot5> bug 1763892 in mutter (Ubuntu Cosmic) "144Hz/120Hz monitor but mutter seems to cap rendering at 60FPS" [Medium,In progress] https://launchpad.net/bugs/1763892 15:02 <Trevinho> duflu area 15:02 <seb128> he's on it, started with cosmic 15:02 <seb128> let's assign to him 15:02 <seb128> bug #1769991 15:02 <ubot5> bug 1769991 in network-manager-openvpn (Ubuntu Bionic) "[16.04] Unable to import OpenVPN configuration into Network Manager" [Undecided,New] https://launchpad.net/bugs/1769991 15:03 <seb128> k, unsure how that got nominated but I think it shouldn't at this point 15:04 <seb128> I'm deleting the xenial/bionic targets and asking that guy to follow the process (he needs to provides details anyway) 15:04 <seb128> and the odrs one is same as cosmic, for Robert 15:04 <Laney> https://bugs.launchpad.net/ubuntu/+source/network-manager-openvpn/+bug/1769991/+activity that guy? 15:04 <ubot5> Launchpad bug 1769991 in network-manager-openvpn (Ubuntu Bionic) "[16.04] Unable to import OpenVPN configuration into Network Manager" [Undecided,New] 15:04 <Laney> :> 15:04 <seb128> yes 15:04 <seb128> does anyone know him? 15:04 <didrocks> nope 15:04 <Laney> if you mean teward, he's an ubuntu-dev 15:05 <Laney> however, that's not the guy I'm referringn to 15:05 <Laney> (scroll down to "bug task added") 15:05 <Trevinho> nope too 15:05 <seb128> lol 15:05 <seb128> I did the xenial one 15:05 <seb128> not bionic :p 15:05 <Laney> :D 15:05 <seb128> aaaanyway 15:05 <seb128> :) 15:05 <seb128> #topic update_excuses_by_team.html#desktop-packages 15:06 <seb128> Laney, your turn! 15:06 <Laney> ok 15:06 <Laney> glib2.0 (2.59.2-2 to 2.59.3-1) in proposed for 5 days 15:06 <Laney> give me a card for that, I don't think Jeremy is going to take it 15:06 <Laney> gnome-software (3.30.6-2ubuntu2 to 3.31.2-0ubuntu1) in proposed for 4 days 15:06 <Laney> two things 15:06 <Laney> Unsatisfiable depends: 15:06 <Laney> libxmlb1: amd64, arm64, armhf, i386, ppc64el, s390x 15:06 <Laney> that's an MIR https://bugs.launchpad.net/ubuntu/+source/libxmlb/+bug/1814997 15:07 <ubot5> Launchpad bug 1814997 in libxmlb (Ubuntu) "[MIR] libxmlb" [Undecided,Triaged] 15:07 <Laney> not sure if we want to get that raised up or not 15:07 <Laney> Blocked by bug: 1817223 15:07 <ubot5> bug 1817223 in libxmlb (Ubuntu) "[disco-proposed] The list of applications in Ubuntu Software is empty" [High,Triaged] https://launchpad.net/bugs/1817223 15:07 <Laney> imho that should be nominated 15:07 <Laney> and tracked that way 15:07 <didrocks> (MIR is pending security) 15:07 <seb128> we should raise it up/ask security, it blocks also the new fwupd 15:07 <seb128> +1, let's do that 15:08 * didrocks agrees 15:08 <Laney> cool 15:09 <Laney> and the bug, nominate/assign to robert? 15:09 <Laney> he's been working on it, but for tracking 15:10 <seb128> yes, I do that 15:10 <Laney> thx 15:10 <Laney> gvfs blocking glibc (2.28-0ubuntu1 to 2.29-0ubuntu1) for 4 days 15:10 <Laney> Regressions 15:10 <Laney> gvfs/1.39.91-1: amd64 (log, history), s390x (log, history) 15:10 <Laney> jbicha uploaded a new one, but http://autopkgtest.ubuntu.com/packages/g/gvfs/disco/amd64 for that looks bad 15:10 <Laney> card it 15:11 <Laney> cairo (1.16.0-2 to 1.16.0-3) in proposed for 3 days 15:11 <Laney> Regressions 15:11 <Laney> gnome-shell-pomodoro/0.14.0-1: amd64 (log, history), arm64 (log, history), armhf (log, history), i386 (log, history), ppc64el (log, history) 15:11 <Laney> card that too, looks like something valaish 15:11 <Laney> I didn't look at the ones that are greyed out 15:11 <Laney> so, end 15:11 <seb128> k 15:12 <seb128> do we kno what's the status of the gnome-shell transition? 15:12 <Laney> going to have to remove some extensions to proposed 15:12 <seb128> do we demote extensions to proposed, if so who is working on getting the list? jbicha? 15:12 <Laney> jeremy did some stuff on his status 15:12 <Laney> but it can't go in until glibc is done anyway 15:13 <seb128> right 15:13 <seb128> I'm looking at poppler which I started (for the record) 15:13 <andyrock> glibc is already fixed upstream right? 15:13 <Laney> dunno, not our team 15:13 <Laney> so I'm not tracking it ;-) 15:13 <Laney> they were mentioning it a bit on release though so I know it's being worked on 15:13 <seb128> andyrock, glib you mean? glibc is libc6 and that has a bunch of autopkgtest issues 15:14 <seb128> but that's for foundations to sort out 15:14 <seb128> #topic aob 15:14 <seb128> other topics? 15:14 <andyrock> oh missed the c :P 15:14 <seb128> reminder we are in feature freeze, so updates including features need a ffe 15:14 <seb128> also if you had a feature that you wanted to land and missed the line please let me know 15:15 <Laney> so it can be DENIED 15:15 <andyrock> ahahaha 15:15 <Trevinho> Iano the terrible 15:15 <Trevinho> Ianus* 15:15 <seb128> :) 15:15 <seb128> reading Jeremy's post again 15:16 <seb128> Laney, trevinho, he mentioned that gnome-shell needs the new g-s-d probably for keybinding to work, did we lock those together through propers packaging tweaks? 15:16 <seb128> (I could check myself, sorry for being lazy) 15:17 <andyrock> I confirm that it requires the new g-s-d 15:17 <Trevinho> seb128: hmhmg... There was no dep change. But not in the released one 15:17 <Trevinho> it's for next one 15:17 <seb128> k 15:17 <seb128> seems all 15:17 <Trevinho> andyrock: maybe send upstream meson change too 15:17 <seb128> no other topic? 15:18 <seb128> k, seems not, let's call it a wrap, the meeting was long enough with a busy list of rls bugs (welcome into post-ff time ;) 15:18 <didrocks> nothing for me 15:18 <seb128> thx desktopers! 15:18 <didrocks> thx! 15:18 <seb128> #endmeeting