[00:10] <arraybolt3[m]> Alright, graphical glitch bug report filed upstream. https://github.com/lxqt/pcmanfm-qt/issues/1597
[00:24] <tsimonq2> Wow, quick response!
[00:25] <tsimonq2> Ohhh.
[00:25] <tsimonq2> He doesn't know we tried that already 
[00:51] <tsimonq2> I guess you gotta follow up on the existing bug report cause yours isn't allowed to stay open ;)
[00:52] <kc2bez[m]> 🤷‍♂️
[00:52] <tsimonq2> I don't sweat it as much as I used to 
[00:53] <kc2bez[m]> It isn't worth it
[00:53] <tsimonq2> Developers have workflows man, he's been maintaining it for a while, who am I to judge?
[00:53] <tsimonq2> Yeah you're right 
[00:53] <kc2bez[m]> He gets a bunch done and is meticulous about it. Hard to complain really.
[00:54] <kc2bez[m]> I think there is a bit of a language/culture difference too.
[00:55] <tsimonq2> Yeah, I can be a bit of a brash American every once in a while ;)
[02:17] <guiverc> Wow & thanks arraybolt3[m], @Leokolb, kgiii, @Noumeno for all your testing I see many hours ago now ^ of LXQt 1.1.1 stuff,  thanks also to our devs tsimonq2 kc2bez[m] 
[02:18]  * guiverc heard a device pinging early this morning as I was in bed... now many hours later & I've finally caught up on it all
[03:49] <tsimonq2> Our entire LXQt stack is waiting on those new packages to migrate.
[03:50] <arraybolt3[m]> Hey, Simon Quigley , can you tell me how exactly to test KWin on Lubuntu? I'm finally back and am fighting with that graphical bug again, and since tsujan couldn't replicate the problem on KWin, I'm trying to use KWin on Lubuntu to test.
[03:50] <tsimonq2> Probably along the lines of sudo apt install kwin
[03:50] <arraybolt3[m]> Doin' that.
[03:50] <tsimonq2> You're going to have to update your default display manager, should do it automatically, lmk if you need help
[03:51] <tsimonq2> Otherwise just systemctl restart kwin or something
[03:51] <tsimonq2> I'm rusty
[03:52] <arraybolt3[m]> Man, I hope I'm not building KLudgebuntu over here...
[03:53] <arraybolt3[m]> Simon Quigley: OK, so about that help... I have never switched display managers in my life before, and have no idea what I'm doing, but I know that sudo apt install kwin followed by reboot didn't do it.
[03:54] <arraybolt3[m]> Oh, hey, looks like "kwin --replace" might do it. Is Openbox ICCCM2.0 complient?
[03:54] <tsimonq2> Try #ubuntu on that one, I know there's a specific command that I can't think of right now. They're quick with it, I'm afk and tired :)
[03:54] <tsimonq2> Don't mean to push you away on this one either - if you don't get it by tomorrow I'll dig in further
[03:55] <arraybolt3[m]> You're fine. We've been working for hours, you probably longer than me, and I'm tired, so I get it.
[03:56] <arraybolt3[m]> OK, kwin --replace seems to have done it!
[03:56] <arraybolt3[m]> And lookie here! Bug still happens!
[03:57] <arraybolt3[m]> OK, should I take this directly to upstream? I've tested compton, picom, and KWin now, all three have the bug. Or should I test something else or wait? (Every time I open an upstream bug, things seem to get closed rather quickly, and I'm afraid it's because I don't know what I'm doing...)
[03:57] <tsimonq2> Keep upstream updated I'd say :)
[03:57] <tsimonq2> One of these times he'll realize what precisely you're saying
[03:57] <tsimonq2> Or comment on the open bug report
[03:57] <tsimonq2> And perhaps try applying that fix again
[03:58] <arraybolt3[m]> OK. Here's hoping that kwin --replace was the right way to do it. (I did this with the PCManFM-Qt fix applied.)
[03:59] <tsimonq2> Sweet.
[04:00] <tsimonq2> https://bileto.ubuntu.com/excuses/4856/kinetic.html#qtermwidget
[04:00]  * tsimonq2 sent a code block: https://libera.ems.host/_matrix/media/r0/download/libera.chat/806ab1824d64b8e5f4d236949dbd768e64a6df38
[04:00] <tsimonq2> I fixed the build dep in texstudio, doing a test build locally then uploading
[04:08] <arraybolt3[m]> OK, reported additional test results. The fact that it isn't reproducible for him on KWin, but is for me, suggests that maybe something is awry with our LXQt stack.
[04:10] <arraybolt3[m]> For in the event this is a problem with our stuff, I'll hold off on reporting the stretched menus bug until we know whether LXQt 1.1.0 is wonky, or if it's our builds and/or config that's causing problems.
[04:43] <tsimonq2> Thanks arraybolt3
[04:44] <tsimonq2> nm-tray update incoming, then featherpad (I'm switching it to the Qt 6 version to test, please pay attention to this update and test thoroughly)
 "Wow & thanks arraybolt3, @..." <- Thank you! You helped me get into this in the first place. Th
[04:49] <arraybolt3[m]> s/th/^U^U
[04:49] <tsimonq2> nm-tray uploaded
 Finally able to log in again on QA test tracker site
[05:36] <guiverc> arraybolt3[m], changing DMs is in our manual; see https://manual.lubuntu.me/stable/3/3.2/3.2.13/session_settings.html   (though you can edit a file; logout/login & be there too) --  likely you worked it out hours ago... but our manual is cool, and I won't miss an opportunity to paste it :)
[09:24] <LeoK[m]> Just performed an update after install with lubuntu daily ISO 02-06-22 and LxQT 1.1.0 looking good - will test further
 The daily ISO has 1.1.0 version? (re @lubuntu_bot: (irc) <LeoK[m]> Just performed an update after install with lubuntu daily ISO 02-06-22 and LxQT 1.1.0 looking good - will test further)
 No but I did an update and got it ..means it will be in todays ISO I believe (re @N0um3n0: The daily ISO has 1.1.0 version?)
 Ahhh ok, thanks!!! (re @Leokolb: No but I did an update and got it ..means it will be in todays ISO I believe)
 NP (re @N0um3n0: Ahhh ok, thanks!!!)
 https://github.com/lxqt/pcmanfm-qt/issues/1597#issuecomment-1145821854 (re @lubuntu_bot: (irc) <arraybolt3[m]> Alright, graphical glitch bug report filed upstream. https://github.com/lxqt/pcmanfm-qt/issues/1597)
[16:26] <tsimonq2> Good morning 
[16:27]  * kc2bez[m] yawns
[16:27] <kc2bez[m]> Afternoon :) 
[16:28] <tsimonq2> Still 11:28 here ;)
 18:28 :p
[16:30] <tsimonq2> I asked in #debian-qt-kde about the Qt bug 
[16:31] <kc2bez[m]> Half past the noon hour here.
[16:31] <kc2bez[m]> Did they concur with the LXQt assessment? 
[16:33] <tsimonq2> https://github.com/tsujan/FeatherPad/discussions/657
[16:33] <tsimonq2> https://github.com/palinek/nm-tray/issues/61
[16:33] <tsimonq2> https://github.com/lxqt/xdg-desktop-portal-lxqt/issues/13
[16:33] <tsimonq2> kc2bez[m]: Don't know yet
[17:45] <tsimonq2> I'd give it a day or two before the images build. We're waiting on those NEW packages and so half the stack migrated...
[18:44] <arraybolt3[m]> Is LXQt 1.1.0 compatible with Qt6? tsujan believes that graphical glitch is a bug in Qt, and since Qt6 exists, I'm leery of opening a bug report against Qt5.
[18:49] <arraybolt3[m]> Nevermind, answered my own question. Qt5 is what LXQt 1.1.0 uses, not Qt6, and the version of Qt5 is uses is LTS, so I'll open the bug report against it.
[19:47] <tsimonq2> Here's the thing, we're waiting on KDE Frameworks 6 to be available 
[19:47] <tsimonq2> If you can find out a) which KF5 modules are used by LXQt; b) how to compile the KF6 versions; c) porting instructions I'll do it 
[19:48] <tsimonq2> I just need some initial research 
[19:48] <tsimonq2> I highly doubt we're there yet though 
[21:56] <arraybolt3[m]> OK, so that bug with the desktop is believed to be in Qt itself, not in LXQt, so I've gone yet another level upstream with the bug report. https://bugreports.qt.io/browse/QTBUG-104020
[21:56] <arraybolt3[m]> (The bug with the rubber band leaving trails behind, I mean.)
 *files a bug against tsimonq2 for reasons*
 i'll be doing critical system updates on our infra shortly.  expect phab and our sites to blip during reboot
[23:58] <kc2bez[m]> Thanks for the heads up @teward001 
 Ok! ;) (re @teward001: i'll be doing critical system updates on our infra shortly.  expect phab and our sites to blip during reboot)