[00:04] <arraybolt3_wc> Learning a lot over here! So far I can make system tray icons, specify the exact icon I want in the systray, create desktop notifications, and I have the needed library to do pretty much all things NetworkManager (thank you KDE for the NetworkManagerQt framework) so things are coming along nicely :D
[00:05] <arraybolt3_wc> teward001: yeah, still some people might have a use for it so I'd like to support it since NetworkManager does. Supposedly there's a custom LTE radio module for the Framework laptop out there.
[00:14] <arraybolt3_wc> kc2bez: lol, only now do I see "lubuntu-net<TAB>", on the Matrix side it only showed up as "lubuntu-net" so I missed half the joke XD
[00:15] <kc2bez> XD
[00:53] <tsimonq2> arraybolt3_wc: Nice work :)
[00:54] <tsimonq2> plasma-∞ will happen in the morning. Let's see if I can hit the gym early like I plan.
[00:54] <arraybolt3_wc> OO cycle isn't here yet, we're on NN :P
[00:55] <arraybolt3_wc> (because the infinity symbol looks like OO... ok nevermind)
[00:55] <tsimonq2> jajajajajajajaja
[00:55] <tsimonq2> whoops one key over, I guess you got a laugh... in Spanish XD
[00:55] <arraybolt3_wc> I thought that was on purpose XD
[00:56] <tsimonq2> @Roberalz did I do it right XD
[00:56]  * tsimonq2 slaps arraybolt3_wc with a wet fish, UDP style
[00:57] <tsimonq2> get it...
[00:57] <tsimonq2> cause... networking
[00:57] <tsimonq2> ok bedtime obviously XD
[00:57]  * arraybolt3_wc reassembles the fish into a TCP stream and sends it back
[00:57] <tsimonq2> o/
[00:57] <arraybolt3_wc> gah, forgot to wrap the fish in TLS!
[00:57] <tsimonq2> btw I hope to be back bright and early to bootstrap Noble
[00:57] <tsimonq2> bahahahahaha
[00:57] <arraybolt3_wc> nice :D
[00:57] <arraybolt3_wc> Fish never tastes good unless it's encrypted...
[00:58] <tsimonq2> *watches the air fryer go up in flames*
 Yes, jajajajja (re @lubuntu_bot: (irc) <tsimonq2> @Roberalz did I do it right XD)
 The only question I have is, what about nm-tray? :)
[01:53] <arraybolt3_wc> tsimonq2: ?
[01:53] <arraybolt3_wc> nm-tray is the old GNOME-based network manager applet we've been using.
[01:54] <arraybolt3_wc> (notice there's *two* network icons in that screenshot, one is the existing applet, the one at the right is the new one in development)
[01:54] <arraybolt3_wc> oh wait... but is it?
[01:54] <arraybolt3_wc> hang on
 No, nm-tray isn't part of Gnome
 The advanced network connection stuff is.
[01:55] <arraybolt3_wc> hmm... aren't we using nm-tray already?
[01:55] <arraybolt3_wc> ohhh
[01:55] <arraybolt3_wc> lol, I thought I was developing the whole thing, tray applet and all
 https://github.com/palinek/nm-tray
[01:56]  * arraybolt3_wc crumples up existing project and starts over
[01:57] <arraybolt3_wc> I didn't realize that we were using nm-tray, I thought we were using network-manager-gnome
[01:57] <arraybolt3_wc> that makes my life a lot easier, and now I wish I hadn't just spent all that time doing something we didn't need
 I apologize for not clarifying. I hope you learned something about tray applets, we might just want that for the update notifier if we can swing it :)
[02:31] <arraybolt3_wc> Definitely learned something, and that sounds awesome :)
[02:32] <arraybolt3_wc> TIL GNOME has an entire list of mobile network providers for various geographical areas, so if I wanted to connect to cellular internet in Uruguay I could >_<
[02:42] <arraybolt3_wc> Alright, if no one minds I'm going to drop mobile broadband support and we can add it back if someone asks for it (and also direct those people to install the old connection editor in the mean time). Mobile broadband is a hot mess due to the fact that different countries do things different ways, so there's literally Kosovo-specific code in here (?!).
[04:06] <arraybolt3_wc> alright, I think I shoudl be done coding for the night. I just finished reading up on how tree-structured tables work so I can implement the known connection list as a QTreeView. Brain feels like it's turning into charcoal now.
 @utkarsh2102 Respectfully, what's the holdup with opening noble? :)
[14:33] <tsimonq2> arraybolt3_wc: Thanks again for your work!
 Probably the fact that everybody is in Riga for sprint already. (re @tsimonq2: @utkarsh2102 Respectfully, what's the holdup with opening noble? :))
[20:58] <arraybolt3_wc> Sheesh. Tree views are almost as hard as symbols files :P
[20:59] <arraybolt3_wc> Like, imagine dealing with a spreadsheet where each cell has a name and an entire (optional) sub-spreadsheet. That's a tree view.
[22:30] <tsimonq2> I would suggest having the format "Name", "Name (1)", "Name (2)" so the user can figure out which name is what.
[22:30] <tsimonq2> I mean, either way, I'm not particular :)
[22:31] <tsimonq2> It just isn't something you really see in other menus
[22:32] <arraybolt3_wc> That should work.
[22:36] <arraybolt3_wc> hmm... DSL Connection 1 (1) - I'm smelling Windows "New Folder" "New Folder (1)" "New Folder (2)" "New Folder (2) (1)" syndrome...
[22:38] <arraybolt3_wc> also the fateful day may come when someone names their DSL connection "DSL Connection 1 (1)" and also has two "DSL Connection 1"s along with it, in which case they'll see "DSL Connection 1", "DSL Connection 1 (1)", and "DSL Connection 1 (1)" in their list :P
[22:38] <tsimonq2> Already looking for edge cases, nice, have fun figuring out a workaround ;)
[22:38] <arraybolt3_wc> An "Index" field works around all of that, though to be fair this may be overthinking things quite a bit. (The GNOME connection editor doesn't bother with disambiguation at all, so we may just want to ignore it.)
[22:39] <arraybolt3_wc> (the user can use the position of each row to disambiguate easily enough :D)
[22:41] <arraybolt3_wc> aaaaaand I just accidentally force-shutdown my VM. Nice.
[22:49] <tsimonq2> Are you iterating on code in an ephemeral VM with no backups?
[22:49] <tsimonq2> Welcome to the big leagues. :P
[22:49] <arraybolt3_wc> lol no of course not
[22:50] <tsimonq2> "Hey, every time I screw up and have to reboot, I rewrite the code cleaner!"
[22:50]  * tsimonq2 sets a Russian roulette cronjob which might nuke the wks once an hour
[22:50] <arraybolt3_wc> The VM is persistent, it's my keyboard shortcut bindings that seem to be a bit ephemeral :P
[22:50] <tsimonq2> ahhh nice heh
[22:50] <arraybolt3_wc> (using raw QEMU with the SDL display, Alt+F4 terminates an app *in* the VM if you have keyboard captured, otherwise it terminates the VM itself...)
[22:51] <tsimonq2> HAHAHAHAHAHAHAHAHAHAHAHAHAHAHA
[22:51] <tsimonq2> Oh that had to be such a facepalm.
[22:51] <arraybolt3_wc> I gasped audibly when it happened :rofl:
[22:51] <arraybolt3_wc> and I've done this many times before
[22:51] <tsimonq2> "if code comments were audio and not text, you’d just hear my dissonant screaming interspersed with swearing"
[22:52] <tsimonq2> src: https://twitter.com/iamdevloper/status/1705494734179823874
[22:52] <arraybolt3_wc> you'd think I'd get tired of it and use virt-manager or GNOME Boxes, but something in my brain just hates the amount of "additional layers" those add on top of QEMU and prefer to work close to the hypervisor.
[22:52] <arraybolt3_wc> So I use raw QEMU most of the time now, sometimes to my own detriment.
[22:52] <tsimonq2> Anyway, my freaking brain is fried. It definitely feels like a Monday. I'm going to bow out of the office early.
[22:52] <tsimonq2> arraybolt3_wc: heh those layers basically have no overhead
[22:52] <arraybolt3_wc> What's really funny is there's literally an option in QEMU I can set to disable closing the window. I need to use that.
[22:53] <tsimonq2> hahahahahahahahahahaha
[22:53] <arraybolt3_wc> tsimonq2: I've gotten a bit addicted to my current setup :P
[22:53] <tsimonq2> Now you know what not to do again XD
[22:53] <arraybolt3_wc> It's smooth, it works well, it even does VM auto resolution resizing without benefit of anything SPICE-related in the mix
[22:53] <arraybolt3_wc> tsimonq2: lol
[22:53] <tsimonq2> Anyway, bye from IRC, I'm on TG unless I get another $dayjob call :)
[22:53]  * arraybolt3_wc goes and enables that "don't hard-boot this VM" setting
[22:53] <tsimonq2> hahahaha
[22:54] <arraybolt3_wc> tsimonq2: o/ nice to see you again!
[22:54] <arraybolt3_wc> OH one more thing...
 Sup?
[22:54] <arraybolt3_wc> remember that bug where sometimes upon shutdown or reboot the screen will be black when you power on next?
[22:54] <arraybolt3_wc> I think I figured out why.
 Oh?
[22:54] <arraybolt3_wc> It only happens when you shut down or reboot from the terminal rather than within LXQt.
[22:54] <arraybolt3_wc> So clicking the shutdown button doesn't seem to do it, but running `shutdown now` in a terminal may cause it.
[22:55] <arraybolt3_wc> That's probably why we see that bug all the time and we've never had a single user report it.
[22:55] <arraybolt3_wc> (that I know of)
[22:55] <arraybolt3_wc> so anyway, whatever in LXQt is getting bypassed when a terminal shutdown is done, we might want to track that down (after verifying that this is indeed the source of the bug) and squish it at some point.
[22:56] <arraybolt3_wc> alright, VM now hardened against keyboard goofs
[22:57] <arraybolt3_wc> (seriously this option needs to be set in QEMU by default, I wonder how many people have lost work because of a fumble like that.)
 Does shutdown emit a connection to systemd?
[22:59] <arraybolt3_wc> I think so? I don't know for sure but I know there's stuff about "failed to connect to init daemon" or something along those lines if you try to shut down and it times out for some reason (i.e., graphics card throwing a tantrum and has the kernel all but locked up)
 Sounds to me like something is bypassing systemd. Just a random shot in the dark :)