[00:07] <arraybolt3_wc> Latest network manager shenanigans - you can read a "cloned MAC address" of a connection with NetworkManagerQt, and you can set that cloned MAC address to something else, but unsetting it so that it's blank is just shy of impossible (I never did figure out a good way to do it). Ended up using nmcli for that job XD
[17:15] <tsimonq2> arraybolt3_wc: Some weird data validation that only applies to the API?
[17:15] <tsimonq2> :P
[17:16] <arraybolt3> Yeah, or something. Glad it works now :P
[17:18] <tsimonq2> Hah, nice
[17:19]  * tsimonq2 will cringe if he sees some weird QProcess calls to nmcli :P
[17:23] <arraybolt3> I split it into its own function and made it as clean as possible if it's any consolation...
[17:23] <tsimonq2> HAHAHAHAHAHAHAAHA
[17:25] <arraybolt3> But yeah, I am basically having to detect whether to wipe the cloned MAC address and if so, I am calling QProcess to run nmcli. Via Bash...
[17:25] <tsimonq2> ouuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuuch lol
[17:25] <arraybolt3> (I could probably cut Bash out of the loop but I've seen that go away so :P
[17:25] <tsimonq2> What magic does nmcli perform on the backend?
[17:25] <tsimonq2> Also, sh is more portable :P
[17:26] <arraybolt3> nmcli connection modify uuid ethernet.cloned-mac-address ""
[17:26] <arraybolt3> ^ does the trick
[17:26] <arraybolt3> uuid is a placeholder obviously
[17:28] <arraybolt3> Setting the clonedMacAddress property of the connection via NetworkManagerQt to a null QByteArray just fails silently, despite the fact that NetworkManagerQt returns a null QByteArray if you read an unused cloned MAC address.
[17:33] <tsimonq2> https://git.launchpad.net/ubuntu/+source/network-manager/tree/src/nmcli/connections.c
[17:35] <arraybolt3>  I'm using the KDE Frameworks library that interfaces with NetworkManager. I assume the issue is a bug there. (plasma-nm seems to have a workaround but it's one that I'm not comfortable implementing since it could blank out important settings that the user set some other way.)
[17:36] <tsimonq2> *shrug* well if it's causing issues and you don't see another way, I'd suggest you not use QProcess without some strict nmcli depends :)
[17:36] <tsimonq2> And make sure the user knows about it, or something like that.
[17:37] <arraybolt3> It works entirely in the background when the user clicks "Save". Is there a particular reason the user needs to know an implementation detail like that?
[17:37] <arraybolt3> +1 on strict depends.
[17:39] <tsimonq2> Well, if you decide not to use QProcess you could always prevent that behavior. If there's a way you could patch NetworkManagerQt to use a method which supports it, that's probably ideal. This also seems like something not *100%* critical, if I'm not mistaken, so we could always take the "quick and dirty" approach and pinky promise to fix it later.
[17:40] <arraybolt3> hmm, didn't think about patching the library... that might be a good idea...
[17:40] <tsimonq2> As a general rule, I hate using CLI interfaces to things which use public, shared libraries, when you can just use the library directly. Less work later for changed CLI behavior.
[17:40] <arraybolt3> (I forget that in FOSS work you're not left at the mercy of your libraries if there's a bug in one :p
[17:41] <tsimonq2> hah :P
[17:41] <tsimonq2> By the way, I think all of our stuff was accepted.
[17:41] <tsimonq2> So, we should probably make sure it all built and stuff :P
[17:41] <arraybolt3> 🎉
[17:41] <tsimonq2> ;) ;)
[17:41] <arraybolt3> Also Noble is open, any work on codename?
[17:41] <arraybolt3> *word
[17:42] <tsimonq2> Nah, it can be weeks before Mark comes up with an animal.
[17:42] <tsimonq2> I had a little chat with Someone Who Knows, and it's still Mark deciding on the codename directly.
[17:42] <arraybolt3> kk
[17:44] <arraybolt3> (r.e. use the hacky way and fix it later) I like this idea, since it'll let me keep making forward progress for now. Then if we're not pressed for time, we can fix the MAC handler later.
[17:45] <tsimonq2> For sure. Thanks again :)
[17:45] <arraybolt3> Sure thing, glad to be able to help :)
[17:45] <tsimonq2> It's great to have you back 🎉🎉🎉🎉
[17:45] <arraybolt3> Great to be back :D
[17:52] <tsimonq2> @guiverc, @Leokolb etc.: If you take a 23.10 ISO and change the sources to noble, then upgrade, there is a brand-new Calamares version to test.
[17:53] <tsimonq2> 23.10 has alpha2, what just migrated into the release pocket is alpha4
[19:41] <tomreyn> did you spot the threat in #lubuntu from some hours ago?
 Please stop spamming other IRC servers immediately. If you don't want your servers to be unavailable.
 LAST WARNING
[19:45] <tomreyn> definitely lacking context
[20:18] <tomreyn> not that i know of, and i'd be somewhat upset if they did.
[20:19] <tomreyn> it's unclear to me whether the threat referred towards the libera network or lubuntu websites, though
[20:28] -queuebot:#lubuntu-devel- New binary: libfm [ppc64el] (noble-proposed/universe) [1.3.2-4] (lubuntu)
[20:29] -queuebot:#lubuntu-devel- New binary: libfm [amd64] (noble-proposed/universe) [1.3.2-4] (lubuntu)
[20:53] <teward> tomreyn: i believe they were targeting IRC, not us.
[20:53] <teward> tomreyn: that's a typical "threat" by irc bot spammers and such to the IRC network
[20:53] <teward> there's mitigations in place if they mean Lubuntu
[21:24] -queuebot:#lubuntu-devel- New binary: libfm [armhf] (noble-proposed/universe) [1.3.2-4] (lubuntu)
[21:25] <tomreyn> teward: good to hear! :)
[21:26] <tomreyn> by the way, did you see my private message the other day?
[21:28] -queuebot:#lubuntu-devel- New binary: libfm [arm64] (noble-proposed/universe) [1.3.2-4] (lubuntu)
[22:03] <Eickmeyer> @tsimonq2: There's your open for development email. Have fun, but just know the queues are about a lightyear in length.
 Oh, you think my stuff hasn't already been uploaded and accepted?
 Lmfao
 Now watch it build like a glacier crawling down a mountain.
 I Love how my point was whooshed over your head. 😂
 I'm already used to the large queues
 Nothing new
[22:12] <arraybolt3> Canonical's datacenters will chew through it eventually.
[22:12]  * arraybolt3 looks at ETA... 12 YEARS WHAT IN THE WORLD?!
 Where is this LMFAO
[22:13] <arraybolt3> I made it up XD
 I need a nap XD
[22:13] <arraybolt3> (granted I have seen apt tell me that downloads would take a day or longer when my connection was just about to drop out so :P
[22:13] <arraybolt3> and once again I never can remember to type the right parenthesis)
 I mean, the amd64 queues are more than a day long
[22:18] -queuebot:#lubuntu-devel- New binary: libfm [s390x] (noble-proposed/universe) [1.3.2-4] (lubuntu)
[22:30] <arraybolt3> The nanimal has been chosen!
[22:30] <arraybolt3> Noble Numbat
[22:30] <arraybolt3> (it's a banded anteater, looks really cute)
[22:30] <arraybolt3> Eickmeyer leaked it first :P
[22:30] <Eickmeyer> I mean, it was in the email. :P
[22:31] <arraybolt3> I'm not getting the emails anymore :P
[22:31] <arraybolt3> so I didn't know until it hit IRC
[22:31] <arraybolt3> I need to sign up for the MLs again
[22:31] <Eickmeyer> I was about to say...