MX-21 beta 1 feedback thread

[AK-47]

One issue with re-using the swap file though is after unlocking and re-using it through the installer, you will end up with a password prompt to unlock every encrypted partition you reused through the installer, so if you reused 2 partions, you will have to type each partitions password at login and if you reused 3 encrypted partitions, you will be asked 3 times at boot for the password for each partition.

This may be a either a bug or an omission in the new installer, or an error in the process I tested with. Maybe others can chip in here to give some clarity.

@m_pav Perhaps your VM or system doesn't have enough free RAM then cryptsetup fails to load a key. This failure wasn't picked up by the installer so it carried on regardless, I have now changed this.
This failure is usually caused by not having enough free RAM. The default PBKDF is Argon2i and if you don't have at least 50-60% of RAM free (on a system with 2GB or less) then either cryptsetup or Xorg crashes (maybe the OOM killer).

If usnig a VM, try increasing the RAM to at least 1280MB and running sudo zram start before running the installer.

[Feuerkl1nge]

Some of the further things I noticed:

MX Package Installer
PlayOnLinux
E: Package wine-staging-compat could not be found.

TorBrowser right click to select something from the context menu while the right click was made on a link results in an immediately opening window of that link instead of seeing the usual context menu.
You can reach the menu by keep holding the click and releasing it on the context menu option you want. That bug is TorBrowser only and did not exist on MX19 (AHS) with same TorBrowser 10.5.2

ClipGrab-3.9.6-x86_64.AppImage from clipgrab.org do not work anymore. I guess old packages within the appimage interfere too much.

I forgot the rest but I may write it later.

[m_pav]

@AK-47 Thanks for your work on this. I'll test it again when I get another opportunity using an updated ISO with my improved understanding of how it should work.

My testing VM is provisioned with 4GB RAM & 2 CPU's so I can test without space or processing limitations on my daily driver in my sig below. This time round, I was testing the new installer and my expected usage of it when MX goes final on my daily driver by reinstalling on encrypted /home and swap within the safety of a disposable VM.

[chrispop99]

Webcamoid bug.

I've reported this earlier, but the more I've thought about it, the more I think it will be a problem. If you have a USB webcam that is recognised by, and works with, Webcamoid, but you accidentally launch the program with the webcam unplugged, Webcamoid will refuse to recognise the webcam in subsequent attempts. You can reboot, delete the local config file, even purge/reinstall, but that camera won't be detected by Webcamoid again.

The problem does not occur with Cheese. (I'm not an advocate for Cheese; I mention it to show it is a Webcamoid problem.)

(Added)
To make certain this wasn't an MX Linux problem, I tested it the same way with Linux Mint, and had the same failure.

I know that a lot of people have laptops with no built in webcam that have needed to buy a USB one during the pandemic; they will be pretty inconvenienced if it didn't work.

Chris

[richb]

Webcamoid bug.

I've reported this earlier, but the more I've thought about it, the more I think it will be a problem. If you have a USB webcam that is recognised by, and works with, Webcamoid, but you accidentally launch the program with the webcam unplugged, Webcamoid will refuse to recognise the webcam in subsequent attempts. You can reboot, delete the local config file, even purge/reinstall, but that camera won't be detected by Webcamoid again.

The problem does not occur with Cheese. (I'm not an advocate for Cheese; I mention it to show it is a Webcamoid problem.)

(Added)
To make certain this wasn't an MX Linux problem, I tested it the same way with Linux Mint, and had the same failure.

I know that a lot of people have laptops with no built in webcam that have needed to buy a USB one during the pandemic; they will be pretty inconvenienced if it didn't work.

Chris

I can confirm the same behavior with MX 19.4.

[drogon69]

how good is the beta 1 version of mxlinux really , and share folders , there is not one bug at al in this beta not one..
my english is not very good , but but my knowledge higher lol
https://www.youtube.com/watch?v=z806Jcz0sEQ

[asqwerth]

how good is the beta 1 version of mxlinux really , and share folders , there is not one bug at al in this beta not one..
my english is not very good , but but my knowledge higher lol
https://www.youtube.com/watch?v=z806Jcz0sEQ

You should also clarify on the youtube page of this new video that this is your own plasma respin of the MX21 XFCE beta as the official MX21 Plasma beta is not released yet.

Otherwise there will be confusion.

Right now we are all trying to get helpful feedback on the XFCE version, so these videos will confuse people if not clarified.

[oops]

-- canceled ---

[VCR58]

Thanks drogon69

I already have a media server running on my MX-21 box. I use NextPVR. I wanted to see if NextPVR would install and run on MX-21 with Debian Bullseye.

It does :-)

[AK-47]

@AK-47 Thanks for your work on this. I'll test it again when I get another opportunity using an updated ISO with my improved understanding of how it should work.

My testing VM is provisioned with 4GB RAM & 2 CPU's so I can test without space or processing limitations on my daily driver in my sig below. This time round, I was testing the new installer and my expected usage of it when MX goes final on my daily driver by reinstalling on encrypted /home and swap within the safety of a disposable VM.

That's odd, 4GB should be more than enough RAM for encryption to work flawlessly. Are you using a respin, snapshot, or the vanilla MX-21 beta 1 ISO?
Can you please give me both /var/log/minstall.log and /etc/crypttab from the installed OS if you see that problem again.