[01:43] <callmepk> good morning
[01:44] <pieq> Morning everyone! Hey callmepk !
[01:45] <callmepk> hi pieq
[02:28] <duflu> Hi callmepk and pieq 
[02:28] <callmepk> hi duflu 
[02:47] <pieq> duflu, you're a star, I saw the Phoronix article about your 4k fix for Gnome, and your praise on Reddit, ahah
[02:47] <pieq> duflu, (and so now I know you have a 4k screen, too!)
[02:48] <pieq> duflu, what scaling do you use? I've been quite disappointed with all the tests I've done: even at 200% (i.e. integer scaling), applications like Telegram and such are blurry
[02:48] <pieq> duflu, the only thing I found was to stay at 100%, and pump the font scaling to 1.5 in GNOME Tweaks
[02:49] <pieq> (and icons, and cursor)
[02:49] <duflu> pieq, it's still pretty slow for me, but that's good because it provides a convenient test environment. I use 200% integer scaling, not fractional. But I also use very few apps so don't depend on anything that doesn't support it
[02:52] <pieq> duflu, xorg or wayland?
[02:53] <pieq> duflu, what IRC client do you use? I found out that hexchat did not support scaling at all (= blurry window and fonts)
[02:53] <duflu> pieq, both actually. My main focal desktop is Xorg and my groovy dev machine is usually with Wayland. They have identical hardware
[02:54] <duflu> pieq, actually HexChat supports 200% kind of, fine. Maybe it just doesn't support fractional
[02:54] <duflu> super sharp, not blurry
[02:54] <pieq> duflu, I wanted to use Polari, but then I'm facing this issue: https://gitlab.gnome.org/GNOME/polari/-/issues/118
[02:55] <pieq> duflu, OK then it's weird, cause when I enable 200% on wayland, a lot of apps are blurry... I'm not sure what I've done wrong.
[02:56] <duflu> pieq, Wayland scaling is different to Xorg, and fractional scaling is different to integer, and there are TWO separate implementations of fractional scaling
[02:57] <duflu> pieq, HexChat is very sharp at 200% in Xorg with fractional scaling off
[02:57] <duflu> pieq, you can also do fine adjustments in Gnome Tweaks > Fonts
[02:59] <pieq> duflu, but "200%" scaling on Wayland is an integer scaling, right? So I should get sharp stuff for this...
[02:59] <pieq> duflu, I'm not near my home desktop right now, I'll keep investigating later
[03:00] <duflu> pieq, depends on the app, and Wayland will do it differently to Xorg
[03:00] <pieq> duflu, what size is your screen? Mine is 27"
[03:00] <duflu> Yep, 27" 3840x2160
[03:00] <pieq> argh... that's too complicated (I mean the fact that different apps react differently, and the xorg/wayland thing)
[03:00] <duflu> Yeah there are too many combinations
[03:00] <duflu> It's a mess
[03:01] <pieq> I wish we could agree upon something to use, and use it. I hope the Xorg → Wayland transition doesn't take 12 years like the Python 2 → Python 3 transition!
[03:11] <duflu> pieq, actually everyone other than Ubuntu and Nvidia have transitioned
[03:11] <duflu> so people are trying
[03:14] <duflu> It's taking a few years for the major web browsers though
[03:17] <pieq> duflu, yeah, I like how there is a dedicated workflow for Firefox on Wayland when using Fedora. I wish we had something like that in place with Ubuntu
[03:18] <duflu> pieq, env MOZ_ENABLE_WAYLAND=1
[03:19] <duflu> or in your /etc/environment
[03:20] <pieq> duflu, yeah that's what I ended up doing
[03:20] <pieq> created different desktop launchers
[03:20] <pieq> and faced the super annoying issue with GNOME only showing the first 12 chars in the overview, so all my launchers are like "Firefo..." and I never know which one to run :D
[04:14] <luna_> watching Wimpress and sil code the Rhino :P
[04:14] <luna_> https://www.youtube.com/watch?v=Q4k8LqEUxlM
[04:17] <luna_> missed it live yesterday but woke up early due to the lightning strikes here in Stockholm this morning
[05:59] <seb128> goood morning desktopers
[06:00] <duflu> Hi seb128 
[06:06] <seb128> hey duflu, how are you? had a good w.e?
[06:09] <duflu> seb128, it went fast but at least I got a few things done. Been raining lots here. You?
[06:11] <duflu> Good to see the post-focal bug expiries are now starting
[06:21] <oSoMoN> good morning desktoppers
[06:28] <seb128> hey oSoMoN, wb, did you have a good week of vac?
[06:29] <seb128> duflu, w.e was nice, a bit windy and rainy but we still managed to walk around a bit
[06:29] <oSoMoN> salut seb128, yeah, quite relaxing, thanks!
[06:30] <duflu> Morning oSoMoN 
[06:39] <oSoMoN> hey duflu
[06:50] <marcustomlinson> morning desktoppers
[06:53] <oSoMoN> good morning marcustomlinson 
[06:58] <marcustomlinson> hey oSoMoN how was your week off?
[07:00] <oSoMoN> pretty good, I spent all the time with friends and family, and slept a lot more than usual
[07:09] <marcustomlinson> sounds excellent
[07:34] <duflu> Hi marcustomlinson 
[07:35] <marcustomlinson> hey duflu
[07:49] <seb128> hey marcustomlinson, wb, did you have a good of vac?
[07:49] <seb128> oSoMoN, sleep sounds nice! I see that you had the laptop with you at the end :p
[07:51] <marcustomlinson> seb128: was very nice thanks! lockdown eased enough for us to visit my parents a couple times. hit the beach too. nice and relaxing.
[07:54] <oSoMoN> seb128, I did, and I don't regret it, I poked at the nodejs/firefox update throughout the week and now I'm less stressed about it
[07:59] <seb128> oSoMoN, as long as you managed to get pulled too much into work mode and properly relaxed still I guess that's fine :)
[08:00] <ricotz> hey desktopers!
[08:00] <Laney> guten morgen
[08:04] <duflu> Hi ricotz and Laney 
[08:08] <Laney> howdy duflu 
[08:14] <seb128> hey ricotz, Laney, how are you? had a good w.e?
[08:19] <Laney> moin seb128 
[08:20] <Laney> yeah was alright, not super nice weather but not as bad as the forecast had predicted
[08:20] <Laney> did some playing with networking, trying to get things in a better order before i get a new connection on friday
[08:20] <Laney> hope you did too!
[08:32] <Laney> why no sound? oh, I restarted, and therefore Pulseaudio forgot which output I had selected before
[08:32] <Laney> :| :| :| :| :|
[08:35] <seb128> w.e was alright, weather was not great but nice enough that we could go to the playground and have some fun there yesterday
[08:35] <jibel> welcome to the club of PA lovers
[08:35] <seb128> @sound bugs :-(
[08:36] <seb128> would probably be useful to report those issues upstream
[08:36] <seb128> we currently fail at deal with audio issue, it would increase chances to have someone looking at the problem
[08:37] <seb128> Laney, is than hdmi that you use?
[08:37] <jibel> yeah but the stack is complex and between the kernel, alsa, pa and the shell it's hard to determine where the problem is
[08:38] <seb128> well, you can always take a guess, if you are wrong they will just close the bug telling you to go to $otherplace
[08:38] <seb128> they might help you to figure out what the right component is :)
[08:39] <duflu> "shotgunning" as my former Texan manager would say
[08:40] <duflu> Which I think refers to spraying multiple locations simultaneously
[08:46] <Laney> seb128: it's a usb device which gets preferred, kind of like that hdmi bug though
[08:46] <Laney> because it's plugged into a usb hub on the monitor
[08:47] <Laney> so it appears on the bus quite late on I guess
[08:49] <seb128> Laney, https://gitlab.freedesktop.org/pulseaudio/pulseaudio/-/issues/886 ?
[08:49] <seb128> bug #1877194
[08:50] <Laney> yeah probably
[08:50] <Laney> I could try moving it out of the monitor to see if that makes a difference
[08:50] <Laney> but then need to find a longer cable
[08:50] <Laney> so not for now
[08:55] <seb128> I guess it's the same issue than the HDMi one at the end, pulseaudio is not smart enough to remember your device preferences
[08:56] <seb128> ideally it would have a ranking of priority and default to the one available according to the ranking
[08:56] <Laney> it's doing switch-on-connect when it's not really on-connect, so yeah
[08:57] <Laney> let me make a debug log and reboot
[08:58] <Laney> systemctl --user --global --full edit pulseaudio!
[08:58] <seb128> I don't know if it's possible to tell whether the device is showing because it has been physically connected or just picked by the usb system
[09:00] <Laney> not sure what you mean
[09:00] <Laney> if this comes up as a hotplug-switch to the usb audio device, that will be the bug
[09:03] <seb128> I mean, does the kernel / udev gives us enough information to know why the add event has been generated?
[09:03] <seb128> like can we tell appart from the OS side whether it's just the usb subsystem picking up a device already connected or if there has been a physical connect ?
[09:06] <Laney> udevadm settle?
[09:07] <Laney> anyway, not sure there's much value in us debating the bug in here
[09:07] <Laney> I will just reply on there
[09:09] <seb128> right, I was just thinking about it, sorry for the noise
[09:09] <seb128> thx
[09:23] <Laney> ok, reproduced without the monitor's hub in the way, better :>
[09:23] <Laney> enough fiddling with that for today
[10:21] <jibel> xnox, ubiquity 20.10.6 is blocked in proposed on a dependency issue. Something from d-i. Did you have a look? 
[10:21] <jibel> current images are not installable with 20.10.5
[10:21] <jibel> https://people.canonical.com/~ubuntu-archive/proposed-migration/update_excuses.html#ubiquity
[10:22] <xnox> jibel:  interesting.
[10:23] <seb128> https://launchpad.net/ubuntu/+source/main-menu/+publishinghistory that has been deleted 'component of d-i which is not supported post-focal'
[10:23] <seb128> someone didn't do their job of checking rdepends before deleting components from the archive
[10:25] <xnox> jibel:  uploading fix.
[10:25] <xnox> seb128:  it's hard to check udeb reverse-deps, no?
[10:26] <jibel> xnox, thanks
[10:28] <seb128> xnox, I don't know how to do that, but the fact that it's not trivial doesn't mean it shouldn't be done ... anyway, problem fixed so thanks
[16:08] <Laney> something weird with arch:all packages in the new proposed-migration :(
[16:08]  * Laney is trying to fix
[16:18] <seb128> Laney, how is the new proposed migration going? aiming at landing it this week? any outcome of the entries that create problems to the by team report?
[16:18] <Laney> what entries?
[16:18] <Laney> yes this week ideally
[16:27] <Laney> ah found the problem It hink
[16:30] <Laney> thanks evolution for notifying me about an event 1 minute before it ends :>
[18:14] <seb128> Laney, sorry, didn't see you reply, the bug ones that are leading to a #0, you said you were discussion in Debian to move them in a place where they don't confuse the current parser
[19:59] <Laney> seb128: ah, I had that, it's not going to change right away so things need to handle the current format for now