MX-21 KDE beta 1 feedback thread

[dolphin_oracle]

wifi: try setting your connection to allow all users to connect.

[junoluna]

The release announcement tells you Discover is used for updates.

Chris

thanks chris...feel pretty dumb now...

I did read the release notes honestly ...maybe more a skim than a read

i went ahead and installed apt-notifier .... should i get rid of it again?

[Adrian]

i went ahead and installed apt-notifier .... should i get rid of it again?

It's not needed, you'll get 2 notifications that you have updates pending, at the same time if you prefer some of its features you could use it instead of discover, I think you could set up discover to never check for updates.

[baldyeti]

Not clear to me, why you want booting in UEFI mode with MBR-partitions. But yes, you can boot in UEFI-mode and tick off/disable the GRUB installation. Not clear how you to boot into the system without boot loader. Actually you can boot in UEFI-mode and do GRUB-bootloader installation in BIOS/MBR mode.

Thanks fehlix. The resaon is this particular machine (at least with this particular USB key) will only boot the (ventoy) live system in UEFI mode. This way I could install then fix grub later from the MX18 instance which owns the MBR on this PC. I will probably rather make some free space on another system to run a more realistic test for the installer but that may take a couple days.

[fehlix]

Not clear to me, why you want booting in UEFI mode with MBR-partitions. But yes, you can boot in UEFI-mode and tick off/disable the GRUB installation. Not clear how you to boot into the system without boot loader. Actually you can boot in UEFI-mode and do GRUB-bootloader installation in BIOS/MBR mode.

Thanks fehlix. The resaon is this particular machine (at least with this particular USB key) will only boot the (ventoy) live system in UEFI mode. This way I could install then fix grub later from the MX18 instance which owns the MBR on this PC. I will probably rather make some free space on another system to run a more realistic test for the installer but that may take a couple days.

As mentioned, even when booting in UEFI mode, the Installer allows to have GRUB installed into MBR or PBR, instead into the ESP (EFI System Partition).
If chosen PBR, this would not overwrite the MBR, but would still create GRUB menu at the KDE installation .
Just select PBR at the GRUB installation window, this would make it easier for MX18-GRUB to find the GRUB-menu of the MX21-KDE installation and to extract the menu-entries found. Not installing GRUB from with the Installer is also possible. In the case of not having installed GRUB (to the PBR), the MX18-GRUB would need to create (based on a bare template) one menu entry for MX-KDE. If having GRUB installed to the PBR, it would allow the MX18-GRUB to properly extract all menu entries from the MX21-KDE grub menu including the menu entry to boot with systemd.
Another advantage of having installed GRUB even to the PBR only would be that you could boot into the installed system using "Boot Rescue" tool from the LiveUSB boot menu and select "Grub menu" to search and find the PBR-installed GRUB menu on the MX-KDE installation.

[baldyeti]

Alright thanks for the clarification - i did not realise the installer would allow installing grub to MBR or PBR even when the installation media is booted in UEFI mode. I barely ever use UEFI as i mostly have older HW and often swap disks between systems.

[davemx]

I really don't like Discover. I spent a while just looking at a rotating logo waiting to discover what was going to happen next, and it never did! It may prove useful for installing Plasmoids but when I tried to get Event Calendar it denied its existence. I'll have another look later, maybe it will win me over in the end! For now, MX-installer and update, in conjunction with Synaptic is my preferred way of doing things. If it ain't broke...

I used MX installer to add a number of packages, and it reported an error while installing Google Earth. I had to recheck a number of packages that hadn't installed, and click Install again. Strangely enough though, Google Earth is installed and working perfectly.

My only real complaint is not directed at MX devs, but the tendency of the developers of Desktop Environments to keep fixing stuff until it's broke!

[davemx]

Another thing: Debian seems to have dropped "Disk Manager", so I'm having to do /etc/fstab by hand. Any advice?

[asqwerth]

Another thing: Debian seems to have dropped "Disk Manager", so I'm having to do /etc/fstab by hand. Any advice?

Install gnome-disk-utility.

Note that you may need, after using the above tool to mount whichever partition you want, to edit it a little (it may mount by default on /mnt instead of /media, for instance, so if you want to change mount points before saving the fstab entry, you have to edit the mount settings from within the said tool)

I thought the above tool was going to be included by default, but I guess not in the beta1 for now.

Disk Manager was not maintained for yonks but continued to work up till MX19.

I think it's based on python2 which is no longer in Debian Bullseye so it's gone.

I'm very sad to see it die off, as it was a good, quick and useful little tool.

[davemx]

Install gnome-disk-utility

I thought it was going to be included by default, but I guess not in the beta1 for now.

Disk Manager was not maintained for yonks but continued to work up till MX19.

I think it's based on python2 which is no longer in Debian Bullseye so it's gone.

I'm very sad to see it die off, as it was a good, quick and useful little tool.

When I tested the XFCE beta, I think I did install that. I spent ages looking at it and eventually did fstab by hand!