filter_logoaway: unresolved symbol DestroyConstitute

Bug #539106 reported by Oliver Cordes
12
This bug affects 2 people
Affects Status Importance Assigned to Milestone
librmagick-ruby (Ubuntu)
Fix Released
Medium
Unassigned
Lucid
Won't Fix
Medium
Unassigned
transcode (Ubuntu)
Invalid
Undecided
Unassigned
Lucid
Invalid
Undecided
Unassigned

Bug Description

[Impact]
<fill me in with explanation of severity and frequency of bug on users and justification for backporting the fix to the stable release>

[Development Fix]
<fill me in with an explanation of how the bug has been addressed in the development branch, including the relevant version numbers of packages modified in order to implement the fix. >

[Stable Fix]
<fill me in by pointing out a minimal patch applicable to the stable version of the package.>

[Text Case]
<fill me in with detailed *instructions* on how to reproduce the bug. This will be used by people later on to verify the updated package fixes the problem.>
1.
2.
3.
Broken Behavior:
Fixed Behavior:

[Regression Potential]
<fill me in with a discussion of likelihood and potential severity of regressions and how users could get inadvertently affected.>

[Original Report]

Binary package hint: transcode

Hi,

using the logoaway filter in transcode produces the following error:

[transcode] warning: Unable to load filter logoaway: /usr/lib/transcode/filter_logoaway.so: undefined symbol: DestroyConstitute

This is also known for other distribution (e.g. Debian) which I think is then an upstream problem. The problem with filter_logoway is that during the compilation there is no check of all used external funtions. A couple of months ago the API of imagemagick has changed and DestroyConstitute() was replaced by ConstituteComponentTerminus() .

So, the solution is to change the in line 868 of filter/filter_logoaway.c

DestroyConstitute(); <--> ConstituteComponentTerminus();

I found this in the 10.04 development version, but as I said this error may exist also in older distributions as well.

>lsb_release -rd
Description: Ubuntu lucid (development branch)
Release: 10.04

The hint in the change of the imagemagick API I found on launchpad as well:

https://code.launchpad.net/~ubuntu-branches/ubuntu/lucid/dx/lucid

Maybe it is worth to check other packages in lucid as well before the final release!

Oliver

Tags: patch
Revision history for this message
Marco Cimmino (cimmo) wrote :
Revision history for this message
Marco Cimmino (cimmo) wrote :

Sorry I meant that same issue affects package: librmagick-ruby and the patch to fix it is above ^.
Please fix!

tags: added: patch
Revision history for this message
Clint Byrum (clint-fewbar) wrote :

Marco, can you provide a snippet of Ruby that reproduces this issue so that we can have a clear test case for it?

The patch looks fine and I'll work on building a source package to upload to lucid-proposed soon, but without a repeatable test case it won't be possible to verify it.

Changed in librmagick-ruby (Ubuntu Lucid):
status: New → Confirmed
Changed in librmagick-ruby (Ubuntu):
status: New → Confirmed
Changed in transcode (Ubuntu Lucid):
status: New → Confirmed
Changed in transcode (Ubuntu):
status: New → Confirmed
Revision history for this message
Marco Cimmino (cimmo) wrote :

I cannot share the code I use, but I will try to make a simple example.

Revision history for this message
Marco Cimmino (cimmo) wrote :

Here we go, you need a png file called example.png, whatever image should work ok.
Launch then inside the dir with: ruby example.rb

and observe the issue, thanks.

Revision history for this message
Marco Cimmino (cimmo) wrote :
Revision history for this message
Marco Cimmino (cimmo) wrote :

Packaged my self since no sign of life here:
http://www.marcocimmino.net/2011/07/30/librmagick-ruby-for-ubuntu-lucid-32-bit-with-destroyconstitute-missing-symbol-fixed/

I didn't add the patch but applied right away.
Ubuntu please fix this broken package in your latest LTS release!!!

Revision history for this message
Alessio Treglia (quadrispro) wrote :

Hi,

thanks for the report.

Could you try to reproduce this with the latest upstream release available in Quantal?

Changed in transcode (Ubuntu):
status: Confirmed → Incomplete
Revision history for this message
Marco Cimmino (cimmo) wrote :

Alessio, this bug is gone after Lucid, the point of the ticket is you left a LTS release with a package that is useless because doesn't use the correct APIs.

You used a bunch of packages that were incompatible between them!
Changing tickets to incomplete after so many months is just embarassing, after we provided even the patch.

Plus Quantal is totally off topic here.

Revision history for this message
Alessio Treglia (quadrispro) wrote :

Sorry, it's my fault, it was a kind of automatic message.

The suggested patch looks good to me, so I'm closing the bug assigned to transcode and subscribing the sponsors team to fix the issue in librmagick-ruby.

Thanks for the great work!

Changed in transcode (Ubuntu):
status: Incomplete → Invalid
Changed in transcode (Ubuntu Lucid):
status: Confirmed → Invalid
Changed in librmagick-ruby (Ubuntu):
importance: Undecided → Medium
status: Confirmed → Fix Released
Changed in librmagick-ruby (Ubuntu Lucid):
importance: Undecided → Medium
Bryce Harrington (bryce)
description: updated
Revision history for this message
Stefano Rivera (stefanor) wrote :

Unsubuscribing ubuntu-sponsors. Please re-subscribe them whin this is ready for review.

Revision history for this message
Rolf Leggewie (r0lf) wrote :

lucid has seen the end of its life and is no longer receiving any updates. Marking the lucid task for this ticket as "Won't Fix".

Changed in librmagick-ruby (Ubuntu Lucid):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.