[03:52] <guiverc> lubuntu live; tested for https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1989163 and no issue today?   @Leokolb can you confirm it's still an issue (ie. ensure I'm not off on a tangent & looking for something else; mild headache today so maybe just me)
[03:52] -ubot93:#lubuntu-devel- Launchpad bug 1989163 in xscreensaver (Ubuntu) "Unable to run screensaver when selected from menu" [Undecided, Confirmed]
[03:53] <guiverc> actually probably certain it's just me; David / kgiii has tagged it on same ISO
[03:54] <guiverc> (just me, as in me misunderstanding issue today; headache distraction maybe3)
[03:55] <kgiii> What'd I do? I only noticed the same two bugs today. The screensaver didn't load and software-properties-qt threw the same error.
[03:55] <kgiii> LOL It's also almost midnight, so I was almost stepping away for the night. But, I have a few minutes. The missus is a patient woman, thankfully.
[03:56] <guiverc> kgiii, you provided the confirmation I just asked for from Leokolb...   Looking for issues on a issue.tracker & didn't re-create that one, but you did... I'm now assuming I didn't test it properly
[03:56] <guiverc> No we'll be right kgiii, sign off... sorry for ping.. 
[03:56] <kgiii> I can double check that the screensaver didn't load if need be. 
[03:56] <kgiii> Give me like two minutes, as I think that's what you're looking to confirm.
[03:57] <guiverc> no need today... you found it, tagged it.. We don't need more, if anyone needs to retest it should be me given your result!
[03:59] <kgiii> Ping any time. I won't hear/notice it, unless I'm at this device and logged in. And, yeah, I can confirm that the screensaver 100% didn't load in today's ISO. There was no .1 release that I may have missed.
[03:59] <kgiii> And, I'm always happy to help - assuming I'm awake. ;-)
[03:59] <guiverc> Thanks kgiii !
[04:00] <kgiii> No problem. I'm going to shuffle off to bed. I just got the Quassel/IRC notification that the day has now changed to Friday so enjoy your weekend!
[04:00] <guiverc> :)  You too  (when you get there..)
[05:36] <guiverc> another box; and I get a crash with xscreensaver just like bug report ^  https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1989163   is it hardware specific?   (I intend to look on other boxes when I can)
[05:36] -ubot93:#lubuntu-devel- Launchpad bug 1989163 in xscreensaver (Ubuntu) "Unable to run screensaver when selected from menu" [Undecided, Confirmed]
 Will this am and get back (re @lubuntu_bot: (irc) <guiverc> another box; and I get a crash with xscreensaver just like bug report ^  https://bugs.launchpad.net/ubuntu/+source/xscreensaver/+bug/1989163   is it hardware specific?   (I intend to look on other boxes when I can))
[05:50] -ubot93:#lubuntu-devel- Launchpad bug 1989163 in xscreensaver (Ubuntu) "Unable to run screensaver when selected from menu" [Undecided, Confirmed]
 Another confirm @guiverc screensaver bug still present latest Kinetic ISO — also think the artwork looks real good !
[10:07] <guiverc> yeah I tested again on the sony.crapbook (post-install) and it occurred again...  no idea why it didn't the first time
[10:08] <guiverc> thanks @Leokolb
[18:20] <arraybolt3> Wrt the LXQt bugs mentioned earlier, we now have a bug report for them. LP: #1992196. I am still working on debugging and hopefully resolving it.
[18:20] -ubot93:#lubuntu-devel- Launchpad bug 1992196 in lubuntu-meta (Ubuntu) "Various highly noticable graphical glitches have all started happening in Kinetic at the same time" [Undecided, New] https://launchpad.net/bugs/1992196
[19:05] <arraybolt3[m]> Oh. My gosh. I've just spent the last few hours trying to compile Qt and couldn't figure out why it wasn't working right. Turns out I was only building qtbase and not the whole rest of it. 🤦‍♂️
[19:10] <arraybolt3[m]> Though admittedly the bug is probably only in qtbase. But Featherpad absolutely will not launch with LXQt using Qt5.15.6 and me directing just Featherpad to launch using Qt5.15.5.
[19:13] <arraybolt3[m]> Hmm. Realizing the bit about the bug probably being only in qtbase is now making me doubt myself.
[19:14] <arraybolt3[m]> Simon Quigley: When I build qtbase 5.15.5, then try to force Featherpad to use it by setting LD_LIBRARY_PATH and PATH properly, Featherpad fails with an error about incompatible Qt versions (5.15.5 and 5.15.6). What am I doing wrong here?
[19:16] <arraybolt3[m]> I don't really want to build qtbase, qtcompat, qtcharts, qtlocation, qtsensors, qtspeech, qtwebengine^U, etc.
[19:16] <arraybolt3[m]> (Not actually building qtwebengine but you get my point.
[19:16] <arraybolt3[m]> )
[19:19] <arraybolt3[m]> I've also tried handing sbuild a custom-made tarball of the Qt source so I could try to git bisect that way, and it was a miserable fail.
 Have you tried to change the widget Qt style? (re @lubuntu_bot: (irc) <arraybolt3> Wrt the LXQt bugs mentioned earlier, we now have a bug report for them. LP: #1992196. I am still working on debugging and hopefully resolving it.)
[19:54] -ubot93:#lubuntu-devel- Launchpad bug 1992196 in lubuntu-meta (Ubuntu) "Various highly noticable graphical glitches have all started happening in Kinetic at the same time" [Undecided, New] https://launchpad.net/bugs/1992196
[19:58] <arraybolt3[m]> @Leokolb: Just tried it, and... interesting. Setting it to Fusion works.
[20:00] <arraybolt3[m]> There aren't any recent uploads of lxqt-themes, though.
[20:00] <arraybolt3[m]> ...but maybe that's the problem, a Qt incompatibility maybe?
[20:00] <arraybolt3[m]> (If this works I'm going to be a little bit upset.)
[20:01]  * arraybolt3[m] attempts a no-change rebuild of lxqt-themes
[20:03]  * arraybolt3[m] shakes GitHub vigorously, our debian/watch for lxqt-themes is broken due to a recent change they made
[20:06] <arraybolt3[m]> Thankfully, looks like I don't need the watch file at all, a simple sbuild in the directory given by pull-lp-source seems to be working.
[20:24] <arraybolt3[m]> No change rebuild failed to fix the problems.
[20:25] <arraybolt3[m]> How is it possible we've missed this for this long? I can't help but think this must be a new thing.
[20:25] <tsimonq2> ¯\_(ツ)_/¯
[20:26] <tsimonq2> Qt did only land in the last week
[20:26] <tsimonq2> Occam's Razor would suggest Qt broke it
[20:32]  * arraybolt3[m] goes back to trying to compile an older Qt with sbuild via a tarball hack
[20:50] <arraybolt3[m]> This thing is making me lose my mind. Trying to use the 5.15.5 tarball just tells me "Cannot process version from .qmake.conf" "Cannot proceed." I see the part of the configure script that's doing it, but I can't tell it to stop it! AGH!
[20:53] <arraybolt3[m]> Oh. My gosh. What is wrong with me. It's a hidden file for crying out loud, and I didn't make my tarball repack include any hidden files.
[20:53] <arraybolt3[m]> (Er, not any hidden files in the base directory.)
[20:53] <arraybolt3[m]> So now that I've thoroughly humiliated myself yet again, NOW let's see if this builds.
 As far as I can see "File is still there just in white color ..and barely visible unless as mentioned the widget style is changed
[21:09] <arraybolt3> @Leokolb: You're able to see it at all? Maybe I just didn't look hard enough. It appears to just vanish outright for me.
[21:13] <arraybolt3[m]> Alright, I officially give up on getting the packaging to work. I'm going to just hack the config options from the packaging and build manually. I probably won't get this done today, but I sure have learned a lot of what I'm doing!
[22:09] <arraybolt3[m]> Alright! Finally got Qt to build and be installed system-wide! Now no Qt apps will open. 🥴
[22:09] <arraybolt3[m]> Because I failed to install the build dependencies before compiling and installing. Sigh.
 Tried 2 different machines/and displays - yes I can see faint white letters after selecting i.e. File or edit etc ..I would not consider this a bug but poor match of coloring etc (re @lubuntu_bot: (irc) <arraybolt3> @Leokolb: You're able to see it at all? Maybe I just didn't look hard enough. It appears to just vanish outright for me.)
[22:16] <arraybolt3[m]> @Leokolb: Well it didn't used to happen, and there haven't been any recent changes to lxqt-themes, so it shouldn't have happened. Something changed so that the once-correct colors are now no longer being displayed right. I guess it's not a bug in the technical sense, but in my opinion, it messes with the user interface in a highly unpleasant way.
[22:17] <arraybolt3[m]> Hey wait a minute. The Breeze theme isn't part of lxqt-themes. So... what is it a part of?
 And it is only in Breeze that this occurs.. (re @lubuntu_bot: (irc) <arraybolt3[m]> Hey wait a minute. The Breeze theme isn't part of lxqt-themes. So... what is it a part of?)
[22:19] <arraybolt3[m]> I see what's happening - it's just that the blue highlighting no longer works. KDE uses the Breeze theme, and when you click on a menu item in Kate, the text turns white, but the blue highlight makes it visible. Maybe rather than trying to revert something in Qt's code, it would be better to chase down what is not incompatible in Breeze and fix it.
[22:19] <arraybolt3[m]> (Also the Breeze theme seems to be it's own thing.)
 Nice -good work- at least we now have some answers .thanks (re @lubuntu_bot: (irc) <arraybolt3[m]> (Also the Breeze theme seems to be it's own thing.))
[22:20] <arraybolt3> Man, if it turns out to be this easy to fix, I'm going to be quite thankful. Qt has given me a fight like no other package so far.
[22:22] <arraybolt3> Doing a no-change rebuild of Breeze...
 Just noticed that the box in numer 2 under Qt palette settings is missing - see the difference in Jammy
[22:29]  * LeoK[m] uploaded an image: (83KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/uosuiqMCydTVFXXblgFkufsf/Jammy.png >
[22:31] <arraybolt3> @Leokolb: The GTK themes stuff?
 Yes ..so maybe a bug after all ..compare that image with kinetic (re @lubuntu_bot: (irc) <arraybolt3> @Leokolb: The GTK themes stuff?)
[22:32] <arraybolt3> In Kinetic, it appears to have been moved to a "GTK Style" section - scroll down in the left menu a little bit.
[22:32]  * LeoK[m] uploaded an image: (139KiB) < https://libera.ems.host/_matrix/media/r0/download/matrix.org/wZCuaRQYSJivLHztuuaMIqan/kinetic.png >
[22:34] <arraybolt3> @Leokolb: Notice the scrollbar in the menu on the left. The botton entry that's hiding off the size of the screen has those settings now. (Just confirmed this on a Kinetic VM in front of me.)
[22:34] <arraybolt3> s/size/bottom edge/
[22:34] <LeoK[m]> arraybolt3: Ah...see it now ..getting late here (obviously..)
[22:36] <arraybolt3[m]> LOL you should see me over here. I've lost count of the number of "I did WHAT?" moments I've had today. :P
 Calling it a day..see ya! (re @lubuntu_bot: (irc) <arraybolt3[m]> LOL you should see me over here. I've lost count of the number of "I did WHAT?" moments I've had today. :P)
[22:37] <arraybolt3[m]> @Leokolb: 👋 Thanks for your help!
[22:53] <arraybolt3[m]> OK, I'm mostly done for today. Depending on the speed of this zsync, I'm going to report back whether or not Kubuntu also suffers from this issue, because if so, it's something that KDE will probably want to look into. I may end up not doing that today though. Hopefully I'll see you guys tomorrow night!
[23:11] <RikMills> arraybolt3[m]: what bug?
[23:19] <arraybolt3[m]> Rik
[23:19] <arraybolt3[m]> RikMills: LP: #1992196
[23:19] -ubot93:#lubuntu-devel- Launchpad bug 1992196 in lubuntu-meta (Ubuntu) "Various highly noticable graphical glitches have all started happening in Kinetic at the same time" [Undecided, New] https://launchpad.net/bugs/1992196
[23:22] <arraybolt3> RikMills: Just updated the bug report, so if you opened it, refresh the page.
[23:43] <RikMills> urgh
[23:51] <RikMills> arraybolt3: in lxqt appearance settings, widget style tab, you change 'selected text' colour to black, does that not fix it?
[23:52] <RikMills> the white menu text, anyway