MX Linux Forum

could be a device defined in your /etc/fstab is not present. this tends to freak out systemd. given that you have no swap active, I'm guessing its your swap partition. likely wiped out by another OS install (just reformatted likely). adding the proper UUID to your /etc/fstab will likely clear it up....

I suggest that this is the culprit: Active apt repos in: /etc/apt/sources.list.d/home:danpla.list 1: deb http://download.opensuse.org/repositories/home:/danpla/Debian_12/ / The best way to screw up MX is to go outside of our repositories rather than putting in a package request. With this new repos...

The installer was in fact originally laid out 20 years ago.

it cannot create lvm.

I don't think you need an lvm to have a seperate /var and /tmp partition. but you would need a separate partition(s).

you installed qcontrol rather than qjournalctl.

qcontrol is a specific thing, according to debian archive:

qcontrol - Hardware control for QNAP Turbo Station

so doubtful it work work on the orange pi anyway.

I think you can drag the archive onto the Appearnce setting window too IIRC.

Jerry3904 wrote: ↑Wed Apr 17, 2024 7:44 pm Ok, thanks. That repo is blanked out, so instead of adding it I'll download the package and move it over.

I'm slightly confused. can you not install from mxpi?

they are already in the test repo.

the error message is not that the device is out of storage space, its that the file is too large. this could be a limit of the file system, especially if the device is formatted fat.

a fat formatted system would have a max file size of around 3.5 GB. You're estimated iso size is over 5gb.

That’s not red shift. We recently added saving back the keyboard timezone and language live boot parameters.

make sure that kernel namespaces is not disabled. you can check in mx-tweak on the last tab.

I have confirmed that the 6.1.0-20 does support the feature, and flatpaks work here (I use kdenlive flatpak).