You are not logged in.

#1 2017-03-15 11:38:04

dev11
Member
Registered: 2017-02-19
Posts: 4

Pacman fails to run

Im on fresh install of ArchBang Console only (= no X's);
ive booted OK, logged as root, issued:

pacman -Syu

and got:

ERROR while loading shared library.

No matter what I do with pacman, above msg appears.
Pacman is unusable.

Offline

#2 2017-03-15 19:33:53

seventh
Member
Registered: 2017-02-07
Posts: 73

Re: Pacman fails to run

There was some news on the arch linux site this morning that may be of importance, by the sounds of it if you don't do this pacman wont work.

...

https://www.archlinux.org/news/ca-certi … ervention/

ca-certificates-utils 20170307-1 upgrade requires manual intervention

2017-03-15 - Jan Steffens

The upgrade to ca-certificates-utils 20170307-1 requires manual intervention because a symlink which used to be generated post-install has been moved into the package proper.

As deleting the symlink may leave you unable to download packages, perform this upgrade in three steps:

# pacman -Syuw                                  # download packages
# rm /etc/ssl/certs/ca-certificates.crt   # remove conflicting file
# pacman -Su                                       # perform upgrade

EDIT: I have https://www.archlinux.org/ set as my homepage so i catch the news as soon as my browser opens which i think is a good idea having a rolling release such as archbang. This maybe your problem with pacman or may not be.

Last edited by seventh (2017-03-15 19:43:29)

Offline

#3 2017-03-16 09:39:20

dev11
Member
Registered: 2017-02-19
Posts: 4

Re: Pacman fails to run

hey thanks for reply,\
Ive tried this but no luck.
Being remotely connected, I cannot get KVM instantly. But today I drove 120 km and connected KVM. Once there, I did a lot of research on the issue.

My findings:
1. this has nothing to do with ca-certificates. After removing file in question, problem still exists,
2. Pacman complains about files within LZO package

:: Proceed with installation? [Y/n] y
(238/238) checking keys in keyring                 [######################] 100%
(238/238) checking package integrity               [######################] 100%
(238/238) loading package files                    [######################] 100%
(238/238) checking for file conflicts              [######################] 100%
error: failed to commit transaction (conflicting files)
lzo: /usr/include/lzo/lzo1.h exists in filesystem
lzo: /usr/include/lzo/lzo1a.h exists in filesystem
lzo: /usr/include/lzo/lzo1b.h exists in filesystem
lzo: /usr/include/lzo/lzo1c.h exists in filesystem
lzo: /usr/include/lzo/lzo1f.h exists in filesystem
lzo: /usr/include/lzo/lzo1x.h exists in filesystem
lzo: /usr/include/lzo/lzo1y.h exists in filesystem
lzo: /usr/include/lzo/lzo1z.h exists in filesystem
lzo: /usr/include/lzo/lzo2a.h exists in filesystem
lzo: /usr/include/lzo/lzo_asm.h exists in filesystem
lzo: /usr/include/lzo/lzoconf.h exists in filesystem
lzo: /usr/include/lzo/lzodefs.h exists in filesystem
lzo: /usr/include/lzo/lzoutil.h exists in filesystem
lzo: /usr/include/lzo/minilzo.h exists in filesystem
lzo: /usr/lib/liblzo2.so exists in filesystem
lzo: /usr/lib/liblzo2.so.2 exists in filesystem
lzo: /usr/lib/liblzo2.so.2.0.0 exists in filesystem
lzo: /usr/lib/libminilzo.so exists in filesystem
lzo: /usr/lib/libminilzo.so.0 exists in filesystem
lzo: /usr/share/doc/lzo/AUTHORS exists in filesystem
lzo: /usr/share/doc/lzo/COPYING exists in filesystem
lzo: /usr/share/doc/lzo/LZO.FAQ exists in filesystem
lzo: /usr/share/doc/lzo/LZO.TXT exists in filesystem
lzo: /usr/share/doc/lzo/LZOAPI.TXT exists in filesystem
lzo: /usr/share/doc/lzo/NEWS exists in filesystem
lzo: /usr/share/doc/lzo/THANKS exists in filesystem
Errors occurred, no packages were upgraded.
pacman -Su  22.15s user 0.71s system 64% cpu 35.212 total

3. I deleted files listed (moved them away) and then Pacman began its unresponsiveness

FUCK !!!!!!!!!!!!!!!!!!!!!!!!!

Offline

#4 2017-03-16 14:34:23

Mr Green
Administrator
Registered: 2010-11-07
Posts: 6,913

Re: Pacman fails to run

You should always check what package owns lzo file before deleting it, there could be a number of reasons why file is already in system.

Have you tried to reinstall lzo? looks like it is required by cairo...

Did you force or install anything that was not via pacman? or from aur?


Comments, suggestions, donations please feel free to contact me mrgreen(at)archbang(dot)org Artix information https://artixlinux.org/migrate.php

Offline

Board footer

Powered by FluxBB