A post was split to a new topic: Systems hangs after update on Plymouth boot screen
hello @Joshua-17
please open a thread for this issue. i suspect the following problem:
the broken update is using the new grub-version while your chroot-image is using the previous one. that’s my suggestion why chrooting troubles.
Good point. 
Will create a thread and also a usb stick with an updated iso image and retry the chroot process
Cinnamon edition took error.
(2/4) Compiling GSettings XML schema files...
オーバーライドファイル“/usr/share/glib-2.0/schemas/99_manjaro-cinnamon.gschema.override”で指定されたスキーマ“org.nemo.preferences”のキー“bulk-rename-tool”の解析中にエラーが発生しました: 0-10:can not parse as value of type 'ay': このキーのオーバーライドを無視します。
I already moved your post to Support - Manjaro Linux Forum. Updated 23.1.1 ISOs are expected later today, as we are currently testing those.
1 Like
What about system that’s not EFI?
Then you will know how you installed the system - and subsequently know which command to use.
As non efi systems is unpredicable it is not possible to provide explicit guidance as you need to know which device you installed grub onto in the first place - and if you used BIOS/GPT - in which case it is not a device but a partition
Another great update. “It’s a Festivus miracle!”
1 Like
Just for clarification, when the wiki about reinstalling grub says “You need to be in chroot for this procedure”, I’m assuming this is just needed if rescuing a system rather than when booted into it as normal?
That is correct.
3 Likes
Thanks.
1 Like
Hello everyone,
after the update Grub still shows the version 2.06-4 (on reboot), although it should be 2.12. Is this correct?
Best regards
Check if your primary mirror is up-to-date.
pacman-mirrors --status
On unstable branch the grub version is
$ pamac info grub
Name : grub
Version : 2.12-3
Description : GNU GRand Unified Bootloader (2)
URL : https://www.gnu.org/software/grub/
Licenses : GPL-3.0-or-later
Repository : core
Installed Size : 50,2 MB
Groups : --
Depends On : sh xz gettext device-mapper
Optional Dependencies : freetype2: For grub-mkfont usage [Installed]
fuse3: For grub-mount usage [Installed]
dosfstools: For grub-mkrescue FAT FS and EFI support [Installed]
lzop: For grub-mkrescue LZO support
efibootmgr: For grub-install EFI support [Installed]
libisoburn: Provides xorriso for generating grub rescue iso using grub-mkrescue [Installed]
os-prober: To detect other OSes when generating grub.cfg in BIOS systems [Installed]
mtools: For grub-mkrescue FAT FS support
update-grub: Script to update Grub Menu on Linux Kernel updates [Installed]
libusb: For grub-emu USB support [Installed]
sdl: For grub-emu SDL support [Installed]
Required By : grub-btrfs grub-theme-manjaro
manjaro-tools-iso-git update-grub
Optional For : --
Provides : grub-common grub-bios grub-emu grub-efi-x86_64
Replaces : grub-common grub-bios grub-emu grub-efi-x86_64
Conflicts With : grub-common grub-bios grub-emu grub-efi-x86_64
grub-legacy
Packager : Mark Wagie <mark@manjaro.org>
Build Date : fre 22 dec 2023 15:12:41 CET
Install Date : lør 23 dec 2023 07:30:33 CET
Install Reason : Explicitly installed
Validated By : Signature
Backup files : /etc/default/grub /etc/grub.d/40_custom
/boot/grub/grub.cfg
Hello linux-aarhus,
the version 2.12 is installed:
[snydar@snydar-manjaro ~]$ pacman-mirrors --status
Local mirror status for stable branch
Mirror #1 OK 00:11 Germany https://ftp.gwdg.de/pub/linux/manjaro/
Mirror #2 OK 00:11 Germany https://mirror.alpix.eu/manjaro/
[snydar@snydar-manjaro ~]$ pamac info grub
Name : grub
Version : 2.12-3
Beschreibung : GNU GRand Unified Bootloader (2)
URL : https://www.gnu.org/software/grub/
Lizenzen : GPL-3.0-or-later
Paketquelle : core
Installierte Größe : 50,2 MB
Gruppen : --
Hängt ab von : sh xz gettext device-mapper
Optionale Abhängigkeiten : freetype2: For grub-mkfont usage [Installiert]
fuse3: For grub-mount usage [Installiert]
dosfstools: For grub-mkrescue FAT FS and EFI support [Installiert]
lzop: For grub-mkrescue LZO support
efibootmgr: For grub-install EFI support [Installiert]
libisoburn: Provides xorriso for generating grub rescue iso using grub-mkrescue
os-prober: To detect other OSes when generating grub.cfg in BIOS systems [Installiert]
mtools: For grub-mkrescue FAT FS support [Installiert]
update-grub: Script to update Grub Menu on Linux Kernel updates [Installiert]
libusb: For grub-emu USB support [Installiert]
sdl: For grub-emu SDL support [Installiert]
Benötigt von : update-grub
Optional für : --
Stellt bereit : grub-common grub-bios grub-emu grub-efi-x86_64
Ersetzt : grub-common grub-bios grub-emu grub-efi-x86_64
Konflikt mit : grub-common grub-bios grub-emu grub-efi-x86_64
grub-legacy
Packer : Mark Wagie <mark@manjaro.org>
Erstelldatum : Fr 22 Dez 2023 15:12:41 CET
Installiert am : Sa 23 Dez 2023 11:25:03 CET
Installationsgrund : Ausdrücklich installiert
Validiert von : Signature
Dateisicherungen : /etc/default/grub /etc/grub.d/40_custom
/boot/grub/grub.cfg
But it still shows version 2.06-4 on reboot.
Sorry if I bother someone here with my question, but I need to have a confirmation on this before to make this upgrade. Regarding grub, those magic lines after upgrade and before reboot are this?
Thank you in advance.
sudo grub-install --efi-directory=/boot --no-nvram
sudo grub-mkconfig -o /boot/grub/grub.cfg
Or this one are more complete?
sudo grub-install --target=x86_64-efi --efi-directory=/boot/efi --bootloader-id=manjaro --recheck
sudo grub-mkconfig -o /boot/grub/grub.cfg
I have put sudo before because I don’t understand how to go in chroot after upgrade and before reboot and don’t use a live USB. Or I must do in console su and after that those command without sudo. Can someone tell me what is the correct procedure ?
2 Likes
Hello
so according to the announcement,i install this update(Pamac GUI for my part),and then in a terminal grub-install and then restart?
and what about sudo update grub ?
1 Like
On my other test bench, I’ve updated without using grub install.
Everything seems to work though, since it already detected and rebuild booting images.
1 Like
The package rog-control-center from the stable extra repo contains conflicting/duplicate files from asusctl (dependency for rog-control-center).
Conflicting:
/usr/bin/rog-control-center exists in both asusctl and rog-control-center
/usr/share/applications/rog-control-center.desktop exists in both asusctl and rog-control-center
/usr/share/icons/hicolor/512x512/apps/rog-control-center.png exists in both asusctl and rog-control-center
/usr/share/rog-gui/layouts/fa506i_US.ron exists in both asusctl and rog-control-center
/usr/share/rog-gui/layouts/fa507_US.ron exists in both asusctl and rog-control-center
/usr/share/rog-gui/layouts/fx505d_US.ron exists in both asusctl and rog-control-center
/usr/share/rog-gui/layouts/g512_US.ron exists in both asusctl and rog-control-center
/usr/share/rog-gui/layouts/g513i-per-key_US.ron exists in both asusctl and rog-control-center
/usr/share/rog-gui/layouts/g513i_US.ron exists in both asusctl and rog-control-center
/usr/share/rog-gui/layouts/g533q-per-key_US.ron exists in both asusctl and rog-control-center
/usr/share/rog-gui/layouts/g533q_US.ron exists in both asusctl and rog-control-center
/usr/share/rog-gui/layouts/g634j-per-key_US.ron exists in both asusctl and rog-control-center
/usr/share/rog-gui/layouts/g733pz-per-key_US.ron exists in both asusctl and rog-control-center
/usr/share/rog-gui/layouts/g814ji-per-key_US.ron exists in both asusctl and rog-control-center
/usr/share/rog-gui/layouts/ga401q_US.ron exists in both asusctl and rog-control-center
/usr/share/rog-gui/layouts/gl503_US.ron exists in both asusctl and rog-control-center
/usr/share/rog-gui/layouts/gx502_US.ron exists in both asusctl and rog-control-center
/usr/share/rog-gui/layouts/gx531-per-key_US.ron exists in both asusctl and rog-control-center
Current workaround: Build rog-control-center and asusctl from AUR and ignore suggested update/change to the packaged versions from stable extra repo for now. Currently both repos contain the same version afaik.
Still, thanks for the update and cheers!