| Summary: | Unable to start ufraw in Mageia 2 RC, libexiv2.so.10 not found | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Matthieu Nguyen <nguyen.matthieu> |
| Component: | RPM Packages | Assignee: | Mageia Bug Squad <bugsquad> |
| Status: | RESOLVED INVALID | QA Contact: | |
| Severity: | major | ||
| Priority: | Normal | CC: | fundawang, mageia, pterjan |
| Version: | Cauldron | ||
| Target Milestone: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | ufraw | CVE: | |
| Status comment: | |||
| Attachments: | output of ldd /usr/bin/ufraw | ||
|
Description
Matthieu Nguyen
2012-05-09 23:34:04 CEST
I cheated (a bit) and created a symlink to /usr/lib64/libexiv2.so.11 named /usr/lib64/libexiv2.so.10 ufraw then complained that libtiff.so.3 was also missing: [matt@localhost ~]$ ufraw ufraw: error while loading shared libraries: libtiff.so.3: cannot open shared object file: No such file or directory Checking in /usr/lib64, I had libtiff.so.5 and not libtiff.so.3. Again, created a symlink, and then ufraw started successfully. So in summary, there is a problem with two libs for ufraw: - libexiv2 - libtiff Hope that helps How did you upgrade your system (what command exactly)? And what is the output of these commands: rpm -qa |grep exiv rpm -qa |grep tiff exiv's version 10 and tiff's version 3 seem very much like a mga1 packages. CC:
(none) =>
sander.lepik I used the command line update, as per: https://wiki.mageia.org/en/Mageia_2_Release_Notes#Upgrading_from_Mageia_1 So I ran: killall mgaapplet mgaapplet --testing I posted above the rpm -qis output for the exiv and tiff libs. They seem to be the mga2 version. Here's the rpm -qa output [matt@localhost ~]$ rpm -qa | grep exiv lib64gexiv2_0-0.3.92-1.mga2 exiv2-0.22-1.mga2 lib64exiv2_11-0.22-1.mga2 lib64exiv2-devel-0.22-1.mga2 [matt@localhost ~]$ rpm -qa | grep tiff lib64tiff-devel-4.0.1-2.mga2 libtiff5-4.0.1-2.mga2 lib64tiff5-4.0.1-2.mga2 My guess is that ufraw has been built against the wrong exiv/tiff libs (if such a thing is possible).
Manuel Hiebel
2012-05-10 12:03:35 CEST
CC:
(none) =>
fundawang, pterjan Cannot reproduce in latest cauldron i586. Well, it's not. ldd shows it's built correctly. Can you try reinstall of ufraw? Or what's the output of ldd /usr/bin/ufraw Can you also run rpm -V ufraw? Created attachment 2240 [details]
output of ldd /usr/bin/ufraw
What about "which ufraw" or running /usr/bin/ufraw? Do you have a manually built one which would be broken? Just thought about the "which ufraw" at the same time as your comment. Although I have no recollection of building ufraw myself, I did have a copy under /usr/local/bin/ufraw... I removed the old binaries. ufraw now starts fine. Apologies for the inconvenience, this bug can be closed as a PEBKAC... OK thanks for confirming :) Status:
NEW =>
RESOLVED |