MX-21 beta 1 feedback thread

[dolphin_oracle]

Brightness Systray in Settings Manager fails to start.

@Gaer Boy thanks. so no icon in the systray? Looks like a little half-sun type icon

[entropyfoe]

More testing...
All working so far.

Lots of sleep and wake, no problems.
Took all synaptic upgrades.
disabled sudo per I think swamprabit's tip.
compositor changed to compton.
installed Warpinator, it works.
Audacity works.
conky changed and edited all with normal operation.
The usual firefox customization

I changed the theme and stuff. It was a black window title bar, right?
That makes it hard if two title bars overlap, it is hard to see what is what.
The old MX greybird has a row of pixels at the window edge with a different color to differentiate the edge.

Fortunately there are many options to choose from.
But what should be the default for wide appeal to reviewers and new MX users?

[entropyfoe]

During the install you can go to advanced, and disable services.
I do that and take off sudo and bluetooth.

So what does that un-checking sudo do ?

I go and had to change it in the MX Tweak ---> Other to turn off the sudo authentication for admin tasks like synaptic. (SwampRabit's tip)

[dolphin_oracle]

During the install you can go to advanced, and disable services.
I do that and take off sudo and bluetooth.

So what does that un-checking sudo do ?

I go and had to change it in the MX Tweak ---> Other to turn off the sudo authentication for admin tasks like synaptic. (SwampRabit's tip)

unchecking sudo disables the sudo service, but it does not affect the gui authentication prompts because that is polkit not sudo.

[Adrian]

So what does that un-checking sudo do ?

https://askubuntu.com/questions/228288/ ... service-do

[entropyfoe]

Thanks Adrian and d_O.

A little bench-marking now, since I have MX 21 and MX 19.4, both full updated on the same machine, different partitions.
So running the System Profiler and Benchmark tool, the only difference is the OS, and therefore the kernel.
MX 21 5.10.0-8
MX 19.4 5.10.0-5mx
Significant means the difference on OS is much greater than the difference from repeated running of the test. Testing after fresh reboots, only a terminal open besides the Profiler. The system is in the signature.

Test ..............MX21 .....MX 19.4
CPU Blow fish ..... 0.47 .....0.48 seconds
Cryptohash ......5339 ....1953 (wow that's a big difference, it is repeatable and significant)
Fibonacci .........0.30 .....0.49 sec MX21 faster, it is repeatable and significant)
n-Queens ........4.62 ......4.54 sec
CPU z-lib ........2.93 .....3.00 High Mark score
fft ...............0.71 ......0.69
fpu ray tracing ....4.2 .....2.25 sec (wow MX 21 much slower it is repeatable, and significant)
gpu drawing .....13298 .....14663

[SwampRabbit]

Interesting. I wouldn't use the System Profiler and Benchmark tool as a measure of benchmarking too much... good, bad, or indifferent.

1) Debian's version of hardinfo is really old in the stock Debians (don't know if we updated it for MX-19 after)... something to look at later
2) Everything in Buster/MX-19 has gone through so many updates/tweaks over their lifespan that its kinda unfair to compare it to both Debian and MX Betas.

Do let us know if you see real world differences or do more benchmarking.

[entropyfoe]

SwampRabbit,

Yup, I don't attribute any absolute signifficance to the Bench marking numbers. But a relative comparison should be valid.
But assuming the benchmark code is the same in MX19.4 and Mx21, on the exact same hardware, then what is the differences?
The OS, libraries, the kernel maybe some flags set different.

It is interesting some benchmarks are almost identical and some have big changes.
The crypto hash, for example, if it has any relevance to actual mining, then you are making twice as much money per day.

[entropyfoe]

What is that Thunar icon?
How anti-intuitive !

I tried different icon sets in the MX Tweak, but they are all the same for Thunar.
Can we get a new one?

[m_pav]

Hi, I tried installing on an existing MX-19 machine with encrypted root filesystem (and no separate /home partition): although the installer help on the left mentions the "Preserve /home" option, I actually couldn't see that in the drop down list, so I aborted installation. Am I missing something, is the installer unable to preserve /home if root is encrypted, or is this a bug in the installer?
Thanks

@Leo C. There is no bug, just a new process. Scroll down in the help and you'll see what to do. It's relatively straightforward and it helps a lot if you have the naming schema already in use on your existing install. This is not strictly necessary, but the names you give to the encrypted partitions will be used in /dev/mapper/

To get the naming convention in use, start by looking in /dev/mapper/ on your existing installation. Here you'll find a control file and symlinks to the partition names used when you last installed MX Linux. if you want to re-use these names, write them down, commit them to memory and when you're asked to provide a name for the encrypted partition, type it in.

When selecting your partitions, right click the encrypted partition and select unlock or add to crypt tab, then type in the name you wish to use and the encryption password.

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.