Description of problem:
It appears the ImageMagick-perl is no longer functioning on my system. I
believe this bug was most likely introduced with the August 23 ImageMagick
updates (126.96.36.199-4.2.1.fc5.4) as I know I have accessed the web pages that make
use of ImageMagick within the last two weeks and the only updates in the past
month to ImageMagick were the ones on August 23. If I can figure out where to
find the fc5.2 versions, I might try to revert to those.
Version-Release number of selected component (if applicable):
100% of the time on my system. I don't have access to any other FC5 systems
for other testing.
Steps to Reproduce:
1. Install ImageMagick and ImageMagick-perl on a x86_64 system.
2. From a prompt: perl -e 'use Image::Magick;'
perl: symbol lookup error: /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-
thread-multi/auto/Image/Magick/Magick.so: undefined symbol: InitializeMagick
I would expect that Perl not crash and that my scripts that use ImageMagick
would function properly.
I have verified the following dates and file sizes:
ls -l /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-
-r--r--r-- 1 root root 91 Aug 22 23:05 autosplit.ix
-r-xr-xr-x 1 root root 281888 Aug 22 23:06 Magick.so
ls -l /usr/lib64/perl5/vendor_perl/5.8.8/x86_64-linux-thread-multi/Image/
-r--r--r-- 1 root root 3220 Aug 22 23:00 Magick.pm
As always, huge thanks to whomever ends up resolving this - I'm a very happy
FC5 user, and I love that so many people spend their time to make it relatively
trouble free and easy to keep up-to-date!
I can confirm that reverting to 188.8.131.52-4.2.1.fc5.3 fixes the issue (but of
course leaves the machine vulnerable to the security issue that prompted the
I'm having this same problem on an i386 machine too.
Hmm, this is odd. There were no perl-related changes at all, and
the InitializeMagick symbol _is_ defined in libMagick.so. I'll have to
find an FC5 install for further debugging.
Imagemagick forum was topic about same problem, but it is removed.
There was conclude: if ithreads enabled in perl it breaks perlMagick.
If perl compiled witout ithread perlMagick works.
With all due respect, this bus is a picture perfect example of why Fedora has
gotten such a bad reputation in the community, and why people long time Red Hat
users are moving to other distros.
In his August 18 interview with slashdot:
Max Spevack stated in his answer to question #8 "...it gives me a chance to try
to bust the NUMBER ONE MYTH about Fedora -- that Fedora is "just a beta for
RHEL" or that "Fedora only exists to make Red Hat money" or "Red Hat doesn't
care about Fedora, it's just a dumping ground for half-tested code". I hear all
of those things from time to time, and *none* of them are true. "
This bug is one (of many) examples of half-tested (ie: not tested at all!) code
that was put up as an update to Fedora Core. It has now been 2 weeks since this
August 23rd announcement was posted:
One week after posting a completely broken update, Mattias writes back (see
comment 3 of this bug) that "I'll have to find an FC5 install for further
What? Are you serious? We are to trust Red Hat with these updates when the
person who posted unrunnable update to Image Magick does not have ready access
to a FC5 installation?
Max further stated in his interview, "We strive to produce a quality
distribution of free software that is cutting-edge, pushes the envelope of new
open source technology, and is also robust enough that it can be relied on for
server or desktop use."
Please, Mattias, fix this regression. This is not a corner case problem, IT IS
IMPOSSIBLE TO USE IMAGEMAGICK. As has been stated in the initial bug
description, the following command fails:
perl -e 'use Image::Magick;'
I will provide a testing box for you if necessary. What package set is required
for you to test/fix it?
* I can confirm this bug on a current system, FC5 as updated.
* However, on a FC5 system which has not been updated, I do not get
that error and the script runs nominally. It has:
* I can also confirm that the simple test
perl -e 'use Image::Magick;'
fails on the former system, and suceeds on the latter.
* Mr. Clausen's comment about having to borrow an FC5 box to test (# 3
above) makes me wonder how serious he is as a maintainer.
*** This bug has been marked as a duplicate of 203975 ***