You are not logged in.

#1 2025-05-02 13:19:49

KyleDaCow
Member
Registered: 2025-04-24
Posts: 7

[SOLVED] System unable to boot after changing icon pack

Hello, my friend had an issue with an icon pack when launching virt-manager, so he wanted to change it. Here was the problem:
(virt-manager:28938): Gtk-WARNING **: 09:11:35.429: Theme directory 16/16 of theme Infinity has no size field

So, he edited the GTK 3 config file: (nano ~/.config/gtk-3.0/settings.ini)
and changed:
[Settings]
gtk-icon-theme-name = Adwaita

Now, when he booted, systemd gave him the option to only boot into firmware interface, the arch boot entry had disappeared, and we were both confused.

So, what we tried doing, we booted into the archiso from a usb, and chroot into his system, and checked if there was anything in /boot/efi/loader/entries , there was nothing. so we created /boot/efi/loader/entries/arch.conf, with this content:
title   Arch Linux
linux   /vmlinuz-linux
initrd  /initramfs-linux.img
options root=PARTUUID=d8583c29-0114-485a-a95e-21c4996013fb rw
EOF

And saved it, when he booted, he saw Arch Linux as an entry, but when he tried booting, it gave this error in red for 3 seconds and shutdown: ../systemd/src/boot/boot.c:2556@image_start: Error preparing initrd: Not found

So, we chrooted back into the system via the usb, and reinstalled the kernel "pacman -Syu linux linux-zen" and when it was done, we ran "mkinitcpio -P", then we exited chroot and rebooted into the main system, we chose the Arch Linux entry, and got the same error (../systemd/src/boot/boot.c:2556@image_start: Error preparing initrd: Not found)

So now im not even sure what to do.

Last edited by KyleDaCow (2025-05-07 18:07:21)

Offline

#2 2025-05-07 05:32:20

Kadenistoopog
Member
Registered: 2025-05-05
Posts: 1

Re: [SOLVED] System unable to boot after changing icon pack

Im that friend and this issue has been Solved

Offline

#3 2025-05-07 18:09:03

KyleDaCow
Member
Registered: 2025-04-24
Posts: 7

Re: [SOLVED] System unable to boot after changing icon pack

We basically chrooted again, reinstalled the kernel and systemd, and we manually configed and edited some of the files related to the kernel and systemd, then it started working, there is no clear answer, but after tinkering, the problem has been solved.

Offline

Board footer

Powered by FluxBB