[Solved] Pacman no longer works at all!!

banshee28 · 2013-02-17 17:01:15

Ok, did some searches and found a few hits, but not really sure how to fix this one. Here are 2 links I found.
links:
http://unix.stackexchange.com/questions … -libraries
https://bbs.archlinux.org/viewtopic.php?pid=1232052

In my case, I dont think any pacman option/command works. Cant run 'pacman' with ANY options or with no options??
error:

 $ pacman
pacman: error while loading shared libraries: libcurl.so.4: cannot open shared object file: No such file or directory

I guess I was updating something using curl libraries, but not sure whats the best way to fix this.

ldconfig -p | grep curl

Returns nothing.

Not sure if this was the right thing to do but I also tried this from the first link.

echo /usr/local/lib | sudo tee -a /etc/ld.so.conf.d/local.conf

Here is another one:

$ sudo ldd $(which pacman)
	linux-vdso.so.1 (0x00007fff4a3ff000)
	libalpm.so.7 => /usr/lib/libalpm.so.7 (0x00007f16be091000)
	libc.so.6 => /usr/lib/libc.so.6 (0x00007f16bdce4000)
	libcurl.so.4 => not found
	libgpgme.so.11 => /usr/lib/libgpgme.so.11 (0x00007f16bdab1000)
	libarchive.so.12 => /usr/lib/libarchive.so.12 (0x00007f16bd81c000)
	libcrypto.so.1.0.0 => /usr/lib/libcrypto.so.1.0.0 (0x00007f16bd412000)
	/lib/ld-linux-x86-64.so.2 (0x00007f16be2bd000)
	libassuan.so.0 => /usr/lib/libassuan.so.0 (0x00007f16bd202000)
	libgpg-error.so.0 => /usr/lib/libgpg-error.so.0 (0x00007f16bcfff000)
	libacl.so.1 => /usr/lib/libacl.so.1 (0x00007f16bcdf6000)
	libattr.so.1 => /usr/lib/libattr.so.1 (0x00007f16bcbf1000)
	libexpat.so.1 => /usr/lib/libexpat.so.1 (0x00007f16bc9c7000)
	liblzma.so.5 => /usr/lib/liblzma.so.5 (0x00007f16bc7a4000)
	libbz2.so.1.0 => /usr/lib/libbz2.so.1.0 (0x00007f16bc594000)
	libz.so.1 => /usr/lib/libz.so.1 (0x00007f16bc37e000)
	libdl.so.2 => /usr/lib/libdl.so.2 (0x00007f16bc17a000)
	libpthread.so.0 => /usr/lib/libpthread.so.0 (0x00007f16bbf5e000)

So looks like thats the issue .. libcurl.so.4 => not found ...
I dont have strace installed and not sure if I need it to continue....I did a quick search and dont see a libcurl installed, so either i need to install it or remove that reference too it? LOL

Any suggestions?

Last edited by banshee28 (2013-02-19 03:28:09)

Army · 2013-02-17 17:52:05

Show us what you did with pacman which caused this = show us your /var/log/pacman.log. Do you use testing repos?

Last edited by Army (2013-02-17 17:52:24)

WonderWoofy · 2013-02-17 18:20:55

If you think it was a curl update that borked your shit, why not just try to set pacman to use wget in pacman.conf and then reinstall the suspect packages.

falconindy · 2013-02-17 18:27:37

WonderWoofy wrote:

If you think it was a curl update that borked your shit, why not just try to set pacman to use wget in pacman.conf and then reinstall the suspect packages.

Because this won't work. You still need library present to run the pacman binary.

No curl update would have caused this. There's not been a soname bump in libcurl in over a decade. OP seems to have removed the curl package, or at least the shared lib.

WonderWoofy · 2013-02-17 18:32:00

Ah I see I should probably have read the l entire first post.

Sorry about the noise here...

banshee28 · 2013-02-17 19:59:54

Army wrote:

Show us what you did with pacman which caused this = show us your /var/log/pacman.log. Do you use testing repos?

Never use testing repos.
I dont see anything for libcurl in that log, but I did see this recently for curl. Perhaps this is the culprit. Pacman -Sc ??

[2013-02-07 03:05] Running 'pacman -Sc --noconfirm'
[2013-02-08 03:05] Running 'pacman -Sc --noconfirm'
[2013-02-08 17:19] Running 'pacman -Sy'
[2013-02-08 17:19] synchronizing package lists
[2013-02-08 17:19] starting full system upgrade
[2013-02-08 17:19] Running 'pacman -S -u'
[2013-02-08 17:19] starting full system upgrade
[2013-02-08 17:21] upgraded perl (5.16.2-2 -> 5.16.2-3)
[2013-02-08 17:21] upgraded openssl (1.0.1.c-1 -> 1.0.1.d-1)
***** [2013-02-08 17:21] upgraded curl (7.28.1-1 -> 7.29.0-1)  *******

Full log file:

[2012-09-22 09:01] installed filesystem (2012.8-1)
[2013-02-11 20:12] ------------------------------------------------------------------------
[2013-02-11 20:12] upgraded profile-sync-daemon (5.13-1 -> 5.16-1)
[2013-02-12 03:05] Running 'pacman -Sc --noconfirm'
[2013-02-12 18:19] Running 'pacman -Sy'
[2013-02-12 18:19] synchronizing package lists
[2013-02-12 18:19] starting full system upgrade
[2013-02-12 18:19] Running 'pacman -S -u'
[2013-02-12 18:19] starting full system upgrade
[2013-02-12 18:20] upgraded device-mapper (2.02.98-1 -> 2.02.98-3)
[2013-02-12 18:20] upgraded cryptsetup (1.5.1-1 -> 1.6.0-1)

Last edited by banshee28 (2013-02-19 03:29:37)

falconindy · 2013-02-17 20:03:04

So you blame a curl update from a week ago?

ls /usr/lib/libcurl.so*

Please pay attention to pacman's output. You have much work to do.

banshee28 · 2013-02-17 20:09:00

falconindy wrote:

So you blame a curl update from a week ago?
ls /usr/lib/libcurl.so*
Please pay attention to pacman's output. You have much work to do.

Yes its been about a week .... yes it looks like there is no libcurl, but not sure why or how to fix it.

$ ls /usr/lib/libcurl.so*
ls: cannot access /usr/lib/libcurl.so*: No such file or directory

Last edited by banshee28 (2013-02-17 20:10:34)

falconindy · 2013-02-17 20:22:12

You can use a liveCD to reinstall the package.

banshee28 · 2013-02-17 20:24:32

falconindy wrote:

You can use a liveCD to reinstall the package.

Thanks, was not sure if that was the only way to do this...Will try that.

WorMzy · 2013-02-17 20:39:26

Alternatively, you can unpack the curl package to /, assuming you still have the package in your cache, and the package itself isn't to blame here (which I doubt it is).

# tar -xpf /var/cache/pacman/pkg/curl-7.29.0-1-x86_64.pkg.tar.xz -C / --exclude .PKGINFO --exclude .INSTALL

Assuming that fixes pacman, you should then make sure that pacman is aware of the files you've just extracted

# pacman -U --dbonly /var/cache/pacman/pkg/curl-7.29.0-1-x86_64.pkg.tar.xz

And finally do a full system update

# pacman -Syyu

banshee28 · 2013-02-19 03:27:55

WorMzy wrote:

Alternatively, you can unpack the curl package to /, assuming you still have the package in your cache, and the package itself isn't to blame here (which I doubt it is).
# tar -xpf /var/cache/pacman/pkg/curl-7.29.0-1-x86_64.pkg.tar.xz -C / --exclude .PKGINFO --exclude .INSTALL
Assuming that fixes pacman, you should then make sure that pacman is aware of the files you've just extracted
# pacman -U --dbonly /var/cache/pacman/pkg/curl-7.29.0-1-x86_64.pkg.tar.xz
And finally do a full system update
# pacman -Syyu

THANK YOU!!! This worked perfectly.
Thats what I was looking for

partho222 · 2013-10-29 05:35:18

Faced same problem , but this post saved my day

THANKS WorMzy

Arch Linux

#1 2013-02-17 17:01:15

[Solved] Pacman no longer works at all!!

#2 2013-02-17 17:52:05

Re: [Solved] Pacman no longer works at all!!

#3 2013-02-17 18:20:55

Re: [Solved] Pacman no longer works at all!!

#4 2013-02-17 18:27:37

Re: [Solved] Pacman no longer works at all!!

#5 2013-02-17 18:32:00

Re: [Solved] Pacman no longer works at all!!

#6 2013-02-17 19:59:54

Re: [Solved] Pacman no longer works at all!!

#7 2013-02-17 20:03:04

Re: [Solved] Pacman no longer works at all!!

#8 2013-02-17 20:09:00

Re: [Solved] Pacman no longer works at all!!

#9 2013-02-17 20:22:12

Re: [Solved] Pacman no longer works at all!!

#10 2013-02-17 20:24:32

Re: [Solved] Pacman no longer works at all!!

#11 2013-02-17 20:39:26

Re: [Solved] Pacman no longer works at all!!

#12 2013-02-19 03:27:55

Re: [Solved] Pacman no longer works at all!!

#13 2013-10-29 05:35:18

Re: [Solved] Pacman no longer works at all!!

Board footer