 *retorts with 50kW lasers pointed right at Simon, causing third degree burns* ... ooops?  :P
 it was either that or the GTK1 fiasco
 :P
[00:44] <guiverc> boys, this type of discussion is usually in other rooms
 nah we're all good
 i will be rebooting the infra swrver for security updates shortly
 so everything will kaput briefly (bare metal host)
[00:47] <guiverc> ack & thanks @teward001
[02:23] <guiverc> arraybolt3, have you installed a recent Lubuntu to thumb-drive easily?  (your answer on discourse)..   I have no reason to do it & don't test for it; but I have tested for it in the past & whilst easy on 18.04/ubiquity, I did have issues on some boxes with calamares but didn't I care to explore
[02:26] <arraybolt3> Actually, I've not! I should do that. I'm about to have a bare-metal system to do it on. I've done it so many times before with earlier Linux versions, so I didn't expect that there might be a problem there.
[02:26] <arraybolt3> Thanks for the heads-up!
[02:27] <guiverc> sorry for my poor wording; ... s/didn't i care/i didn't care/
[02:28] <arraybolt3> I actually read it as "i didn't care" lol
[02:28] <guiverc> :)  (I didn't type the word I until later, but inserted it in the wrong spot)
[02:29] <arraybolt3> Hey, I'm writing the LibreOffice localization workaround guide, and I've hit a bit of a problem.
[02:29] <arraybolt3> Sometimes the packages are just names things like "libreoffice-l10n-de" for German, or "libreoffice-l10n-fr" for French.
[02:30] <arraybolt3> But sometimes they're named "libreoffice-l10n-en-gb" (notice the "en-gb" at the end as opposed to just one "code" like "de").
[02:30] <arraybolt3> I was going to tell people to just Google what their language code should be, and then customize the "apt install" command accordingly, but I'm not sure if I can do that.
[02:31] <guiverc> I'd likely pick one language as example, eg. using French.. then at the end note that some languages have slightly different names, using english as example of that....   Do whatever you consider best
[02:31] <arraybolt3> Do you happen to know if there's a shell command that will bring up the localization code so that I can provide a Bash oneliner that will auto-detect the right language and install it?
[02:31] <arraybolt3> That's a good idea. I just don't want people to have to dig through "apt-cache search" trying to figure out how to fix the bug.
[02:31] <guiverc> me no, I barely speak english (dumb aussie), @Leokolb may have the best idea but I don't know
[02:32] <arraybolt3> ok
[02:33] <guiverc> there are other team members who speak/use multiple languages too.. they might now too
[02:33] <arraybolt3> OK. I only speak English, you should see me trying to navigate German Lubuntu... they scrambled the keyboard!
[02:36] <arraybolt3> Thanks for your help!
[02:44] <arraybolt3> Great, Lubuntu Discourse just went down, so I guess I'll have to write the manual later...
[02:45] <arraybolt3> s/write the manual later.../post the manual later.../
[02:45] <guiverc> teward gave warning of that earlier ^     10:44 my local time
 It is getting updates applied.
[02:46] <teward> yeah updates area  pain
[02:46] <teward> but they're overdue so
[02:46] <guiverc> but sorry arraybolt3 :(
[02:46] <arraybolt3> Ah, didn't get that notice. Thanks for letting me know!
[02:47] <guiverc> notice was ~two hours ago
[02:48] <arraybolt3> Yeah, looking at IRC logs, there it is, but I logged into IRC too late. At least I've got a dedicated client now rather than using KiwiIRC, which kept disconnecting every way too often
[02:50] <teward> yeah sorry about it it took 2 hours for me to finish getting updates on it
[02:50] <teward> it's also a bare metal box so when the host system reboots, it takes a *while* to reboot
[02:50] <teward> (all the individual sites, etc. are containerized within there)
[02:51] <arraybolt3> Ah, that's fine. If anyone knows the importance of security updates, it's me, who's been hacked not once, but possibly twice thanks to outdated systems
[02:55] <teward> heheh.  my job is Network and INfo Security so i mean
[02:55] <teward> security is my thing :p
[02:57] <arraybolt3> Cool!
[02:58] <guiverc> teward is also a collector of hats, so you'll see him in many ubuntu/debian places...
[02:58] <teward> do you want me to list my hats guiverc?  lol
[02:59] <teward> guiverc is not wrong, I have Many Hats(TM)
[02:59] <guiverc> no thanks, you'll just make me jealous !
[03:00] <arraybolt3> Kinda weird to have jumped in with a silly question about documentation writing two days ago, and now be knee-deep in Lubuntu development and talking to the main admins. It's fun!
[03:02] <guiverc> :)
[03:04] <teward> ALRIGHT guiverc  you made me do it
[03:05] <teward> guiverc: Ubuntu Community Council; Ubuntu Server Team; Ubuntu Developer Membership Board; Lubuntu Council, Lubuntu Developer; Debian Maintainer (for a handful of packages - primary/sole maintainer of: xca, vmfs6-tools; comaintainer of: nginx, pv.
[03:05] <teward> oh i forgot a few others, like Ask Ubuntu moderator
[03:05] <teward> and Lubuntu sysadmin for all the core Lubuntu infra :p
[03:06] <teward> but i digress
[03:06] <teward> arraybolt3: well, if you hang around #lubuntu-devel you end up talking to those of us in the higher positions.
[03:06] <teward> ... and witness the chaos between a few of us sometimes ;)
[03:08] <arraybolt3> You mean the stuff like with the 50kW lasers? (Yes, I monitor the IRC logs)
[03:08] <guiverc> :)
[03:08] <teward> yeah that's just me and Simon taking friendly stabs at each other ;)
[03:08] <teward> you'll notice random chaos like that - it's usually my fault 'cause i'm chaotic as heck.  and random.
[03:08] <teward> but as an IT Security guy, well... :P
[03:09] <teward> we're definitely on the chaotic end of the spectrum :P
[03:14] <arraybolt3> I've sorta got myself in chaos mode over here - I'm working with two manuals, chasing down two Lubuntu bugs, and am about to crack open 
[03:14] <arraybolt3> a laptop so I can do bare-metal testing for two different reasons...
[07:12] <arraybolt3> guiverc: Well, crud. I finally got everything set up for me to try doing an installation of Lubuntu 22.04 to a USB drive. And... it didn't work. I tried three times, twice with a USB 3.0 drive, once with a USB 2.0 SD card reader. The installer crashed every time. The last time, I saw it crash on unpacking file 369358. This was on a Dell Chromebook 3120.
[07:13] <arraybolt3> I attempted to reproduce the bug in a virt-manager (QEMU/KVM) virtual machine, using a USB disk target with the Removable box checked. However, the install succeeds in the VM with this setup, both with BIOS and UEFI firmware.
[07:14] <guiverc> crash on unpacking file makes me think squashfs errors (ie. errors on installation media)... but it may not be that.. you can always file a bug report so we can have a look
[07:14] <arraybolt3> Also, I can install to the Chromebook's internal storage, so the installer works.
[07:14] <arraybolt3> Can't be a media issue - my ISO check
[07:14] <arraybolt3> my ISO checks clean, and I verified the drive with a bit-by-bit compare before using it.
[07:15] <arraybolt3> The installation drive, I mean.
[07:15] <guiverc> I know what you mean... that's just my reaction 
[07:16] <arraybolt3> I do have a Calamares log. I peeked inside it, it doesn't appear to have any failures at the end. The installer just... stops.
[07:16] <guiverc> :(
[07:18] <arraybolt3> OK, guess it's bug filing time. But hey, I've got a bare-metal test system up and running, so that's good, plus I finished writing the LibreOffice localization workaround guide, so whenever Discourse is back up, I can post it!
[07:18] <guiverc> :) & can't wait to read it !
 @teward001 I don't think discourse came back cleanly. It appears to be down still.
[15:32] <kgiii> ^ what @kc2bez said. I got a PM on Linux.org asking what was up with it. I told 'em it'd be back up and running eventually and that I'd mention it. So, it has been mentioned.
 i'll look.  docker is weird (re @kc2bez: @teward001 I don't think discourse came back cleanly. It appears to be down still.)
 FT job comes first tho
[18:25] <arraybolt3> Ack, Discourse is still down, and so are parts of Phabricator (unless it's just that I don't have an account yet and so it won't let me see inside the repositories).
 ok well that was painful
 arraybolt3: not all repos are visible unless you have an account, that's By Design
 as for Discourse, I had to rebuild the entire container.  No data was lost, but it was painful
[18:40] <arraybolt3> teward: I'm guessing the Calamares configuration is one of the non-visible repos?
 No it should be visible.
[18:41] <arraybolt3> It's not. I'm getting a 502 Bad Gateway error trying to view it.
 I have an account and I can see anything in the webview either
 ffs
 i hate phab
 can't disagree
 *shoves an EMP into the phab container*
 i need to get gitlab launched here
 then get forced labor volunteers to start migrating repositories and project divisions over
 try phab now
 see if it works again
[18:44] <arraybolt3> Testing...
 or if it errors (and use F12 dev console to take a look)
 (and see what errors if any you see other than 500)
[18:44] <arraybolt3> EMP blew up
[18:44] <arraybolt3> Still can't view Calamares settings
 Uncaught (in promise) Error: The message port closed before a response was received.
[18:44] <arraybolt3> OK, I'll try F12
[18:45] <arraybolt3> 502 bad gatewat
[18:45] <teward> grrrrrrrrr
 Calamares and Cala-settings are on launchpad anyway and just mirrored to phab
[18:45] <arraybolt3> And I don't have an F12 key cause Im on chromeos
[18:45] <arraybolt3> OK, good to know
 Actually everything is mirrored to github too.
[18:46] <arraybolt3> got dev console loaded, nothing special on 502 page
[18:46] <arraybolt3> kc2bez: :thumb
[18:46] <arraybolt3> kc2bez: :thumbs-up:
 fatal: unsafe repository ('/var/repo/2' is owned by someone else)  <— for pretty much every repo
[18:47] <arraybolt3> Turns out clicking in Weechat sends the message instantly...
 well... this sucks
 time for us to move :P
 can one of you link me to an example page where you get this
 Awesome
 yes
 https://phab.lubuntu.me/source/lubuntu-artwork/
 Our GitHub in case someone is looking for it. https://github.com/lubuntu-team
 @kc2bez problem 1 fixed.  the problem is that backend is returning the error logs
 and I have no idea how to fix *that* error message take a look
 Yeah, that is a new level of chaos I've not seen before.
 and there's no documentation that I can find there so
 ooooooooooooo
 > Git recently pushed a change in response to a cve that causes git commands to fail if the parent directory changes ownership from the current directory. You may see errors like
 ah
 and that's not something I can... easily fix I don't think
 *checks apt*
[19:02] <arraybolt3> @kc2bez Thanks for the GitHub link!
 sure thing
 @kc2bez i'm very likely to make this work again but then make it so it's not writable anymore - readonly
 so we can start migrating OFF of phab
 but first i have to downgrade git
 >.>
 That makes sense.
 i'm going to get a gitlab running in a container so i can start prepping.
 we'll figure out issue tracking later
 repo stuff is more important at the moment
 Agreed
 git executable revert complete
 phab won't ever have a fix for this so
 It looks like the tasks are still there and working anyway
 same with the wiki
 well the won't anymore...
 *just chmod 555'd all the repo dirs*
 understood. As long as we can read them.
 well i unddid that to let tasks run
 but i'm going to 555 them once i get gitlab launched
[19:08] <arraybolt3> Make snapshots first!
 of what?
 git?
 containers?
 the containers are LXD system containers
 each acts as its own system
 'snapshots' doesn't help there ;)
[19:09] <arraybolt3> Sorry if that was silly - I've shredded so many VMs in the past, and I thought maybe containers had a failsafe like QEMU snapshots...
[19:09] <arraybolt3> I'll stay out of it, you know what you're doing
 hehe nah no worries
 these aren't VMs where things asplode
 and i know my way around chmod ;)
[19:10] <arraybolt3> :thumbs-up:
 the problem is /var/repo/* (for phabricator) isnt owned by www-data
 and the new git CVE that was fixed fixed that problem by saying 'unsafe directory'
 but even whne changed for pHP to use 'safe dirs' it didn't work so i had no choice but tor evert
 i'm tempted to use gitea which is lighter than gitlab for repos...
 we can always go to gitlab later...
 not opposed
 I like GitTea too
 *installs PostgreSQL backend for GitTea*
 sqlite is meh
 Agree
 the only thing i don't like about our bare metal is because the disks arent ssds there's extra latency
 it's still responsive enough for what we need
 just.. a little slower
 (it's twice the price for SSDs)
 It works for us.
[19:38] <arraybolt3> Hey, guys, I think I just figured out how to fix the LibreOffice locale issue in Calamares.
[19:39] <arraybolt3> In calamares-settings-ubuntu/lubuntu/modules/packages.conf, I think we can just add "libreoffice-l10n-$LOCALE" in the "try_install" section.
 For some reason i think that fails to install EN though. It is worth a try. We need to redo a bunch of the calamares modules along with an updated version of calamares once kinetic opens up.
[19:44] <arraybolt3> Argh... so basically it causes an installer crash even though nothing went particularly wrong?
 In your testing?
[19:45] <arraybolt3> I don't know how to tweak these things to test this sort of stuff...
[19:45] <arraybolt3> I was asking if that was something that you had experienced.
[19:46] <arraybolt3> Sorry, I'm really new to this whole thing.
 No it doesn't fail, it just doesn't install anything if you are in the EN locale. I could be wrong though and it warrants testing.
 So you can test this on a live iso.
 the configuration files are in `/etc/calamares/
 If you edit them in the live session you can attempt an install.
[19:50] <arraybolt3> Nice. Thank you! I'll dig around and see how it works! (It shouldn't require anything to be installed in the EN locale, since EN is default AFAIK, and we're able to do "libreoffice-help-$LOCALE" just fine, I think.)
 Sounds good
 The calamares section on this page can help you find the logs: https://phab.lubuntu.me/w/debugging/
[19:51] <arraybolt3> Nice.
[20:08] <arraybolt3> Hmm, just tested it out, and it appears that not only does atting "libreoffice-l10n-$LOCALE
[20:08] <arraybolt3>  not fix the problem,
[20:08] <arraybolt3> but additionally, "libreoffice-help-$LOCALE" isn't working, either.
[20:09] <arraybolt3> s/atting/adding
[22:07] <arraybolt3> @guiverc The LibreOffice localization workaround guide is finished and posted on Discourse in the Development section. I also did a massive amount of debugging on Calamares trying to fix the root of the problem, and have some ideas on what might be going wrong.
 So, not even going to lie to you guys, I spent about 6 hours on that btrfs bug last night and I'm stumped. Trying with a fresh coffee brain today, I'm hoping Manjaro fails with the same error so it's not an Ubuntu-only issue, but since stock Ubuntu 22.04 works and forward-porting 21.10's kpmcore (and rebuilding cala against it) doesn't work
[22:11] <guiverc> :) arraybolt3, the devs will understand it better than me (non-dev)
[22:11] <arraybolt3> oh ok
 @lynorian: see workaround guide above, perhaps worth looping into the manual? Unless there's a fix inbound
 It broke my brain too. (re @tsimonq2: So, not even going to lie to you guys, I spent about 6 hours on that btrfs bug last night and I'm stumped. Trying with a fresh coffee brain today, I'm hoping Manjaro fails with the same error so it's not an Ubuntu-only issue, but since stock Ubuntu 22.04 works and forward-porting 21.10's kpmcore (and rebuilding cala against it) doesn't work)
 arraybolt: Thanks! Much appreciated :)
[22:12] <arraybolt3> :)
 yeah it's an odd issue isn't it. (re @tsimonq2: So, not even going to lie to you guys, I spent about 6 hours on that btrfs bug last night and I'm stumped. Trying with a fresh coffee brain today, I'm hoping Manjaro fails with the same error so it's not an Ubuntu-only issue, but since stock Ubuntu 22.04 works and forward-porting 21.10's kpmcore (and rebuilding cala against it) doesn't work)
 i gave up trying to wrap the head around it :P
[22:13]  * genii 's ears shoot up at the multiple mentions of coffee
[22:13] <guiverc> arraybolt3, just moved your libreoffice.langauge.post to doco; add <kbd></kbd> tags & made it wiki.  you're a 'basic' user to discourse so may not yet be able to edit it; yell out if you need to any changes; and Thank You !
 fyi @kc2bez email is in to Canonical IS to set up the dns for git.lubuntu.me which will be the gitea
 arraybolt3: Any ideas on bug 1966774?  No pressure/rush but we're stumped and fresh eyes may help :)
 FYI @kc2bez as soon as I find my flash drive with my GPG key, I'll be starting with Calamares and working my way back on updating the stack
[22:15] <arraybolt3> First thought is that "Failed to start Snap daemon" is the same error we're getting with DVD boot on slow computers https://discourse.lubuntu.me/t/bug-failed-snap-daemon-in-lubuntu-22-04-lts-no-firefox-help-please/3246/37
[22:15] <arraybolt3> Not sure if the two are related, though.
 I'm going to try editing the cala settings to purge snapd then and see if it works :P
 Sounds fair. We got very behind on that so it is a good possibility. (re @tsimonq2: FYI @kc2bez as soon as I find my flash drive with my GPG key, I'll be starting with Calamares and working my way back on updating the stack)
 That's been my sneaking suspicion but there hasn't been enough evidence to back it
 I mean, updating the packaging in this case may be nearly a no-op (re @kc2bez: Sounds fair. We got very behind on that so it is a good possibility.)
[22:17] <arraybolt3> I'll try 
[22:17] <arraybolt3> a BTRFS install just so I can get a better idea of what's happening.
 Sounds good, thank you!
[22:23] <arraybolt3> Out of curiosity, has anyone tried installing to EXT4, then cloning the filesystem to BTRFS, setting up the bootloader and trying to boot that? That might tell us whether it's a Calamares problem or a problem with the rest of Lubuntu.
[22:23] <arraybolt3> I'mma try it if no one else has.
 It acts like a permissions sort of issue since I can mount the file system Calamares creates from a live image. Navigating it looks normal.
 I created a separate boot if I remember correctly.
[22:29] <arraybolt3> I can get into a BTRFS system by booting recovery mode and dropping to a root shell. I did notice various errors occurring during boot, but they went by way too fast to see.
[22:30] <tsimonq2> ohhhhhh yeah?
[22:30] <tsimonq2> That was also going to be my next step, although I was tired last night :)
[22:30] <tsimonq2> The various errors may be documented in that bug. Perhaps see if they seem familiar?
[22:31] <arraybolt3> I'll try booting a BTRFS system in painfully slow pure QEMU and screen record the session. That ought to catch the errors.
[22:31] <tsimonq2> Either way, trying with the snapd purge now and if that doesn't work I'll drop to recovery and start reading logs
[22:31] <arraybolt3> Right now I'm doing an ext4 install that I'm going to clone to BTRFS to see what happens.
[22:33] <tsimonq2> Sounds good, thanks
[22:45] <tsimonq2> Okay, so take a peek, if it'll share the image...
[22:45]  * tsimonq2 uploaded an image: (11KiB) < https://libera.ems.host/_matrix/media/r0/download/linuxdelta.com/LgfUVDwZwETmKaqVOYgcqyLk/image.png >
 Weird. Why can't it mount that?
[22:47] <tsimonq2> After remounting with the correct permissions, all of the services start with no issue.
[22:47] <tsimonq2> Let me take a peek at an fstab from a freshly-installed 21.10 system...
[22:48] <arraybolt3> ?!
[22:49] <arraybolt3> Clone in progress, we'll see what happens.
 *shoves more lxde into tsimonq2's hands*
[22:50]  * tsimonq2 throws @teward001 into a pit of broken GTK 1 applications
 tsimonq2: too late, i'm already there, we call it /dev/urandom
 We'll get that GTK polished up.
[22:50] <arraybolt3> teward: How does LXDE have anything to do with BTRFS? lol
[22:51] <teward> arraybolt3: remember what i said about 'random chaos'?
[22:51] <teward> that's just me and Simon greeting each other regularly xD
[22:51] <arraybolt3> Yep.
[22:51] <tsimonq2> (it doesn't, we just poke each other from time to time, have been for years :P)
[22:51] <teward> yep we just poke at each other to have fun :)
[22:51]  * tsimonq2 throws @teward001 into the grand canyon
[22:51] <teward> yes it divulges a little from things here and channel topic, but for some of us it keeps it light and friendly and chaotic xD
[22:52]  * teward drags tsimonq2 with him into the fiery pits of /dev/hell
[22:52] <teward> diverges*
[22:52] <teward> stupid autocorrect
[22:52] <teward> *yawns and goes back to testing Lubuntu 22.04 in the VM*
[22:52] <arraybolt3> You mean auto-incorrect.
 ACCURATE
 oops caps
[22:52] <guiverc> :)
[22:52] <tsimonq2> $ apt-file find /dev/hell
[22:52] <tsimonq2> systemd: /dev/hell
[22:52] <tsimonq2> :P
[22:54] <kc2bez[m]> I think arraybolt3 's clone ide should work. The permissions will likely come out correct. 
[22:54]  * tsimonq2 uploaded an image: (56KiB) < https://libera.ems.host/_matrix/media/r0/download/linuxdelta.com/kcZMHSqZPZYbTBlfUptcaCuS/image.png >
[22:54] <arraybolt3> Here's hoping. I finished the clone, now I probably just need to reboot. I'll probably end up fighting with GRUB, but we'll see.
[22:56] <arraybolt3> Yep, fighting with GRUB. :(
[22:56] <tsimonq2> The fstab is the same on both systems :(
[22:57] <kc2bez[m]> Yeah, that doesn't help.
[22:58] <tsimonq2> hold on
[22:58] <tsimonq2> what if I try a clean 22.10 install and upgrade to 22.04?
[22:58] <arraybolt3> Failed to activate swapfile?
[22:58] <arraybolt3> I'm booting the newly cloned system and just saw that error.
[22:58] <tsimonq2> ohhhhhh yeah?
[22:59] <tsimonq2> okay let's try that first...
[22:59] <arraybolt3> Failed to start Remount Root and Kernel File Systems. Failed to activate swap.
[23:00] <arraybolt3> And now Linux can't seem to find the EFI partition. I just got dropped to an emergency console.
[23:00] <arraybolt3> Hold on, I gotta stop for a bit
[23:01] <tsimonq2> All good, I'll be carrying on
[23:01] <tsimonq2> I appreciate your help :)
[23:05] <arraybolt3> OK did I miss anything?
[23:06] <kc2bez[m]> Nope
[23:06] <arraybolt3> Gookd.
[23:06] <arraybolt3> ARGH! Good.
[23:07] <tsimonq2> Argh. Removing swap entries from fstab doesn't work
[23:07] <tsimonq2> Trying the upgrade... if it's successful, then it's still an installer problem, if it's unsuccessful it means it's an underlying system issue
[23:07] <arraybolt3> I don't get it. It's like it's having trouble mounting stuff, even though systemd is on and doing stuff, so obviously it's able to access the disk.
[23:08] <arraybolt3> Hey, since you had a problem with remount in the emergency shell, I'm wondering if this is an initramfs problem?
[23:09] <tsimonq2> hmm, maybe
[23:09] <arraybolt3> I remember Puppy Linux will install to /dev/vda, but then not be able to boot because the initramfs is missing drivers. It has to be installed to /dev/sda to work.
[23:10] <tsimonq2> The only issue with that precisely is it happens on real hardware
[23:10] <arraybolt3> Does anyone know if plain Ubuntu 22.04 can BTRFS install correctly?
[23:10] <tsimonq2> Yeah, tried it earlier. Works fine
[23:10] <tsimonq2> Which is making me think this upgrade will be successful
[23:10] <arraybolt3> Crud. That seems to rule out an initramfs problem, since I believe Ubuntu and Lubuntu use the same initramfs. Your upgrade idea is good.
[23:11] <tsimonq2> In the meantime, I'm also grabbing a Manjaro ISO to rule out those versions of things.
[23:12] <arraybolt3> 👍
[23:21] <arraybolt3> Maybe I did the clone wrong? I'm realizing I cloned the ext4 image to BTRFS using "rsync -avxHAWX --progress ./srcroot/ ./trgroot/". I'm wondering if maybe rsync messed something up, 'cause I'm pretty sure rsync is the tools Calamares uses to clone the squashfs
[23:21] <arraybolt3> Or maybe I just botched my command...
[23:28] <kc2bez[m]> In theory you could just convert the filesystem to btrfs with btrfs-convert.
[23:29] <arraybolt3> Another idea I just had was to chmod 777 root. If there's a permissions problem anywhere, that ought to clear it up (or whatever, you know what I'm trying to say)
[23:29] <arraybolt3> @kc2bez Good idea!
[23:38] <arraybolt3> Hey, look what I just found: https://bbs.archlinux.org/viewtopic.php?id=178329
[23:39] <arraybolt3> Ah, found my problem. My clone trick didn't work because it's still looking for an ext4 partition, and it's probably looking for the wrong UUID. Let's see if I can get it to boot now.
[23:44] <arraybolt3> Making progress, got the remount errors to go away. Still booting since I botched fstab AGAIN, but it's better than last time.
[23:47] <arraybolt3> I GOT IT TO BOOT!!!!!!!!!!!!!!!!!!!! With BTRFS.
[23:48] <arraybolt3> @tsimonq2 @teward Successful BTRFS boot of Lubuntu 22.04.
[23:51] <teward> cloning ext4 -> btrfs you mean
[23:51] <arraybolt3> Yes.
[23:52] <teward> what we need to replicate is cala installing to / exploding and then not working after the fact, I think, but IDK how to replicate at this second (err:busy)
[23:52] <arraybolt3> I cloned ext4 to btrfs, cloned the EFI partition, and fixed fstab. I had to enter the boot code into GRUB manually, but it worked.
[23:54] <arraybolt3> I'm going to try doing a regular BTRFS install (the kind that explodes), and see if there's any tweaks that will fix it.
[23:54] <kc2bez[m]> That makes me think the clone process that cala implements is to blame.