Head_on_a_Stick wrote:Isakku wrote:I had set a GRUB custom theme from Manjaro with a different background and all, now the theme is Debian's GRUB theme!
^ This would only happen if `grub-install` was run from Debian, no change in any file on the Debian system would cause GRUB to change if it had been installed from Manjaro and no update in Debian would cause GRUB to be installed to the hard drive (AFAIK), and even if there was there would be a dialogue asking you where to install the bootloader — did you see such a dialogue?
You can install and run the boot-info script if you want, that may clarify things.
https://packages.debian.org/stretch/boot-info-scripthttps://aur.archlinux.org/packages/bootinfoscript/
Well, of course grub-install had to run when I installed Debian the first time.
Well, digging the web I found this
https://askubuntu.com/questions/705063/ ... l-the-osesI would like to know how to prevent the installer from running grub-install (even the grub update command seems to do the same, since this happened after updating Debian)
If Debian didn't have another grub installed this would simply not happen.
Something simmilar happened to me when I tried installing Manjaro alongside Linux Mint in my Laptop.
https://forum.manjaro.org/t/some-crazy- ... etup/30552Every time I installed or updated something system related in one of the distros, the distro's GRUB was also automatically updated and that caused strange inconsistencies. In the end I had to start from scratch and I ended up installing Mint KDE alongside Mint Cinnamon. Since those are basically the same distro with a different desktop environment, there was no GRUB conflict (seems it's exaclty the same GRUB unlike when you mix completely different distros such as Manjaro and Mint)
Being exactly the same GRUB perhaps made it simply overwrite when I installed it instead of making another instance in the boot partition (EFI laptop).
But my current problem happens in a non UEFI system. it's older and I thought all the mess was caused by the UEFI boot system complexity messing up when you had different GRUBs. Seems I was wrong because now I do have a similar problem (two GRUBs) in a non UEFI system. GRUB doesn't get overrided nor overwritten. Except that instead of being shown at boot (UEFI system showed the two GRUBs) now it lies somewhere, dormant, and when I update a distro and that update updates any GRUB config in a certain way, sometimes it breaks the other distro! I was able to run some changes (such as theming it) without breaking anything, maybe because I was making the changes in the GRUB that had become the "default" because it was installed later (I installed Manjaro some time after installing Debian) But the Debian update appears to have updated Debian's GRUB, and now it became the "default" GRUB, breaking Manjaro's booting! Manjaro is still listed, but it doesn't boot, booting it crashes with that Kernel panic message I posted before.
