Bug 588136 - [abrt] crash in gnash-1:0.8.7-1.fc12: Process /usr/bin/gtk-gnash was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in gnash-1:0.8.7-1.fc12: Process /usr/bin/gtk-gnash was killed b...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: gnash
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Kevin Kofler
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:401c62fac4e028a7044832578d9...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-02 20:13 UTC by wcschumacher
Modified: 2010-12-03 15:10 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-12-03 15:10:55 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (26.06 KB, text/plain)
2010-05-02 20:13 UTC, wcschumacher
no flags Details

Description wcschumacher 2010-05-02 20:13:14 UTC
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/gtk-gnash -x 75497652 -j 659 -k 518 -u http://d1.scribdassets.com/ScribdViewer.swf -F 12 -U http://www.scribd.com/doc/6921299/Basic-Data-Structure-codes-in-C -P align=middle -P allowfullscreen=true -P allowscriptaccess=always -P bgcolor=#ffffff -P devicefont=false -P flashvars=&viewMode=list&auto_size=false&disable_related_docs=true&privacy=1&docinfo=6FVkXls6AQp151eVEiDYMmHCj8fXhN8VkEGqp%2Fr1%2BTb4O3ddOjmnb1r0wYqTrCt%2FF2t90FW0YQn4quS0SGWPp1juBcypJRz34y2A1pBlnb8qtgx9erjC2oE9z7PYA8BJ970IjsPKM9R06RPPKDmE5ZQbjanH8e7gO9Vngh9P1DabmJcsE9BKFeCCCcWTgZHG6hayc%2F8nCCvgANvoJwRgkInjAWI3v0cif08TQOY2JlMAHkF7MOjTK27QZWCg8f5g7EqDcoH1JASEDevCIiixp6hEIPmtm3FBU4YFBngrXn4fhOTS9wN8faxXkg%2FOve%2FNlPQTwOstO4dCZjN%2Fv%2BdjaYV3j3%2FkeioeH8yRVaIoSqKJvNhnG7NdJrGRhb55VYvLTEkpjzhtAfi%2FyYKKp9o4t1r2HO%2BP7naeKAXXaoCLwnv6Cde0kNZWKcRtfw%2BJsZ%2Bb535ocr2VUC%2BYCkivPS8GsCoN0Xz0KZoYZcLTvHUomdDwjm9F2Z%2BJiYh1nian0k3dRBh6FC07zzzssFuV%2BCfPKCxi4Kgwc6zd85jzOSsP1LPQhRK43gLmZtxd3EdukI9flYB%2F5qzc0oAFrjnIr8VUM0vogErfZobVX%2BXenY1b%2FZ0iRC4mfDVSDiNi8G861geks0WsJiE27dqwn4fBVBpOeMWRfPQv9SVbJ20re2vyv6fu4I1gRmruywC736FpaoVc8Zu4JDjtoj8i5bscRwos%2B6opz3ho2SmgER1WKM01M4VbFyvAdrGkihpzlB0sHx9oz7KDzEbftlWSP9x6dodBFE8j97L7XnSgl6qHyC9URog%2F%2FRwFmnmScMfGCxv%2FX57kPKnIv4moDKOuU3SUSMZa%2FP%2FWSQZ%2Fl%2BcIhB9MqvR4Ek8sHXmnGf9lYUo7%2BCyvlEwRAvNBdJs5h3T6Jvi4c0XQjrNWsQseNOmuqgMNnpN4u3%2BXgrZatzjOttP%2FIcrhDjwx3R%2FWw%2FnCot1D%2BL0biWe64LCduBHXPPBMcAGm20ugmrt1vOxgauovOtWA%2BK6R0SvRnsUpzABgsj2x%2Bd0XZDQqV42P9CGFJPbxKG9mgl1GlVZECpB80mZnU4ihlZFfU9oCWDE4u25RFEJkkTca%2Fs6QbLNuZk9j1Y4RkKnkpEtOH8cWol4wFrtHKwpc%2BrTEwfH6eF6P7t6VdX6azNhLZOUyUWpbI0GfwZ4MGVxT5DIkJp%2BTg1kRFEknpm112%2FbWW69nTc6JJUZDo9o%2Bq1L5YdG9buLAtZwFsfLvfhFPikBDtwhnBb044BGmgvxh9K1OQD%2B4NBdeO3HNlFsnSI7XjF8lRng1lJ83ouOb3VWHYvuHTVoAv%2Fkhm8%2BGKu9D2ucY8XZQa6IS0aUFeJC%2F10kOBSNpDoboEUCGQ%2BCfLAUGphs8XzeE3%2F7huh9zDrZuZG6yEq8uQZJ5cyHcgGvIPYdmgrfHpsHEKtOdOfzVuhdZgwewF2XdnHw72t5mPxL6MJFW5uNEz9gnV5RvX%2FGh7QemNvYM%2F8IUyZ56twpGSA%2BJalN3qOHhOpDUPtk9DbtzaCZ6QUpxY8Ccat8WV7DrZunjLN7lVNT%2BMorb%2BzrvpGWulylpNMsSa8T
component: gnash
executable: /usr/bin/gtk-gnash
global_uuid: 401c62fac4e028a7044832578d96f7aee912fd9b
kernel: 2.6.32.11-105.fc12.x86_64
package: gnash-1:0.8.7-1.fc12
rating: 4
reason: Process /usr/bin/gtk-gnash was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)

Comment 1 wcschumacher 2010-05-02 20:13:19 UTC
Created attachment 410849 [details]
File: backtrace

Comment 2 Kevin Kofler 2010-05-05 11:53:57 UTC
Thank you for taking the time to report this issue to us. This is an issue
which is best addressed by the upstream developers.

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. (Unfortunately, the automated abrt tool cannot do this by itself.)

If you do not report this bug upstream, we will be forced to close it as INSUFFICIENT_DATA.

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
updates.

Thank you for the bug report.

Comment 3 Dave Gordon 2010-05-08 23:42:02 UTC
Package: gnash-1:0.8.7-1.fc12
Architecture: x86_64
OS Release: Fedora release 12 (Constantine)


Comment
-----
This time was on site - you-tube but gnash crashed

Comment 4 Bug Zapper 2010-11-03 15:49:06 UTC
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

Comment 5 Bug Zapper 2010-12-03 15:10:55 UTC
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.


Note You need to log in before you can comment on or make changes to this bug.