abrt 1.1.0 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: mono --debug /usr/lib64/beagle/DocExtractor.exe /tmp/tmp29465827.doc component: mono crash_function: IA__g_malloc executable: /usr/bin/mono global_uuid: b1e30e5bc6c4487485b913657321dfce25572e06 kernel: 2.6.33.4-95.fc13.x86_64 package: mono-core-2.6.1-2.fc13 rating: 4 reason: Process /usr/bin/mono was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard)
Created attachment 417734 [details] File: backtrace
Package: mono-core-2.6.1-2.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. nothing .. just booted and it appeared. 2. 3.
Package: mono-core-2.6.1-2.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.crash after cp dozen gigabytes to another ext4 partition Comment ----- seems no apparant reason?
Package: mono-core-2.6.1-2.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Unknown - no operator intervention involved 2. 3. Comment ----- No user/operator actions involved except that it happened while using yum to remove outdated kernel packages soon after restarting the system.
Package: mono-core-2.6.1-2.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Install DropBox 2. Have DropBox sync 3. Comment ----- Syncing files with dropbox. What's interesting is that this didn't occur on my laptop which is similarly configured. Both are running fedora 13 x86_64
Package: mono-core-2.6.1-2.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- Beagle was indexing my home folder
Package: mono-core-2.6.1-2.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. It reproduces itself, every few seconds. 2. 3. Comment ----- I installed a bunch of packages, including mono and beagle. I rebooted and logged into Gnome and the ABRT icon was on the panel. As I'm writing, ABRT announces a new crash of mono-core every few seconds.
*** Bug 597373 has been marked as a duplicate of this bug. ***
*** Bug 610985 has been marked as a duplicate of this bug. ***
*** Bug 584257 has been marked as a duplicate of this bug. ***
*** Bug 596139 has been marked as a duplicate of this bug. ***
*** Bug 596409 has been marked as a duplicate of this bug. ***
*** Bug 596708 has been marked as a duplicate of this bug. ***
*** Bug 599028 has been marked as a duplicate of this bug. ***
*** Bug 599029 has been marked as a duplicate of this bug. ***
*** Bug 608102 has been marked as a duplicate of this bug. ***
*** Bug 612980 has been marked as a duplicate of this bug. ***
*** Bug 644834 has been marked as a duplicate of this bug. ***
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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.