[01:30] <callmepk> Morning
[01:31] <duflu> Morning callmepk 
[01:32] <callmepk> Hi duflu 
[04:14] <pieq> Hi!
[04:14] <pieq> I'm checking 20.04 beta image install process and I faced a crash
[04:15] <pieq> but when I tried to report the issue, I was told it was an existing issue
[04:15] <pieq> the problem is... I cannot access the issue (it's bug #998492)
[04:15] <pieq> there is a "oops" everytime I try to access it
[04:18] <pieq> trying again but in safe graphics mode (this laptop has a nvidia card...)
[04:19] <pieq> duflu, do you know what logs I should be looking at during the install process? Just anything in /var/log/installer?
[04:19]  * duflu looks
[04:20] <duflu> pieq, I can't access that bug either. If it really is a crash then I can only suggest following all the steps in https://wiki.ubuntu.com/Bugs/Responses#Missing_a_crash_report_or_having_a_.crash_attachment
[04:28] <tjaalton> pieq: you left #hwe before an answer ;)
[04:29] <pieq> duflu, install crashes again... but there is nothing in /var/crash and the whoopsie id points to an empty page
[04:29] <pieq> tjaalton, ah! Sorry, I wanted to backup the /home partition
[04:29] <pieq> tjaalton, so I had to leave hexchat
[04:29] <pieq> let me reconnect from another computer
[04:30] <pieq> I dont see anything bad in /var/log/installer/debug
[04:33] <pieq> but whenever I'm trying to log a bug (ubuntu-bug ubiquity) I am told bug #998492 exists
[04:33] <duflu> pieq, no idea. I suggest not being connected to the Internet during install. It will go faster and might avoid that crash
[04:34] <pieq> ok, let me try this
[04:35] <duflu> pieq, also ask jibel to see if he can access that bug..?
[04:38] <pieq> duflu, I think this bug is very old and has a lot of dependencies, and Launchpad crashes when trying to access it. I've asked in the launchpad channel
[04:44] <jibel> morning all
[04:45] <jibel> pieq, Salut
[04:45] <jibel> pieq, anything in /var/log/syslog?
[04:46] <pieq> jibel, not much. I've captured the log and I'm reinstalling without internet to see if that helps (but I'm busy with something else atm)
[04:46] <jibel> I saw 2 occurrences of a bug during installation where libc fails to install
[04:46] <pieq> jibel, yeah, I saw that error in /var/lib/ubiquity
[04:47] <pieq> it's talking about an i386 version 
[04:47] <jibel> yes
[04:47] <jibel> so it's a real bug 
[04:47] <pieq> jibel, do you have the bug id? 
[04:47] <jibel> cf bug 1871268
[04:47] <pieq> jibel, shit, it's my work laptop... no running system ATM
[04:47] <jibel> the error is in spanish
[04:48] <jibel> install should pass without network
[04:49] <pieq> Apr  7 01:14:48 xubuntu /plugininstall.py: apt_pkg.Error: E:No se pudo configurar «libc6:i386», E:No se pudo realizar la configuración inmediata de «libgcc-s1:i386». Consulte la página de manual con «man 5 apt.conf» bajo «APT::Immediate-Configure» para más información. (2)
[04:49] <pieq> jibel, yes, I saw the same error but in English
[04:49] <pieq> I'll attach the logs later if that can help
[04:50] <jibel> yes please
[04:50] <jibel> pieq, it's Ubuntu not Xubuntu?
[04:51] <jibel> the bug report is for xubuntu
[04:51] <jibel> it doesn't really matter, just making sure it affects everyone and not limited to a flavor
[04:53] <pieq> jibel, done
[04:54] <pieq> jibel, oh yeah I forgot to mention it's for Ubuntu, not Xubuntu
[04:54] <pieq> jibel, and the error is in /var/lib/ubiquity/install.trace
[04:57] <jibel> thank you
[05:01] <pieq> jibel, this system has secure boot enabled, and nvidia card
[05:02] <pieq> I can see the installer is trying to install a nvidia-dkms, and I know dkms don't play well with secure boot
[05:02] <pieq> jibel, added that info in the bug, in case of
[05:04] <jibel> pieq, the OP also has an nVidia GPU, it could be the common denominator
[05:05] <pieq> jibel, duflu the bug https://bugs.launchpad.net/ubuntu/+source/ubiquity/+bug/998492 can now be accessed, and also mentions i386
[05:06] <jibel> it's just apport being confused. They seem unrelated
[05:06] <duflu> Morning jibel 
[05:07] <jibel> good morning duflu 
[05:11] <pieq> jibel, just finished the install. The workaround of not being connected during install worked
[06:26] <oSoMoN> good morning desktoppers
[06:29] <callmepk> Hi oSoMoN 
[06:29] <oSoMoN> hey callmepk 
[06:41] <seb128> goood morning desktopers
[06:41] <seb128> hey oSoMoN, callmepk, how are you today?
[06:41] <callmepk> Good. How are you seb128 ?
[06:42] <seb128> I'm good thanks!
[06:44] <didrocks> good morning
[06:54] <pieq> good morning Europe-based desktoppers! :)
[06:54] <pieq> (jibel doesn't count cause he wakes up waaaay too early)
[06:55] <oSoMoN> salut seb128, I'm tired (didn't sleep enough), but good otherwise
[06:55] <oSoMoN> salut pieq, ça va?
[06:56] <oSoMoN> salut didrocks 
[06:56] <didrocks> hey pieq, salut oSoMoN 
[06:57] <pieq> oSoMoN, oui ça va, merci ! Try to get a nap this afternoon! ;)
[07:00] <marcustomlinson> morning desktoppers
[07:01] <didrocks> hey marcustomlinson 
[07:03] <marcustomlinson> hey didrocks, how's things?
[07:04] <didrocks> good good, yourself?
[07:05] <marcustomlinson> yeah doing well thanks
[07:05] <marcustomlinson> oSoMoN: ditto on the lack of sleep though :P
[07:23] <seb128> lut didrocks pieq
[07:23] <seb128> hey marcustomlinson
[07:23] <didrocks> salut seb128 
[07:23] <seb128> oSoMoN, same here, could do with more sleep, days are challenging atm
[07:23] <marcustomlinson> morning seb128
[07:35] <duflu> Hi oSoMoN, seb128, marcustomlinson, didrocks 
[07:36] <didrocks> hey duflu 
[07:42] <seb128> hey duflu, how are you?
[07:42] <duflu> seb128, stressed. Family life peaks in line with focal beta. How are you?
[07:43] <marcustomlinson> hey duflu
[07:43] <seb128> duflu, oh, sorry to read, there is no ermergency with the release so don't overstress and take time if needed
[07:44] <duflu> seb128, yeah I keep thinking there are no emergencies so that's good
[07:52] <marcustomlinson> take it easy duflu
[08:04] <mwhudson> jibel, didrocks999: hey would zsys be ok with having go 1.14 as default in focal?
[08:04] <Laney> yo
[08:08] <didrocks999> mwhudson: we build upstream with 1.14 since its release, so nothing bad should happen
[08:08] <didrocks999> hey Laney 
[08:08] <duflu> lo Laney 
[08:08] <mwhudson> didrocks999: thanks
[08:09] <seb128> hey Laney, how are you?
[08:10] <marcustomlinson> morning Laney
[08:19] <Laney> hey didrocks999 duflu seb128 marcustomlinson 
[08:19] <Laney> yeah doing alright
[08:19] <Laney> you?
[08:20] <Wimpress> Morning desktopers o/
[08:21] <marcustomlinson> morning Wimpress
[08:21] <seb128> I'm alright, I could do with a bit more sleep and some extra exercice, I can feel the ratio food/movement isn't great atm
[08:21] <seb128> hey Wimpress
[08:25] <Wimpress> didrocks999: We had a catch up with Yaru team last night.
[08:26] <Wimpress> They've got some fixes that are preparing for an update release.
[08:28] <clobrano> good morning all 0/
[08:32] <duflu> Hi Wimpress 
[08:32] <duflu> and hi clobrano 
[08:33] <clobrano> hi duflu 
[08:40] <clobrano> Wimpress, looking at the PopOS commit that solves the build with libsass 3.6.3 issue we talked about yesterday, it seems they squashed the gtk-3.20 folder in gtk-3.0. Now, I am unsure about what gtk version is currently supporting our gtk-3.0 folder
[08:41] <ricotz> good morning desktopers :)
[08:41] <seb128> hey clobrano
[08:41] <marcustomlinson> heya ricotz
[08:41] <ricotz> seb128, hey, please sync vala :)
[08:41] <clobrano> good morning seb128, ricotz :)
[08:42] <didrocks999> Wimpress: nice! let’s get that as soon as possible :)
[08:43] <seb128> ricotz, hey, ok :)
[08:44] <marcustomlinson> woa didrocks leveled up
[08:45] <ogra> even above seb !
[08:45] <marcustomlinson> XD
[08:51] <duflu> tjaalton, I'm confused. Can you please explain how modeset gets used with the nvidia kernel driver without drm explicitly enabled? bug 1870637
[08:51] <didrocks999> \o/
[08:51] <didrocks999> thanks IRC timeout :p
[08:52] <tjaalton> duflu: you mean tseliot?
[08:52] <Laney> marcustomlinson: https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#update-manager sux
[08:52] <duflu> Err, maybe :)
[08:52] <duflu> tseliot, any idea?
[08:53] <duflu> Sorry, I have nick blindness in this area
[08:53] <marcustomlinson> Laney: ah what a lame failure
[08:55] <marcustomlinson> hmm, oh it's not the PyGIWarning that's the issue
[08:56] <marcustomlinson> odd that I didn't see that locally
[08:57] <Laney> different linters run during the autopkgtests
[08:57] <Laney> quality
[08:57] <Laney> kind of questionable as an autopkgtest at all imho, but there we are
[08:58] <marcustomlinson> very questionable
[08:58] <marcustomlinson> sigh, I'll MR asap
[08:58] <tseliot> duflu, that doesn't look right. I'll have a look
[09:28] <marcustomlinson> Laney: could you trigger this for me: https://autopkgtest.ubuntu.com/request.cgi?release=focal&arch=amd64&package=update-manager&ppa=marcustomlinson/test&trigger=update-manager/1:20.04.4
[09:29] <Laney> I can do, but
[09:29] <Laney> do you know how to run autopkgtests locally?
[09:29]  * Laney puts teacher hat on
[09:34] <marcustomlinson> Laney: oh would I not run into the same problem of different linter?
[09:48] <Laney> marcustomlinson: nah, it should run basically the same thing that would get run if I click that link
[09:49] <marcustomlinson> teach away good sir
[09:49] <Laney> ok, install autopkgtest
[09:49] <Laney> then run `autopkgtest-buildvm-ubuntu-cloud -r focal --verbose` and wait for that to finish, it will make a qemu VM in the current working directory
[09:52] <Laney> meanwhile build the package so you get an _amd64.changes with the source in it too, e.g. sbuild -d focal -s -A foo.dsc
[10:00] <duflu> seb128, xnox, if I want to create a file in /usr/share/plymouth, how do I make it seen at boot time?
[10:00] <duflu> It's still not found
[10:00] <seb128> duflu, do you use disk encryption?
[10:00] <duflu> seb128, no
[10:01] <seb128> it should be available then...
[10:01] <seb128> what's the error?
[10:01] <Laney> marcustomlinson: and then, you can run something like "autopkgtest --shell-fail --apt-upgrade update-manager_20.04.4_amd64.changes -- qemu ~/temp/autopkgtest-focal-amd64.img"
[10:01] <Laney> and it should do the thing
[10:01] <duflu> seb128, creating a plymouthd.defaults is ignored
[10:02] <marcustomlinson> Laney: ok I'll give it a go thanks!
[10:03] <Laney> meanwhile I clicked that link
[10:04] <duflu> Oh, maybe our distro patch is blocking it
[10:04] <seb128> could well be
[10:11] <duflu> seb128, yeah that's it. I think I will rewrite that patch. There's nothing wrong with the proposed one but fixing more bugs requires a new design. Let the proposed one release first?
[10:12] <seb128> duflu, yes, it's annoying that riscv blocked migration now :/
[10:12]  * duflu shrugs. I accidentally closed email and decided not to reopen it till tomorrow
[10:13] <seb128> don't, it's late enough
[10:13] <seb128> go enjoy your evening!
[10:13] <Wimpress> duflu: Also, I see you made the news again :-)
[10:13] <duflu> Wimpress, yeah someone reads the status reports :)
[10:14] <duflu> Triggered upstream to wake up and answer my comments
[10:18] <xnox> duflu:  has it been included in the initrd? i.e. did you do $ sudo update-initramfs -u ?
[10:19] <duflu> xnox, yes I tried that
[10:19] <duflu> The plymouth debug log still claims it can't file that file which exists
[10:20] <duflu> (/usr/share/plymouth//plymouthd.defaults)
[10:20] <duflu> generally the // is not a problem
[10:21] <duflu> *find that file
[10:21] <xnox> i've never heard of such a path
[10:22] <duflu> xnox, we don't ship it. It's an upstream thing that plymouthd checks for though
[10:22] <xnox> duflu:  lsinitramfs /boot/initrd.img | grep plymouthd.defaults ? does it have it
[10:23] <duflu> Ah that's the command I wanted
[10:23] <xnox> duflu:   /usr/share/initramfs-tools/hooks/plymouth is probably need to be edited to copy new/extra things
[10:24] <xnox> (if plymouthd.defaults is not in the initrd)
[10:24] <xnox> duflu:  also not sure if that's something that should be in /usr, or in /etc/plymouth.
[10:24] <duflu> xnox, I think it knows about it already. More likely the problem is just that the config file is skipped after we patch in a hardcoded value
[10:24] <xnox> # copy defaults file if exist
[10:24] <xnox> if [ -r /usr/share/plymouth/plymouthd.defaults ]
[10:24] <xnox> then
[10:24] <xnox> 	cp -a /usr/share/plymouth/plymouthd.defaults "${DESTDIR}/usr/share/plymouth/"
[10:24] <xnox> fi
[10:24] <xnox> it is there....
[10:24] <duflu> Yes
[10:24] <xnox> no idea, sorry
[10:24] <duflu> So I will modify the patch
[10:25] <duflu> After the proposed one releases
[10:50] <duflu> Huh, efifb remembers its mode (and has modes?!) across reboots
[11:34] <marcustomlinson> Laney: thanks for the lesson by the way :) I did get the tests running locally and it's a good thing I did too as there were more issues
[11:37] <Laney> ah great
[11:37] <Laney> blasted issues
[11:38] <Laney> would the pyflakes3 test run at build-time too if we added a build-dep on it?
[11:38] <Laney> if so, that would be a way better time to catch these issues
[11:56] <marcustomlinson> doesn't look like it
[11:58] <Laney> AH
[12:03] <marcustomlinson> Laney: https://code.launchpad.net/~marcustomlinson/update-manager/update-manager/+merge/381817
[12:03] <marcustomlinson> that'll do it
[12:05] <Laney> ok lemme see in a minute
[12:08] <cmatsuoka> oSoMoN: hi, have you ever seen problems related to invalid opcodes when calling xdg-open from chromium?
[12:09] <oSoMoN> cmatsuoka, that doesn't ring a bell
[12:09] <cmatsuoka> oSoMoN: we got this bug report: https://bugs.launchpad.net/ubuntu/+source/snapd/+bug/1870861
[12:10] <cmatsuoka> it's not something I could reproduce
[12:15] <oSoMoN> cmatsuoka, sorry, I've never seen that
[12:16] <cmatsuoka> oSoMoN: thanks, just checking :)
[12:46] <clobrano> hey Trevinho! Do you know if Yaru gnome shell in 20.04 builds the gresource? (It should, if I got it right)
[13:30] <hellsworth> good morning desktopers
[13:30] <marcustomlinson> howdy ho!
[13:30] <hellsworth> hi there mr hankey ;)
[13:30] <hellsworth> meeting time?
[13:31] <Wimpress> Yes.
[13:31] <Wimpress> And hello hellsworth o/
[13:31] <hellsworth> howdy ho Wimpress 
[13:31] <Wimpress> #startmeeting Desktop Team Weekly Meeting - 2020-04-07
[13:31] <meetingology> Meeting started Tue Apr  7 13:31:37 2020 UTC.  The chair is Wimpress. Information about MeetBot at http://wiki.ubuntu.com/meetingology.
[13:31] <meetingology> Available commands: action commands idea info link nick
[13:31] <Wimpress> Roll call:  didrocks, duflu, hellsworth, jamesh, jibel, kenvandine, Laney, marcustomlinson, oSoMoN, seb128 , tkamppeter, trevinho, robert_ancell, callmepk 
[13:31] <marcustomlinson> \o
[13:31] <hellsworth> o/
[13:32] <kenvandine> \o
[13:32] <seb128> _o/
[13:32] <Trevinho> o/
[13:32] <jibel> o/
[13:32] <Wimpress> #topic rls-bb-bugs
[13:33] <Wimpress> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-incoming-bug-tasks.html
[13:33] <Wimpress> http://launchpad.net/bugs/1870270
[13:33] <Wimpress> Fix released.
[13:34] <seb128> not for bionic?
[13:34] <seb128> we are on 3.32 there
[13:34] <Wimpress> Yep, looks like Daniel is working this one.
[13:34] <seb128> assign to him and untag?
[13:34] <Wimpress> Yep.
[13:35] <Wimpress> Done
[13:36] <Wimpress> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-bb-tracking-bug-tasks.html
[13:36] <callmepk> okay here
[13:36] <oSoMoN> ( late o/ )
[13:36] <Wimpress> o/
[13:37] <Wimpress> Look fine. Only unassisgned bug is the one we just dealt with.
[13:37] <Wimpress> https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1559650
[13:38] <Wimpress> Again, looks like Daniel is tracking it.
[13:39] <Wimpress> Assign to Daniel?
[13:39] <seb128> yes, the numbers of e.u.c reports seem enough to keep it on the list if he wants to deal with it
[13:39] <seb128> so I would do that yes
[13:39] <Wimpress> Done
[13:39] <Wimpress> #topic rls-ee-bugs
[13:39] <Wimpress> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ee-incoming-bug-tasks.html
[13:40] <Wimpress> All clear.
[13:40] <Wimpress> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ee-tracking-bug-tasks.html
[13:40] <hellsworth> wait
[13:40]  * Wimpress waits
[13:40] <hellsworth> https://bugs.launchpad.net/ubuntu/+source/libreoffice/+bug/1870564
[13:40] <hellsworth> i just tagged that ee-incoming (sorry for that)
[13:40] <hellsworth> i haven't looked at it yet..
[13:41] <hellsworth> but wonder if we want to spend time on it
[13:41] <Wimpress> Want that assigning to you to triage?
[13:41] <hellsworth> sure
[13:41] <hellsworth> but then what happens with the tag?
[13:42] <seb128> doesn't look like rls material to me
[13:42]  * ricotz hopes seb128 didn't forget vala ;)
[13:42] <seb128> especially not for a stable which is about to be superseeded and is not a LTS
[13:42] <seb128> I would vote wontfix for 19.10
[13:42] <Wimpress> seb128: Yeah, I'll drop the tag. It will be loved by hellsworth :-)
[13:42] <seb128> wfm
[13:42] <hellsworth> ok 
[13:42] <hellsworth> thx
[13:42] <seb128> ricotz, no, I just had to step out for a bit and I'm only catching up with things now, will do in a bit
[13:43] <Wimpress> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ee-tracking-bug-tasks.html
[13:43] <ricotz> seb128, ah, I see, thanks!
[13:44] <Wimpress> https://bugs.launchpad.net/ubuntu/+source/network-manager/+bug/1733321
[13:44] <seb128> Wimpress, I would wontfix that for 19.10
[13:44] <seb128> we don't really care about ppc autopkgtest there at this point
[13:45] <Wimpress> Makr  won't fix for 19.10
[13:46] <Wimpress> Looks like sts are tracking that bug.
[13:46] <seb128> yes, I was pondering uploading to focal
[13:46] <seb128> but the current patch is an hack adding a sleep
[13:46] <seb128> and one of their guy asked to work on a proper fix so I will rather wait for that :)
[13:47] <Wimpress> Agreed.
[13:47] <Wimpress> seb128: Can you comment accordingly please?
[13:47] <seb128> sure
[13:48] <Wimpress> Thanks.
[13:48] <Wimpress> #topic rls-ff-bugs
[13:48] <Wimpress> http://reqorts.qa.ubuntu.com/reports/rls-mgr/rls-ff-incoming-bug-tasks.html
[13:48] <Wimpress> OK, there's a lot here.
[13:48] <marcustomlinson> holy moly
[13:48]  * Laney cries
[13:49] <Wimpress> http://launchpad.net/bugs/1867613
[13:49] <Wimpress> Looks like a rls bug to me.
[13:50] <seb128> I tagged it, it has some dups
[13:50] <Trevinho> I was tracking it anyways though
[13:50] <seb128> and even if the bottom of the screen is not the default I saw some comments of users having issues with dock on the left
[13:50] <Laney> take it
[13:50] <seb128> so I would vote +1 and assigning to Trevinho
[13:50] <Wimpress> Done
[13:51] <Wimpress> http://launchpad.net/bugs/1867763
[13:52] <Wimpress> Needs an owner I think.
[13:52] <seb128> I vote +1, it has some duplicates and is trivial to trigger (at least on my xps 13)
[13:52] <Wimpress> Who wants it?
[13:52] <seb128> Trevinho, is that gjs or dock or shell in you opinion? do you have capacity to look at it or should we ask Daniel?
[13:52]  * Trevinho hides
[13:53] <Trevinho> I'm a bit busy... 
[13:53] <Wimpress> I've assigned to Daniel
[13:53] <seb128> thanks
[13:54] <Wimpress> http://launchpad.net/bugs/1870046
[13:54] <Trevinho> it's likely the dock though, so in case I would steal when i'm about to release the dokc
[13:54] <seb128> k, talk to Daniel if needed
[13:55] <seb128> Wimpress, wgrant fixed it (I guess because it was in riscv path), https://launchpad.net/ubuntu/+source/appstream-glib/0.7.16-1ubuntu1
[13:55] <Wimpress> Is 1870046 release blocking?
[13:55] <Wimpress> Marked as fixed released and commented.
[13:56] <Wimpress> http://launchpad.net/bugs/1870062
[13:56] <seb128> we need to accept the ftbfs ones
[13:56] <seb128> so it's just a matter to find assignes
[13:57] <Wimpress> Who want libcmis then?
[13:57] <Laney> I'll have that one
[13:57] <seb128> thanks
[13:57] <Wimpress> Thank Laney.
[13:58] <Wimpress> launchpad.net/bugs/1870508
[13:58] <Wimpress> is rls bug. Who wants it?
[13:58] <seb128> was it a one time thing or is it doing it every time?
[13:58] <Wimpress> Everytime.
[13:59] <seb128> are you sure?
[13:59] <jibel> yes
[13:59] <seb128> there is no dup and no other comment
[13:59] <Wimpress> Can repreoduce everytime.
[13:59] <seb128> and 1 affect person
[13:59] <seb128> those info should be written on bugs :p
[13:59] <jibel> it's the screenreader
[13:59] <Wimpress> I've just +1'd it.
[13:59] <jibel> there is a test case 
[13:59] <seb128> jibel, do you want to try to have a go at fixing it?
[13:59] <Wimpress> I have comments (no via LP) from community about this.
[13:59] <jibel> no
[13:59] <seb128> :(
[14:00] <seb128> Wimpress, want to take on some bugs to help? ;)
[14:00] <seb128> we are going to be short to assign all the things there...
[14:00] <seb128> I can put that one on my backlog but I'm already overcommited at this point
[14:00] <marcustomlinson> I can try
[14:00] <Wimpress> I don't have time this week or next.
[14:00] <seb128> but it's the case of most people
[14:01] <Wimpress> marcustomlinson: Thanks.
[14:01] <seb128> marcustomlinson, thanks
[14:02] <Wimpress> http://launchpad.net/bugs/1870758
[14:02] <seb128> +1 to take it
[14:02] <Wimpress> Yep. 
[14:02] <Laney> They can be fixed by SRUing and we might want to make use of the milestone feature to express that
[14:02] <seb128> Marco thinks it's a driver bug
[14:02] <Laney> possibly by doing a separate pass of all the rls bugs
[14:02] <Laney> not in this meeting
[14:02] <seb128> Laney, good idea
[14:03] <Wimpress> So assign it to Daniel for now?
[14:03] <seb128> tseliot said he would have a look this week, assign to him
[14:03] <seb128> Wimpress, ^
[14:03] <Wimpress> Or just move on?
[14:03] <Wimpress> OK
[14:03] <Trevinho> yeah, I mean... it didn't happen with previous drivers, and anything changed for non-nvidia...
[14:03] <Wimpress> http://launchpad.net/bugs/1871195
[14:03] <seb128> I suggested that one
[14:04] <seb128> see the short video to see the issue
[14:04] <seb128> it's looking lame and I would suggest we disable the adaptive layout, it brings little on a desktop and create those issues
[14:04] <Wimpress> Sounds senisble.
[14:04] <Wimpress> Want to take that one seb128?
[14:04] <seb128> kenvandine, could robert look at it?
[14:04] <kenvandine> sure
[14:04] <seb128> Wimpress, Robert is our gcc maintainer :p
[14:05] <seb128> but he can't I can try to have a look
[14:05] <Wimpress> Assigned to Robert
[14:05] <Wimpress> http://launchpad.net/bugs/1843982
[14:05] <seb128> it has a few duplicates
[14:06] <seb128> I vote +1 to take it
[14:06] <seb128> it's a gdm segfault, not nice
[14:06] <Wimpress> I agree.
[14:06] <seb128> upstream also gave some hints to a fix
[14:06] <Wimpress> Who would like to take that one?
[14:06] <seb128> Laney, sounds like something in your skillset if you have cycles?
[14:07] <seb128> that can probably be a SRU
[14:07] <seb128> well, maybe it's just doing what upstream suggested and trivial, we should sanity check what he wrote though
[14:08] <Laney> I guess so
[14:08] <Laney> Probably should be more than the same few people taking all the bugs though
[14:08] <seb128> indeed
[14:09] <marcustomlinson> I can try this too if kenvandine is fine with me postponing my other work
[14:09] <Wimpress> http://launchpad.net/bugs/1870089
[14:09] <seb128> that's an easy one, need some appstream update
[14:09] <seb128> kenvandine can you maybe take it? 
[14:10] <seb128> (also update to 3.36 maybe while you are at it, the update is done in Debian an trivial, the build issue is what stopped the upload)
[14:11] <Wimpress> Ken wins a bug ;-)
[14:11] <Wimpress> http://launchpad.net/bugs/1870356
[14:11] <kenvandine> yay :)
[14:11] <seb128> unsure about that one
[14:12] <seb128> it's not new but it sucks
[14:12] <seb128> https://www.reddit.com/r/gnome/comments/flpy74/does_anyone_else_see_this_bug_with_bluetooth_ive/?sort=new has stack of users mentioning having the problem and I could confirm
[14:12] <seb128> the bluetooth panel generates constant activity which block the pairing to work by creating resource access conflicts
[14:12] <seb128> well, not pairing, connecting
[14:12] <Wimpress> This feel like a .1 SRU
[14:13] <seb128> at the same time it's not new and ...
[14:13] <seb128> right, my feeling
[14:13] <seb128> do we have a prcoess for that? accept and use milestone?
[14:13] <Wimpress> Do we need to give it an owner right now?
[14:13] <Wimpress> We don't have a 20.04.1 milestone yet.
[14:13] <Wimpress> Who can create those?
[14:14] <seb128> that meeting is long enough, let's deal with that after?
[14:14] <Wimpress> OK
[14:15] <Wimpress> https://bugs.launchpad.net/ubuntu/+source/gnome-shell-extension-desktop-icons/+bug/1844808
[14:15] <seb128> probably also a .1 thing
[14:15] <Wimpress> Agree.
[14:15] <Wimpress> UPstream dev is working on a fix too.
[14:15] <Wimpress> http://launchpad.net/bugs/1870053
[14:15] <seb128> hopefully he manages to fix it and is not something to fix in shell
[14:16] <seb128> gnome-keyring worked after a retry, a test is flacky
[14:16] <Wimpress> OK, move on for now then?
[14:16] <seb128> I would just wontfix, we are too busy
[14:16] <Wimpress> Done.
[14:16] <seb128> flackyness would be nice to resolve but not rls material
[14:16] <seb128> thx
[14:16] <Wimpress> http://launchpad.net/bugs/1867763
[14:17] <Wimpress> That however is a rls bug.
[14:17] <seb128> we already talked about it
[14:17] <seb128> it was listed earlier on gnome-shell
[14:17] <Wimpress> http://launchpad.net/bugs/1869897
[14:18] <seb128> wishlist, would be nice to have but I don't see that making it for .0 at this point
[14:18] <Wimpress> I agree.
[14:18] <seb128> maybe a good .1 candidate
[14:19] <Wimpress> http://launchpad.net/bugs/1870259
[14:19] <Laney> we can say rls notfixing don't forget
[14:19] <Laney> just saying, feel like we are accepting almost everything this week
[14:19] <seb128> sure, all those look important to me
[14:19] <Laney> ok
[14:20] <seb128> but feel free to state -1 when you feel like we should push back
[14:20] <seb128> it's a discussion :)
[14:20] <Wimpress> Olivier seems to be tracking the Firefox one.
[14:20] <Laney> -1 on that touch bug then
[14:20] <seb128> Laney, ubikey one?
[14:20] <Laney> indeed
[14:21] <Wimpress> http://launchpad.net/bugs/1870600
[14:21] <seb128> Wimpress, I would probably vote -1 / notfixing for the firefox one
[14:21] <seb128> kenvandine, ^ do you know if that is by design? (the permission one)
[14:21] <kenvandine> seb128: i do not know
[14:22] <Wimpress> Assign to robert to triage?
[14:22] <seb128> Laney, I agree with that, I want a way to flag .1 potential work though before we get them off the list (maybe just using the desktop-lts-wishlist tag?)
[14:22] <seb128> I tagged it but I would be happy to have opinions
[14:22] <seb128> I think I'm probably -1 for rls
[14:22] <seb128> but I wanted to check with the snap people here
[14:23] <Wimpress> I'd like to know if the snap permissions one is actually a bug.
[14:23] <Wimpress> Making it a .1 is fine by me.
[14:24] <marcustomlinson> assign to robert and leave a comment
[14:24] <hellsworth> idk if the issue reported is by design or not. makes sense to assign to robert for initial look
[14:25] <Wimpress> Done.
[14:25] <marcustomlinson> also, I -1 for the yubikey one too, seems edgey
[14:25] <Wimpress> http://launchpad.net/bugs/1871069
[14:25] <Wimpress> Not rls bug IMO
[14:26] <seb128> -1 from me as well
[14:26] <Wimpress> Tagged accordingly.
[14:26] <kenvandine> thx
[14:26] <hellsworth> maybe they could confirm with other networking tools, like iperf
[14:26] <Wimpress> http://launchpad.net/bugs/1871329
[14:27] <seb128> I think we should accept this one
[14:27] <Wimpress> Daniel suggests it is this bug: http://launchpad.net/bugs/1871329
[14:27] <seb128> after investigation it looks like it might be an upgrade issue
[14:28] <Wimpress> https://bugs.launchpad.net/bugs/1866194
[14:28] <Wimpress> That one ^
[14:28] <seb128> I got that reply from upstream
[14:28] <seb128> 'I would understand if you need to remove the config once after upgrading to PA 13.99 because the way audio is routed has changed significantly. If there is an old preference left, a stream may always play to that old preferred sink.'
[14:28] <seb128> I asked upstream if pulseaudio should then delete its config or migrate it in some way
[14:28] <seb128> anyway I think we need to get that sorted out
[14:29] <Wimpress> Yep.
[14:29] <seb128> so +1 and I'm happy to take assignement
[14:29] <hellsworth> i also vote +1
[14:29] <Wimpress> Done
[14:29] <Wimpress> I have another meeting to get to.
[14:30] <Wimpress> Shall we schedule another one of these later this week to review the remaining bugs?
[14:30] <hellsworth> sgtm
[14:30] <Wimpress> And decide what to do about marking some bugs as .1
[14:31] <Wimpress> OK, ending the meeting here. 
[14:31] <Wimpress> We'll circle back to this.
[14:31] <Wimpress> #endmeeting
[14:31] <meetingology> Meeting ended Tue Apr  7 14:31:28 2020 UTC.  
[14:31] <meetingology> Minutes:        http://ubottu.com/meetingology/logs/ubuntu-desktop/2020/ubuntu-desktop.2020-04-07-13.31.moin.txt
[14:31] <didrocks> thx Wimpress, good next meeting :p
[14:32] <oSoMoN> thanks
[14:32] <seb128> thanks...
[14:33] <seb128> Wimpress, I think we should have covered https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses_by_team.html#desktop-packages still
[14:33] <seb128> I would have been happy to do that, it's late in the cycle to postpone items by a week...
[14:33] <Wimpress> I will schedule a follow up call.
[14:33] <seb128> anyway, I will do it alone and trello cards things as appropriate
[14:45] <Saviq> hellsworth: are you guys aware of a problem with gtk in snaps recently?
[14:45] <Saviq> https://paste.ubuntu.com/p/HZWDzXk8Y9/
[14:46] <Saviq> I can't run firefox or remmina at the moment
[14:48] <apw> hey ... with an up-to-date focal the alt-TAB chooser the 'highlight' is near exactly the smae colour as the background; is this known ?
[14:48] <Saviq> hmm reinstalling the snap helped
[14:50] <marcustomlinson> Saviq: that looked like you either didn't have the gnome-3-xx-1804 installed or the plug was disconnected
[14:50] <marcustomlinson> weird
[14:51] <ogra> btw, it would be great if someone could append "2>/dev/null" to all these relapath calls 
[14:52] <seb128> apw, not known, could you open a bug with ubuntu-bug gnome-shell and include a screenshot showing the issue?
[14:54] <Saviq> marcustomlinson: I did need a hard reset today for other reasons…
[14:55] <marcustomlinson> did you try turning the snap off and on again
[14:55] <marcustomlinson> :)
[14:55] <ogra> or wiggle the cable !
[14:56] <marcustomlinson> yeah the plug obviously came loose :D
[14:56] <apw> seb128, apparently not ... as you cannot take a screenshot while holding alt-TAB
[14:56] <Saviq> marcustomlinson: yeah, that (plus regenerating the pixbuf loaders cache) made firefox go
[14:57] <ogra> where to ??
[15:00] <kenvandine> seb128: https://gitlab.gnome.org/GNOME/yelp/-/merge_requests/21
[15:01] <kenvandine> seb128: i'll work on getting that patch into the package in a bit
[15:03] <seb128> apw, no smartphone?
[15:03] <seb128> kenvandine, thanks!
[15:03] <apw> seb128, yep working on it, but i'd hoped to not have to add 25Mb to it
[15:04] <seb128> 25Mb for a phone picture?
[15:05] <Saviq> marcustomlinson: yeah, mystery solved, all my snap connections went away…
[15:05] <marcustomlinson> oh joy
[15:05] <seb128> Saviq, it's a bit scary that those things do happen still :-/
[15:12] <Saviq> seb128: I'm on zfs root, got ENOSPC (or that's what zfs was reporting…) had to hard shutdown… can't blame it for sync getting wonky
[15:12] <Saviq> s/sync/things/
[15:13] <apw> seb128, https://bugs.launchpad.net/ubuntu/+source/gnome-shell/+bug/1871416
[15:16] <Saviq> love the bjf cameo in that image ;)
[15:16] <apw> seb128, gnome-tweaks says that gnome-shell doesn't have theme support enabled; is that right?
[15:16] <seb128> Saviq, I see
[15:16] <seb128> apw, thanks
[15:17] <seb128> apw, doesn't sound right no, did you change settings or session type?
[15:18] <apw> seb128, not that i know of; this is a very old install since like 8 cycles
[15:18] <apw> seb128, all the others are drop boxes with Yaru in, shell has a triangle with exclamation which has the tool-tip of no theme support
[15:19] <apw> oh it says user-theme extension not enabled
[15:19] <apw> is that somewhere else i wonder
[15:19] <clobrano> apw, you need to install user-theme extension to enable that dropdown menu
[15:19] <apw> why would it not be installed if it is required
[15:20] <clobrano> it's not required in fact, it is optional
[15:21] <apw> clobrano, hmmm, isn't yaru our theme though ?
[15:21] <clobrano> ^ it is needed only to change gnome-shell theme from gnome-tweaks
[15:23] <clobrano> apw, I don't get what you mean. Yaru shell theme is available, what is not available out of the box is the ability to change it to another gnome-shell theme
[15:24] <apw> clobrano, /me backtracks, would the alt-TAB colours be part of that ...
[15:24] <apw> clobrano, as i don't seem to have the right colours in gnome-shell alt-TAB
[15:28] <clobrano> apw, that colors comes from yaru theme for sure. The alt-tab background is #222222, while the highlight is #323232. Honestly, I've never thought it was a problem
[15:29] <clobrano> but the ratio is indeed a bit low
[15:29] <apw> clobrano, so there is nothing wrong with my colours, they are as expected ?
[15:30] <apw> in any kind of backlight i am struggling to even see it
[15:30] <clobrano> apw, it is expected
[15:30] <apw> can i change it without editing yaru ?
[15:31] <clobrano> apw, I don't think so, in 20.04 shell css is in gresource, you should change and rebuild the file
[15:32]  * apw looks sad
[15:32] <apw> feel free to close my bug then, thanks
[15:33] <clobrano> apw, well it's worth a discussion in yaru team :)
[15:33] <apw> designers ... heh ...
[15:34] <clobrano> :)
[16:10] <seb128> kenvandine, there is a .1 vte, want to do that update/merge again? (and maybe g-t also if you have some free cycle this week)?
[16:16] <kenvandine> seb128: we'll see
[16:16] <kenvandine> going to try to do yelp
[16:16] <seb128> right, one step at the time :)
[16:17] <seb128> oSoMoN, want to do the librsvg point update this week if you have some cycles?
[16:17] <oSoMoN> seb128, can do
[16:17] <seb128> thx
[16:22] <kenvandine> seb128: yelp doesn't have an ubuntu/master branch
[16:23]  * kenvandine checks the wiki for instructions :)
[16:24] <Laney> yelp's in sync!
[16:37] <seb128> kenvandine, right, just upload to Ubuntu the build fix since Debian Vcs has a newer version WIP (&MP the fix to Debian), unless you want to finish the update for Debian and MP that with the fix then sync back to Ubuntu
[16:38] <kenvandine> i was going to look at  updated to 3.36
[17:04] <kenvandine> Laney: i just pushed the fix for debian.  Could you sponsor that to debian then we can just sync?
[17:04] <kenvandine> Laney: yelp was UNRELEASED in debian because of this
[17:05] <kenvandine> pushed to debian/master that is
[17:05] <kenvandine> this would fix it for debian and ubuntu
[17:05] <Laney> kenvandine: I'm out of time, will look tomorrow
[17:05] <kenvandine> thx