abrt detected a crash. Attached file: backtrace cmdline: metacity component: metacity executable: /usr/bin/metacity kernel: 2.6.31.5-127.fc12.i686 package: metacity-2.28.0-9.fc12 rating: 4 reason: Process was terminated by signal 11
Created attachment 374317 [details] File: backtrace
Looks like memory corruption; crash is inside calloc(). Possibly not a pulseaudio-libraries issue, but it's the prime suspect since that is the immediately precedoing code, and I haven't seen any memory-corruption crashes reported elsewhere in metacity.
*** Bug 545420 has been marked as a duplicate of this bug. ***
*** Bug 547890 has been marked as a duplicate of this bug. ***
Hmm, any chance anyone can reproduce this inside of valgrind?
Since we've had only three reported examples of this in the last month, with no clear instructions to reproduce, I think it's a little unlikely anybody is going to be able to reproduce on this demand. But if anybody wants to try, basic instructions are: [ as root ] yum install yum-utils debuginfo-install metacity yum install valgrind [ as user ] valgrind metacity --replace > /tmp/metacity-valgrind.log 2>&1 Then try to get Metacity to crash (this probably will leave you without a window manager, since the 'metacity --replace' call will break the auto-restart that is normally happens, in that case it may be easiest to log out and log back in.) If you succeed in crashing, then attach the log file. (It's possible that Valgrind might catch problems even when Metacity doesn't crash, but it takes an expert eye to distinguish real problems from false positives, so it's probably not useful to attach log files where Metacity doesn't crash.)
*** Bug 548727 has been marked as a duplicate of this bug. ***
*** Bug 550726 has been marked as a duplicate of this bug. ***
*** Bug 551812 has been marked as a duplicate of this bug. ***
*** Bug 551977 has been marked as a duplicate of this bug. ***
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: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.