For the third time: reinstall kernels you have and you won’t have to run any of these two commands.
For the rest, you’ll see how it goes or where you’ll get stuck. Post output of commands you run.
If you have working internet in chroot you can run commands with
<command> |& tee >(curl -F 'f:1=<-' ix.io)
and you’ll get link to a paste service so you can easily copy and paste output here.
the actual name of the command is similar, but yours is incorrect
it is:
update-grub
I’m sorry, I did not post back during last 11 days.
After rebooting some times with error explained above my PC suddenly refused to boot.
It could not get to POST, just BIOS splash screen, no access to BIOS configuration.
I finally discovered that it was related to a HDD, I used for backup. When I disconnected it from the motherboard, the computer let me enter BIOS and I manage to boot from live USB.
I did as you recommended above, chroot, upgraded system, this included in the package list openssl and also upgrade of installed kernels.
It also auto magically executed mkinitcpio and update-grub.
No errors shown that I can paste here.
But again, when I boot the system, the same ‘error while loading shared libraries: libcrypto.so.3’ error as above.
When I try to upgrede the system, it reports nothing to upgrade.
When I browse from live Manjaro to my PC installation, I can see in /usr the link to lib64, and in /usr/lib64 I can see libcrypto.so.3
It is owned by root.
What else can I do?
First error is actually regarding kmod - which is not included in any recent update.
Since you mentioned the link to /usr/lib64:
This:
ls -al /usr
should look like this:
ls -al /usr
insgesamt 344
drwxr-xr-x 9 root root 4096 25. Dez 12:00 .
drwxr-xr-x 18 root root 4096 6. Nov 11:12 ..
drwxr-xr-x 6 root root 122880 25. Dez 12:00 bin
drwxr-xr-x 496 root root 36864 25. Dez 11:56 include
drwxr-xr-x 203 root root 155648 25. Dez 11:56 lib
drwxr-xr-x 8 root root 4096 17. Dez 08:46 lib32
lrwxrwxrwx 1 root root 3 18. Okt 23:01 lib64 -> lib
drwxr-xr-x 11 root root 4096 28. Aug 22:55 local
lrwxrwxrwx 1 root root 3 18. Okt 23:01 sbin -> bin
drwxr-xr-x 226 root root 4096 25. Dez 11:56 share
drwxr-xr-x 2 root root 4096 24. Dez 07:19 src
Also this:
ls -al /usr/lib/libcrypto*
should look like this:
ls -al /usr/lib/libcrypto*
lrwxrwxrwx 1 root root 14 14. Dez 18:22 /usr/lib/libcrypto.so -> libcrypto.so.3
-rwxr-xr-x 1 root root 4484080 14. Dez 18:22 /usr/lib/libcrypto.so.3
If it does not, there is something seriously messed up!
At this point I’d chroot again,
check the output of the commands above
(to be clear: from within chroot, we are not interested in doing anything while not in chroot)
remove the three following packages from the pacman cache,
to make sure they are freshly downloaded, to make sure that no already existing package is used:
rm /var/cache/pacman/pkg/kmod*
rm /var/cache/pacman/pkg/openssl*
rm /var/cache/pacman/pkg/systemd*
reinstall kmod
reinstall systemd
reinstall openssl
pacman -Syu kmod systemd openssl
run:
mkinitcpio -P
and
update-grub
(first is redundant and should not be needed, I’d do it anyway)
exit chroot (CTRL-D if I remember correctly - or type “exit”)
These are the three packages involved in the initial error message.
Only openssl should be needed - but I’d do the two others as well.
When that is all done and still not working I’m all out of ideas.
Thank you, @Nachlese ,
Output of:
ls -al /usr
[manjaro /]# ls -al /usr
total 572
drwxr-xr-x 11 root root 4096 Dec 25 11:44 .
drwxr-xr-x 19 root root 4096 Dec 25 11:35 ..
drwxr-xr-x 7 root root 143360 Dec 25 11:44 bin
drwxr-xr-x 3 root root 4096 Apr 19 2022 doc
drwxr-xr-x 621 root root 49152 Dec 25 11:44 include
drwxr-xr-x 249 root root 278528 Dec 25 11:44 lib
drwxr-xr-x 37 root root 40960 Dec 25 11:43 lib32
lrwxrwxrwx 1 root root 3 Oct 19 15:12 lib64 -> lib
drwxr-xr-x 11 root root 4096 May 11 2020 local
drwxr-xr-x 3 root root 4096 Oct 10 22:28 man
lrwxrwxrwx 1 root root 3 Oct 19 15:12 sbin -> bin
drwxr-xr-x 368 root root 12288 Dec 25 11:43 share
drwxr-xr-x 4 root root 4096 May 23 2021 src
And next code:
[manjaro /]# ls -al /usr/lib/libcrypto*
lrwxrwxrwx 1 root root 14 Dec 14 17:22 /usr/lib/libcrypto.so -> libcrypto.so.3
-r-xr-xr-x 1 root root 2828704 Jan 25 2020 /usr/lib/libcrypto.so.1.0.0
-rwxr-xr-x 1 root root 4484080 Dec 14 17:22 /usr/lib/libcrypto.so.3
Very similar to the code you posted.
I then run all commands as you suggested.
Indeed, aftar reinstalling kmod, systemd and openssl it run mkinitcpio.
But I did run it again.
Sadly, exactly the same result.
After booting, the same error complaining about libcrypto.so.3: cannot open shared object file.
What else can I do to recover my system?
Why cannot open libcrypto.so.3?
chroot again and post logs:
journalctl -b-1 -p4 --no-pager
were there any errors when installing?:
Hi @brahma
No errors reported when installing kmod, systemd and openssl
The code
journalctl -b-1 -p4 --no-pager
outputs a loooooong log that starts in november 13th and ends in november 14th.
I cannot see the beginning of the log, exceeds the maximum number of lines of terminal, and ends in november 14th, long before the problem started.
Do you want me to post here what is shown, anyway?
did you type it correctly? because the journal command is only for the previous boot and nothing else…
run again this:
pacman -S openssl
and post output from it
I copy-pasted your code.
And did it again right now, with the same result.
Here the output from reinstalling openssl:
[manjaro /]# pacman -S openssl
warning: openssl-3.0.7-4 is up to date -- reinstalling
resolving dependencies...
looking for conflicting packages...
Packages (1) openssl-3.0.7-4
Total Download Size: 5.07 MiB
Total Installed Size: 10.69 MiB
Net Upgrade Size: 0.00 MiB
:: Proceed with installation? [Y/n] Y
:: Retrieving packages...
openssl-3.0.7-4-x86_64 5.1 MiB 19.2 MiB/s 00:00 [####################################] 100%
(1/1) checking keys in keyring [####################################] 100%
(1/1) checking package integrity [####################################] 100%
(1/1) loading package files [####################################] 100%
(1/1) checking for file conflicts [####################################] 100%
(1/1) checking available disk space [####################################] 100%
:: Processing package changes...
(1/1) reinstalling openssl [####################################] 100%
:: Running post-transaction hooks...
(1/1) Arming ConditionNeedsUpdate...
No errors reported
it shouldnt output that much logs, unless you have some spam there…
post output from:
journalctl -b-1 -p4 --no-pager | tail -50
spam does not sound good…
Here the output (I hope no sensitive information disclosed):
` [manjaro /]# journalctl -b-1 -p4 --no-pager | tail -50
Nov 14 23:13:45 pc-papas kwin_x11[1103]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 28895
, resource id: 29370558, major code: 18 (ChangeProperty), minor code: 0
Nov 14 23:13:55 pc-papas kwin_x11[1103]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 31429
, resource id: 56623147, major code: 18 (ChangeProperty), minor code: 0
Nov 14 23:13:55 pc-papas kwin_x11[1103]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 31607
, resource id: 50331653, major code: 18 (ChangeProperty), minor code: 0
Nov 14 23:13:55 pc-papas kwin_x11[1103]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 31611
, resource id: 44040197, major code: 18 (ChangeProperty), minor code: 0
Nov 14 23:13:55 pc-papas kwin_x11[1103]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 31615
, resource id: 35651590, major code: 18 (ChangeProperty), minor code: 0
Nov 14 23:13:55 pc-papas kwin_x11[1103]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 31626
, resource id: 48234502, major code: 18 (ChangeProperty), minor code: 0
Nov 14 23:13:55 pc-papas kdeconnectd[1234]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1b
.0.analog-stereo.monitor"
Nov 14 23:13:55 pc-papas kdeconnectd[1234]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1b
.0.analog-stereo"
Nov 14 23:13:55 pc-papas kdeconnectd[1234]: org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1b
.0.analog-stereo.monitor"
Nov 14 23:13:56 pc-papas kwin_x11[1103]: QMetaProperty::read: Unable to handle unregistered datatype 'KWin::Se
ssionState' for property 'KWin::EffectsHandlerImplX11::sessionState'
Nov 14 23:13:56 pc-papas kwin_x11[1103]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 31661
, resource id: 29360145, major code: 15 (QueryTree), minor code: 0
Nov 14 23:13:56 pc-papas kwin_x11[1103]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 31678
, resource id: 29360174, major code: 15 (QueryTree), minor code: 0
Nov 14 23:13:56 pc-papas kwin_x11[1103]: qt.qpa.xcb: QXcbConnection: XCB error: 3 (BadWindow), sequence: 31737
, resource id: 37748741, major code: 18 (ChangeProperty), minor code: 0
Nov 14 23:13:57 pc-papas kded5[1102]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDED
Module*): Pointers are not supported: KDEDModule*
Nov 14 23:13:57 pc-papas kded5[1102]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDED
Module*): Pointers are not supported: KDEDModule*
Nov 14 23:13:57 pc-papas kded5[1102]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDED
Module*): Pointers are not supported: KDEDModule*
Nov 14 23:13:57 pc-papas kded5[1102]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDED
Module*): Pointers are not supported: KDEDModule*
Nov 14 23:13:57 pc-papas kded5[1102]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDED
Module*): Pointers are not supported: KDEDModule*
Nov 14 23:13:57 pc-papas kded5[1102]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDED
Module*): Pointers are not supported: KDEDModule*
Nov 14 23:13:57 pc-papas kded5[1102]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDED
Module*): Pointers are not supported: KDEDModule*
Nov 14 23:13:57 pc-papas kded5[1102]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDED
Module*): Pointers are not supported: KDEDModule*
Nov 14 23:13:57 pc-papas kded5[1102]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDED
Module*): Pointers are not supported: KDEDModule*
Nov 14 23:13:57 pc-papas kded5[1102]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDED
Module*): Pointers are not supported: KDEDModule*
Nov 14 23:13:57 pc-papas kded5[1102]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDED
Module*): Pointers are not supported: KDEDModule*
Nov 14 23:13:57 pc-papas kded5[1102]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDED
Module*): Pointers are not supported: KDEDModule*
Nov 14 23:13:57 pc-papas kded5[1102]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDED
Module*): Pointers are not supported: KDEDModule*
Nov 14 23:13:57 pc-papas kded5[1102]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDED
Module*): Pointers are not supported: KDEDModule*
Nov 14 23:13:57 pc-papas kded5[1102]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDED
Module*): Pointers are not supported: KDEDModule*
Nov 14 23:13:57 pc-papas kded5[1102]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDED
Module*): Pointers are not supported: KDEDModule*
Nov 14 23:13:57 pc-papas kded5[1102]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDED
Module*): Pointers are not supported: KDEDModule*
Nov 14 23:13:57 pc-papas kded5[1102]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDED
Module*): Pointers are not supported: KDEDModule*
Nov 14 23:13:57 pc-papas kded5[1102]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDED
Module*): Pointers are not supported: KDEDModule*
Nov 14 23:13:57 pc-papas kded5[1102]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDED
Module*): Pointers are not supported: KDEDModule*
Nov 14 23:13:57 pc-papas kded5[1102]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDED
Module*): Pointers are not supported: KDEDModule*
Nov 14 23:13:57 pc-papas kded5[1102]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDED
Module*): Pointers are not supported: KDEDModule*
Nov 14 23:13:57 pc-papas kded5[1102]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDED
Module*): Pointers are not supported: KDEDModule*
Nov 14 23:13:57 pc-papas kded5[1102]: QDBusAbstractAdaptor: Cannot relay signal KDEDModule::moduleDeleted(KDED
Module*): Pointers are not supported: KDEDModule*
Nov 14 23:13:58 pc-papas sddm[741]: Authentication error: "Process crashed"
Nov 14 23:13:58 pc-papas sddm[741]: Auth: sddm-helper crashed (exit code 15)
Nov 14 23:13:58 pc-papas sddm[741]: Authentication error: "Process crashed"
Nov 14 23:13:58 pc-papas sddm[741]: Auth: sddm-helper exited with 15
Nov 14 23:13:58 pc-papas systemd-coredump[523730]: Failed to connect to coredump service: Connection refused
Nov 14 23:13:58 pc-papas systemd[1]: udisks2.service: Main process exited, code=dumped, status=6/ABRT
Nov 14 23:13:58 pc-papas systemd[1]: udisks2.service: Failed with result 'core-dump'.
Nov 14 23:13:59 pc-papas systemd[1004]: app-org.kde.konsole-785be9cfddee402180df11b57d378f5a.scope: Failed to
kill control group /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.konsole-785be9cfddee402
180df11b57d378f5a.scope, ignoring: Operation not permitted
Nov 14 23:13:59 pc-papas systemd[1004]: app-org.kde.konsole-785be9cfddee402180df11b57d378f5a.scope: Failed to
kill control group /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.konsole-785be9cfddee402
180df11b57d378f5a.scope, ignoring: Operation not permitted
Nov 14 23:13:59 pc-papas systemd[1004]: xdg-permission-store.service: Failed with result 'exit-code'.
Nov 14 23:13:59 pc-papas sddm[741]: Signal received: SIGTERM
Nov 14 23:14:00 pc-papas sddm[741]: QProcess: Destroyed while process ("/usr/lib/sddm/sddm-helper") is still r
unning.
Nov 14 23:14:01 pc-papas systemd[1004]: xdg-document-portal.service: Failed with result 'exit-code'.`
these logs are after something already failed, so not much helpfull… try logs from this:
journalctl -b-1 -p3 --no-pager
if there are from this output again too many logs, try this:
journalctl -b-1 -p3 --no-pager | tail -50
also provide output from:
mhwd-kernel -li && mhwd -l -li
First code also a loooong output.
Output from
journalctl -b-1 -p3 --no-pager | tail -50
is:
[manjaro /]# journalctl -b-1 -p3 --no-pager | tail -50
Nov 05 09:04:52 pc-papas kernel: usb 3-1: device descriptor read/64, error -71
Nov 05 09:04:52 pc-papas kernel: usb 3-1: device descriptor read/64, error -71
Nov 05 09:04:53 pc-papas kernel: usb 3-1: device descriptor read/64, error -71
Nov 05 09:04:53 pc-papas kernel: usb 3-1: device descriptor read/64, error -71
Nov 05 09:04:54 pc-papas kernel: usb 3-1: device not accepting address 69, error -71
Nov 05 09:04:54 pc-papas kernel: usb 3-1: device not accepting address 70, error -71
Nov 05 09:04:54 pc-papas kernel: usb usb3-port1: unable to enumerate USB device
Nov 08 00:47:42 pc-papas kernel: usb 3-1: device descriptor read/64, error -71
Nov 08 00:47:43 pc-papas kernel: usb 3-1: device descriptor read/64, error -71
Nov 08 00:47:43 pc-papas kernel: usb 3-1: device descriptor read/64, error -71
Nov 08 00:47:43 pc-papas kernel: usb 3-1: device descriptor read/64, error -71
Nov 08 00:47:44 pc-papas kernel: usb 3-1: device not accepting address 75, error -71
Nov 08 00:47:45 pc-papas kernel: usb 3-1: device not accepting address 76, error -71
Nov 08 00:47:45 pc-papas kernel: usb usb3-port1: unable to enumerate USB device
Nov 10 08:26:47 pc-papas kpat[445055]: kf.coreaddons: Error detected in cache, re-generating
Nov 10 10:17:41 pc-papas kernel: usb 3-1: device descriptor read/64, error -71
Nov 10 10:17:41 pc-papas kernel: usb 3-1: device descriptor read/64, error -71
Nov 10 10:17:41 pc-papas kernel: usb 3-1: device descriptor read/64, error -71
Nov 10 10:17:42 pc-papas kernel: usb 3-1: device descriptor read/64, error -71
Nov 10 10:17:42 pc-papas kernel: usb 3-1: device not accepting address 79, error -71
Nov 10 10:17:43 pc-papas kernel: usb 3-1: device not accepting address 80, error -71
Nov 10 10:17:43 pc-papas kernel: usb usb3-port1: unable to enumerate USB device
Nov 10 17:16:08 pc-papas kpat[454042]: kf.coreaddons: Error detected in cache, re-generating
Nov 12 22:59:05 pc-papas kernel: usb 3-1: device descriptor read/64, error -71
Nov 12 22:59:05 pc-papas kernel: usb 3-1: device descriptor read/64, error -71
Nov 12 22:59:06 pc-papas kernel: usb 3-1: device descriptor read/64, error -71
Nov 12 22:59:06 pc-papas kernel: usb 3-1: device descriptor read/64, error -71
Nov 12 22:59:07 pc-papas kernel: usb 3-1: device not accepting address 83, error -71
Nov 12 22:59:07 pc-papas kernel: usb 3-1: device not accepting address 84, error -71
Nov 12 22:59:07 pc-papas kernel: usb usb3-port1: unable to enumerate USB device
Nov 14 22:27:33 pc-papas kernel: sd 6:0:0:0: [sdd] No Caching mode page found
Nov 14 22:27:33 pc-papas kernel: sd 6:0:0:0: [sdd] Assuming drive cache: write through
Nov 14 22:31:08 pc-papas kernel: sd 6:0:0:0: [sdd] No Caching mode page found
Nov 14 22:31:08 pc-papas kernel: sd 6:0:0:0: [sdd] Assuming drive cache: write through
Nov 14 22:39:04 pc-papas kernel: FAT-fs (sdd1): error, fat_get_cluster: invalid start cluster (i_pos 122976, start c4a9d2d0)
Nov 14 22:39:04 pc-papas kernel: FAT-fs (sdd1): Filesystem has been set read-only
Nov 14 22:39:04 pc-papas kernel: FAT-fs (sdd1): error, fat_get_cluster: invalid start cluster (i_pos 122976, start c4a9d2d0)
Nov 14 22:39:04 pc-papas kernel: FAT-fs (sdd1): error, fat_get_cluster: invalid start cluster (i_pos 122976, start c4a9d2d0)
Nov 14 22:39:04 pc-papas kernel: FAT-fs (sdd1): error, fat_get_cluster: invalid start cluster (i_pos 122976, start c4a9d2d0)
Nov 14 22:39:04 pc-papas kernel: FAT-fs (sdd1): error, fat_get_cluster: invalid start cluster (i_pos 122976, start c4a9d2d0)
Nov 14 22:39:04 pc-papas kernel: FAT-fs (sdd1): error, fat_get_cluster: invalid start cluster (i_pos 122976, start c4a9d2d0)
Nov 14 22:39:04 pc-papas kernel: FAT-fs (sdd1): error, fat_get_cluster: invalid start cluster (i_pos 122976, start c4a9d2d0)
Nov 14 22:39:04 pc-papas kernel: FAT-fs (sdd1): error, fat_get_cluster: invalid start cluster (i_pos 122976, start c4a9d2d0)
Nov 14 22:39:04 pc-papas kernel: FAT-fs (sdd1): error, fat_get_cluster: invalid start cluster (i_pos 122976, start c4a9d2d0)
Nov 14 22:39:04 pc-papas kernel: FAT-fs (sdd1): error, fat_get_cluster: invalid start cluster (i_pos 122976, start c4a9d2d0)
Nov 14 22:39:52 pc-papas kernel: sd 6:0:0:0: [sdd] No Caching mode page found
Nov 14 22:39:52 pc-papas kernel: sd 6:0:0:0: [sdd] Assuming drive cache: write through
Nov 14 23:10:46 pc-papas systemd[515547]: /usr/lib/systemd/system-environment-generators/60-flatpak-system-only failed with exit status 127.
Nov 14 23:10:46 pc-papas systemd[515554]: /usr/lib/systemd/system-generators/ostree-system-generator failed with exit status 127.
Nov 14 23:13:58 pc-papas systemd-coredump[523730]: Failed to connect to coredump service: Connection refused
And:
[manjaro /]# mhwd-kernel -li && mhwd -l -li
Currently running: 6.1.1-1-MANJARO (linux61)
The following kernels are installed in your system:
* linux515
* linux54
> Installed PCI configs:
--------------------------------------------------------------------------------
NAME VERSION FREEDRIVER TYPE
--------------------------------------------------------------------------------
video-linux 2018.05.04 true PCI
Warning: No installed USB configs!
> 0000:00:02.0 (0300:8086:0412) Display controller Intel Corporation:
--------------------------------------------------------------------------------
NAME VERSION FREEDRIVER TYPE
--------------------------------------------------------------------------------
video-linux 2018.05.04 true PCI
video-modesetting 2020.01.13 true PCI
video-vesa 2017.03.12 true PCI
your usb is damaged … and some failed flatpak, not much usefull info …
try reinstalling all dependencies of openssl:
pacman -S glibc lib32-glibc coreutils cryptsetup curl git gnustep-base gst-plugins-bad kmod ldns lib32-openssl libarchive libevent libgit2 libsasl libshout libssh libssh2 libtorrent-rasterbar libzip ntp openssh openvpn pipewire-zeroconf pkcs11-helper ppp python rsync ruby s-nail socat sqlcipher srt sudo systemd tpm2-tss unarchiver vpnc wpa_supplicant xmlsec kded
if there are no errors, exit chroot, reboot
Is that possible?, USB has always been working well.
And I don’t have any flatpak installed…
Do I have to rm cache for all these dependencies?
After reinstalling them do I also reinstall openssl?
maybe damaged was a strong word, but there are some errors regarding to the usb in the logs, also for flatpak:
theres no need to remove cache, and also no need to reinstall openssl, since the output from above is without any error
I was asking about reinstalling openssl in case it was built against depedencies.
I will try as you recommend and report back
It complains that pipewire-zeroconf and manjaro-pulse conflict…
Do I remove manjaro-pulse?
i was doing the dependencies from my system, where i switched to pipewire, instead of pulse…
so use the command without the pipewire package:
pacman -S glibc lib32-glibc coreutils cryptsetup curl git gnustep-base gst-plugins-bad kmod ldns lib32-openssl libarchive libevent libgit2 libsasl libshout libssh libssh2 libtorrent-rasterbar libzip ntp openssh openvpn pkcs11-helper ppp python rsync ruby s-nail socat sqlcipher srt sudo systemd tpm2-tss unarchiver vpnc wpa_supplicant xmlsec kded
No errors shown.
During the automatic mkinitcpio part it always reports
==> WARNING: Possibly missing firmware for module: qed
==> WARNING: Possibly missing firmware for module: qla1280
==> WARNING: Possibly missing firmware for module: qla2xxx
==> WARNING: Possibly missing firmware for module: bfa
But it happened always, so I thought it is not important.
Just referring it now in case…
Also some
(11/13) Reloading system bus configuration...
Skipped: Running in chroot.
here and there, but I suppose that cannot be run as chroot and so skipped.
No further errors.
After reboot, all the same…
Would changing kernel make any difference? I guess no.
Something that should happen during the start of the system that does not occur and so shared libraries cannot be reached?