[01:31] <teward[m]> Simon Quigley yeah if you had coredev and just recently dropped off any DMB member has the ability to JFDI and reinstate
[01:31] <teward[m]> Simon Quigley now, this said.  you need to fine tune your mail filters :P
[03:35] <guiverc> Lubuntu Manual icon on desktop (live session) still isn't doing anything but give error for me.. It's been mentioned before, is there a bug for it?
[03:51] <arraybolt3> guiverc: I'm not aware of a bug for it.
[03:53] <guiverc> thanks arraybolt3 , I may have just mentioned it before (often do before filing, often don't file too)
[07:47] <guiverc> ^ 'lubuntu manual' desktop link works on installed systems, plus if an additional user is added to a live session it'll work (on additional user) there too; so at worst a release doc mention maybe required
 If you wait 2 or 3 minutes after booting the Manual link works - connected to the Fiirefox bug in Live CD (re @lubuntu_bot: (irc) <guiverc> ^ 'lubuntu manual' desktop link works on installed systems, plus if an additional user is added to a live session it'll work (on additional user) there too; so at worst a release doc mention maybe required)
[08:40] <guiverc> ack... and trying again.. I can confirm it works with uptime of 5hrs 14mins, so it continues to work :)
[08:40] <guiverc> thanks @Leokolb.. I'd have thought I'd have tried it after that time, but I don't recall
 Wow! :) (re @lubuntu_bot: (irc) <guiverc> ack... and trying again.. I can confirm it works with uptime of 5hrs 14mins, so it continues to work :))
[08:42] <guiverc> I suspect that should be mentioned in the release notes though (not specific time period, just a delay after staring before it'll work maybe)
[08:43]  * guiverc on occasion uses a live session as a machine OS
 Agree @guiverc should be mentioned ..
 The bug @guiverc is 1991011
[08:47] <guiverc> thanks @Leoolb, greatly appreciated !
[08:48] <guiverc> yeah I remember that one.. I noted Ubuntu have ref. to release notes too :)  
[08:56] <guiverc> noted in kinetic issue tracker 
 on faster machines the wait is sometimes only 10 or 15 seconds... (re @lubuntu_bot: (irc) <guiverc> noted in kinetic issue tracker)
[09:02] <guiverc> we could mention the speed of machine too... but in my experience it's longer than 3 mins on c2d type hardware  (at least it sure feels that way)
 I don´t think we should mention the speed (give no false promises etc) (re @lubuntu_bot: (irc) <guiverc> we could mention the speed of machine too... but in my experience it's longer than 3 mins on c2d type hardware  (at least it sure feels that way))
[09:19] <guiverc> specifically no, I was thinking just a warning that 'some older hardware may take a little longer to be ready than newer hardware'  (ie. vague)
 Ah..yes @guiverc agree
 "[telegram] <Leokolb> If you wait..." <- OH this bug is just a race condition, I could tell you what's causing it
[13:45] <arraybolt3[m]> Simon Quigley: Ah, it's that thing with the livecd-rootfs, isn't it?
[13:45] <tsimonq2> Well, snaps do take a minute to preseed when the image is first booted.
[13:46] <tsimonq2> I'm on paid time so I'll save you from the entire explanation - but the short of it is, snapd isn't done installing the snaps before Firefox is launched, that's what it is 
[13:46] <tsimonq2> (And you can't install snaps in a chroot, so that's their workaround, use preseeding which basically formats a YAML and downloads the files)
[13:48] <arraybolt3[m]> Yeah, I remember that bug. Here's hoping they figure out how to fix it.
[13:56] <Eickmeyer[m]> It's already fixed, but just like everything else in the release queue, nothing has been worked on.
[13:57] <tsimonq2> I mean, the active members of the team only include Canonical employees at the moment as far as I know
[13:57] <tsimonq2> I get it... people are busy. Just don't tell me I didn't upload it in time :P
[13:57] <Eickmeyer[m]> No, one is not a Canonical employee, but two are on vacation this week.
[13:58] <tsimonq2> Sounds about right. Hey, people gotta take vacation eventually. Once everyone is back if stuff isn't any better we can raise further hell... but I have a lot of patience here
[13:59] <Eickmeyer[m]> But that's only 2 out of 8, so I really don't think that's any excuse. It's an equally-shared responsibility this time of the cycle, so there's a ball being dropped.
[14:00] <Eickmeyer[m]> Others have commented on how long the unapproved queue is this close to Final Freeze.
[14:02] <tsimonq2> I have to choose my battles these days, and this is not a battle we can really win unless someone volunteers, and I'm getting there...
[14:02] <tsimonq2> I'm definitely not disagreeing with you
[14:02] <tsimonq2> Is it worth further action? Not yet, to me at least...
[14:04] <Eickmeyer[m]> No, not worth further action. I'm just venting/a little concerned.
[14:04] <tsimonq2> Yeah no, I definitely get where you're coming from
[19:37] <arraybolt3[m]> Did anyone see any Qt-related or LXQt-related changes go into the archive recently? LXQt has a couple of severe graphical problems that manifested just recently, and I'm wondering where to start looking.
[19:37] <arraybolt3[m]> (Also, if anyone knows an easy way for me to find out, that would be awesome.)
[19:37] <tsimonq2> DDG: !upkg qtbase-opensource-src
[19:37] <arraybolt3[m]> Code decrypted, executing...
[19:37] <tsimonq2> https://launchpad.net/ubuntu/+source/qtbase-opensource-src/5.15.6+dfsg-1
[19:38] <tsimonq2> https://launchpad.net/ubuntu/+source/qtbase-opensource-src/5.15.6+dfsg-1
[19:38]  * tsimonq2 uploaded an image: (13KiB) < https://libera.ems.host/_matrix/media/r0/download/linuxdelta.com/rTIDwyIJtQVzfwceEHysCaYn/image.png >
[19:38] <arraybolt3[m]> Simon Quigley: Wow, looks like you're faster at this than I am.
[19:38] <tsimonq2> https://launchpad.net/ubuntu/+source/lxqt-qtplugin/1.1.0-1build1
[19:38] <tsimonq2> Migrated the same time as Qt did
[19:39] <arraybolt3[m]> OK, lemme try downgrading some stuff and see what happens.
[19:39] <tsimonq2> Raw list of package uploads to Kinetic: https://lists.ubuntu.com/mailman/listinfo/kinetic-changes
[19:39]  * arraybolt3[m] really really hopes that this isn't a new Qt bug
[19:39] <tsimonq2> Congratulations, guess what kind of bugs I've fixed before :P
[19:40] <arraybolt3[m]> OK, into the fray I go. Wish me luck!
[19:40] <tsimonq2> If you need help git bisecting Qt and you can identify reproducible steps w/ no ability to reproduce on Debian Testing https://tracker.debian.org/pkg/qtbase-opensource-src then lmk
[19:41] <arraybolt3[m]> 👍️
[19:42] <arraybolt3[m]> (wait, I have to compile all of Qt? 😰)
[19:42] <tsimonq2> well if it's a Qt bug yes
[19:42] <arraybolt3[m]> Guess this is what sbuild is good for.
[19:42] <tsimonq2> don't worry though, we don't seed QtWebEngine
[19:42] <arraybolt3[m]> \o/
[19:42] <tsimonq2> (That takes 24 hours to compile on my machine, still, in 2022...)
[19:43] <arraybolt3[m]> I've compiled KDE Plasma multiple times in just the last few days so I don't know why I think Qt will be daunting. Anyways, I have it downloading now and will begin the attack shortly.
[19:46] <arraybolt3[m]> Oh lovely. Well on the bright side I don't have to fight with git-buildpackage. On the dark side, the packaging and source code are decoupled so that means I have to integrate the actual Qt source itself from a different Git repo.
[19:46] <tsimonq2> Welcome to packaging Qt ;)
[19:47] <arraybolt3[m]> And it's pulling almost a million files (not an exaggeration). 🤪
[19:47] <arraybolt3[m]> (836,197 objects to be exact.)
[19:47] <tsimonq2> Oh yeah. If your connection isn't fast I'd use a shallow clone
[19:47] <tsimonq2> --depth=1 or similar
[19:47] <tsimonq2> But if you're bisecting you need a full clone soooooo
[19:48] <tsimonq2> ¯\_(ツ)_/¯
[19:48] <arraybolt3[m]> Eh, it's fast enough. Probably about as fast as an ISO download. Will --depth=1 still let me bisect?
[19:48] <arraybolt3[m]> Yeah, that's kinda what I figured.
[19:48] <arraybolt3[m]> (I guess almost a million files actually is an exaggeration to some degree - about a million files is more accurate, but whatever.)
[19:49] <arraybolt3[m]> s/almost/about/
[19:54] <tsimonq2> (Isn't exaggerating a highball not a lowball? :) )
[19:55] <arraybolt3[m]> Almost a million would be like 950,000 or something, so that would be a highball IMO.
[19:55]  * arraybolt3[m] blames the Qt mess on teward
[19:56] <tsimonq2> oh, you didn't <em> *about*, I catch your drift
[19:56] <teward[m]> hey i don't touch GUI stacks as far as I can throw them
[19:57] <tsimonq2> he's right, he's the reason all of the infra is down ;)
[19:57] <arraybolt3[m]> Right but it's about time we blamed everything on someone other than Simon and you're the next most obvious target. :P
[19:57] <teward[m]> *throws simon into the abyss*
[19:57] <arraybolt3[m]> Abyss is closed on Thursday.
[19:57] <teward[m]> no, not that abyss
[19:58] <teward[m]>  /dev/abyss which links to /dev/null
[19:58] <arraybolt3[m]> I thought I deleted that symlink long ago!
[19:58]  * arraybolt3[m] immediately runs rkhunter to find out what teward's malware analysis team did to my laptop
[19:58] <tsimonq2> teward: I just want all this PHP code I'm working on to be piped straight into /dev/null tbh
[19:58] <teward[m]> that i believe lol
[19:59] <arraybolt3[m]> Simon Quigley: That's easy. `cat * | tee /dev/null > /dev/null`
[19:59] <arraybolt3[m]> Throw it away twice and keep it all!
[19:59] <tsimonq2> nonono like this: `mv *.php /dev/null` oops all the code is gone 
[19:59] <teward[m]> or the more dangerous version of that command: [CENSORED]
[20:00] <arraybolt3[m]> H*&8rgofsefiu`rm -rf /`ius7yS*tf6767tow4tuhi5urhtg
[20:00] <tsimonq2> wait is it taboo to say that now?
[20:00]  * tsimonq2 goes on a dad-style "society sucks" ranyt
[20:00]  * tsimonq2  * goes on a dad-style "society sucks" rant
[20:01] <arraybolt3[m]> In a technical support room, probably.
[20:01]  * teward[m] charges tsimonq2 with treasonous sedition
[20:01] <arraybolt3[m]> But I don't think anyone in here will read our conversation and be like "Hey I wonder what *that* command does! <clackety clackety> *GASP*"
[20:02] <arraybolt3[m]> `sudo apt install photorec`
[20:02] <tsimonq2> Yeah, and if you, dear reader, are one of those people. Don't. We warned you.
[20:02] <arraybolt3[m]> s/photorec/testdisk/
[20:03] <arraybolt3[m]> Alright, QT code pulled, guess I'm going to descend into the caverns of Gobble Important Treasures (what git really stands for).
[20:03]  * tsimonq2 goes back to wondering why mPDF has to be this convoluted, or at least this implementation of it...
[20:48] <arraybolt3[m]> Man, VirtualBox seems to always be so grumpy. /me has got to remember to go GNOME Boxes, always.
[20:48] <arraybolt3[m]> Unless I have no other choice.
[20:48] <arraybolt3[m]> (Or I need the power of virt-manager.)
 "Man, VirtualBox seems to..." <- Throw the baby out with the bathwater imo - VirtualBox sucks
 QEMU-KVM is god xD
[23:03] <tsimonq2> ^^^^^^^^
 arraybolt: just dont do what i do - chain KVM and LXD bridges together heh
[23:03] <tsimonq2> Masochist lol
 my LXD DHCP box handles the DHCP for the bridge I put my qemu vms on
[23:04] <tsimonq2> just why XD
 @tsimonq2 better than having to hardcode new bridges and NAT rules
 because qemu autonat is broke when lxd is installed and functional
[23:04] <tsimonq2> I mean... true.
 no idea qhy
 but at least qemu can use the bridge xS
 just like a container can.
[23:04] <tsimonq2> OH that explains a lot thanks teward :P
[23:05] <tsimonq2> (I've seen that functionality recently and didn't connect the dots... until now heh)
[23:05] <tsimonq2> yeah, thankfully bridges don't require their own JVM embedded inside Haskell :P
 yeah i have two LXD bridges on my env - one for persistent services thats static ip only configs and one thats DHCP enabled for everything ephemeral.  qemu can use either bridge and not need to set up its own
[23:06] <tsimonq2> that's really neat actually
 so yay saves me a chaos
 ye well lxd can speak KVM under the hood too so
 when using lxd to deploy full vms with the cloud images it uses kvm.
[23:37] <arraybolt3[m]> I use QEMU/KVM most of the time.
[23:38] <arraybolt3[m]> But KDE developers are a picky bunch. All the good QEMU/KVM frontends are GNOME-based, and VBox is Qt, so...