MX 25 Beta 1 Feedback thread

[dolphin_oracle]

I would recommend waiting for official instructions (@dolphin_oracle when do you think we should publish them?)
The issue is not that simple because of how we have systemd-ship set up in MX23 and is not available in Debian Trixie the user will have to choose to switch to systemd or to sysvinit and there are some extra steps involved in that.

I think we will publish them a little closer to RC, if not RC1.

The only error-message in Synaptic when I changed "bookworm" to "trixie" in the repo-gui occured with the mx-repos.
It said that the keys are wrong. I don't remember the exact words.
Right now the upgrade takes place with the mx-updater.

I think you will get a partial upgrade, at best.

[fehlix]

OK, here is a "funny" one, for testing I tried to install from a MX-25-xfce beta1 LiveUSB, and
got "Failed to format partition"
It was an empty drive, with no partition table on it.
So I started to use the build-in-partition manager to add my usual partitions
vda1... vda4, (bios_grub, esp, swap, main labeled MX-25_xb1)
But the build-in partition'er was too boring, when I wanted to add 16GB size, it did not allow me just to type 16 gb,
I was asked to hold scroll up the up-button to count in mb. That i didn't like and clicked on the Gparted symbol to open Gparted
and prepared partition table GPT and all partitions I wanted.
Everything went fine until this huge a failure pop'd up:

Failed-to-format-partition.jpg

[Jerry3904]

I got that error early Monday morning until I upgraded and the new installer version came in -- without such problems.

[MintHawk]

The issue is that it can't find a bootable device, as it says. Of course I've tried that in many different ways such as with UEFI/Secure Boot Off, Legacy, etc.
It just won't install...When I was running 23.6 it had some trouble booting and prompted me for CTRL+D to resume normal boot (maybe a hardware thing...?).
Because I was curious, I installed Windows 10 on the Dell and it runs fine, so I'm not sure that it is definitely a hardware issue...

[dolphin_oracle]

The issue is that it can't find a bootable device, as it says. Of course I've tried that in many different ways such as with UEFI/Secure Boot Off, Legacy, etc.
It just won't install...When I was running 23.6 it had some trouble booting and prompted me for CTRL+D to resume normal boot (maybe a hardware thing...?).
Because I was curious, I installed Windows 10 on the Dell and it runs fine, so I'm not sure that it is definitely a hardware issue...

after install is when you get the boot error, correct?

its quite possible your system is still trying to boot a previous UEFI install.

[MintHawk]

after install is when you get the boot error, correct?

Correct.

[Eadwine Rose]

Would a sudo update-grub maybe help here?

Or wrong direction of thought?

[fehlix]

I got that error early Monday morning until I upgraded and the new installer version came in -- without such problems.

That's the latest I got

Code: Select all

apt policy mx-installer
mx-installer:
  Installed: 25.09.1mx25
  Candidate: 25.09.1mx25
  Version table:
 *** 25.09.1mx25 500
        500 http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo trixie/main amd64 Packages
        500 https://mxrepo.com/mx/repo trixie/main amd64 Packages

But another minor "issue", can anybody explain what the Active partition table column
is good for an UEFI installation. The help panel tried to give some ideas:

Active partition
For the installed operating system to boot, the appropriate partition (usually the boot or root partition) must be the marked as active.
The active partition of a drive can be chosen using the Active partition menu action.
A partition with an asterisk (*) next to its device name is, or will become, the active partition.

AFAIK, Active partitions flags are neither needed nor even used in UEFI boot. After UEFI system handed over to efiGRUB loader there is no intention of GRUB
to try to analyze what flags a partition may hold.
Suggest to "hide the Active Partition column for ESP UEFI installs, and adjust the explaining (now missleading) help text, that this flag is only used for legacy BIOS booting by some BIOS//CSM emulators.
In geparted in legacy boot shown as "boot" flag and in UEFI boot as "legacy_boot".

[siamhie]

roxterm won't install because roxterm-data is missing. Happens on both XFCE and fluxbox installs. @Stevo?

Code: Select all

Reading package lists...
Building dependency tree...
Reading state information...
Solving dependencies...
Some packages could not be installed. This may mean that you have
requested an impossible situation or if you are using the unstable
distribution that some required packages have not yet been created
or been moved out of Incoming.
The following information may help to resolve the situation:

The following packages have unmet dependencies:
 roxterm : Depends: roxterm-data (= 3.12.1-1mx23) but it is not installable
E: Unable to correct problems, you have held broken packages.
E: The following information from --solver 3.0 may provide additional context:
   Unable to satisfy dependencies. Reached two conflicting decisions:
   1. roxterm:amd64=3.12.1-1mx23 is selected for install
   2. roxterm:amd64 Depends roxterm-data (= 3.12.1-1mx23)
      but none of the choices are installable:
      [no choices]

[Jerry3904]

I got that error early Monday morning until I upgraded and the new installer version came in -- without such problems.

That's the latest I got

Code: Select all

apt policy mx-installer
mx-installer:
  Installed: 25.09.1mx25
  Candidate: 25.09.1mx25
  Version table:
 *** 25.09.1mx25 500
        500 http://ftp.halifax.rwth-aachen.de/mxlinux/packages/mx/repo trixie/main amd64 Packages
        500 https://mxrepo.com/mx/repo trixie/main amd64 Packages

Yeah, me too. So I don't know what effect "upgrading" had but when I logged out/in and tried again all went well--twice, in fact, on two different boxes and inits.