Red Hat Bugzilla – Bug 543533
[abrt] crash detected in gnash-0.9.0-0.6.20090809bzr11401.fc12
Last modified: 2010-03-25 13:29:14 EDT
abrt 1.0.0 detected a crash.
Attached file: backtrace
reason: Process was terminated by signal 6
Created attachment 375468 [details]
Created attachment 375469 [details]
Thank you for taking the time to report this issue to us. This is an issue
which is best addressed by the upstream developers. (Unfortunately, the
automated abrt tool cannot do this by itself.)
You encountered this issue with a prerelease of Gnash 0.8.6. The 0.8.6 release
is now available as an update for Fedora 12. Please check whether this issue is
still reproducible with the 0.8.6 release. If the issue is fixed, we will close
If this issue is still reproducible with the Gnash 0.8.6 release, please file a
report at https://savannah.gnu.org/bugs/?group=gnash (the upstream Gnash bug
tracker), and when done add the upstream report info to this report.
We will continue to track the issue in the centralized upstream bug tracker,
and will review any bug fixes that become available for consideration in future
Thank you for the bug report.
Gnash 0.8.7 is now available as an update for Fedora 13 Alpha, 12 and 11. Is this problem still reproducible after updating?
If it is still reproducible, please report the issue to the upstream Gnash project and provide a bug link in this bug report, as already requested in the initial needinfo request.
If it is no longer reproducible, please report this fact here so that we can close this bug as fixed by 0.8.7.
If you do not reply within 2 weeks, I will be forced to close this bug as INSUFFICIENT_DATA.
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received feedback to the
information we have requested above, we will assume the problem was not
reproducible, or has been fixed in one of the updates we have released for the
Users who have experienced this problem are encouraged to upgrade to the latest
update of their distribution, and if this issue turns out to still be
reproducible in the latest update, please reopen this bug with additional
Closing as INSUFFICIENT_DATA.