Looks like it's fixed but there's no feedback to the user when there's a fail. Filed a separate bug about that. At the least, though, we can have folks check the casper-md5check.json file in /run in live or /var/log/installer in installed. And I've confirmed the results are included in bug reports.

It looks like the bug is scheduled to be fixed for release so I suspect with that this issue will be resolved.

I'm going to just call this good.

Actually reopening this because we should also ensure that any references to ark are swapped in rDEFAULTSETTINGS.

BTW there's a bug where the check isn't even working right. It seems that this is a regression after they tried to keep the boot going while the check was happening. If they do get that working, then this will be irrelevant, since the confusing text won't be there and the desire to skip won't be there, either.

@guiverc @Leok @KGIII it would be super helpful if you could test lxqt-archiver for functionality, especially as it relates to the functionality of ark. You'll need to install it. Note that you will also want to check how it integrates with pcmanfm-qt. In the settings you can change the archiver integration to lxqt-archiver. Drag and drop SHOULD be something that it should have that ark doesn't, but confirmation would be helpful.

Closing this because it's not well explained and hasnt' been.

So a few things:

• It seems now that running picom results in it not using the compton.conf, but effectively using a null config. That's an improvement.
• There are two transparency options in QTerminal: application and terminal. Application (the first one) changes the entire application. Terminal changes just the text area. I was able to get both to work with picom running, so I think maybe that was just a misunderstanding there.

@teward with Dan's approval here and on the other task (which should be taken as an "all of the above" sort of thing), I think we're set. We've got a critical bug fix for EFI installs in kpmcore (which needs Calamares rebuilt against it; also we're pulling in a new release which just popped out), so if we could get this resolved quickly that would be great. Alternately, if you or someone want to sponsor that, it would be most appreciated (but we're still otherwise good to go on packageset changes).

kpmcore!

Thanks to a bunch of testing from others, this works everywhere (all the flavors) but sometimes (especially Lubuntu?) it needs to be hit multiple times for it to work. So maybe something else is going on.

We've got other applications like LibreOffice and VLC that I did not include as those really aren't our babies. I'm comfortable with this list and await further input from others.

• qapt-deb-installer
• plasma-discover
• muon
• openbox
• sddm
• pavucontrol-qt
• qps
• partitionmanager
• k3b
• kcalc
• pinentry-qt
• usb-creator-kde
• lxqt-metapackages

Here's the aforementioned fix to show unknown by default unless there's a clear skip or pass.

Well, trivial, but not THAT trivial. It should be pointed out automirror is using a json parser, so we need an xml one. Looking at the docs and the vulnerabilities in XML, I'm inclined to use defusedxml.

The only other two that aren't core LXQt/Calamares/Lubuntu stuff are zram-config and arc-theme and I don't mind having upload access there.

I'm all for removing the above. I can't see any reason why we *need* upload access to any of them.

I'm gonna pass on the consolidation. Given the modular nature of Calamares and the fact that not everyone is going to use every module AND the fact that automirror is solely ours, I don't think that it's going to be quite easy to implement a one time lookup sort of thing.

Why are you requesting a review on something so simple? XD

You want to SRU LibreOffice 7??????

@The_LoudSpeaker there's now a task list in the description.

The official build order is here so that's what we should be following.

The more I look at this the crazier it makes me. Like why are we commenting out the backlight crap that we are then installing in the install file? This is madness. That said, it does seem to build without errors (confirmed by my own hand), so I guess I'll just turn a blind eye. I guess we can always fix it later if needed.

This is now a part of all Ubuntu ISOs. Horray!

I have one little problem.