Bug 678380 - [abrt] ImageMagick-6.6.4.1-15.fc14: Process /usr/bin/display was killed by signal 6 (SIGABRT)
Summary: [abrt] ImageMagick-6.6.4.1-15.fc14: Process /usr/bin/display was killed by si...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: ImageMagick
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Pavel Alexeev
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:5c6eee73b2733baffc37723463f...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-17 18:17 UTC by Dimitri Papadopoulos
Modified: 2011-06-29 15:37 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-29 15:37:04 UTC
Type: ---


Attachments (Terms of Use)
File: backtrace (44.84 KB, text/plain)
2011-02-17 18:17 UTC, Dimitri Papadopoulos
no flags Details

Description Dimitri Papadopoulos 2011-02-17 18:17:10 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: display Dimitri66.png
component: ImageMagick
executable: /usr/bin/display
kernel: 2.6.35.11-83.fc14.x86_64
package: ImageMagick-6.6.4.1-15.fc14
reason: Process /usr/bin/display was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
How to reproduce: 1. Trying to draw on an image read from a PNG file.
time: 1297966121
uid: 500

Comment 1 Dimitri Papadopoulos 2011-02-17 18:17:13 UTC
Created attachment 479375 [details]
File: backtrace

Comment 2 Pavel Alexeev 2011-02-20 18:49:52 UTC
Please provide image on what it is reproduced.

Additionally please check if it reproduced on version in rawhide.

Comment 3 Pavel Alexeev 2011-06-24 05:41:17 UTC
Try new build http://koji.fedoraproject.org/koji/taskinfo?taskID=3157603

Comment 4 Dimitri Papadopoulos 2011-06-24 05:46:51 UTC
This was an isolated crash and don't have a way to reproduce the problem. I cannot find the PNG file anymore. I cannot recall how it occurred exactly. I'm sorry. Anyway I hope this new build fixes the problem.

Comment 5 Pavel Alexeev 2011-06-29 15:37:04 UTC
Ok, then I close it now.

Please do not hesitate open it if problem appeared again.


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