MX-17 Release Candidate 1 - Feedback

[Stevo]

Yes, the touch just fixes the nonexistent file problem, like testing for the existence first...but both a missing or an empty file are equally bad, since it's really essential the full contents of the file be there. Or it could just be a bad install or a bad spot on the hard drive, too.

[tascoast]

The SATA drive I use is around 12 months old and should be OK, but I'll have another go installing with a fresh download later today. The data partition (but not two other common partitions) being read-only/owned by root is good enough reason to begin anew. Please continue with the fine work and cheers meanwhile. )

[timkb4cq]

Eureka!
Grub Customizer changes that filename.
It sets up 10_linux_proxy and moves the original 10_linux to /etc/grub.d/backup/10_linux *and* to /etc/grub.d/proxifiedScripts/linux
I'm pretty sure it's the latter one that is used by 10_linux_proxy.
So I guess there needs to be a test to see if the user has used grub-customizer

[dolphin_oracle]

I was too quick I think but installed the *.deb above and had no errors in Synaptic with mx-tweak being updated.
Folder contents post update attached.

10_linux is the only file showing a creation date of today, however.

Have you used grub customizer by chance?

[tascoast]

I was too quick I think but installed the *.deb above and had no errors in Synaptic with mx-tweak being updated.
Folder contents post update attached.

10_linux is the only file showing a creation date of today, however.

Have you used grub customizer by chance?

Indeed I did. Apart from basic desktop personalisations, I routinely use Grub Customizer after an install. Greetings from my local library.

[sunrat]

I just installed RC1 and it completed smooth as silk. One minor error I noticed is default Conky shows free HD space after the word USED. Checked the config file and indeed it has fs_free where it should be fs_used

[asqwerth]

I was too quick I think but installed the *.deb above and had no errors in Synaptic with mx-tweak being updated.
Folder contents post update attached.

10_linux is the only file showing a creation date of today, however.

Have you used grub customizer by chance?

Indeed I did. Apart from basic desktop personalisations, I routinely use Grub Customizer after an install. Greetings from my local library.

I have always felt that repeated use of GC to modify menu entries, particularly when you have many distros on your system, will eventually lead to one's grub menu being messed up. I think I mentioned in this forum before that GC began to add extra os_prober entries in my /etc/grub.d folder, leading to a grub menu that was repeated 2 or 3 times whenever grub was updated/re-generated. I stopped using it maybe 2 years ago.

[Jerry3904]

I just installed RC1 and it completed smooth as silk. One minor error I noticed is default Conky shows free HD space after the word USED. Checked the config file and indeed it has fs_free where it should be fs_used

Oops, thanks. I switched at the end to simplify and forgot to change that.

[tascoast]

Take two for installing and all looks OK so far. I suspect the NZ repo might not be up-to-date yet, and switched to LA again.
/etc/grub.d/10_Linux is 12.4KB

[m_pav]

When the MX installer is told to use the whole drive for installation, it creates the partitions dependent on what type of Live-boot environment it running in, e.g., EFI boot or Legacy boot, and as a part of the process, it marks one partition as bootable and the rest is music to my ears.

The same is not true of an installation to custom or existing partitions, and in some rare cases, especially those where the user starts with a fully blank drive, the installation routine finishes but after rebooting, the computer BIOS fails to find an installed OS and requests some form of bootable device be inserted. This is what happens with one of my laptops and a similar thing was reported on our facebook page.

In such a situation, the solution is simple, reboot from Live-media, fire up gparted and on MBR formatted drives, set the boot flag on the partition used for root, or on GPT drives set the boot flag to the esp partition and reboot.

I believe it prudent to have this written up someplace, possibly our wiki or our troubleshooting section of the manual, and maybe even release notes because this is a complex issue that likely can not be addressed in this release cycle.