[13:59] Hi all [16:35] * arraybolt3 boots up the latest daily to see what happens [16:35] hmm, still booting into an autologin KDE session [16:36] and the casper version is fully up-to-date [16:36] alright, so that's wrong [16:37] the installer prompt session is there though... [16:44] gah, I see what I did wrong [16:45] slipped past vorlon too so I don't feel quite so bad :P [22:52] ok, I have hit very strange behavior with the new kubuntu-installer-prompt. [22:52] In a VM, it works fine. [22:52] On physical hardware (HP Pavilion dv7) it instantly segfaults. [22:53] Files are identical, ISO download is good, flash drive is good according to both balenaEtcher's verification and casper-md5check. [22:53] * tsimonq2 hands arraybolt3 a valgrind, a GDB, and a large hammer [22:53] ...wha?! [22:53] tsimonq2: thanks :P [22:53] arraybolt3: Warning, it will break your brain for like four hours the first goaround. :P [22:53] meh, I've used both those tools before, no big deal. [22:53] valgrind is slow though [22:54] To be fair, it does a *lot*. ;) [22:54] alright, hitting it with gdb and debuginfod [22:55] <3 [22:55] this is the first time in my life I've had software I wrote have a hardware-triggered failure. [22:55] which probably means I've been lucky up until now :P [22:55] bah my gut tells me it's related to NM [22:56] or perhaps the multi screen logic [22:56] oh that could be true [22:56] either that or my ancient NVIDIA card throwing a tantrum, but more likely that. [22:57] old NVIDIA cards are prone to tantrums, I wouldn't rule that out so quickly ;P [22:57] (I no longer have that opinion about new NVIDIA cards after talking to Mike btw) [22:58] yeah this machine is old enough there aren't proprietary drivers for the card anymore. [22:58] It's Nouveau or bust (or patch the NVIDIA drivers which is questionably legal and definitely risky) [23:04] niceeeeeeee [23:08] ooof, yeah I definitely shouldn't rule out the NVIDIA card, I have ample evidence that this machine is... on its last leg. [23:09] (opened System Monitor and the graphics are berzerk) [23:09] (looks like possible VRAM failure) [23:09] and now a total system freeze. Nice. [23:17] I don't see any obvious memory management errors looking at the code, so I'm going to hope it's a graphics driver issue. [23:17] Switching to an Intel-based machine now. [23:57] *an Intel-based machine with crummy Broadcom WiFi