Red Hat Bugzilla – Bug 625249
[abrt] metacity-2.30.0-3.fc13: miRegionOp: Process /usr/bin/metacity was killed by signal 11 (SIGSEGV)
Last modified: 2011-06-07 08:12:11 EDT
abrt version: 1.1.13
Attached file: backtrace
reason: Process /usr/bin/metacity was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
How to reproduce
1. Clicked on the clock applet on the panel.
2. Clicked on the Edit button to update the locations available in the list.
3. At this point the crash happened.
Created an attachment (id=439547)
This and a couple of other crashes have disappeared and my system has been running stable over the last 3 days since I did the change as described in bug 625586, comment 3.
Hope this helps. Shall be monitoring my system over the next few days.
Please see my comment : bug 625586, comment 4.
This issue has also not shown up since the update mentioned in bug 625586, comment 4. I'll close off this bug in the near future if it does not manifest itself. Hope that is the correct thing to do.
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:
I believe the issue was down to bad hardware (RAM obviously).