Trying to report a manjaro issue on gitlab

Just tried to report my first issue on manjaro gitlab about the grub package, but my issue is classified as spam and i am told to change this text?!

Topic: grub 2.12rc1.r49.ge58b870ff-1 Manjaro stable branch

On manjaro Gitlab i am user: john Landmesser (JohnML)

The strange formatting is not from me but gitlab after spam warning

This settings in /etc/default/grub are not applied at boot:


Whole /etc/defaulr/grub

GRUB_CMDLINE_LINUX_DEFAULT="quiet udev.log_priority=3" 
GRUB_CMDLINE_LINUX=""If you want to enable the save default function, 
uncomment the followingline, and set GRUB_DEFAULT to 
saved.GRUB_SAVEDEFAULT=trueUncomment to disable submenus in boot 
menu#GRUB_DISABLE_SUBMENU=yPreload both GPT and MBR modules so that 
they are not missedGRUB_PRELOAD_MODULES="part_gpt part_msdos"Uncomment 
to enable booting from LUKS encrypted 
devices#GRUB_ENABLE_CRYPTODISK=yUncomment to use basic 
consoleGRUB_TERMINAL_INPUT=consoleUncomment to disable graphical 
terminal#GRUB_TERMINAL_OUTPUT=consoleThe resolution used on graphical 
terminalnote that you can use only modes which your graphic card 
supports via VBEyou can see them in real GRUB with the command 
'videoinfo'GRUB_GFXMODE=autoGRUB_GFXMODE=800x600Uncomment to allow the 
kernel use the same resolution used by 
grubGRUB_GFXPAYLOAD_LINUX=keepUncomment if you want GRUB to pass to the 
Linux kernel the old parameterformat "root=/dev/xxx" instead of 
"root=/dev/disk/by-uuid/xxx"#GRUB_DISABLE_LINUX_UUID=trueUncomment to 
disable generation of recovery mode menu 
entriesGRUB_DISABLE_RECOVERY=trueUncomment this option to enable 
os-prober execution in the grub-mkconfig 
commandGRUB_DISABLE_OS_PROBER=falseUncomment and set to the desired 
menu colors. Used by normal and wallpapermodes only. Entries specified 
as foreground/background.GRUB_COLOR_NORMAL="light-gray/black" 
GRUB_COLOR_HIGHLIGHT="green/black"Uncomment one of them for the gfx 
desired, a image background or a 
#GRUB_THEME="/path/to/gfxtheme"Uncomment to get a beep at GRUB 
start#GRUB_INIT_TUNE="480 440 1"Uncomment to ensure that the root 
filesystem is mounted read-only so thatsystemd-fsck can run the check 
automatically. We use 'fsck' by default, whichneeds 'rw' as boot 
parameter, to avoid delay in boot-time. 'fsck' needs to beremoved from 
'mkinitcpio.conf' to make 'systemd-fsck' work.See also Arch-Wiki: 

Perhaps it didn’t conform to their posting requirements. :person_shrugging:

What are you trying to achieve?
Are you sure it’s really a bug?

If ‘timeout_style’ (see timeout_style) is set to ‘countdown’ or ‘hidden’, the timeout is instead counted before the menu is displayed.

I think until ??? there was at the bottom of grub boot menu seconds count down and after that saved item has been started automatic. That automtic start has vanished and i miss that.

I have a laptop that uses my old PC display as primary screen and now i have to open the laptop lid to see whats going on and hit ENTER to reboot:

Ok, much noise about next to nothing!

So if I understand you correctly, you want to see the countdown at the same time as you see the menu?

I think I was playing around that a long time ago, but never got to actually get it working. (ie, I realized that is just a silly thing to spend time on, the countdown worked just fine for me in the background)

As you can see in the link above countdown is NOT what you are after then.

The part about you having to open the lid to see the menu I think has less to do with grub settings and more to do with your kernel, I think… Hopefully someone else can chim in on that part.