Red Hat Bugzilla – Bug 600721
[abrt] crash in mono-core-126.96.36.199-1.fc12: Process /usr/bin/mono was killed by signal 11 (SIGSEGV)
Last modified: 2010-11-03 14:50:42 EDT
abrt 1.0.9 detected a crash.
Attached file: backtrace
cmdline: f-spot /usr/lib64/f-spot/f-spot.exe --import gphoto2:[usb:000,000]
comment: had picture open. dragged open dialog across picture went to open another picture and crashed.
reason: Process /usr/bin/mono was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
Created attachment 421475 [details]
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12. 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 '12'.
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 12'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 12 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:
havent used f-spot much in fc13/fc14 but the few times i have there was no error so closing as nextrelease unless someone else has had the problem in fc13/fc14.
if anyone still has this error in fc13/fc14 then let me know and i will re-open and bump the version of this bug.
let me know.