Issues should be resolved with grub 2:2.12.r260.gaae2ea619-1.
Chrome/Chromium-based browsers and GNOME 48 - Global Shortcuts
If you have extensions who use shortcuts installed on these browsers, you’ll face an issue of many dialogs opening when the browser starts, it’s quite annoying. The bug has been reported and fixed, but the commit is not yet on a stable release.
The workaround for now, is to disable the feature via --disable-features=GlobalShortcutsPortal
AUR (Arch User Repository) packages are neither supported by Arch nor Manjaro. Posts about them in Announcements topics are off-topic and will be flagged, moved or removed without warning.
For help with AUR packages, please create a new topic in AUR and a helpful volunteer may be able to assist you.
[2025-03-02T00:25:02+0100] [ALPM-SCRIPTLET] /etc/grub.d/10_linux: Zeile 164: Syntaxfehler beim unerwarteten Symbol »fi«
[2025-03-02T00:25:02+0100] [ALPM-SCRIPTLET] Warning: GRUB bootloader at /boot/efi/EFI/Manjaro was updated,
[2025-03-02T00:25:02+0100] [ALPM-SCRIPTLET] but it seems like you are not using it by default.
[2025-03-02T00:25:02+0100] [ALPM-SCRIPTLET] Please check your EFI boot priorities!
sudo update-grub generates no errors
(besides the normal /usr/bin/grub-probe: warning: unknown device type nvme0n1.
details
Generating grub configuration file ...
Found theme: /usr/share/grub/themes/manjaro/theme.txt
Found linux image: /boot/vmlinuz-6.13-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-6.13-x86_64.img
Found linux image: /boot/vmlinuz-6.12-x86_64
Found initrd image: /boot/amd-ucode.img /boot/initramfs-6.12-x86_64.img
Warning: os-prober will not be executed to detect other bootable partitions.
Systems on them will not be added to the GRUB boot configuration.
Check GRUB_DISABLE_OS_PROBER documentation entry.
Adding boot menu entry for UEFI Firmware Settings ...
Found memtest86+ EFI image: /boot/memtest86+/memtest.efi
/usr/bin/grub-probe: warning: unknown device type nvme0n1.
done
I don’t see where recordfail function is called to set it to 1 or 0. Seems like it is always 1 so it uses the defined 30 seconds timeout.
//EDIT:
OK I found something, GRUB_RECORDFAIL_TIMEOUT parameter is defined in grub-mkconfig as a user definable parameter. I added it to my /etc/default/grub config, generated the menu, and I now see the recorfail timeout in /boot/grub/grub.cfg is the one I set in /etc/default/grub for GRUB_RECORDFAIL_TIMEOUT
It doesn’t explain why recorfail equals 1 but it kinda fixes the issue for the ones needing a 1 second timeout for GRUB menu.