MX-23 beta 2 feedback thread

[dolphin_oracle]

OK, my initial effort was to run the beta-2 as a live USB - no problems noticed

Second was to go to an installed beta-1 and updat / upgrade - no problem, everything looked to be upgraded nicely

What I didn't try was to install from the beta-2 USB - that failed. I was going to overwrite an MX-21.3 partition on one of the spare laptops BUT at the step ti select the partition (the SSD has 2 partitions, MX-21.3 and Debian 11 + a swap) things looked odd, almost I would guess like the Antix system? The MX-23 beta-1 didn't look like that and an install on another old laptop worked fine as expected.

Has anyone else had this problem?

Forgot to add - MX-23 beta-2 XFCE on a Lenovo X240

antix uses the same installer, so likely identical or near to. should be dropdowns for the various partitions discovered.

[BV206]

I installed beta 2 in VirtualBox. Everything worked until I tried to remove all the locales I don't need.
In System Locales I unchecked everything except en_US.UTF-8.
Then I set that to be the default.
It fails and gives this error.

Code: Select all

Generating locales (this might take a while)...
en_US.UTF-8...[error] cannot open locale definition file `en_GB': No such file or directory
done
Generation complete.
*** update-locale: Error: invalid locale settings:  LANG=en_US.UTF-8
"Configure System Locales" canceled: exit [255]

I don't know why it's looking for `en_GB'. when that isn't selected.
It seems like this also happend earlier this year when I installed MX 21 but I don't remember how I fixed it.

[fehlix]

I installed beta 2 in VirtualBox. Everything worked until I tried to remove all the locales I don't need.
In System Locales I unchecked everything except en_US.UTF-8.
Then I set that to be the default.
It fails and gives this error.

Code: Select all

Generating locales (this might take a while)...
en_US.UTF-8...[error] cannot open locale definition file `en_GB': No such file or directory
done
Generation complete.
*** update-locale: Error: invalid locale settings:  LANG=en_US.UTF-8
"Configure System Locales" canceled: exit [255]

I don't know why it's looking for `en_GB'. when that isn't selected.
It seems like this also happend earlier this year when I installed MX 21 but I don't remember how I fixed it.

what would this show:

Code: Select all

cat /etc/default/locale

and

Code: Select all

locale 

and

Code: Select all

locale -a

[dolphin_oracle]

...

did you assign a /boot partition? the installer shouldn't have let you proceed without one if encryption was enabled. I didn't see a /boot in your log.

Indeed, I did not. Why? From former experiences, knowing that installer has a good checking for improper setup (always had halted me, when encryption was enabled and I was trying to have boot on root partition), so I was experimenting, if it finally supports boot on root together with encryption.
So, installer let continue, with wrong (unsupported) setting.
(( Why, in the age of surveillance, when attacks on encryption are much easier, and funded by big entities, we still does not have working LUKS2 (which enables much safer PBKDF)?
What is holding smart programmers from making it working? ))

BUT:
Timeshift does not recognise BTRFS.
(its radio button is disabled)

Code: Select all

$ sudo btrfs subvolume list / 
ID 256 gen 36 top level 5 path @

So, I double checked it (reinstalled once more), same result.

ok we are looking into why the installer let you continue without a boot partition, thanks for the report.

I can confirm the timeshift report as well. apparently it doesn't like a btrfs format inside a luks container. works OK if the btrfs partition is not encrypted.

[peter_li]

+++EDIT+++
On UEFI systems, you can use rEFInd efi-bootmanager, to multi-boot through rEFInd provided EFI-bootoption menu,
which should also allow boot into any btrfs install.

That's fine especially cause one can install Grub2 and rEFInd as I read. But you will have to inform it about OS updates or added/deleted systems?
Would it there not be the better or equal behavior to hammer on the F12(at least on a DELL Latitude E6510) key at boot?

I idea for inventing rEFInd was something like an easier efi-bootmanager. It can be set as default efi-loader and would list all found efi-loader, not only those which are listed with NVRAM(and may be invalid already).

I thought when I hammered F12 the computer shows me the content of the EFI-SYSTEM parttion direct but you mean its the content of the NVRAM which is on the computer board? So a installation need to write to both? Therefore more than only one EFI partition may exist as long as in the NVRAM is stated which to use?

But what to do when there is only one time Ubuntu shown in the UEFI Boot but there are three partitions: Ubuntu-Mate, Xubuntu and Pinguy egg created Ubuntu? This seems a bit complicated.

That's Ubuntu and secure-boot related issue, as all those ubuntu-flavors use just one efi-loader entry.
That's actually similar what Debian is now doing, so if you have to install two debian installations, you would only find one EFI-loader. One way to solve it, use for every such install a separate ESP.

So you mean that more than one may be created maybe on the same disk? Is this supported now? As I read on this page it seems not to be supported? So I would need three or more to access my three Ubuntu-flavors, okay?

[asqwerth]

OK, my initial effort was to run the beta-2 as a live USB - no problems noticed

Second was to go to an installed beta-1 and updat / upgrade - no problem, everything looked to be upgraded nicely

What I didn't try was to install from the beta-2 USB - that failed. I was going to overwrite an MX-21.3 partition on one of the spare laptops BUT at the step ti select the partition (the SSD has 2 partitions, MX-21.3 and Debian 11 + a swap) things looked odd, almost I would guess like the Antix system? The MX-23 beta-1 didn't look like that and an install on another old laptop worked fine as expected.

Has anyone else had this problem?

Forgot to add - MX-23 beta-2 XFCE on a Lenovo X240

While you can continue to upgrade beta1 to use it, some default configs were changed in beta 2, so you won't really be helpful in debugging beta 2 in this thread.

[asqwerth]

@peter_li

From what I understand, normal grub in say, Arch, has os prober disabled but the user can edit /etc/default/grub to say no to disable os prober.

Apparently in Debian 12, in every update of grub package , they will redo the disabling of os prober so multi boot machines will not search for other distros or OSes again.

MX devs added their own script so that os prober will always be re-enabled. However that means that a user can't manually disable os prober from within that grub file. That instruction is ignored.

[pbear]

FWIW, I prefer to use 40_custom rather than manually editing grub.cfg. Haven't tested btrfs in a couple years (don't use), but worked fine then. Be sure to use /@ on the configfile line if appropriate.

[Edited for clarity.]

[pbear]

The MX-23 beta-1 didn't look like that and an install on another old laptop worked fine as expected.

Has anyone else had this problem?

FWIW, I installed XFCE beta2 to a similar multi-boot test box. Worked fine.

[Freja]

Thanks to everyone involved in building this great distro. I have been testing Libretto XFCE since beta 1, hereby my issues encountered.

Hardware:
Asus Vivobook Oled 3k 12th gen Intel
24 Ghz Ram

- Scaling issues. It happens frequently that I need to rescale on boot (Display->Scaling->0.5). The system sometimes (not always) forgets my settings during reboots/wakepups.
- Crashes when connecting to an external screen (HDMI). First the option is shown how to use the external screen (mirror, extension, etc). After choosing, the computer reboots
- MX Linux animation on startup and shutdown is extremely slow, it takes almost a minute to run (this was smooth in a VM, not sure why not on metal)
- The notification 'Do not show this message again', for example when a network is found, is ignored. The message keeps on showing up. I had to put the machine in Do not disturb mode
- Telegram Desktop Flatpak cannot be installed using the software installer (Error pulling from repo: GPG verification enabled, but no signatures found)

My MacBook Pro 2013 13inch still has same problem.
And, I saw that In the youtube MX-23-b2 review movie,
boot animation protruding to the screen (too big animation image).

Then, We need to fix boot animation.
I will made 60% shrink animation .png. I will send it to @CharlesV tonight,
I want you to prepare a test machine and review the code. I'm sorry for increase your work.

If you don't have a test machine, you might want something my 2013 MacBook Pro,
or closer to the Asus Vivobook Oled 3k 12th gen Intel.