[Unstable Update] March 2025

Announcements Unstable Updates
,
1

Welcome to the new monthly unstable branch thread.

Recent News

Notable Package Changes

Known Issues

There are known issues with grub / os-prober

Stay tuned…

Additional Info

Info about AUR packages

:warning: 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.

Get our latest daily developer images now from Github: Plasma, GNOME, XFCE. You can get the latest stable releases of Manjaro from CDN77.

Check if your mirror has already synced:

2 Likes
2

after grub update from 2:2.12.r226.g56ccc5ed-1 to 2:2.12.r226.g56ccc5ed-2

and sudo update-grub i got

The grub configuration file is generated ...
Theme found: /usr/share/grub/themes/stylish-color-1080p/theme.txt
/etc/grub. d/10_linux: string 164: syntax error next to unexpected «fi» token

returning to 2:2.12.r226.g56ccc5ed-1 fixes this

I don’t know what you tried to fix in the previous discussion, temporarily back to arch version.

1 Like
3

I just came here to report this.

4

same here

[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!

grub is updated and work

5

Can the 10_linux file been posted to pastebin or so for analysis?

6
7

Line 158 needs to go.
At least in my case that seems to result in stable and expected outcomes.

diff 
index 6bb8b12..9ab8a14 100644
--- a/10_linuxUF
+++ b/10_linuxUN
@@ -155,7 +155,6 @@ linux_entry ()
   fi
 
   message="$(gettext_printf "Loading Linux %s ..." "${version}")"
-  sed "s/^/$submenu_indentation/" << EOF
   if [ x"$quiet_boot" = x0 ] || [ x"$type" != xsimple ]; then
     message="$(gettext_printf "Loading Linux %s ..." ${version})"
     sed "s/^/$submenu_indentation/" << EOF
8

Should be fixed with: [pkg-upd] 2:2.12.r226.g56ccc5ed-3 (ac3bc2b2) · Commits · Packages / core / grub · GitLab

5 Likes
9

Whoops. :grimacing:

Thanks @philm!

10

Seems all good. :+1:

1 Like
11

dont forget to update pacman pkgfile

12

But now timeout is set to 30s because of recordfail?

13

Now I get the following message when trying to start OS:

error:sparse file not allowed.

What changes are you trying to make compared to the original grub package?

upd: find GRUB error: sparse file not allowed - #6 by linux-aarhus

don’t pay attention.

14

A post was merged into an existing topic: Tracking nvidia 570 drivers status

15

Grub ignore

GRUB_TIMEOUT=5

i have 30s

2 Likes
16

Same here, set to 5 seconds, counts 30 seconds.

GRUB_TIMEOUT=5
GRUB_TIMEOUT_STYLE=menu

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

grub 2:2.12.r226.g56ccc5ed-3

17

look into /etc/default/00_header and search for 30
Riese: ==> recordfail is not managed at time?

18

The updated Ubuntu patches added record fail. We can see what happens when we remove those. @Yochanan

19

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.

1 Like
20

DOC:
https://docs.hetzner.com/robot/dedicated-server/operating-systems/deactivate-grub2-recordfail/