MX-18 beta 1 feedback

[dolphin_oracle]

Thanks Rose. I seem to recall somebody mentioning that same issue with MX17 in the past, but cannot find back that thread.
Later tonight i'll add some details about this particular system, although it seems rather standard to me.

It can happen. I haven't found a fix but a workaround is to run update-grub after install and first boot.

[Richard]

I think it is a quirk in update-grub.
Was told several years ago,
that if the first run fails, run again.
Some run it twice, just in case.

Never heard a reason why?
Perhaps a late change in permissions?

[baldyeti]

I am aware of the work-around, just concerned of the fit it might give a newbie to reboot to a startup menu that does not include the other OS.

No idea how often this occurs; perhaps the installer could run upgrade-grub a 2nd time (unconditionally would make it slower for everyone I guess, so perhaps if there is a bootable MS-type partition yet no "windows" entry in the 1st grub.cfg ?)

[dolphin_oracle]

We do runs update-grub, but there seem to be some key differences when running inside the chroot environment the installer sets up.

Not picking up windows is one. Another is not using uuids for the root partition designation on grub.cfg.

[chrispop99]

Is xscreensaver going to be available in the Package Installer for Final?
At the moment, if using MX-18 testrepo, it appears and installs from the PI, but neither of the extra screensavers install, failing with an 'Unable to locate package' error.

Chris

[baldyeti]

We do runs update-grub, but there seem to be some key differences when running inside the chroot environment the installer sets up.

Alright, i doubt indeed that re-running update-grub in the same (installer) environment would yield a different result. The fix probably comes from running it from the rebooted, non-chrooted system. I see this is covered in the fine manual (2.6.1 - No operating system found)

[manyroads]

Hello all... I believe the problem described in this thread may be an MX18 beta bug with the snapshot creation function:

viewtopic.php?f=92&t=47305

[darth.severus]

Hi, I need to decide what to install. Has it any disadvantages to install MX-17.1 instead waiting for MX-18. Since there is no new Debian.
Also, can someone who tested MX-18 beta as a new install please point out how the system encryption per installer is working now. Will boot be encrypted?

[dolphin_oracle]

Hi, I need to decide what to install. Has it any disadvantages to install MX-17.1 instead waiting for MX-18. Since there is no new Debian.
Also, can someone who tested MX-18 beta as a new install please point out how the system encryption per installer is working now. Will boot be encrypted?

boot is not encrypted. at this time we require an unencrypted boot partition.

[Adrian]

Hi, I need to decide what to install. Has it any disadvantages to install MX-17.1 instead waiting for MX-18. Since there is no new Debian.
Also, can someone who tested MX-18 beta as a new install please point out how the system encryption per installer is working now. Will boot be encrypted?

No problems, I do recommend updating at least the installer before you install to get the latest fixes (including the ability to install on encrypted partitions)
/boot will not be encrypted either with MX17 or MX18. In our view there's no security info available there and if somebody has access to your computer to change stuff on /boot then you have bigger problems than encryption. I've heard that GRUB should be able to boot from encrypted /boot, I could not make it work in my tests.