Bug 24934 - lib64bz2_1: Please add a symlink /usr/lib64/libbz2.so.1.0 pointing to libbz2.so.1 (was: impossible to start XnView in MGA7 RC)
Summary: lib64bz2_1: Please add a symlink /usr/lib64/libbz2.so.1.0 pointing to libbz2....
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Base system maintainers
QA Contact:
URL: https://www.xnview.com/fr/xnviewmp/
Whiteboard:
Keywords: 7RC
Depends on:
Blocks:
 
Reported: 2019-06-08 09:38 CEST by j pierre LAJOIE
Modified: 2019-06-16 07:11 CEST (History)
3 users (show)

See Also:
Source RPM: bzip2-1.0.6-12.mga7
CVE:
Status comment:


Attachments

Description j pierre LAJOIE 2019-06-08 09:38:46 CEST
Description of problem:
go to Xnview : https://www.xnview.com/fr/xnviewmp/
Download : XnViewMP-linux-x64.tgz
uncompress in /opt/XnView
Verify in XnView.desktop if :
Exec=/opt/XnView/xnview.sh %F
and 
Icon=/opt/XnView/xnview.png

Copy XnView.desktop in /usr/share/applications

Xnview correcly appear in mageia application menu in graphical
if i click on it a rotating icon appear a few seconds and disappear 
the programm don't start
 It's was Ok with MGA6
Ilk i try to start from Kinsole  i have this :

[root@localhost opt]# xnview
/opt/XnView/XnView: error while loading shared libraries: libbz2.so.1.0: cannot open shared object file: No such file or directory
[root@localhost opt]# 




Version-Release number of selected component (if applicable):


How reproducible:always


Steps to Reproduce:see above 
1.
2.
3.
j pierre LAJOIE 2019-06-08 19:47:25 CEST

Component: BuildSystem => RPM Packages
Product: Infrastructure => Mageia
Summary: impossible to start in MGA7 RC => impossible to start XnView in MGA7 RC
Version: unspecified => 7

j pierre LAJOIE 2019-06-08 19:48:38 CEST

Keywords: (none) => 7RC

Jani Välimaa 2019-06-08 19:54:54 CEST

Assignee: sysadmin-bugs => bugsquad

Comment 1 Jani Välimaa 2019-06-08 20:05:48 CEST
We don't provide library named libbz2.so.1.0, but libbz2.so.1.

You need to create a symlink /usr/lib64/libbz2.so.1.0 pointing to libbz2.so.1.
Comment 2 Jani Välimaa 2019-06-08 20:55:33 CEST
Looks like we are patching the build to provide libbz2.so.1 instead of libbz2.so.1.0.

So, we could add a compatibility symlink mentioned in comment 1.
Comment 3 Jani Välimaa 2019-06-08 20:56:09 CEST
(In reply to Jani Välimaa from comment #2)
> Looks like we are patching the build to provide libbz2.so.1 instead of
> libbz2.so.1.0.
> 
> So, we could add a compatibility symlink mentioned in comment 1.

And the pkg is bzip2.
Comment 4 j pierre LAJOIE 2019-06-09 08:54:36 CEST
tks the sym link is working fine  and my xnview start 

but what's can be do for starting Xnview directly for lamba users ?
maybe copying the library libbz2.so.1 in another library libbz2.so.1.0. ?
or patching xnview ?
Comment 5 Marja Van Waes 2019-06-11 11:42:04 CEST
(In reply to Jani Välimaa from comment #1)
> We don't provide library named libbz2.so.1.0, but libbz2.so.1.
> 
> You need to create a symlink /usr/lib64/libbz2.so.1.0 pointing to
> libbz2.so.1.

(In reply to Jani Välimaa from comment #2)
> Looks like we are patching the build to provide libbz2.so.1 instead of
> libbz2.so.1.0.
> 
> So, we could add a compatibility symlink mentioned in comment 1.


Thanks a lot, Jani, I wouldn't have figured that out!

Assigning to our Base System maintainers, CC'ing our bzip2 maintainer.

Summary: impossible to start XnView in MGA7 RC => lib64bz2_1: Please add a symlink /usr/lib64/libbz2.so.1.0 pointing to libbz2.so.1 (was: impossible to start XnView in MGA7 RC)
Assignee: bugsquad => basesystem
Source RPM: XnViewMP-linux-x64.tgz => bzip2-1.0.6-12.mga7
CC: sysadmin-bugs => marja11, tmb

Comment 6 Jani Välimaa 2019-06-13 19:24:43 CEST
Fixed in SVN:
http://svnweb.mageia.org/packages?view=revision&revision=1399924

A freeze push request is also needed.

CC: (none) => jani.valimaa

Comment 7 Jani Välimaa 2019-06-16 07:11:34 CEST
Fixed in bzip2-1.0.6-13.mga7.

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.