I hereby confess, that I’m not a big fan of the Manjaro-green theme, so I always switch to the Gnome default blue theme. This has been very inconsistent for a long time (since the introduction of the adwaita accent colors I guess). With this update, it seems that the issue has finally been fixed!
Thanks
Just some days before this update, I switched my more than year old install of Manjaro Plasma with Gnome: I removed (almost) all kde/plasma related packages and installed the list of packages taken from the minimal gnome iso; then cleaned my home from all plasma configurations. Before doing it I made a btrfs snapshot.
No big problems to make this big change.
Yesterday I updated my system without issues.
The only difference I notice on boot is that the grub holds for many more seconds before the system boots (I have the install-grub package installed).
Thanks Manjaro Team!
A post was split to a new topic: Issues with matcha-gtk-theme
Update process hung up on micro-manjaro package update. Next command stuck:
$ ps aux|grep micro
root 3024529 0.0 0.0 19524 10556 ? S 18:53 0:00 systemctl enable --now micro-keymap.service
I just run sudo kill -9 3024529 to continue. And disable it before reboot. Just for case.
Yeah, but unfortunately the developer doesn’t want to use AppStream to retrieve apps descriptions, screenshots and more.
So it already is outdated.
I don’t see the edit button anymore.
The general idea and design principles behind Secure Boot actually aren’t that bad and might’ve even improved overall security - it’s just that it wasn’t that well thought out and executed.
But that’s what always happens whenever M$ is heading some project, isn’t it? As an open standard with a community-driven committee, Secure Boot could’ve been a great addition.
Hello
i don’t care about the Grub vulnerabilities and don’t want to mess my dual boot on separate disks.
is the right procedure is to do the Pamac update and before rebooting to run update-grub ?
Do what I did:
install-grub script is installed…sudo install-grub
update-grub gets called regularly. It only updates the grub menu after kernel updates. No risk involved there.
OK, Deepseek helped me with install-grub.
In my case /dev/sda1 (which is mounted as /boot/efi) had wrong flags. I have added flags “boot” and “esp” in gparted.
After that $sudo install-grub finished with no issues.
Hello all!
Before I choose to do my update today I have a quick question regarding the grub update as the wording around the entire thing isn’t super clear to me and I’m getting a little bit confused.
Would I be correct in assuming that after I update and restart (maybe I shouldn’t restart?), I am free to manually install GRUB as per the wiki’s instructions to apply the security fixes? I have been meaning to do this anyways as I installed it to my Windows drive and I’d like to get it off of there and onto my Manjaro drive, and I would rather do it manually as I’m comfortable with that instead of using the script as it’s what I did at the end of 2023 during the grub update that was required then.
Thank you.
You have it correct.
Restarting or not restarting should, theoretically at least, make no difference.
do you dual boot?
Nah, man.
it seems to have worked,
no apparent issues and Grub looks the same as before with all the boot entries.
Thanks.
i had install-grub already installed in my system.
the update automatically run isntall-grub at the end and now it seems i lost my Windows boot entry (os-prober is installed and doesn’t find the windows installation).
EDIT: Windows and Linux are both installed using MBR (no EFI)
EDIT2 : Just fixed by manually adding the menu entry in /etc/grub.d/40_custom
However, os-prober still does not detect the windows partition/installation
I was getting this error when I tried running flutter commands for development:
unionfs failed
I was able to fix it by rebuilding the unionfs-fuse package from the AUR.
The grub update broke my system. After reboot, the system failed into the grub rescue shell after indicating grub_cli_set_auth_needed error.
To recover my system I had to boot from an USB and do a Timeshift restore.
This is because permissions were recently changed; you now need TL3 (Regular) or above to edit Wiki posts.
In the meantime, you can, of course, still suggest edits here.
I have this same issue on a laptop. This happens when you don’t have the Windows partition mounted when you do the grub update and it misses it. If you click on the NTFS partition and have it mounted in Dolphin, grub will see it and make a Win boot option in your menu.