Bug 6820 - ultrastardx cannot be run
Summary: ultrastardx cannot be run
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 2
Hardware: x86_64 Linux
Priority: Normal normal
Target Milestone: ---
Assignee: Mageia Bug Squad
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2012-07-18 20:55 CEST by Jan Merta
Modified: 2013-08-29 17:04 CEST (History)
5 users (show)

See Also:
Source RPM: ultrastardx
CVE:
Status comment:


Attachments

Description Jan Merta 2012-07-18 20:55:08 CEST
ultrastardx 1.1 4.mga2 cannot be run

trying to run in terminal gives error:

ultrastardx: relocation error: ultrastardx: symbol ffurl_register_protocol, version LIBAVFORMAT_53 not defined in file libavformat.so.53 with link time reference
Comment 1 Manuel Hiebel 2012-07-21 02:50:04 CEST
Hi, thanks for reporting this bug.
As there is no maintainer for this package I added the committers in CC.

(Please set the status to 'assigned' if you are working on it)

CC: (none) => balcaen.john, fundawang
Source RPM: (none) => ultrastardx

Comment 2 Michael Schütt 2013-01-21 10:41:17 CET
confirm this bug for Mageia 2 x86-64

CC: (none) => michael.schuett.lwl

Comment 3 Johnny A. Solbu 2013-03-28 18:03:00 CET
The problem is that ultrastardx depends on a fixed ffmpeg version. So when ffmpeg was updated, it broke ultrastardx.
Because of this, it will not be shipped in the next mageia 3.

And I don't know how to fix it for Mageia 2.

CC: (none) => johnny

Comment 4 Samuel Verschelde 2013-08-29 16:55:05 CEST
Wouldn't a simple rebuild do the trick?

CC: (none) => stormi

Comment 5 Samuel Verschelde 2013-08-29 17:04:10 CEST
Thinking twice, I guess you would already have thought of a rebuild if it would be enough. Closing as wontfix then, sorry Jan Merta, the upstream project didn't seem to make their software maintainable in the context of a linux distribution.

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


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