Grub wont open + Libarchive.so.13 deleted

Support
22

i just did it and it copied normally … so if you navigate via dolphin into your home folder its not there?

23

Ok, what happened is that it did get copied as /home/username in the usb and not in the partition where my manjaro is installed. What I had to do was cp from the usb device or while chrooting? Because I did it from the usb
I dont know if im clear but the file got copied in the usb as username in a directory named home that I just created

24

i just uploaded it from mine system:

so download it and put it into your installation: /usr/lib/

25

If you want to try copying the file then.

# exit chroot
exit

# mount the / partition
sudo mount /dev/sda1 /mnt/  # replace sda1 with the proper id

# copy
sudo cp /usr/lib/libarchive.so.13 /mnt/usr/lib/libarchive.so.13

# unmount
sudo umount /mnt

# chroot and update

Or

1 Like
26

Thank you both for your answers so far,
It seems Im heading towards the right direction!

I dit what dmt told me to do, and now Im getting when I pacman -Syu

:: Synchronizing package databases…
error: failed to synchronize all databases (unable to lock database)

27

rm /var/lib/pacman/db.lck
update again

28

Seems to work, until the end of the update where I get this long message.

(247/247) checking for file conflicts [#####################################################] 100%
error: failed to commit transaction (conflicting files)
jre8-openjdk-headless: /usr/lib/jvm/java-8-openjdk/jre/bin/java exists in filesystem
LOOOOTS OF LINES SIMILAR TO THIS
vulkan-radeon: /usr/share/drirc.d/00-radv-defaults.conf exists in filesystem
Errors occurred, no packages were upgraded.

29

run this:
pacman -Syyu --overwrite '*'

30

It did work but when I try to boot from manjaro I my pc stays frozen in the symbol ASUS

31

so chroot again and post logs:
journalctl --boot=-1 --priority=3 --no-pager

32

Jun 06 21:54:47 omar-fx503vd systemd[184]: /usr/lib/systemd/system-environment-generators/60-flatpak-system-only terminated by signal BUS.
Jun 06 21:54:47 omar-fx503vd systemd[189]: /usr/lib/systemd/system-generators/ostree-system-generator terminated by signal BUS.

33

did you chrooted again and are those all logs?

34

yeah, I did and those are all the logs (I turned off the computer after trying to boot again after the update)

35

and output from this:
journalctl --boot=-0 --priority=3 --no-pager

36

– No entries –

37

and this:
journalctl --boot=-1 --priority=5 --no-pager

38

Jun 06 21:54:47 omar-fx503vd kernel: Linux version 5.10.117-1-MANJARO (builduser@fv-az208-243) (gcc (GCC) 12.1.0, GNU ld (GNU Binutils) 2.38) #1 SMP PREEMPT Wed May 18 09:22:50 UTC 2022
Jun 06 21:54:47 omar-fx503vd kernel: Kernel command line: BOOT_IMAGE=/boot/vmlinuz-5.10-x86_64 root=UUID=173c4f10-a14c-4dd0-837e-09a7e22b786a rw quiet apparmor=1 security=apparmor udev.log_priority=3
Jun 06 21:54:47 omar-fx503vd kernel: random: get_random_u64 called from __kmem_cache_create+0x2a/0x4c0 with crng_init=0
Jun 06 21:54:47 omar-fx503vd kernel: audit: type=2000 audit(1654545281.006:1): state=initialized audit_enabled=0 res=1
Jun 06 21:54:47 omar-fx503vd kernel: ENERGY_PERF_BIAS: Set to ‘normal’, was ‘performance’
Jun 06 21:54:47 omar-fx503vd kernel: SCSI subsystem initialized
Jun 06 21:54:47 omar-fx503vd kernel: VFS: Disk quotas dquot_6.6.0
Jun 06 21:54:47 omar-fx503vd kernel: Initialise system trusted keyrings
Jun 06 21:54:47 omar-fx503vd kernel: Key type blacklist registered
Jun 06 21:54:47 omar-fx503vd kernel: Key type asymmetric registered
Jun 06 21:54:47 omar-fx503vd kernel: Asymmetric key parser ‘x509’ registered
Jun 06 21:54:47 omar-fx503vd kernel: ACPI: Invalid active0 threshold
Jun 06 21:54:47 omar-fx503vd kernel: hpet_acpi_add: no address or irqs in _CRS
Jun 06 21:54:47 omar-fx503vd kernel: resource sanity check: requesting [mem 0xfdffe800-0xfe0007ff], which spans more than pnp 00:05 [mem 0xfdb00000-0xfdffffff]
Jun 06 21:54:47 omar-fx503vd kernel: caller pmc_core_probe+0x7c/0x400 mapping multiple BARs
Jun 06 21:54:47 omar-fx503vd kernel: Loading compiled-in X.509 certificates
Jun 06 21:54:47 omar-fx503vd kernel: Loaded X.509 cert ‘Build time autogenerated kernel key: 737a7cd83283775bb9fa33241bcf5eab55c6abb8’
Jun 06 21:54:47 omar-fx503vd kernel: Key type ._fscrypt registered
Jun 06 21:54:47 omar-fx503vd kernel: Key type .fscrypt registered
Jun 06 21:54:47 omar-fx503vd kernel: Key type fscrypt-provisioning registered
Jun 06 21:54:47 omar-fx503vd kernel: scsi 2:0:0:0: Direct-Access ATA ST1000LX015-1U71 SDM1 PQ: 0 ANSI: 5
Jun 06 21:54:47 omar-fx503vd kernel: sd 2:0:0:0: [sda] 1953525168 512-byte logical blocks: (1.00 TB/932 GiB)
Jun 06 21:54:47 omar-fx503vd kernel: sd 2:0:0:0: [sda] 4096-byte physical blocks
Jun 06 21:54:47 omar-fx503vd kernel: sd 2:0:0:0: [sda] Write Protect is off
Jun 06 21:54:47 omar-fx503vd kernel: sd 2:0:0:0: [sda] Write cache: enabled, read cache: enabled, doesn’t support DPO or FUA
Jun 06 21:54:47 omar-fx503vd kernel: sd 2:0:0:0: [sda] Attached SCSI disk
Jun 06 21:54:47 omar-fx503vd kernel: usb: port power management may be unreliable
Jun 06 21:54:47 omar-fx503vd kernel: random: fast init done
Jun 06 21:54:47 omar-fx503vd systemd[184]: /usr/lib/systemd/system-environment-generators/60-flatpak-system-only terminated by signal BUS.
Jun 06 21:54:47 omar-fx503vd systemd[189]: /usr/lib/systemd/system-generators/ostree-system-generator terminated by signal BUS.
Jun 06 21:54:47 omar-fx503vd kernel: audit: type=1130 audit(1654545287.247:2): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg=‘unit=modprobe@fuse comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
Jun 06 21:54:47 omar-fx503vd kernel: audit: type=1131 audit(1654545287.247:3): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg=‘unit=modprobe@fuse comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’
Jun 06 21:54:47 omar-fx503vd systemd-random-seed[224]: Kernel entropy pool is not initialized yet, waiting until it is.
Jun 06 21:54:47 omar-fx503vd kernel: audit: type=1130 audit(1654545287.281:4): pid=1 uid=0 auid=4294967295 ses=4294967295 subj==unconfined msg=‘unit=systemd-journald comm=“systemd” exe="/usr/lib/systemd/systemd" hostname=? addr=? terminal=? res=success’

39

and post output from:
mhwd-kernel -li

40

Currently running: 5.15.16-1-MANJARO (linux515)
The following kernels are installed in your system:
error: could not open file /var/lib/pacman/local/konversation-22.04.1-1/desc: No such file or directory

  • linux510
  • linux54
    error: could not open file /var/lib/pacman/local/konversation-22.04.1-1/desc: No such file or directory
41

so lets first fix the error:
touch /var/lib/pacman/local/konversation-22.04.1-1/desc
pacman -S konversation
and check with:
pacman -Syu