[00:42] <lubot_> [matrix] <arraybolt3> I am currently literally going through each individual mode of BSOD making sure the fonts still work right. This is the most hilarious software testing I have ever done :P
[01:27]  * guiverc does really like BSOD, except for the using of $HOSTNAME that can give me mini-heart-attacks if it's a GNU/Linux when I return to my box...
[01:27] <arraybolt3> lol that's happened to me more than once :P
[01:50] <lubot_> [matrix] <arraybolt3> Simon Quigley: I'm in a slight pickle - how do I create a new binary file from within the Debian packaging? I can repack to remove one of the offending fonts from XScreenSaver, but to replace it with a new one, I don't know how to do. Quilt appears to break if you try to use it on binary files.
[01:50] <lubot_> [matrix] <arraybolt3> Technically I probably *could* create a shell script with the file in question Base64-encoded, and have the script generate the file at build time, but that's extremely hacky and I suspect there's a better way to do it.
[01:51] <lubot_> [matrix] <arraybolt3> I think new files can be introduced in a repack also, but then i think I'd need to make a whole repack shell script, which again feels hacky.
[02:03] <lubot_> [matrix] <tsimonq2> arraybolt3: I *think* that requires a manual repack... jeez :/
[02:04] <lubot_> [matrix] <tsimonq2> arraybolt3: At this point, despite your best efforts I'd ask the Debian Maintainer before doing a full repack in Debian... in Ubuntu it's different heh
[02:04] <lubot_> [matrix] <tsimonq2> I apologize :/
[02:04] <lubot_> [matrix] <arraybolt3> I even had to convert the free OCRA font from TTF to OTF. This may be one of the more in-depth fixes.
[02:04] <lubot_> [matrix] <arraybolt3> Except for the maintainer appears to have vanished... I mean I can look for him more but :-/
[02:04] <lubot_> [matrix] <tsimonq2> Let me do some searching...
[02:05] <lubot_> [matrix] <arraybolt3> His last commit in Salsa was 11 months ago. I don't have a whole lot of hope that we'll find him.
[02:06] <lubot_> [matrix] <arraybolt3> Hmm, I see him in Launchpad in July 2022.
[02:07] <lubot_> [matrix] <arraybolt3> And again in September. OK, he might not be so unreachable then.
[02:08] <lubot_> [matrix] <arraybolt3> Found him most recently here: https://launchpad.net/~tormodvolden/+archive/ubuntu/m6809
[02:09] <lubot_> [matrix] <arraybolt3> Ah, and now I've found him on GitLab's main website just a few hours ago!
[02:09] <lubot_> [matrix] <arraybolt3> https://gitlab.com/tormod
[02:12] <lubot_> [matrix] <arraybolt3> And I have an email for him specifically for Debian packaging.
[02:14] <lubot_> [matrix] <tsimonq2> There you go :) ask him if you can fix his RC bug lol
[05:38] <lubot_> [matrix] <arraybolt3> Alright, I think everything's done. I'm doing a final build and test, we'll see how it works.
[05:38] <lubot_> [matrix] <arraybolt3> (At least it's trying to build after the brain surgery I just did on it :P
[05:38] <lubot_> [matrix] <arraybolt3> )
[05:49] <lubot_> [matrix] <arraybolt3> And it builds! Testing time \o/
[06:09] <lubot_> [matrix] <arraybolt3> Alright, looks like it works! All BSOD screensavers are functioning right.
[06:09] <lubot_> [matrix] <arraybolt3> Guess I'll push this to my Salsa fork and ask for review.
[06:30] <lubot_> [matrix] <arraybolt3> Simon Quigley: https://salsa.debian.org/ArrayBolt3/xscreensaver/-/commits/arraybolt3/fontfix Ready for review.
[06:32] <arraybolt3> I'll let you know when and if we get permission.
[15:02] <lubot_> [matrix] <tsimonq2> arraybolt3: Looks like we got permission. ;)
[18:10] <lubot_> [matrix] <arraybolt3> K, reading through and looking.
[18:32] <lubot_> [matrix] <arraybolt3> Simon Quigley: Is it even possible for me to be a comaintainer of xscreensaver, or would you be the comaintainer and then I'd just help you do that?
[20:09] <tsimonq2> @arraybolt3: Co-maintainer = Uploader
[20:10] <lubot_> [matrix] <arraybolt3> kk, I thought it was like commit access to the repo. So I can't do that.
[20:10] <tsimonq2> Nonono, not upload rights
[20:10] <tsimonq2> Literally just your name in Uploaders :P
[20:10] <lubot_> [matrix] <arraybolt3> Oh. So I can do that?
[20:11] <tsimonq2> Yes :)
[20:11]  * lubot_ [matrix] <arraybolt3> may not know how this works...
[20:11] <lubot_> [matrix] <arraybolt3> \o/
[20:20] -queuebot:#lubuntu-devel- Unapproved: lubuntu-default-settings (kinetic-proposed/universe) [22.10.4 => 22.10.5] (lubuntu)
[20:21] <arraybolt3> XScreenSaver fix for Lubuntu only in Kinetic uploaded and awaiting approval.
[20:22] <tsimonq2> Now for you to get your key signed so you can upload to it in Debian :P
[20:22] <lubot_> [matrix] <arraybolt3> lol, well this particular fix is just the Lubuntu configuration file, the fix for everything other than Lubuntu is a bit different.
[20:23] <tsimonq2> Delay in the message sending lol
[20:23] <lubot_> [matrix] <arraybolt3> Oh lol
[20:44] <arraybolt3> Heh. Every item in our "In Progress" list is awaiting something else to finish, so... woot! We have almost everything under control!
[20:44] <lubot_> [matrix] <tsimonq2> I'm working on another lubuntu-update-notifier update at the moment
[20:45] <arraybolt3> @tsimonq2: I have an SRU pending on that in Focal currently.
[20:45] <arraybolt3> What's happening?
[20:45] <arraybolt3> (I guess I could tackle how to make it so that we can get rid of KDE System Settings...)
[20:46] <lubot_> [matrix] <tsimonq2> How were we going to do that again? :)
[20:46] <arraybolt3> I think our last idea was figure out how to hide the Update Settings button in Discover so that we can just omit systemsettings entirely.
[20:47] <arraybolt3> Either that or else figure out how to get LXQt to honor the NotShowIn .desktop setting.
[20:47]  * arraybolt3 zsyncs
[20:48] <lubot_> [matrix] <tsimonq2> I'm actually working on a PyQt6 port right now :)
[20:48] <arraybolt3> Oh nice!
[20:49] <lubot_> [matrix] <tsimonq2> Update Settings... you'll have to refresh me heh
[20:50] <arraybolt3> I'll find the button in a bit. Basically, there's some Update Settings button in Discover in an obscure place people will probably never find that relies on KDE System Settings being present - if you remove systemsettings, the button does nothing, which we considered to be a regression, so we left systemsettings.
[20:50] <arraybolt3> But the button isn't always visible (I noticed that Kubuntu had it hidden) so obviously there's some way to make it go away, and if the button isn't there, then it's no regression for it to not work :D
[20:54] <lubot_> [matrix] <arraybolt3> https://matterbridge.lubuntu.me/50db136f/Screenshot_from_2023_01_24_14_53_22.png
[20:54] <lubot_> [matrix] <arraybolt3> Behold, the problem button.
[20:54] <lubot_> [matrix] <tsimonq2> Oh, I see
[20:54] <lubot_> [matrix] <tsimonq2> Probably needs a conditional... "if no Plasma settings, no show button"
[20:54] <lubot_> [matrix] <tsimonq2> likely just a few lines
[20:55] <lubot_> [matrix] <arraybolt3> Kubuntu has it hidden entirely (at least on the Kubuntu Focus Suite), so there's someway to make that button just go away.
[20:55] <lubot_> [matrix] <arraybolt3> Maybe the KFocus people patched it though.
[20:55] <lubot_> [matrix] <tsimonq2> Eickmeyer: ^^^^^^
[20:56] <lubot_> [matrix] <eickmeyer> TL;DR me?
[20:57] <lubot_> [matrix] <arraybolt3> Eickmeyer: How did you guys get that Configure Updates button above to go away?
[20:57] <lubot_> [matrix] <eickmeyer> Never did.
[20:57] <lubot_> [matrix] <arraybolt3> Or was it just always not there and there's something weird with Lubuntu?
[20:57] <lubot_> [matrix] <eickmeyer> Yup.
[20:57] <lubot_> [matrix] <arraybolt3> ...ok I'll do some more digging.
[20:57] <lubot_> [matrix] <arraybolt3> Maybe this is something new in Discover in Kinetic, because I'm now remembering Kubuntu on KFocus was 22.04, not 22.10.
[20:57] <lubot_> [matrix] <eickmeyer> We never touched Discover.
[20:58]  * lubot_ [matrix] <arraybolt3> spins up another VM
[20:58] <lubot_> [matrix] <arraybolt3> Checking Kubuntu Kinetic to see what's up there.
[20:59] <lubot_> [matrix] <eickmeyer> I'm not on the team anymore (furlough/layoff), but I'd still know if there was a config there, and there isn't.
[21:00] <lubot_> [matrix] <arraybolt3> Yeah, that button *is* in Discover in Kinetic.
[21:00] <lubot_> [matrix] <arraybolt3> Tar.
[21:01] <lubot_> [matrix] <arraybolt3> And it does indeed just stop working once you remove kde-config-updates and systemsettings. So... let's see what the logs tell me to see if I can find where an option can be set.
[21:05] <arraybolt3> OK, I've found the QML file at "fault"... but here's the thing, do we want to submit the patch to fix this upstream, or do we want to just patch it here?
[21:06] <arraybolt3> (And actually there's two QML files at "fault", but at least I've found where it is, and it sadly is baked right into the code.)
[21:29] <lubot_> [matrix] <arraybolt3> And I'm not finding any separate qml files, so I'm assuming that they're baked all the way into the binary itself. :-/
[21:39] <lubot_> [matrix] <tsimonq2> Where is the settings binary actually called?
[21:39] <lubot_> [matrix] <tsimonq2> Also bad arraybolt3 :P
[21:39] <lubot_> [matrix] <tsimonq2> you forgot to tag lubuntu-default-settings
[21:39] <lubot_> [matrix] <tsimonq2> I will fix
[21:39] <lubot_> [matrix] <tsimonq2> but bad arraybolt3 :P
[21:39] <lubot_> [matrix] <arraybolt3> I think that's because it's not accepted into the archive yet :)
[21:39]  * lubot_ [matrix] <arraybolt3> checks
[21:39] <lubot_> [matrix] <tsimonq2> Lunar
[21:40] <lubot_> [matrix] <tsimonq2> Also, you skipped 23.04.3 ;)
[21:40] <lubot_> [matrix] <arraybolt3> Oh tar.
[21:40] <lubot_> [matrix] <tsimonq2> (Cosmetic. No big deal. Still gonna give you crap about it ;) )
[21:40] <lubot_> [matrix] <arraybolt3> I thought that was for a reason, hang on...
[21:40] <lubot_> [matrix] <arraybolt3> I skipped *uploading* it, true. I thought that was acceptable for some reason.
[21:41] <lubot_> [matrix] <arraybolt3> It got uploaded at the same time as 23.04.4... though I probably should have used a debuild option that RAOF taught me later on.
[21:42] <lubot_> [matrix] <arraybolt3> FWIW, you and Dan both have an untagged upload in Kinetic ;-)
[21:42] <lubot_> [matrix] <arraybolt3> But yeah, we should get those fixed.
[21:42] <lubot_> [matrix] <tsimonq2> No worries :D
[21:42] <lubot_> [matrix] <arraybolt3> discover/qml/Feedback.qml in the source code
[21:42] <lubot_> [matrix] <arraybolt3> Also discover/qml/SourcesPage.qml
[22:08] <lubot_> [matrix] <arraybolt3> Dawns on me that this might be helpful:
[22:08] <lubot_> [matrix] <arraybolt3> ```
[22:08] <lubot_> [matrix] <arraybolt3>     readonly property list<QtObject> actions: [
[22:08] <lubot_> [matrix] <arraybolt3>         Kirigami.Action {
[22:08] <lubot_> [matrix] <arraybolt3>             text: i18n("Submit usage information")
[22:08] <lubot_> [matrix] <arraybolt3>             tooltip: i18n("Sends anonymized usage information to KDE so we can better understand our users. For more information see https://kde.org/privacypolicy-apps.php.")
[22:08] <lubot_> [matrix] <arraybolt3>             displayHint: Kirigami.DisplayHint.AlwaysHide
[22:08] <lubot_> [matrix] <arraybolt3>             onTriggered: {
[22:08] <lubot_> [matrix] <arraybolt3>                 provider.submit()
[22:08] <lubot_> [matrix] <arraybolt3>                 showPassiveNotification(i18n("Submitting usage information…"), "short", i18n("Configure"), provider.encouraged)
[22:08] <lubot_> [matrix] <arraybolt3>             }
[22:08] <lubot_> [matrix] <arraybolt3>         },
[22:08] <lubot_> [matrix] <arraybolt3>         Kirigami.Action {
[22:08] <lubot_> [matrix] <arraybolt3>             text: i18n("Configure feedback…")
[22:08] <lubot_> [matrix] <arraybolt3>             displayHint: Kirigami.DisplayHint.AlwaysHide
[22:08] <lubot_> [matrix] <arraybolt3>             onTriggered: {
[22:08] <lubot_> [matrix] <arraybolt3>                 provider.encouraged()
[22:08] <lubot_> [matrix] <arraybolt3>             }
[22:08] <lubot_> [matrix] <arraybolt3>         },
[22:08] <lubot_> [matrix] <arraybolt3>         Kirigami.Action {
[22:08] <lubot_> [matrix] <arraybolt3>             text: i18n("Configure Updates…")
[22:08] <lubot_> [matrix] <arraybolt3>             displayHint: Kirigami.DisplayHint.AlwaysHide
[22:08] <lubot_> [matrix] <arraybolt3>             onTriggered: {
[22:08] <lubot_> [matrix] <arraybolt3>                 KQCA.KCMShell.openSystemSettings("kcm_updates");
[22:09] <lubot_> [matrix] <arraybolt3>             }
[22:09] <lubot_> [matrix] <arraybolt3>         }
[22:09] <lubot_> [matrix] <arraybolt3>     ]
[22:09] <lubot_> [matrix] <arraybolt3> ```
[22:09] <lubot_> [matrix] <arraybolt3> From the Feedback.qml file.
[22:09] <guiverc> arraybolt3, :(
[22:09] <arraybolt3> Oh no. I forgot you can't do that. Sorry.
[22:09] <lubot_> [matrix] <tsimonq2> arraybolt3: What actually calls those QML files?
[22:10] <arraybolt3> @tsimonq2: Lemme find out.
[22:10] <arraybolt3> Also, I'm going to leave this room in Matrix so I stop accidentally flooding the chat and just stick to IRC until the bot gets sorted out.
[22:10] <lubot_> [matrix] <tsimonq2> BTW, if you're subscribed to lunar-changes@l.u.c you may see me uploading like a madman :P
[22:10] <arraybolt3> Heh
[22:12] <arraybolt3> tsimonq2: I think it's discover/qml/DiscoverWindow.qml.
[22:13] <tsimonq2> arraybolt3: I'm sending lubuntu-default-settings with your changes to Backports. Want a testing window or nah?
[22:13] <arraybolt3> I mean I already tested it so I say full steam ahead :)
[22:13] <tsimonq2> Cool :)
[22:13] <tsimonq2> Note: any work related to Qt 6 porting should NOT go to Backports
[22:13] <tsimonq2> that's still fairly experimental
[22:14] <arraybolt3> tsimonq2: https://dpaste.com/F9YFS8WC2 <-- Where Feedback.qml is called
[22:14] <arraybolt3> I could paste the whole file if that's helpful.
[22:16] <arraybolt3> So... here's the problem, I don't know QML well enough to know how to tell it to only show the Kirigami action that displays the Configure Updates button if kcm_updates is available.
[22:17] <arraybolt3> In fact I don't even know it well enough to know if what I just said even makes sense.
[22:19] <tsimonq2> (TBH, in hindsight, backporting settings isn't the move)
[22:19] <tsimonq2> arraybolt3: Looking
[22:20] <arraybolt3> The main worry I have here is, with kde-config-updates present, Lubuntu is currently kind of like LKubuntu - there's KDE-specific features that may interfere with Lubuntu-specific features present. If a user actually finds and uses that button, they could cause their whole system to do weird things. So IMO, figuring out how to hide KDE System Settings isn't the way. Getting Discover to live
[22:20] <arraybolt3> without kde-config-updates is.
[22:21] <arraybolt3> Or maybe we just chuck Discover entirely and say "We can't make this non-dangerous without causing a regression, therefore this is no longer our app store - it's too KDE-specific now."
[22:21] <arraybolt3> In which case the question is, what alternative to use? GNOME Software fits very poorly and works horribly.
[22:21] <RikMills> arraybolt3: why is discover dangerous?
[22:22] <tsimonq2> I knew you'd come by ;)
[22:22] <arraybolt3> RikMills: I'm worried about the "Offline Updates" and "Automatic Updates" features that can be enabled via kde-config-updates possibly conflicting with lubuntu-update-notifier.
[22:22] <arraybolt3> I don't think we want KDE trying to automatically update the system while the user's trying to manually update it.
[22:22] <RikMills> don't installkde-config-updates then
[22:23] <arraybolt3> Which breaks a button in Discover, which is a regression.
[22:23] <RikMills> add space there ish ^
[22:23] <arraybolt3> (Personally, I say the "regression" in question is worth it, but I don't think we can do that.)
[22:23] <RikMills> a button that does nothing is "dangerous"?
[22:24] <RikMills> peroanlly I find buttons that do things more so ;)
[22:24] <tsimonq2> I mean, you're not exactly wrong :P
[22:24] <RikMills> you could always as the president of the KDE e.V. about the code
[22:25] <RikMills> he is the main dev
[22:25] <arraybolt3> Exactly. I want to just say get rid of it, but Ubuntu in general *hates* all regressions. Then again the KDE System Settings thing in Lubuntu looks badly out of place and somewhat bare.
[22:25] <arraybolt3> RikMills: I mean, doesn't he have more important things to do?
[22:25] <arraybolt3> The feature works just as intended in KDE land, the fact that we're MacGyver'ing Discover into Lubuntu is a bit of a hack that was never intended to be done but uesd to work.
[22:26] <RikMills> he has always been very good at responding to my stupid questions
[22:27] <tsimonq2> I would never usually agree with pinging the president of KDE but I did meet him at the Ubuntu Summit
[22:27] <tsimonq2> I asked him about QTerminal text resizing and he told me "use Konsole" :P
[22:27] <arraybolt3> Heh :)
[22:28] <tsimonq2> Anyway, I think we can blacklist this package from the seed
[22:28] <RikMills> he might be more keen if it means his baby stays in one more distro/flavour
[22:28] <tsimonq2> arraybolt3: Wanna do the honors of seed mangling or would you like to let me do it in 0.000001 seconds? :P
[22:28] <arraybolt3> Valid point. And I really like Discover, it's leaps and bounds better than GNOME Software and works pretty well IME.
[22:29] <tsimonq2> +1
[22:29] <arraybolt3> tsimonq2: I can do it :)
[22:29] <tsimonq2> cool :)
[22:29] <RikMills> anyway, if I can changes recommends and seeds in kubuntu to help, shout
[22:29] <tsimonq2> !kde-config-updates right below (plasma-discover) I think
[22:29] <tsimonq2> bah
[22:29] <tsimonq2> XD
[22:29] <arraybolt3> !cookie
[22:30]  * tsimonq2 continues Qt 6 porting for now
[22:32] <arraybolt3> Seed mangled, proceeding with updating the desktop file.
[22:32] <arraybolt3> Er... metapackage.
[22:32] <arraybolt3> (Wow that was a wrong term.)
[22:33] <arraybolt3> Oh. No. I'm on Kinetic.
[22:33] <arraybolt3> ...
[22:33] <arraybolt3> Meh, let's do this chaos-mode.
[22:34]  * arraybolt3 installs debootstrap from Lunar onto Kinetic
[22:34] <tsimonq2> lxc launch --ephemeral ubuntu-daily:devel
[22:34]  * arraybolt3 has very little clue how to use lxc
[22:34] <arraybolt3> Will have to learn that.
[22:34] <tsimonq2> uh did you know the debootstrap version in Lunar literally creates a symlink ;)
[22:35] <tsimonq2> (I know... I did it :P)
[22:35] <arraybolt3> I will go ahead and install LXD real quick.
[22:35] <arraybolt3> tsimonq2: I think you told me that once.
[22:35] <tsimonq2> sudo snap install lxd && sudo lxd init && sudo lxd list
[22:35] <arraybolt3> But the update script is all gripey about version numbers and such.
[22:35] <RikMills> it can be fooled
[22:36]  * tsimonq2 sometimes wonders how Rik fools some of the scripts...
[22:36] <arraybolt3> Hmm... this will make me always have to manually update debootstrap, let's just crash-course into LXD and see how it goes. I have the data.
[22:37] <lubot_> [matrix] <kc2bez> Really? Uff can't believe I missed that. Sorry.
[22:38] <arraybolt3> tsimonq2: I'm all but blindly running that --ephemeral command right now XD
[22:40] <arraybolt3> tsimonq2: What does the --ephemeral switch do anyway? I know what "ephemeral" means but don't know what an ephemeral instance is going to behave like.
[22:41] <arraybolt3> The help is lacking, and Google is being unhelpful :P
[22:41] <arraybolt3> Ah, finally, found it.
[22:44] <arraybolt3> tsimonq2: And... my container has no network access :-/
[22:45] <arraybolt3> Ah, now it's working for no reason.
[22:46] <lubot_> [matrix] <kc2bez> By default lxc containers are nat
[22:51]  * arraybolt3 has to go afk for a sec, brb
[23:00] <arraybolt3> Back.
[23:02] <arraybolt3> YES I can share the home dir.
[23:02] <arraybolt3> Alrighty! Wow, this is going to make things easier I bet.
[23:04] <arraybolt3> tsimonq2: I'm long overdue learning lxd, thanks for getting me to finally take the plunge :)
[23:05] <tsimonq2> No worries :D
[23:05] <tsimonq2> Figuring it all out?
[23:05] <tsimonq2> also btw you can also do
[23:05] <tsimonq2> images:debian/sid instead of ubuntu-daily:devel
[23:05] <arraybolt3> Yep. Got a persistent Lunar container and my home dir mounted.
[23:05] <tsimonq2> or even ubuntu:22.04 :)
[23:05] <arraybolt3> Now I'm installing devscripts and germinate and all that stuff and then I'm going to run the update script.
[23:05] <tsimonq2> sweet :D
[23:06] <tsimonq2> arraybolt3: Fun fact for you, autopkgtest supports LXD on the backend
[23:07] <arraybolt3> Alright, update in progress.
[23:08] <arraybolt3> tsimonq2: Yeah but does sbuild? :P just kidding.
[23:10] <tsimonq2> hah
[23:14] <arraybolt3> (btw if anyone in LP asks why my IP just tried to log into root on git.launchpad.net, welcome to Aaron Fumbles His SSH Config Yet Again.)
[23:18] <arraybolt3> tsimonq2: Hmm. Adding a blacklist did nothing to the lubuntu-desktop metapackage (which I guess is unsurprising).
[23:21] <arraybolt3> Soooo.... I guess that job's done!
[23:22] <arraybolt3> I sort of expected it to be harder than that.
[23:22] <tsimonq2> LXD? Or the seed?
[23:22] <tsimonq2> heh
[23:22] <arraybolt3> Both :)