Bug 1756940 - linphone: symbol lookup error: /lib64/libmediastreamer_voip.so.3: undefined symbol: stunParseHostName
Summary: linphone: symbol lookup error: /lib64/libmediastreamer_voip.so.3: undefined s...
Keywords:
Status: CLOSED DUPLICATE of bug 1718221
Alias: None
Product: Fedora
Classification: Fedora
Component: linphone
Version: 31
Hardware: x86_64
OS: Linux
unspecified
high
Target Milestone: ---
Assignee: nucleo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-30 09:09 UTC by felix.bouynot
Modified: 2019-11-28 14:00 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-10-30 16:55:11 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description felix.bouynot 2019-09-30 09:09:09 UTC
Description of problem:
Linphone don't start int fedora31
Error message: linphone: symbol lookup error: /lib64/libmediastreamer_voip.so.3: undefined symbol: stunParseHostName

Version-Release number of selected component (if applicable):
linphone 3.6.1
ortp 0.24.2-2

How reproducible:
Everytime

Steps to Reproduce:
1. start linphone

Actual results:
linphone: symbol lookup error: /lib64/libmediastreamer_voip.so.3: undefined symbol: stunParseHostName

Expected results:
Linphone does start

Additional info:
We can't downgrade ortp in Fedora 31

Comment 1 Stuart D Gathman 2019-10-30 16:51:36 UTC
Sigh, ortp-0.24.2 claims to be binary API comaptible, but isn't.  We have to go back to 0.23.0 - or manage to get newer linphone compiled.  Since 0.24.2 has already been released, there is something complex needed to roll it back.  I think we need to increment an "epoch".  I'll ask on dev chat how to do that.

In the meantime, savvy users can downgrade to ortp-0.23.0.  For f31, it might be necessary to grap the ortp-0.23.0 rpm from f30.

Comment 2 Stuart D Gathman 2019-10-30 16:55:11 UTC

*** This bug has been marked as a duplicate of bug 1718221 ***


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