Bug 598195 - [abrt] crash in gnash-1:0.8.7-1.fc12: raise: Process /usr/bin/gtk-gnash was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in gnash-1:0.8.7-1.fc12: raise: Process /usr/bin/gtk-gnash was k...
Alias: None
Product: Fedora
Classification: Fedora
Component: gnash
Version: 12
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Kevin Kofler
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:1a06e05cf007b2ef2f420c908f4...
Depends On:
TreeView+ depends on / blocked
Reported: 2010-05-31 17:35 UTC by totti4343
Modified: 2010-12-03 14:09 UTC (History)
4 users (show)

Clone Of:
Last Closed: 2010-12-03 14:09:25 UTC

Attachments (Terms of Use)
File: backtrace (35.50 KB, text/plain)
2010-05-31 17:35 UTC, totti4343
no flags Details

Description totti4343 2010-05-31 17:35:25 UTC
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/gtk-gnash -x 77595554 -j 240 -k 200 -u http://www.cisco.com/assets/cdc_content_elements/flash/video-player/mediaplayer.swf?cacheReset=1275327255901-426 -F 15 -U http://www.cisco.com/en/US/products/ps5853/index.html -P allowfullscreen=true -P allowscriptaccess=always -P 'flashvars=width=240&height=200&callback=true&file=http://www.cisco.com/assets/cdc_content_elements/embedded-video/video-data-sheets/1800-isr.flv&image=http://www.cisco.com/assets/cdc_content_elements/embedded-video/video-data-sheets/1800-isr.jpg&pagename=Cisco 1800 Series Integrated Services Routers Video Data Sheet&sitearea=Products&contentgroup=&pagetype=video&basepage=http://www.cisco.com/en/US/products/ps5853/index.html&countrycode=US&captions=http://www.cisco.com/assets/cdc_content_elements/embedded-video/video-data-sheets/1800-isr-captions-US.xml' -P height=200 -P id=videoplayer -P name=videoplayer -P quality=high -P src=/cdc_content_elements/flash/video-player/mediaplayer.swf?cacheReset=1275327255901-426 -P style= -P type=application/x-shockwave-flash -P width=240 -P wmode=opaque -
component: gnash
crash_function: raise
executable: /usr/bin/gtk-gnash
global_uuid: 1a06e05cf007b2ef2f420c908f4b43e26e177716
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 totti4343 2010-05-31 17:35:27 UTC
Created attachment 418355 [details]
File: backtrace

Comment 2 Bug Zapper 2010-11-03 13:47:28 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: 

Comment 3 Bug Zapper 2010-12-03 14:09:25 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.