Arch Linux

Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines

Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.

REPEAT: Do NOT report bugs for outdated packages!
Tasklist

FS#40357 - [fontforge] fontforge won't start after the upgrade of libsodium package

Attached to Project: Arch Linux
Opened by massimo (mazrimtaim1914) - Wednesday, 14 May 2014, 13:46 GMT
Last edited by Felix Yan (felixonmars) - Wednesday, 14 May 2014, 13:55 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 0
Private No

Details

Description:
After the libsodium 0.5.0-1 upgrade (package updated on 2014-05-14)
fontforge version 20140101-2 won't start anymore.
If fontforge is executed from the terminal you should see the following stderr message:
"fontforge: error while loading shared libraries: libsodium.so.4: cannot open shared object file: No such file or directory".

If I do a "pacman -Qil libsodium", among other files, I see following files:
libsodium /usr/lib/libsodium.so
libsodium /usr/lib/libsodium.so.10
libsodium /usr/lib/libsodium.so.10.0.0

As you see the libsodium.so.4 library is not present; instead libsodium.so.10 is present.

Additional info:
* package fontforge 20140101-2 provides the breaked fontforge
* package libsodium 0.5.0-1

Steps to reproduce:
1. upgrade libsodium via pacman to 0.5.0-1
2. execute in a terminal fontforge
This task depends upon

Closed by  Felix Yan (felixonmars)
Wednesday, 14 May 2014, 13:55 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#40355 

Loading...