Then why did I get this sneak peek piece with “welcome to GRUB”, which was even out of place. It really looked like a bug. The screen was there, but I saw only a small and useless part of it.
If there was a true hidden value used, the GRUB wouldn’t show up and the black screen would be for a fraction of a second. For me, this bugged screen waited the normal 5 or 10 seconds to launch the system, just as I set it to do.
I don’t know if you had one and if you checked the difference between your grub and your eventual grub.pacnew.
For me this update was smooth, except the os-prober to reactivate.
But some former grub updates have already killed my grub, when I have had dual or triple Manjaro system.
Still cautious when I see a grub update.
Since I had no Grub there was no problem on my side. I use UEFI means to boot my Windows. Yes, that’s not as handy as it is when you have Grub + os-prober. But I don’t care and that’s the way I prefer things to be. I’ve already posted here a link to the mailing list where people discussed security issues related to Grub and I can’t blame them for taking actions against possible attacks.
Maybe the lack of all Grub options you are referring to is no more no less a silent Grub concept that was discussed here 2 years ago?
Anyway, I recommend everyone to consider using systemd-boot or rEFInd instead of Grub, because the latter is a prime target of hackers attacks due to its popularity and wide-spreadness so you surely will hear about new Grub vulnerabilities soon. If you’re really concerned, of course.
Thanks for the detailed announcment. I was wondering what happend with my bootloader.
This feels like it was a mistake. I am going to keep using Manjaro myself but now I’m going to refrain from recommending it to anyone that isn’t computer knowledgeable. Would be fun to get calls from friends/family members who dual boot with Windows about “hey why did Windows disappear”, would it not?
I think Manjaro is pretty user-friendly, all things considered, but I’m gonna remember this.
No, that couldn’t be further from the truth. Silent GRUB is OK, I tested it and on some computers I turned it on. It simply skips GRUB and go to boot immediately. In my case, the GRUB was there, waiting for the set time but covered. The only visible part was this Welcome to GRUB:
I wanted to take a picture but it was so tiny on the black screen that there was no focus and white stripe was a result.
Pretty sure this will effect any system with grub eventually as grub is not developed by manjaro team.
It’s only because manjaro is rolling release that it is seen here before other systems, meanwhile non rolling distros still have the unsecure grub.
Yes, I agree. Personally, I didn’t even know there were update announcements until today. And I definitely thought it was a bug when Windows got removed from grub.
Ah alright, I have confused it with another case then. Now it looks like a real issue to me.
I have checked it on OpenSUSE Tumbleweed, also rr.
Grub os-prober stays enabled if you had it this way before. The only thing that goes back to default is the theme.
Anyway, OpenSUSE has an easy graphical way to switch os-prober on and off (a checkbox in the bootloader config). Very convenient if you want to help out someone who’s not tech-savvy.
Interesting. Not surprised that it got the update as it is rr, nice to have a fancy gui tho.
You are correct that it is not the same as silent GRUB
I think changing the menu to hidden was unintended
But if /etc/default/grub was updated with the unintended change, it would also have the intended change to add the os-prober option
Just wanted to thank the devs for reenabling os-prober.
I got a funny error when this hook/script failed to find Grub cuz neither Grub nor os-prober were installed. 
No need to worry about GRUB security issues if there is no GRUB.
Yea, I stopped worrying and loved the bomb systemd-boot.
now you can worry about security on systemd
Thank you. Also many thanks to @openminded who gave a very simple and quick explanation of the meaning of all this.
About grub.pacnew files… I have read the wiki on System Maintenance, but I’m having trouble understanding. I have an original (I suppose old) grub file edited to my preferences. And everytime there was a grub update, I would get a grub.pacnew file, which I suppose was the updated version of grub. I have never attempted to merge or overwrite my original grub file with the grub.pacnew file before. Currently my system (dual-boot installation with Windows which I never use, only have it as a backup plan) runs with the original grub file and therefore the os-prober is enabled by default (and lots of other lines that exist in the .pacnew file are missing from the original grub file).
Can you please explain to me if I have to completely ovewrite the original file with the .pacnew and then re-edit in my preferences? What risks are involved in doing so (is there a risk of being unable to boot into manjaro) and what happens if I never handle the .pacnew file and let my old grub file as is? Is there a safe or recommended way of handling this?
EDIT: I found a topic that answers my questions aptly enough, for anyone else out there who is inexperienced about .pacnew file maintenance. Timeshift is up and running, copied the current grub file as a backup on a separate partition, doing a back-up of my personal data just in case (nobody can really afford to lose working hours) and then I am going to tackle the handling of grub.pacnew with DIFFPROG=meld pacdiff, while being aware about the latest changes in grub configuration (os-prober). I honestly had a lot of trouble trying to understand what I need to do and which command to use exactly, but things are getting clearer now.
I apologize if I went off on a tangent here.
It is enabled because it now defaults like before and Manjaro Settings automatically enable it for the user on update to keep the old behavior as there is no real reason to disable it on Manjaro, which requires secure boot to be disabled in the first place.
Globally your question has no definitive answer as every system is different, so you nned to look the difference between the new default file and your current one, and think about if you add the new default settings to your config file or not.
I don’t know whether it’s Ventoy or Grub update, but now it is finally not possible to boot Manjaro iso on a SecureBoot-enabled machine using Ventoy. Previously it was perfectly doable, which in fact was an indicator of a huge security flaw in Ventoy and/or Grub.
EDIT: Seems like a Grub thing: now it requires a kernel signed with some allowed certificate, and it prevents booting with no/wrong signature.