[01:19] <callmepk> morning
[01:26] <duflu> Morning callmepk 
[03:11] <callmepk> hey duflu 
[04:37] <seb128> goood morning desktopers
[04:57] <duflu> Morning seb128 
[04:57] <seb128> hey duflu, how are you?
[04:58] <duflu> seb128, tired, but pleased that bug 1872159 is fixed sooner than I expected. How are you?
[04:59] <seb128> I'm alright, I saw that nice yesterday and have it on my review list
[04:59] <seb128> why do we have that distro specific timeout to start with?
[04:59] <duflu> seb128, Brian had reasons and a bug it fixed, so I thought it better not to go and remove it. Yet
[05:00] <duflu> It's only useful on a slow or hung plymouthd process, so still useful
[05:08] <duflu> Actually it's not useful on a slow plymouthd process. It's only useful on a permanently hung/frozen plymouthd process
[05:09] <duflu> But even in that case, it will return an incorrect result: Is plymouth running? No, but yes, not in a useful way but still likely hogging the graphics hardware
[05:10] <seb128> duflu, it's annoying, another of those cases where people cowboyed a patch that workaround the issue without taking time to try to upstream it or have a probably review on whether that's the right solution
[05:11] <seb128> the case they tried to deal with what --ping hanging forever, which is something worth upstreaming I think
[05:12] <seb128> duflu, on other news, do you have any idea about bug #1897934 maybe? r-t flagged it as potential blocker for 20.10 now (they emailed a few people in the middle of the night asking if we could help debugging)
[05:25] <duflu> seb128, no I don't have any thoughts other than the three reports there are from old slow Intel systems with old-ish Intel HDA audio. Probably a bug, but I doubt it should block anything
[05:28] <seb128> I tried the iso on boxes and it's muted, but sounds like focal was the same here by trying to start a .1 image (or it's specific to the vm)
[05:37] <duflu> For a small number of people, or even for a large number of people, it shouldn't block anything. Lack of volume with a trivial workaround is not a serious bug worth worrying about. We've actually had more complaints over the years about the default volume being too loud, so zero is probably the lesser evil
[05:38] <duflu> Plus, if failure to reach the login screen is not a release blocker, then low volume definitely is not
[06:28] <seb128> duflu, the rational behind the blocker status was that it makes screen reader not work out of the box which lock some users out of being able to install
[06:29] <duflu> That makes sense
[06:30] <duflu> Although anyone who needs that probably has volume buttons on their keyboard
[06:31] <duflu> That doesn't tell you when to use them though
[06:32] <oSoMoN> good morning desktoppers
[06:32] <oSoMoN> happy release day!
[06:36] <duflu> Morning oSoMoN 
[06:37]  * duflu puts on a helmet
[06:42] <seb128> hey oSoMoN, how are you?
[06:43] <jibel> good morning everyone
[06:46] <seb128> lut jibel, happy release day!
[06:48] <pieq_> salut tout le monde!
[06:49] <marcustomlinson> morning callmepk duflu seb128 oSoMoN jibel pieq_ and desktoppers
[06:49] <pieq_> Have you guys seen the T-shirt Ubuntu-fr did for 20.10 release? https://enventelibre.org/fr/ubuntu-fr/179-416-t-shirt-ubuntu-groovy-gorilla.html Super groovy!
[06:50] <marcustomlinson> yeah très cool
[06:51] <pieq_> duflu, hey, do you use Wayland or X.org with your 4k screen? I've noticed that when I come back from either sleep or lock (Super+L), the context menu triggered by right click is offset *a lot* from the mouse cursor
[06:52] <seb128> hey marcustomlinson , lut pieq_ , how are you?
[06:52] <marcustomlinson> seb128: well thanks, you?
[06:53] <pieq_> seb128, not bad! And you? 
[06:53] <seb128> I'm alright!
[06:54] <duflu> Morning jibel, marcustomlinson 
[06:55] <duflu> Salut pieq_, I currently use Xorg with that. Sounds like you should report a bug
[06:55] <pieq_> duflu, OK, will do. I need to spend some time to find a way to reproduce it 100% of the time
[06:56] <pieq_> (I also use X.org, need to check if the same problem happens on Wayland)
[06:56] <duflu> pieq_, if it's just the desktop then the component is gnome-shell-extension-desktop-icons
[06:56] <pieq_> duflu, no, I've seen the problem with Thunderbird and Files as well
[06:59] <didrocks> good morning
[07:00] <duflu> Morning didrocks 
[07:01] <marcustomlinson> hey didrocks
[07:01] <didrocks> hey duflu, marcustomlinson 
[07:03] <seb128> lut didrocks 
[07:03] <didrocks> salut seb128 
[07:21] <jibel> Salut didrocks999 
[07:22] <jibel> salut marcustomlinson and seb128 and duflu 
[07:24] <didrocks999> salut jibel 
[07:26] <callmepk> hi marcustomlinson and morning/afternoon seb128 oSoMoN jibel pieq_ didrocks 
[07:26] <didrocks> hey callmepk 
[07:27] <jibel> hi callmepk 
[08:15] <Laney> moin!
[08:17] <marcustomlinson> hey Laney
[08:18] <seb128> hey Laney, how are you?
[08:18] <Laney> hey marcustomlinson seb128 
[08:18] <Laney> doing ok yeah
[08:19] <didrocks999> hey Laney 
[08:20] <marcustomlinson> Laney: doing good yeah, you?
[08:20] <seb128> duflu, the overview and mouse over thing, I guess it's a non trivial change? (I'm asking wondering if we should consider backporting to the LTS if possible)
[08:21] <duflu> seb128, IMHO the design is finished/polished yet. But when ready it looks small. Not sure
[08:21] <duflu> is *not*
[08:21] <seb128> k
[08:21] <duflu> Hi Laney
[08:22] <duflu> seb128, I was wondering why we are still forced to have single line labels. Then I looked at my iPhone and it does the same, although that's due to lack of screen space
[08:23] <seb128> duflu, it's not a big issue for default GNOME because their naming convention
[08:23] <seb128> boxes, files, etc
[08:23] <seb128> it's more of an issue for apps that have a brand name like libreoffice...
[08:24] <duflu> Yeah I don't think there's any excuse for not using 2 lines on a typical desktop monitor. There's lots of space
[08:24] <duflu> Maybe I will write a new fix and see what they say
[08:54] <duflu> If kernel 5.8.0-xyz is based on 5.8.n then how do you find out the value of n?
[08:54] <duflu> It's not related to xyz that I can see
[08:57] <seb128> duflu, try asking #ubuntu-kernel ?
[09:02] <duflu> Maybe it doesn't matter. My current bug appears to not exist in mainline kernels
[09:08] <duflu> Hah. Laney I finally found that bug 1893217. What was the upstream link you found?
[09:10] <duflu> Looks like Alan posted a different Chromium bug in the previous conversation. 
[09:12] <tjaalton> duflu: you can grep the changelog, don't think there's any other way to find out the kernel upstream stable release
[09:12] <duflu> tjaalton, probably not needed right now. Thanks
[09:22] <seb128> duflu, https://bugs.chromium.org/p/chromium/issues/detail?id=1122224
[09:24] <seb128> duflu, ah, I see you found it also from your comment, yes it does sound different
[13:52] <luna_> Ubuntu 20.10 release day and my sisters birthday :p
[14:03] <seb128> luna_, happy birthday to them then, you can offer them a new Ubuntu ISO :-)
[14:11] <luna_> seb128: heh, she mostly runs iOS to be honest but yeah
[15:32] <hellsworth> good morning desktopers. happy release day!
[15:33] <marcustomlinson> hey hellsworth
[15:35] <hellsworth> hey there marcustomlinson 
[15:35] <kenvandine> indeed, happy release day!
[15:39] <oSoMoN> good morning hellsworth 
[15:39] <hellsworth> hi there oSoMoN 
[15:45] <jibel> good morning hellsworth 
[15:45] <hellsworth> hi there jibel !
[18:34] <luna_> congrats on the release :)
[18:35] <seb128> luna_, thanks!