I’m getting what I think is the the Manjaro GUI GRUB menu before and after Plymouth splashscreen animation during boot up…
How do I get rid of it? (And it goes away when sddm loads up)
The “second splash screen” is actually just held in the frame buffer for that TTY during boot, as far as I am aware. That’s why you get to see it again during the switch to the GUI login (or, if set to auto-login, your DE loading). People have reported seeing it on shutdown, as well.
However, do you really need Plymouth etc. …? — I’d suggest booting and selecting “GRUB cmdline” as a (non-persistent) test, removing quiet and splash from that command line, then booting from there. Does it still appear then?
… Also, I think this question deserves its own Topic. 
1 Like
I had to restore to a Timeshift snapshot yesterday due to a problem with updates ( Error during update, and Keyboard being weird )
Since then a GUI menu of manjaro appears before and after Plymouth splashscreen…
It is similar to this : Having updated, GRUB menu now appears at boot with a five second timer and duplicate entries
But the person didn’t use Timeshift, and no solution is in that topic.
Can I get rid of this menu?
Also it seems like inputting doesn’t do anything on it, so it’s just a image that persists after timer reaches 0… until SDDM login screen is rendered
Pressing arrow keys or C didn’t do anything.
Yes I thought the same at first, but decided to post here as there is more context
Here : Manjaro GRUB GUI menu appears during boot after using Timeshift
I’d keep it, I don’t see any issues with it, and I have a custom theme for it as well (which is just a duplicate of manjaro Plymouth theme with changed name and stuff in files and replaced manjaro logo with custom full screen image)
Mod edit: Consecutive posts merged to tidy-up.
1 Like
The “after” is probably just a ghost image in the video framebuffer. Test it with the arrows, the selected item will probably not move. In this case, nothing you can do as far as i know.
Yes the after is exactly that. But I don’t wanna see the grub GUI menu in the first place…
It also appears sometimes during shutdown if I shutdown from SDDM login screen without logging in, if I shutdown from logged in session, then it doesn’t appear.
I’ve merged in the remaining relevant posts from the other thread, for continuity.
I tried GRUB_TIMEOUT=0
And followed by grub sudo update-grub
And it still appears with 5 sec timer…
Seems like it’s fully functional at start for 5 sec..
then it disappears after timeout, and then for split sec it flashes before plymouth splashscreen, then reappears after plymouth animation
As mentioned, it’s just an “artifact” of the system switching between TTYs and (briefly) showing the non-updated GRUB display from the other.
It’s not a fault (or really, a bug, in any sense).
Timeshift might be doing something in the background which holds the TTY/display switching up for a bit longer than “usual”, so you get to notice it, but as I don’t have any real knowledge of how Timeshift works, can’t say for sure.
Update : Half Solution (Enough for me)
Because of unfamiliarity to this menu, I did not realise that the entries were duplicated for Manjaro… (Had to ask gemini for context…)
The Half Solution:
Wiping the existing environment and recreation new
sudo grub-editenv /boot/grub/grubenv create
Adding overrides to config:
GRUB_RECORDFAIL_TIMEOUT=0 GRUB_DISABLE_OS_PROBER=true
(I do not have dual boot so it’s fine to disable prober, I think…)
sudo update-grub
I can still get into the grub menu by shift during boot.
This is partial solution because it doesn’t fix anything with framebuffer. Or as @BG405 said it’s not a bug anyways… As now the framebuffer is taking a black screen.
In past I have seen the last frame of Plymouth Splashscreen being taken as the said framebuffer cache…
I think it created a second entry of manjaro in grub, that’s probably what it was…
Also I have diabled prober now so idk if the entry is wiped by env change or it just not fetching it up…
If anyone uses Limine, I’d be curious if this happens with it as well.
This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.