[06:30] <didrocks> good morning
[06:32] <jibel> hi
[06:32] <didrocks> Am I the only one to see 2 things? Scaling factor is all messed up for the Shell UI on boot and some slowdown, like pause for 5s sometimes, second array, all UI frozen?
[06:33] <jibel> I don't see that
[06:33] <didrocks> opening a bug on the first one at least, easily reproducible here
[06:39] <duflu> Morning didrocks and jibel
[06:39] <duflu> didrocks, there's a known issue for Nvidia
[06:40] <duflu> scaling...
[06:41] <duflu> biab
[06:43] <didrocks> duflu: is there a bug opened? It's indeed Nvidia. Is it worked on?
[06:43] <didrocks> (and hi!)
[06:44] <RAOF> didrocks: Oh! You also see the 5 second pauses!
[06:45] <RAOF> bug# 1815550
[06:45] <didrocks> RAOF: oh, so nvidia specific as well?
[06:46] <RAOF> didrocks: For me, gnome-shell spins, unresponsive, at 100% CPU usage each time a zsh prompt is displayed.
[06:46] <didrocks> good that you spot it on RSS
[06:46] <RAOF> didrocks: Yeah. My intel + amd box is much, much smoother.
[06:47] <didrocks> it's really a PITA. Let's nominate it for -incoming
[06:47] <RAOF> Yeah, it's a tremendously bad experience.
[06:49] <didrocks> RAOF: do you have the scaling factor issue as well on that box?
[06:49] <RAOF> I do not have the scaling factor issue on that box.
[06:50] <RAOF> I'm booting with `nvidia_drm.modeset=1`, though, which has… different behaviours.
[06:50] <RAOF> (Mostly the behaviour is that GDM can't log in until I manually start an X server on a VT)
[06:50] <didrocks> unnince
[06:50] <didrocks> ok, another pause :(
[06:51] <didrocks> and I didn't start any app anything
[06:51] <didrocks> just switched window
[06:53] <RAOF> I don't *normally* notice it just generally mousing around. But that's partially because it happens *every* *single* *time* I press <enter> in a terminal.
[06:59] <oSoMoN> good morning desktoppers
[07:04] <duflu> didrocks, https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bugs?field.tag=x11-scaling
[07:04] <duflu> Hi oSoMoN and RAOF
[07:05] <oSoMoN> hi duflu
[07:05] <RAOF> Ello!
[07:06] <oSoMoN> salut didrocks
[07:06] <oSoMoN> didrocks, mw_hudson already handled the rust-cbindgen no-change rebuild
[07:13] <duflu> RAOF, didrocks, sounds easy to reproduce. I might switch to NVIDIA instead of reverting to SRU work soon
[07:14] <duflu> RAOF: where you using modeset=1 when the bug was first reported?
[07:14] <duflu> *were*
[07:15] <RAOF> I think I was using modest=1 when U first reported the bug. It'll be recorded in the apport details anyway.
[07:15] <duflu> RAOF, it's not
[07:16] <RAOF> Oh, /proc/cmdline isn't captured?
[07:16] <RAOF> Anyway, I probably was using it.
[07:16] <duflu> Unless you count the loaded module name
[07:16] <RAOF> I can try without, if you like.
[07:16] <duflu> RAOF, yes please
[07:19] <RAOF> I might need to get to that tomorrow.
[07:19] <didrocks> oSoMoN:oh nice! THANKS :)
[07:19] <didrocks> (without caps)
[07:21] <didrocks> duflu: FYI, I have modeset=1
[07:21] <didrocks> I have it for a couple of cycles
[07:25] <duflu> RAOF: yeah I thought that too. Night...
[07:26] <duflu> didrocks, thanks
[07:26] <didrocks> duflu: if I can help debugging, do not hesitate
[07:27] <duflu> Oooh. Actually mutter uses a completely different code path for Nvidia modeset=1
[07:27] <duflu> One which I don't use or test normally
[07:27] <didrocks> ahhh, so you might be able to reproduce :)
[07:40] <duflu> didrocks, but you weren't using modeset=1 with the scaling issue right?
[07:41] <duflu> I also assume people using nvidia-drm.modeset=1 are using Wayland sessions because there's no point otherwise. Although that might have its own bugs if used with Xorg
[07:44] <didrocks> duflu: I do have the scaling issue with modeset=1
[07:44] <didrocks> and I'm using the Xorg session, I switched to modeset=1 a while ago, when testing Wayland
[07:45] <didrocks> to test the "Run that on intel, run this on nvidia" IIRC
[07:45] <RAOF> I am not using the Wayland session, either.
[07:45] <RAOF> (because Steam doesn't work in it 😀)
[07:46] <RAOF> I use `modeset=1` to test Mir
[07:47] <didrocks> RAOF: Steam doesn't start at all with Wayland?
[07:48] <RAOF> didrocks: XWayland has no GL acceleration on NVIDIA.
[07:48] <duflu> Cool, thanks didrocks and RAOF. That's odd but now I know.
[07:48] <RAOF> So while Steam might *start*, it's not very useful 😀
[07:49] <didrocks> duflu: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822478/comments/12 FYI
[07:49] <ubot5`> Ubuntu bug 1822478 in mutter (Ubuntu) "[regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable." [High,Triaged]
[07:49] <didrocks> RAOF: ahah :)
[07:49] <didrocks> ok, got it
[07:49] <didrocks> duflu: so basically, when "resetting" on g-c-c, it does what I expect, the issue is only initial state on boot
[07:50] <didrocks> duflu: s/upon/until/ btw
[07:50] <duflu> didrocks, OK. I need to get through my pending work yet. I'll try and remember when I start on that bug proper
[07:52] <didrocks> sounds good :)
[07:55] <willcooke> morning all
[07:57] <didrocks> hey willcooke
[08:00] <seb128> good morning desktopers
[08:02] <oSoMoN> salut seb128
[08:02] <seb128> lut oSoMoN, en forme ?
[08:02] <oSoMoN> ça va, et toi?
[08:02] <seb128> ça va !
[08:03] <didrocks> hey seb128
[08:03] <Laney> whats up
[08:03] <seb128> lut didrocks, hey Laney
[08:04] <duflu> Morning willcooke and Laney
[08:04] <oSoMoN> good morning willcooke, Laney
[08:04] <duflu> And good morning seb128
[08:05] <seb128> hey duflu willcooke
[08:05] <willcooke> hey seb128.  Do I remember you saying you would take a look at this one?  https://bugs.launchpad.net/ubuntu/+source/libnfs/+bug/1746598
[08:05] <ubot5`> Ubuntu bug 1746598 in libnfs (Ubuntu Cosmic) "[MIR] libnfs" [Undecided,New]
[08:06] <didrocks> hey Laney
[08:07] <seb128> willcooke, Eric has been working on it and I told him I would help if needed, it's a bit complicated. If that's for bug triaging purpose I can do that
[08:08] <willcooke> thx seb128, yes for tracking purposes
[08:08] <seb128> willcooke, security team would prefer to have the new serie if we promote it, but that includes a soname change so it's non trivial
[08:08] <Laney> hi seb128 duflu oSoMoN didrocks
[08:08] <seb128> k, done
[08:13] <duflu> Hmm still April 1st on Stack Overflow
[08:15] <willcooke> oSoMoN, there is a huge openjdk upgrade bug open which has some LibreOffice tasks : https://bugs.launchpad.net/ubuntu/+source/saaj/+bug/1814133
[08:15] <ubot5`> Ubuntu bug 1814133 in virtualbox-hwe (Ubuntu Cosmic) "update to openjdk 11 in 18.04 LTS" [Undecided,New]
[08:15] <willcooke> oSoMoN, is that on your list somewhere?  i.e. should I assign it to you?
[08:32] <oSoMoN> willcooke, yes, that's under control: I backported a couple of patches to fix the build against the new openjdk, the updated packages are in bionic-proposed and should migrate to -updates soon
[08:33] <oSoMoN> do_ko and t_daitx are overseeing the update
[08:33] <willcooke> thx oSoMoN
[08:34] <oSoMoN> you can assign the libreoffice tasks to me if you want (and if LP lets you…)
[08:34] <oSoMoN> updating such huge bug reports tends to timeout more often than not
[08:34] <willcooke> indeed :D
[08:43] <willcooke> duflu, re:  https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1803319 can I assign you on that one?  You already fixed it upstream, but it's targetted to a release and so either needs untargetting or an assignee
[08:43] <ubot5`> Ubuntu bug 1803319 in mutter (Ubuntu Disco) "GNOME Shell task bar menus not updated with external monitor primary and laptop screen fractionally scaled" [High,Triaged]
[08:44] <duflu> willcooke, yes I was thinking the same and then forgot. That's the first time I've decided to unassign myself. The intention was to say that I won't be the one doing the 3.32.1 release which contains the fix
[08:44] <duflu> Now assigned again
[08:45] <willcooke> duflu, merci!
[09:18] <duflu> willcooke, Jonas confirmed he expects there to be a 3.32.1 so I am assuming we will want to grab that in one go instead of patching each fix that it contains
[09:19] <andyrock> monring all!
[09:19] <andyrock> *morning
[09:19] <duflu> moaning andyrock
[09:19] <duflu> :)
[09:19] <duflu> Also good morning
[09:19] <andyrock> 😂
[09:19] <seb128> hey andyrock
[09:20] <seb128> duflu, yeah, we are going to want to update, do you know when they plan to roll it out?
[09:20] <duflu> seb128, I don't know anything more
[09:20] <andyrock> hey seb128! did you have good holidays? :)
[09:20] <duflu> Some gnome stuff is already at 3.32.1
[09:20] <seb128> duflu, k, no worry, probably this week
[09:20] <seb128> right
[09:21] <seb128> andyrock, yes, excellent, thx!
[09:44] <willcooke> duflu, cool, thanks.  (sorry was otp)_
[11:29] <seb128> willcooke, did you see the comment on https://bugs.launchpad.net/ubuntu/+source/ubuntu-wallpapers/+bug/1819744 ?
[11:29] <ubot5`> Ubuntu bug 1819744 in ubuntu-wallpapers (Ubuntu) "19.04 Disco default wallpapers" [Undecided,Fix released]
[11:30] <willcooke> The last one?  yeah, the wallpaper is slightly different for the grey one.  NFA as far as I'm concerned
[11:32] <seb128> k, thx, I just wanted to make sure it was ok/expected
[11:35] <willcooke> thx
[11:51] <Laney> is the team meeting in 99 minutes or 159 minutes or 219 minutes?
[11:52] <willcooke> Laney, 98 mins
[11:52] <Laney> thx
[11:58] <Laney> it is pinned to 14:30 UK time then?
[11:58] <Laney> I'll ask the fridge calendar people to update it
[12:00] <willcooke> Laney, yeah, looks like it's pinned to "United Kingdom Time"
[12:00] <Laney> righto
[12:00] <willcooke> https://imgur.com/a/xJKFUv5 \o/
[13:10] <willcooke> Laney, do you use IPv6 generally?  And if so, have you seen any problems in Disco?
[13:15] <willcooke> Laney, unping.  Seems there are general connectivity problems
[13:15] <willcooke> with the archive
[13:22] <Laney> doh
[13:22] <Laney> but yes, most of the time
[13:29] <willcooke> #startmeeting Desktop Team Meeting  2019-04-02
[13:29] <meetingology> Meeting started Tue Apr  2 13:29:49 2019 UTC.  The chair is willcooke. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[13:29] <meetingology> Available commands: action commands idea info link nick
[13:30] <willcooke> Roll call: andyrock, didrocks, duflu (out), jbicha, jamesh (out), jibel, kenvandine, laney, oSoMoN, seb128, tkamppeter, trevinho, robert_ancell (out)
[13:30] <kenvandine> \o
[13:30] <oSoMoN>      o/
[13:31] <didrocks> hey
[13:31] <jibel> bonjour
[13:31] <willcooke> We'll do the usual rls incoming bugs.  I already went through the tracking bugs and made sure they are all assigned etc.
[13:31] <andyrock> o/
[13:32] <willcooke> Let's start with B
[13:32] <willcooke> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-incoming-bug-tasks.html
[13:32] <willcooke> Nice, zero.
[13:32] <willcooke> C:  http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-cc-incoming-bug-tasks.html
[13:32] <willcooke> Also 0.
[13:33] <willcooke> #winning
[13:33] <willcooke> D: http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-dd-incoming-bug-tasks.html
[13:33] <willcooke> we have some bugs to review  :)
[13:33] <willcooke> First up:
[13:33] <willcooke> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1815550
[13:33] <ubot5`> Ubuntu bug 1815550 in gnome-shell (Ubuntu) "[nvidia] gnome-shell RSS grows without limit, general slowness" [Critical,Confirmed]
[13:34] <didrocks> we discussed it this morning. It's really making disco unusable
[13:34] <didrocks> (nvidia drivers)
[13:34] <willcooke> +1 to investigate.
[13:34] <seb128> +1 for nominating/assigning
[13:34] <didrocks> +1, duflu started to have a look
[13:35] <willcooke> duflu seems like a good person to assign
[13:35] <seb128> yes
[13:35] <willcooke> ok, targetted and assigned
[13:36] <willcooke> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822478
[13:36] <ubot5`> Ubuntu bug 1822478 in mutter (Ubuntu) "[regression][nvidia] All on screen text is tiny. Icons are normal size but text is nearly unreadable." [High,Triaged]
[13:36] <willcooke> +1 and already assigned to Trevinho
[13:36] <didrocks> same, annoying regression due to scaling factor with nvidia, so +1
[13:36] <seb128> wfm
[13:37] <willcooke> done
[13:37] <willcooke> next: https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1822072
[13:37] <ubot5`> Ubuntu bug 1822072 in gnome-shell (Ubuntu) "User selector doesn't have focus from login screen after screen turned off" [Medium,Confirmed]
[13:38] <willcooke> I logged this one.  It's a regression IMO.  But I'm interested to know if you think it's rls worthy or not.
[13:38] <seb128> I would vote -1 from the steps
[13:38] <seb128> but if that also happens when you lock the screen by keybinding so maybe that's a +1
[13:39] <willcooke> I dont think it does effect lock screen
[13:39] <seb128> I don't think the "wait on the lock screen" is that common of an usecase and while slightly annoying the workaround is obvious
[13:39] <seb128> on the login screen*
[13:39] <seb128> I vote -notfixing
[13:39] <seb128> would still be worth reporting upstream/fixing if we can
[13:40] <willcooke> kk, I'm happy with notfixing then
[13:40] <willcooke> and I can upstream
[13:40] <didrocks> same
[13:40] <seb128> thx
[13:40] <willcooke> https://bugs.launchpad.net/ubuntu/+source/gnome-initial-setup/+bug/1821901
[13:40] <ubot5`> Ubuntu bug 1821901 in gnome-initial-setup (Ubuntu) "Location services option should be off by default" [Undecided,New]
[13:41] <willcooke> Legal team say this needs to be off by default.  So I think +1 on rls
[13:41] <seb128> k, +1 if legal says so
[13:41] <seb128> you can assign to me
[13:41] <kenvandine> +1
[13:42] <willcooke> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1821895
[13:42] <ubot5`> Ubuntu bug 1821895 in gnome-shell (Ubuntu) "Gnome Shell crashes after resume on Disco" [Undecided,Incomplete]
[13:43] <willcooke> Seems to be wayland only.  So -1 for rls
[13:43] <seb128> -notfixing
[13:43] <seb128> it's lacking info, not confirmed and wayland only
[13:43] <seb128> the report doesn't even state what release he's using
[13:44] <seb128> ah, in the title
[13:44] <seb128> still, almost no info and not impacting the default session
[13:44] <willcooke> https://bugs.launchpad.net/ubuntu/+source/gnome-terminal/+bug/1821019
[13:44] <ubot5`> Ubuntu bug 1821019 in gnome-terminal (Ubuntu) "gnome-terminal does not gain focus upon launch via clicking icon" [Undecided,Confirmed]
[13:44] <willcooke> I've got a feeling that duflu might have fixed this upstream
[13:44] <seb128> yes
[13:45] <oSoMoN> that one is really annoying
[13:45] <seb128> it's a dup of bug #1817924
[13:45] <ubot5`> bug 1817924 in mutter (Ubuntu Disco) "(In Xorg sessions only) apps launched from gnome shell do not get input focus" [High,Triaged] https://launchpad.net/bugs/1817924
[13:45] <willcooke> Do we patch or wait for a point release upstream
[13:45] <seb128> the fix has been commited upstream
[13:46] <seb128> tarballs are due next week
[13:46] <seb128> we might want to backport a fix fixes meanwhile, up to Trevinho/duflu I guess
[13:46] <seb128> we can talk about that out of the meeting though
[13:46] <willcooke> oki
[13:46] <willcooke> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1821933
[13:46] <ubot5`> Ubuntu bug 1821933 in gnome-shell (Ubuntu) "Touch input is offset with two screens (even appearing on the wrong screen)" [Undecided,Confirmed]
[13:47] <willcooke> Another one of mine.  It doesnt affect Fedora.  +1 to work on this
[13:47] <seb128> I would vote -notfixing
[13:48] <seb128> I don't think using touch screen with 2 monitors is common
[13:48] <willcooke> uh, that's a fair point
[13:48] <seb128> touch support is already not great and we don't get lot of flack for it
[13:48] <seb128> so I think our touch users number is low
[13:48] <willcooke> any other votes?  Otherwise notfixing
[13:48] <seb128> those who use docked is problem even lower
[13:48] <didrocks> -notfixing as well for now
[13:48] <kenvandine> -1
[13:49] <willcooke> k, that's the end of the incoming bugs
[13:50] <willcooke> As I said earlier, the unassigned tracking bugs are all clear.
[13:50] <andyrock> maybe let's just add a trello card for it
[13:50] <willcooke> andyrock, will do
[13:50] <willcooke> Laney, anything in the proposed migrations you want to raise?
[13:50] <Laney> nope
[13:51] <willcooke> Cool
[13:51] <willcooke> #topic AOB
[13:51] <willcooke> Anyone got anything?
[13:51] <andyrock> nope
[13:51] <willcooke> Oh, while I remember, jibel do you know how that backlight / blackscreen issue is going off hand?
[13:52] <seb128> what issue is that?
[13:52] <jibel> willcooke, it's going nowhere afaik
[13:52] <willcooke> jibel,  do you have a bug number handy?
[13:53] <jibel> i'ms searching
[13:53] <willcooke> thx, I will follow up after the meeting then
[13:53] <willcooke> anything else for anyone?
[13:53] <willcooke> 1 min before I end the meeting
[13:53] <seb128> not me
[13:53] <oSoMoN> nothing here
[13:54] <willcooke> #endmeeting
[13:54] <meetingology> Meeting ended Tue Apr  2 13:54:44 2019 UTC.
[13:54] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2019/ubuntu-desktop.2019-04-02-13.29.moin.txt
[13:54] <willcooke> thanks all
[13:54] <didrocks> thx
[13:54] <jibel> willcooke, bug 1821882
[13:54] <ubot5`> bug 1821882 in linux (Ubuntu) "Screen is very dark and brightness cannot be adjusted" [Undecided,Incomplete] https://launchpad.net/bugs/1821882
[13:54] <willcooke> thanks jibel
[13:55] <willcooke> kk, I will poke Pierre to reply
[13:56] <willcooke> and done
[13:57] <seb128> willcooke, is there of any concern to us? the report states it already exist in bionic so not a new issue, also seems to be a video driver problem on a specific config...
[13:59] <willcooke> I'd like that confirming by Pierre.  If it means that new machines (like that beefy Dell gaming laptop) get a black screen when trying to install, I'd love to see if fixed.  I'll see what t_jaalton says after Pierre has confirmed
[14:00] <seb128> k
[14:00] <seb128> willcooke, also is your touch coordinate bug happening only on the desktop view? or in other UI elements/apps?
[14:00] <Trevinho> morning...
[14:00] <seb128> hey trevinho
[14:00] <seb128> just in time to miss the meeting :p
[14:00] <willcooke> seb128, everything is offset, shell, window titles, etc
[14:00] <Trevinho> seb128: hey...
[14:01] <seb128> willcooke, that's new from disco?
[14:01] <willcooke> seb128, yeah
[14:01] <seb128> k
[14:01] <Trevinho> yes I set the alarm, but I think I put the wrong tz in it 😭
[14:08] <Trevinho> saw the backlog by the way. but starting next week it will be too early anyways (7 am)
[14:59] <seb128> Laney, do you think you could skip the n-m/ppc64el failure? the current disco version has the same problem, it's not a regression from 1.16 in proposed
[15:42] <Laney> seb128: see my comment on the card, I already did do that
[15:44] <seb128> Laney, ah, I was not on this card/didn't see the comment before, I've just been trying to clean stuff from update_excuses_by_team.html#desktop-packages today
[15:44] <seb128> got cairo, pygobject and few others off :)
[15:45] <seb128> Laney, thx!
[15:46] <seb128> (it's still blocking migration but I guess we need to wait a bit longer?)
[15:46] <seb128> the page refreshed 10 mins ago though...
[16:15] <greyback> kenvandine: hey, with demise of remote desktop-helper, how should one use desktop helpers now? Copy/paste the yaml?
[16:15] <greyback> I've not had to look into the topic in a while, hence being very out of date!
[16:31] <kenvandine> greyback: yes, copy the yaml
[16:32] <kenvandine> until we have the extension
[16:34] <greyback> kenvandine: ack, thanks!
[17:28]  * willcooke -> haircut
[17:28] <willcooke> night all
[17:32] <oSoMoN> good night
[18:06] <seb128> andyrock, bdmurray was asking if bug #1807900 is still on your todolist (I guess it should be an easy change?)
[18:06] <ubot5`> bug 1807900 in update-manager (Ubuntu Bionic) "update-manager suggests to use Livepatch, which is not available" [High,Triaged] https://launchpad.net/bugs/1807900
[18:06] <andyrock> checking
[18:07] <andyrock> yup thanks for reminding me that
[18:07] <andyrock> :)
[18:11] <seb128> andyrock, np! :)