MX Linux Forum

I think it well may be the disk space. given the host of errors. it may be more full that the inxi output suggests since both home and / are on btrfs subvolumes. they are reporting very full.

Same here, when general system font is set to bold (as it was in my case) the problem is present, when I change it to semibold or normal the problem is resolved. Is that expected behavior that font weight setting in LO document is overridden by system settings? IMO that shouldn't be the case I tend...

I can duplicate this if you have chosen a bold general system font.

what font are you using?

and please provide the quick-system-info for the affected pc.

So you won’t be able to continue until you at least run the command indicated in the error

If you are not using proton then disable the repo. (Mx repo manager last tab)

@Adrian I pushed a change to the rules file.

thanks for the report. will look into it. probably something in the packaging @Adrian

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...