abrt 1.1.1 detected a crash.
Attached file: backtrace
cmdline: /usr/bin/convert -quality 80 -background white -size 85 /var/www/mediawiki/images/7/72/Wpdbc.jpg -thumbnail 85x119! -depth 8 -sharpen 0x0.4 /var/www/mediawiki/images/thumb/7/72/Wpdbc.jpg/85px-Wpdbc.jpg
reason: Process /usr/bin/convert was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
Created attachment 431925 [details]
Thank you for the bugreport.
How it reproducable?
Can you attach images on what it crashed?
This is happening when convert is making thumbnails for MediaWiki, and has something to do with a recent change in SELinux policy. Basically any image will trigger the problem. See Bug 611308 for more details about the SELinux change.
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '13'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 13's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 13 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
It looks like the issue is not ImageMagick, but a problem with ulimit permissions, see Bug 611308.