abrt version: 1.1.13 architecture: x86_64 Attached file: backtrace cmdline: /usr/lib64/cinepaint/0.22-1/plug-ins/jpeg -gimp 15 13 64 64 component: cinepaint crash_function: raise executable: /usr/lib64/cinepaint/0.22-1/plug-ins/jpeg kernel: 2.6.33.6-147.2.4.fc13.x86_64 package: cinepaint-libs-0.22.1-14.fc12 rating: 4 reason: Process /usr/lib64/cinepaint/0.22-1/plug-ins/jpeg was killed by signal 6 (SIGABRT) release: Fedora release 13 (Goddard) time: 1282301231 uid: 500 How to reproduce ----- 1.Just started the program. 2. 3.
Created an attachment (id=439972) File: backtrace
Package: cinepaint-libs-0.22.1-14.fc12 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.started cinepaint 2. 3.
*** Bug 606167 has been marked as a duplicate of this bug. ***
*** Bug 620230 has been marked as a duplicate of this bug. ***
*** Bug 622133 has been marked as a duplicate of this bug. ***
*** Bug 628107 has been marked as a duplicate of this bug. ***
*** Bug 629409 has been marked as a duplicate of this bug. ***
*** Bug 631979 has been marked as a duplicate of this bug. ***
*** Bug 635621 has been marked as a duplicate of this bug. ***
*** Bug 637382 has been marked as a duplicate of this bug. ***
*** Bug 643623 has been marked as a duplicate of this bug. ***
*** Bug 650530 has been marked as a duplicate of this bug. ***
*** Bug 549707 has been marked as a duplicate of this bug. ***
*** Bug 601302 has been marked as a duplicate of this bug. ***
Short story: ------------- Here are cinepaint updates, please give them test - feedback is awaited: https://admin.fedoraproject.org/updates/cinepaint-0.25.0-0.1.fc15 https://admin.fedoraproject.org/updates/cinepaint-0.25.0-0.1.fc14 https://admin.fedoraproject.org/updates/cinepaint-0.25.0-0.1.fc13 In a day or so , You should be able to do: yum update --enablerepo=updates-testing cinepaint\* Long Story: ---------- Cinepaint upstream hasn't seen a clear 'source code release' since a lot of time. So I couldn't have rebased on this release to provide an update for Fedora. Instead, I've provided an pre-release snapshot of the 0.25 version which should fix most of the experienced bug. I cannot triage every single abrt reports, so I will close the bugs to current release. But please reopen if you are abble to reproduce. I will try to get better care then. Thx for your understanding and sorry for the lack of answer until now.