Bug 12588 - Linphone doesn't launch, wrong libosipparser2.so library
Summary: Linphone doesn't launch, wrong libosipparser2.so library
Status: RESOLVED INVALID
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 4
Hardware: i586 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords: Triaged
Depends on:
Blocks:
 
Reported: 2014-02-04 22:48 CET by Gegetel
Modified: 2014-02-05 18:59 CET (History)
2 users (show)

See Also:
Source RPM: linphone-3.6.1-4.mga4.src.rpm
CVE:
Status comment:


Attachments

Description Gegetel 2014-02-04 22:48:10 CET
Description of problem: Linphone doesn't launch.

When I try to start linphone on Mageia 4 i586, I only get this error message:

$ linphone
linphone: error while loading shared libraries: libosipparser2.so.7: cannot open shared object file: No such file or directory

- The really installed libraries are libosipparser2.so.10.0.0, libosip2.so.10.0.0 and symlinks. So.7 don't exist in Mageia 4 mirrors.
- I did upgrade Mageia 3 to Mageia 4 using urpmi on CLI.
- I know libosipparser2.so.7 was needed by linphone-3.5.2-5mga3
- I don't know which libosip, libosipparser and libeXosip are really needed by linphone-3.6.1 but it seems to me there is an error somewhere.

My apologies in advance if the culprit is not Linphone package...


Reproducible: 

Steps to Reproduce:
Manuel Hiebel 2014-02-05 00:26:12 CET

Keywords: (none) => Triaged
CC: (none) => fundawang

Comment 1 Jani Välimaa 2014-02-05 18:08:01 CET
Can't reproduce this on mga4. Nothing requires libosipparser2.so.7 on mga4. Is your system fully updated?
Comment 2 Gegetel 2014-02-05 18:58:01 CET
I am an idiot. Linphone launches perfectly when called /usr/bin/linphone. :-)
I forgot /usr/local/bin is before /usr/bin in my PATH, so I was attempting to launch a version of Linphone compiled on Mageia 3. Mea Culpa!
Comment 3 Sander Lepik 2014-02-05 18:59:50 CET
Closing..

Status: NEW => RESOLVED
CC: (none) => mageia
Resolution: (none) => INVALID


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