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 1756660 - linphone fails to start citing undefined symbol
Summary: linphone fails to start citing undefined symbol
Keywords:
Status: CLOSED DUPLICATE of bug 1718221
Alias: None
Product: Fedora
Classification: Fedora
Component: linphone
Version: 31
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: nucleo
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-29 01:21 UTC by Harish Pillay
Modified: 2019-12-12 20:14 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-12-12 20:13:37 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Harish Pillay 2019-09-29 01:21:44 UTC 
Description of problem:


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


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Harish Pillay 2019-09-29 01:26:21 UTC 
[accidently clicked on submit]

Description of problem: Linphone fails to start in Fedora 31 beta


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

linphone-3.6.1-32.fc31.x86_64


How reproducible:

In Fedora 31 beta, start linphone in command line and it fails. Spits out: "linphone: symbol lookup error: /lib64/libmediastreamer_voip.so.3: undefined symbol: stunParseHostName"


Steps to Reproduce:
1. Have Fedora 31 beta running
2. Start linphone in terminal
3. linphone fails.

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


Expected results:
linphone should have started correctly and a GUI displayed.

Additional info:
Comment 2 nucleo 2019-09-29 19:37:52 UTC 
Can you try to downgrade ortp to ortp-0.23.0-9.fc30?
Comment 3 Stuart D Gathman 2019-09-29 21:00:33 UTC 
I thought I'd killed the newer ortp version.  The library correctly marks the incompatible API change with a new soname.  0.23.0 is libortp.so.9.0.0 and 0.27.0 is libortp.so.11.0.0.
Comment 4 nucleo 2019-09-29 21:04:15 UTC 
ortp-0.24.2-2.fc31 is in F31

https://koji.fedoraproject.org/koji/buildinfo?buildID=1332456

it have the same soname as 0.23.0

https://koji.fedoraproject.org/koji/rpminfo?rpmID=18384549
Comment 5 Stuart D Gathman 2019-09-30 13:48:21 UTC 
Sadly, 0.24.2 has the same soname, but it not compatible: https://bugzilla.redhat.com/show_bug.cgi?id=1718221

Maybe we should bundle ortp-0.23.0 and upgrade mailline ortp to 0.27.0.  I would suggest modules - but I am still struggling to understand what modules did to my Java package....
Comment 6 nucleo 2019-09-30 18:04:51 UTC 
I build for F32 linphone with oRTP included in linphone sources (looks like 0.22.0 there).
But oRTP 0.27.0 requires bctoolbox that is missing in repo now.
Comment 7 nucleo 2019-10-01 16:19:05 UTC 
Maybe also this should be added to linphone.spec?

Obsoletes: ortp <= 1:0.24.2-2
Obsoletes: ortp-devel <= 1:0.24.2-2
Provides: ortp = 1:0.24.2-2
Provides: ortp-devel = 1:0.24.2-2
Comment 8 Stuart D Gathman 2019-12-12 20:13:37 UTC 

*** This bug has been marked as a duplicate of bug 1718221 ***
Comment 9 Stuart D Gathman 2019-12-12 20:14:25 UTC 
Note, ortp has been patched and release on f31,f32
Note You need to log in before you can comment on or make changes to this bug.