You are not logged in.

#1 2017-04-25 15:35:37

GilJ
Member
Registered: 2017-04-25
Posts: 3

[SOLVED] openssl-1.0 conflict after pacman crashes during an update

Hi,

A few hours ago I have tried to update with "pacman -Syu". I didn't realize I had almost no space on the root partition. There were some packages upgraded, but due to the lack of space "Write failed" errors showed up and eventually the whole system frozen. I had to cold restart the system.

Now after moving some user files from /home to an external disk I have enough space, but when I try to update again I have te following output:

$ pacman -Syu
...
Packages (218) ...huge list of packages...

Total Installed Size:  1800.09 MiB
Net Upgrade Size:        78.58 MiB

:: Proceed with installation? [Y/n] Y
(218/218) checking keys in keyring    [#########################################################################] 100%
(218/218) checking package integrity  [#########################################################################] 100%
(218/218) loading package files       [#########################################################################] 100%
(218/218) checking for file conflicts [#########################################################################] 100%
error: failed to commit transaction (conflicting files)
openssl-1.0: /usr/lib/libcrypto.so.1.0.0 exists in filesystem
openssl-1.0: /usr/lib/libssl.so.1.0.0 exists in filesystem
Errors occurred, no packages were upgraded.

I have the following output for the libcrypto and libssl:

$ ls -lahrtk /usr/lib/libcrypto.* /usr/lib/libssl.*
-rwxr-xr-x 1 root root 2.8M Apr 25 13:32 /usr/lib/libcrypto.so.1.1
-rwxr-xr-x 1 root root 505K Apr 25 13:32 /usr/lib/libssl.so.1.1
-r-xr-xr-x 1 root root 2.8M Apr 25 13:42 /usr/lib/libcrypto.so.1.0.0
-r-xr-xr-x 1 root root 505K Apr 25 13:43 /usr/lib/libssl.so.1.0.0
-rwxrwxrwx 1 root root   22 Apr 25 13:45 /usr/lib/libssl.so -> /usr/lib/libssl.so.1.1
lrwxrwxrwx 1 root root   25 Apr 25 13:45 /usr/lib/libcrypto.so -> /usr/lib/libcrypto.so.1.1

And for pacman -Q openssl:

$ pacman -Q openssl
openssl 1.1.0.e-1

The relevant portion of /var/log/pacman.log when the update occurred with the writing error:

[2017-04-25 12:08] [PACMAN] Running 'pacman -Syu'
[2017-04-25 12:08] [PACMAN] synchronizing package lists
[2017-04-25 12:08] [PACMAN] starting full system upgrade
[2017-04-25 12:37] [ALPM] transaction started
[2017-04-25 12:37] [ALPM] upgraded glib2 (2.50.3-1 -> 2.52.1+4+g2eddcef1e-1)
[2017-04-25 12:37] [ALPM] upgraded openssl (1.0.2.k-1 -> 1.1.0.e-1)
[2017-04-25 12:37] [ALPM] upgraded coreutils (8.26-1 -> 8.27-1)
[2017-04-25 12:37] [ALPM] upgraded libsasl (2.1.26-8 -> 2.1.26-11)
[2017-04-25 12:37] [ALPM] upgraded libldap (2.4.44-3 -> 2.4.44-4)
[2017-04-25 12:37] [ALPM] upgraded krb5 (1.13.7-1 -> 1.15-1)
[2017-04-25 12:37] [ALPM] upgraded adobe-source-han-sans-jp-fonts (1.004-1 -> 1.004-2)
[2017-04-25 12:37] [ALPM] upgraded libtiff (4.0.7-2 -> 4.0.7-3)
[2017-04-25 12:37] [ALPM] upgraded icu (58.2-1 -> 58.2-2)
[2017-04-25 12:37] [ALPM] upgraded gdk-pixbuf2 (2.36.5-1 -> 2.36.6-2)
[2017-04-25 12:37] [ALPM] upgraded gtk-update-icon-cache (3.22.10-1 -> 3.22.12+6+g42aa4c138c-1)
[2017-04-25 12:37] [ALPM] upgraded pango (1.40.4-1 -> 1.40.5-1)
[2017-04-25 12:37] [ALPM] upgraded libcroco (0.6.11-1 -> 0.6.12+4+g9ad7287-1)
[2017-04-25 12:37] [ALPM] upgraded librsvg (2:2.40.16-1 -> 2:2.40.17-1)
[2017-04-25 12:37] [ALPM] upgraded adwaita-icon-theme (3.22.0+1+g58cd459e-1 -> 3.24.0-1)
[2017-04-25 12:37] [ALPM] installed guile2.0 (2.0.14-1)
[2017-04-25 12:37] [ALPM] upgraded atk (2.24.0-1 -> 2.24.0-2)
[2017-04-25 12:37] [ALPM] upgraded dconf (0.26.0-2 -> 0.26.0+1+g701d19d-1)
[2017-04-25 12:37] [ALPM] upgraded dbus (1.10.16-2 -> 1.10.18-1)
[2017-04-25 12:37] [ALPM] upgraded at-spi2-core (2.22.0-1 -> 2.24.0-1)
[2017-04-25 12:37] [ALPM] upgraded at-spi2-atk (2.22.0-1 -> 2.24.0-1)
[2017-04-25 12:37] [ALPM] upgraded json-glib (1.2.6+7+gf98d547-1 -> 1.2.8-1)
[2017-04-25 12:37] [ALPM] error: could not extract /usr/lib/libgtk-3.so.0.2200.12 (Write failed)
[2017-04-25 12:37] [ALPM] error: could not extract /usr/lib/libgailutil-3.so.0.0.0 (Write failed)
[2017-04-25 12:37] [ALPM] error: could not extract /usr/lib/girepository-1.0/Gtk-3.0.typelib (Write failed)
[2017-04-25 12:37] [ALPM] error: could not extract /usr/lib/girepository-1.0/Gdk-3.0.typelib (Write failed)
[2017-04-25 12:37] [ALPM] error: could not extract /usr/lib/gtk-3.0/3.0.0/immodules/im-am-et.so (Write failed)
[2017-04-25 12:37] [ALPM] error: could not extract /usr/lib/gtk-3.0/3.0.0/immodules/im-cedilla.so (Write failed)
[2017-04-25 12:37] [ALPM] error: could not extract /usr/lib/gtk-3.0/3.0.0/immodules/im-cyrillic-translit.so (Write failed)
[2017-04-25 12:37] [ALPM] error: problem occurred while upgrading gtk3

I have read https://wiki.archlinux.org/index.php/pa … 9.22_error , since no package owns those files I have tried to rename them, but then I have the following output when I try to upgrade:

$ pacman -Syu
pacman: error while loading shared libraries: libcrypto.so.1.0.0: cannot open shared object file: No such file or directory

Which seems related to the issue on other thread (https://bbs.archlinux.org/viewtopic.php?id=225478). I'm not sure if I should follow the solution on that thread.

I am using SDDM with Plasma but I also have Gnome.
All KDE applications seem to work but many other programs do not start, e.g. gnome applications and Firefox (output: "Segmentation fault (core dumped)").

Can anyone help, what should I do?

Last edited by GilJ (2017-04-30 00:16:04)

Offline

#2 2017-04-25 15:38:12

Slithery
Forum Moderator
From: Norfolk, UK
Registered: 2013-12-01
Posts: 3,130

Re: [SOLVED] openssl-1.0 conflict after pacman crashes during an update

Boot from an Arch installation disk and then run a full upgrade on your system using pacmans --root flag.


No, it didn't "fix" anything. It just shifted the brokeness one space to the right. - jasonwryan
Closing -- for deletion; Banning -- for muppetry. - jasonwryan

aur - dotfiles

Offline

#3 2017-04-25 17:36:25

GilJ
Member
Registered: 2017-04-25
Posts: 3

Re: [SOLVED] openssl-1.0 conflict after pacman crashes during an update

Thank you, I will try that.

Offline

#4 2017-04-26 04:33:11

vgf89
Member
Registered: 2014-05-12
Posts: 2

Re: [SOLVED] openssl-1.0 conflict after pacman crashes during an update

I ran into the exact same issue as Gilj. Curl seems to have broken on my system due to this openssl/opencrypto issue, which in turn broke pacman and is preventing me from updating from the repos. Don't have a bootable USB on hand.

The conflict is also preventing me from downgrading OpenSSL (since pacman won't work without the openssl.so.1.0.0 and opencrypto.so.1.0.0 symlinks, but the old OpenSSL package sees them as conflicting files and fails).

EDIT: I installed the old version of OpenSSL with
    pacman -U /var/cache/pacman/pkg/openssl-1.0.2.k-1-x86_64.pkg.tar.xz --force

EDIT2: I then updated pacman.

But now pacman is broken again, practically an inversion of the original issue (now it's asking for libcrypto1.1.0 instead of 1.0.0). I'm going to try some symlinks and force install the new OpenSSL to see if I can get around it. It seems the main issue here is that the new version of pacman (5.0.1-5) is not marked as dependent on the new version of openssl (1.1.0.e-1) in the repos.

EDIT3:
    ln -s libssl.so.1.0.0 libssl.so.1.1
    ln -s libcrypto.so.1.0.0 libcrypto.so.1.1
    pacman -U /var/cache/pacman/pkg/openssl-1.1.0.e-1-x86_64.pkg.tar.xz --force

    pacman is broken again. Now it's asking for libcrypto.so.1.0.0. Symlinking back again...

EDIT4:
    ln -s libssl.so.1.1 libssl.so.1.0.0
    ln -s libcrypto.so.1.1 libcrypto.so.1.0.0

But now curl is screwed up. (ran pacman -Sy and got this error message: pacman: symbol lookup error: /usr/lib/libcurl.so.4: undefined symbol: SSL_load_error_strings). Curl is not updated to the latest on my system, but OpenSSL and pacman are. I'd guess that curl, pacman, and openssl would all need to be updated simultaneously to not run into error. Not sure how to proceed short of making a bootable USB.

EDIT5: Downgraded pacman and openssl simultaneously, then tried updating curl, openssl, and pacman at the same time, but it seems then openssh relied on that specific version which, again, breaks pacman, so I downgraded pacman, openssl, and curl again. Trying a full "pacman -Syu" to see what happens. This is probably going to backfire.



EDIT6: Worked fine.

So my problem had the same symptoms but a different cause. I tried to update openssl on its own before running a full upgrade, which had broken my pacman, curl, etc in the same way as OP.

Full solution: Run the following to downgrade to your previous version of openssl (in my case, the most recent old version was 1.0.2.k):
    pacman -U /var/cache/pacman/pkg/openssl-1.0.2.k-1-x86_64.pkg.tar.xz --force

pacman -Sy should now work. If not, you might need to downgrade pacman as well (same process as above, I had to downgrade to 5.0.1-4 after my fenagling in the previous edits).
Then do a full upgrade with pacman -Syu.

Last edited by vgf89 (2017-04-26 05:57:13)

Offline

#5 2017-04-26 15:52:01

lukasm
Member
Registered: 2014-10-24
Posts: 23

Re: [SOLVED] openssl-1.0 conflict after pacman crashes during an update

In my case, problems seem to have started because libssl.so.1.0.0 were not deleted. I somehow managed to get into the segfault described in here https://bbs.archlinux.org/viewtopic.php?id=225489. This segfault occured using plain arch in my case.

I don't know the exact order how I proceeded, but one needs to remove either openssl-1.1.0.so or openssl-1.0.2.so, such that pacman starts again. Finally managed to downgrad to openssl-1.0.2 (with --force) and pacman manually. Afterwards "pacman -Sy" should work to "re"-upgrade.

Seems like everything works now, except spotify which is looking for libssl.so.1.0.0 which does not exist anymore.

Last edited by lukasm (2017-04-26 15:52:22)

Offline

#6 2017-04-30 00:10:42

GilJ
Member
Registered: 2017-04-25
Posts: 3

Re: [SOLVED] openssl-1.0 conflict after pacman crashes during an update

Finally I managed to get some time to deal with this.

I initially tried the upgrade with pacman's --root flag approach, using a recent Arch install image. I followed the instructions on Arch pacman page (https://wiki.archlinux.org/index.php/pa … an_upgrade):

- mount system's root filesystem;
- run: pacman --root=/mnt --cachedir=/mnt/var/cache/pacman/pkg -Syyu

It didn't work, same openssl-1.0 issue.

I followed vgf89 and lukasm solution and the problem was solved. Thanks guys! :-)

Downgrade openssl to a previous version (in my case it was also 1.0.2.k):

$ pacman -U /var/cache/pacman/pkg/openssl-1.0.2.k-1-x86_64.pkg.tar.xz --force

Downgrade pacman to a previous version (this case 5.0.1-4):

$ pacman -U /var/cache/pacman/pkg/pacman-5.0.1-4-x86_64.pkg.tar.xz --force

When updating with pacman -Syu the conflicting files errors refer now to openssl-1.1.
I have moved /usr/lib/libssl.so.1.1 and /usr/lib/libcrypto.so.1.1 to a backup location and "pacman -Syu" now works.

Offline

#7 2017-06-08 14:27:39

spydon
Member
Registered: 2015-02-03
Posts: 6

Re: [SOLVED] openssl-1.0 conflict after pacman crashes during an update

Has nobody managed to fix this properly? If I read your comments correctly you still have some problems afterwards with openssl?

Offline

#8 2017-06-08 14:35:11

V1del
Forum Moderator
Registered: 2012-10-16
Posts: 6,023

Re: [SOLVED] openssl-1.0 conflict after pacman crashes during an update

The topic is SOLVED and the fix has been described in the last post. If you still have issues, you should open up a new thread with concrete info on what is wrong (hint: if what is being discussed here is what's wrong, read this thread a few times again, if you have other issues with openssl and other programs, this has nothing to do with this topic.)

Closing.

Offline

#9 2017-06-08 14:35:38

Trilby
Inspector Parrot
Registered: 2011-11-29
Posts: 20,930
Website

Re: [SOLVED] openssl-1.0 conflict after pacman crashes during an update

Yes it was fixed - that's why the title has been editted to include [SOLVED].  Do not necrobump solved threads.

Closed.  (edit: too slow)


"UNIX is simple and coherent..." - Dennis Ritchie, "GNU's Not UNIX" -  Richard Stallman

Offline

Board footer

Powered by FluxBB