Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.

Bug 1756940

Summary:	linphone: symbol lookup error: /lib64/libmediastreamer_voip.so.3: undefined symbol: stunParseHostName
Product:	[Fedora] Fedora	Reporter:	felix.bouynot
Component:	linphone	Assignee:	nucleo <alekcejk>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	31	CC:	alekcejk, fweimer, rakesh.pandit, stuart
Target Milestone:	---
Target Release:	---
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-10-30 16:55:11 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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 ***