Failed update killed the system - I tried all I could find

I tried updating the system with pamac gui as I always do, the gui crashed, I waited some time, in system monitor I had no activity like downloads or any process called pacman o pamac so I rebooted (my mistake).
At boot it says it can’t find the kernel (I had 2 installed, the second didn’t work either) so I downloaded the new iso, burned it, booted and did
manjaro-chroot -a
[ -f /var/lib/pacman/db.lck ] && rm -f /var/lib/pacman/db.lck
pacman-mirrors -f && pacman -Syyu
update-grub
exit

it said there was nothing to do, grub updated and deleted the windows entry too now showing only enter uefi settings.

Booted again live and tried again but failing.
I tried to download a new kernel with
mhwd-kernel -i linux61
and it said it could not open file var/lib/pacman/local/wine-staging-9.22-1/desc
so I told it to --ignore and it didn’t work so I deleted the dir and tried again but it didn’t work, it only wants to update v86d (don’t know what it is) from aur but it can’t (no systemd as init error).
So now I’m on my laptop, I’m booted live on the other pc but I don’t know what to do or what to search to fix this.

Any suggestiong?
TiA

You may find some tipps in:

:footprints:

Additionally you may need to test with

 ls -lA /boot       

what is missing.
And with

LANG=en; sudo mhwd-kernel -li

what kernels are meant to be there

Then install one additional kernel (one that you did not have before)

LANG=en;sudo mhwd-kernel -i linux612

and

LANG=en;sudo mhwd-kernel -i linux611
1 Like

that is exacly what I did to recover the system but without success, it says there is nothing to do.

this is the output of

ls -lA /boot
amd -ucode.img
efi
grub
linux510-x86_64.kver.old
linux611-x86_64.kver
linux66-x86_64.kver
memtest86+

Mod edit: Please use proper formatting: [HowTo] Post command output and file content as formatted text

If
mhwd-kernel -i linuxXYZ
does not work for you in chroot
then install a kernel the other way:

for example:
pacman -S linux66
mkinitcpio -P
update-grub

exit
to exit chroot, then reboot to test

But you can already see from the output of the above commands whether you now again have a kernel and initrd.

3 Likes

Ok, I’m following the instructions. I downloaded a kernel using pacman because mhwd didn’t work.
Now I’m waiting for the system to reboot, I exited chroot, closed the prompt, and clicked reboot but it went black screen with mouse cursor…I’m giving it some time…

It booted to manjaro
Now I don’t have the boot entry for windows (not that I use it but I have it installed)
I can’t start pamac, it gives error

remote peer disconnected

good

run update-grub again
Windows wasn’t detected from within chroot - totally normal.

I have no suggestion but to use pacman instead.
Someone else might know.

I thank you a lot for helping me good sir.

I’ll start searching the forum for this other issue.

See this thread:

pacman-mirrors --continent && sudo pacman -Syu

It says there are no updates available (I’m translating) so nothing changes, I have the same output from

pacaman -Syyu

If you ever need to post output in english so other people could understand it
and don’t want to have to translate it yourself:
prepend LANG=C

ex:
LANG=C sudo pacman -Syu

If I try to launch pamac from command line using

pamac-manager

I get this error:

(pamac-manager:14783): Gtk-WARNING **: 13:26:16.610: Could not load a pixbuf from icon theme.
This may indicate that pixbuf loaders or the mime database could not be found.
**
Gtk:ERROR:../gtk/gtk/gtkiconhelper.c:495:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /usr/share/icons/breeze-dark/status/16/image-missing.svg: Impossibile aprire il modulo «/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbuf
loader-svg.so» per il caricamento delle immagini: /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so: impossibile aprire il file oggetto condiviso: File o directory non esistente (gdk-pixbuf-error-quark, 5)
Bail out! Gtk:ERROR:../gtk/gtk/gtkiconhelper.c:495:ensure_surface_for_gicon: assertion failed (error == NULL): Failed to load /usr/share/icons/breeze-dark/status/16/image-missing.svg: Impossibile aprire il modulo «/usr/lib/gdk-pixbuf-2.0/2.10.0/loaders
/libpixbufloader-svg.so» per il caricamento delle immagini: /usr/lib/gdk-pixbuf-2.0/2.10.0/loaders/libpixbufloader-svg.so: impossibile aprire il file oggetto condiviso: File o directory non esistente (gdk-pixbuf-error-quark, 5)
Annullato

I am trying to use LANG=C but maybe it works only for 1 line?

That’s incorrect. Accordding to me notes it should be LC_ALL=C.

For example:

LC_ALL=C bluetoothctl
1 Like

I reinstalled pamac using

sudo pacman -Syu libpamac pamac-cli pamac-gtk

and now it starts, icons are missing, if I start it from prompt using

pamac-manager

I get

(pamac-manager:36593): Adwaita-WARNING **: 13:41:28.649: Using GtkSettings:gtk-application-prefer-dark-theme with libadwaita is unsupported. Please use AdwStyleManager:color-scheme instead.

And then a bunch of error for every single icon the app uses.

I think I should stop posting in this topic since the original issue was resolved.
I’m currently trying to figure out how to reinstall the latest updates, maybe reinstalling everything that is reported to have been updated today already.

So ty gyus for helping me recovering the system.

Try reinstalling librsvg.
That seems to help -
what I understood:
the file name changed from
libpixbufloader-svg.so
to
libpixbufloader_svg.so
and some cache update wasn’t triggered
which the reinstallation will do.

sudo pacman -S --asdeps librsvg

I didn’t have problems - others had …

I did that end then

sudo gtk-update-icon-cache /usr/share/icons/*

logged out and back in, now I have he icons.
Also I found the pacman log, it has the list of everything it thinks it has updated, so I will try and update/reinstall everything manually. I started with wine, suddenly it used all my ram (16gb) and all the swap file I had just in case (8gb) and the pc froze for a few minutes, then it freed the memory and started working again, so I’ll go slow.

Also I got suggested to check this, so I’ll do that.

2 Likes

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.