[00:51] <tsimonq2> Eickmeyer: The fix looks sane enough to me as a workaround, it just seems as if we're missing clear instructions for how to reproduce. Given those instructions, I'll have a good idea on where the bug exists. `GreeterApp::addViewForScreen` in `src/greeter/GreeterApp.cpp` seems responsible, and even then, if it can be consistently reproduced there's debug information for how many views are added, and I could work my way back from there.
[00:56] <Eickmeyer[m]> Simon Quigley: Right. Neither he nor I are C++ programmers, so a workaround method was the only thing reasonable. In terms of reproducibility, it's a race condition and depends on which monitors the hardware picks up first.
[00:59] <Eickmeyer[m]> So, as far as clear instructions go, there are prerequisites: you have to have the mixture of native screen resolutions first.
[01:00] <Eickmeyer[m]> For instance, I don't have a single monitor here that is above or below 1080p in native resolution, so ERR:CantReproduce
[01:01]  * arraybolt3[m] now wishes I had a 4K panel and a DisplayPort cable so I could help with these things
[01:07] <tsimonq2> <Eickmeyer[m]> "So, as far as clear instructions..." <- So emulate it :P
[01:07] <arraybolt3[m]> Simon Quigley: I'm thinking VirtualBox probably won't have hardware initialization speed problems though, and that's the only virtualization software I know of that makes it easy to do multi-monitor with a VM.
[01:08] <arraybolt3[m]> (Just my first thought, I could be wrong. I just know that virtualization cuts out a lot of hardware-related speed problems, like floppy disk write speed to a floppy image file.)
[01:09] <Eickmeyer[m]> ^ This is correct. VB is known for making things in the right order and SDDM can't be fooled by that.
[01:10] <arraybolt3[m]> If someone needed to invest in a physical 4K panel, I found one for ~$230.
[01:11] <Eickmeyer[m]> Mike (the script's author) had this tested on multiple setups before it went live, so honestly, the script is the way to go.
[01:11] <arraybolt3[m]> (I currently don't have the ability to spend that much, but it seems reasonable for a hi-res monitor.)
[01:11] <lubot> [telegram] <teward001> whatre you trying to do again...?
[01:11] <Eickmeyer[m]> arraybolt3[m]: I can't even justify that now.
[01:12] <arraybolt3[m]> @teward001: Make SDDM throw a slight tantrum.
[01:12] <arraybolt3[m]> <Eickmeyer[m]> "kubuntu-focus-4k-external-..." <- @teward001: ^
[01:12] <tsimonq2> @teward001: He's working around Qt monitor detection being fo0bar by throwing a Bash script into the packaging lol
[01:12]  * tsimonq2 runs
[01:13] <Eickmeyer[m]> I mean, that's what /usr/share/sddm/scripts/Xsetup is for.
[01:13] <tsimonq2> ¯\_(ツ)_/¯
[01:39] <lubot> [telegram] <teward001> ah
[07:50] <tsimonq2> so I redid the downloads page: https://lubuntu.me/downloads/
[07:50] <tsimonq2> I suck at UX... generally speaking :P
[07:50] <tsimonq2> so any help would be appreciated
[07:50] <tsimonq2> also, Featherpad in Lunar now uses Qt 6
[07:50] <tsimonq2> time to figure out how to make theming transfer over :P
[07:50] <arraybolt3[m]> Hey, cool! Now we're the first flavor to have experimental builds right out there!
[07:51] <tsimonq2> I pushed Featherpad 1.3.3 to Backports too, but without the Qt 6 build flags. Backports and Lunar should have identical Featherpad, except Backports is still Qt 5
[07:51] <arraybolt3[m]> I would suggest putting a colored square behind each download section, with white borders around the square so that things aren't quite so "fused" together.
[07:51] <arraybolt3[m]> I dunno though, that might look awful.
[07:52] <tsimonq2> Well, maybe... remember this thing uses outdated potatoWordPress
[07:52] <tsimonq2> so any kind of CSS is going to be complicated as heck :P
[07:52] <arraybolt3[m]> I think really if the buttons were just all on the same height that would make it look a bit better. And yeah, maybe switching to a static site would be a good idea.
[07:52]  * arraybolt3[m] bets my best friend could do this without too much trouble, she does professional web design
[07:52] <tsimonq2> arraybolt3[m]: I tried... how do you half-<br /> :P
[07:53] <tsimonq2> > * <@arraybolt3:matrix.org> bets my best friend could do this without too much trouble, she does professional web design
[07:53] <tsimonq2> I will send cookies in exchange for the hidden industry WP knowledge we lost with VikingRedwolf :P
[07:53] <tsimonq2> anyway
[07:53]  * tsimonq2 bed
[07:53] <tsimonq2> that was just my braindump for today
[07:53] <arraybolt3[m]> o/
[08:32] <arraybolt3[m]> Simon Quigley: Whenever you get a chance, it would be awesome if you could push the latest website code to Git so I can mess with it locally. (I don't have (and probably shouldn't have!) access to the Wordpress admin UI I don't think.)
[13:19] <lubot> [telegram] <teward001> think you pinged the wrong person arraybolt3, to my knowledge the only person with direct code access is me :P
[13:20] <kc2bez[m]> I concur with that.
[16:11] <tsimonq2> I used to have direct code access. And access to update WP myself :P
[18:31] <kc2bez[m]> I think we lost that when we had to rebuild.
[19:06] <Eickmeyer[m]> Simon Quigley: Starting my day. Where did we land on the patch?
[19:25] <tsimonq2> In short, I think the patch serves its purpose, which is fixing the bug at hand. It seems sanely written, and if real-world testing has proved effective, I think it is okay, simply in my own capacity. A precedent has certainly been set already for such a patch, but it does not necessarily make it correct. If there is a root cause within Qt, I think that is important to explore. That being said, I could very well see the SRU Team causing an
[19:25] <tsimonq2> issue of the fact that there are no instructions to clearly and reliably reproduce this issue. I have been burned by such a thing before, and I don't want to see you fall into the same denial criteria. If you are willing to proceed despite that risk, I would, at the very minimum, suggest updating the SRU bug to reflect any more facts you may have about the situation, to give the SRU Team an easier time accepting your request.
[19:28] <tsimonq2> As for a Lunar upload specifically, I'm a +1
[19:39] <tsimonq2> arraybolt3: Merge-o-Matic, or MoM, is found here: https://merges.ubuntu.com/... (full message at <https://libera.ems.host/_matrix/media/v3/download/libera.chat/a06ca1a52ac6accfd863df5fa9b9a0a0323ca6d1>)
[19:42] <tsimonq2> guiverc, Leo K, arraybolt3 : If any of you (not limited to you three...) are feeling up for a challenge and want to help out, bug 1996085 and bug 1996087 verification. I did these uploads during the Ubuntu Summit, and the verification instructions are pretty easy.
[19:42] -ubot93:#lubuntu-devel- Bug 1996085 in lintian (Ubuntu Lunar) "Add Lunar as a known Ubuntu distribution" [Undecided, Fix Committed] https://launchpad.net/bugs/1996085
[19:42] -ubot93:#lubuntu-devel- Bug 1996087 in vim (Ubuntu Lunar) "Ensure supported codenames are accurate" [Undecided, Fix Committed] https://launchpad.net/bugs/1996087
[19:43] <arraybolt3[m]> It doesn't do file modes? Like... debdiffs don't support file permissions, you're saying?
[19:44] <arraybolt3[m]> (And also, yes, obviously verify anything that comes out of the depths of an automated tool that's trying to do packaging for you. :P)
[19:44] <tsimonq2> lubuntu-dev: Please note when updating Featherpad to new releases that I manually set the ENABLE_QT5 flag to OFF in d/rules, just make sure you take a look at updates to this line https://github.com/tsujan/FeatherPad/blob/master/CMakeLists.txt#L18 which flows over to https://github.com/tsujan/FeatherPad/blob/master/featherpad/CMakeLists.txt#L7
[19:44] <tsimonq2> arraybolt3[m]: Yeah. If you mark a file as executable and try to use debdiff to represent such a change, debdiff will not translate that over
[19:45] <tsimonq2> As for why? Well, I just haven't dug that far yet. :P
[19:45] <arraybolt3[m]> Oh I can immediately think of where that could bite me (lxqt-build-tools).
[19:45] <tsimonq2> But, Git does support that, which is why I've pushed everything that way. :P
[19:46] <arraybolt3[m]> Makes sense.
[19:46] <tsimonq2> I remember ye olden days of sending debdiffs to my sponsors and also having to ask them to chmod :P
[19:46] <arraybolt3[m]> I may be somewhat busy today since I'm intending on once again overhauling my dev machine (switching from Kubuntu Stable to Lubuntu Unstable like a crazy person - I really should be dogfooding the Lubuntu experience and besides, Lubuntu is awesome and lightweight).
[19:47] <tsimonq2> Believe me, my hair has been on fire all day ;)
[19:47] <tsimonq2> No worries, at all
[19:47] <tsimonq2> Speaking of hair on fire... be back in less than an hour heh
[19:47] <arraybolt3[m]> o/
[20:12] <lubot> [telegram] <Leokolb> Will check in the A.M... (re @lubuntu_bot: (irc) <tsimonq2> guiverc, Leo K, arraybolt3 : If any of you (not limited to you three...) are feeling up for a challenge and want to help out, bug 1996085 and bug 1996087 verification. I did these uploads during the Ubuntu Summit, and the verification instructions are pretty easy.)
[20:12] -ubot93:#lubuntu-devel- Bug 1996085 in lintian (Ubuntu Lunar) "Add Lunar as a known Ubuntu distribution" [Undecided, Fix Committed] https://launchpad.net/bugs/1996085
[20:12] -ubot93:#lubuntu-devel- Bug 1996087 in vim (Ubuntu Lunar) "Ensure supported codenames are accurate" [Undecided, Fix Committed] https://launchpad.net/bugs/1996087
[20:20] <Eickmeyer[m]> Simon Quigley: Thanks!
[20:24] <Eickmeyer[m]> Simon Quigley: Adding this: `NOTE: Testing this requires a setup of monitors with mismatched native screen resolutions, such as 720p combined with 1080p or 1080p combined with 4K. These are just examples, but the problem is known to occur reproducibly in situations with three 4K monitors and one 1080p monitor.`
[20:53] <tsimonq2> Sounds good
[22:51] <arraybolt3[m]> libfm-qt updated in Lunar.
[22:53]  * arraybolt3[m] has an application and a reinstall to work on, that's probably where I'm going to be focusing, also going to try to verify those two SRUs
[22:54] <tsimonq2> Sweet :D
[22:54]  * tsimonq2 digs into work for a bit...
[22:54] <Eickmeyer[m]> Heh, uploaded, but won't see the light of day for a while if bos02 has anything to say about it.
[22:55] <tsimonq2> hah