Note: This is a beta release of Red Hat Bugzilla 5.0. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Also email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback here.
Bug 598502 - [abrt] crash in gnash-1:0.8.7-1.fc13: raise: Process /usr/bin/gtk-gnash was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in gnash-1:0.8.7-1.fc13: raise: Process /usr/bin/gtk-gnash was k...
Alias: None
Product: Fedora
Classification: Fedora
Component: gnash
Version: 13
Hardware: x86_64
OS: Linux
Target Milestone: ---
Assignee: Kevin Kofler
QA Contact: Fedora Extras Quality Assurance
Whiteboard: abrt_hash:6935247624b309d6ca2287949d3...
Depends On: 626352
TreeView+ depends on / blocked
Reported: 2010-06-01 14:14 UTC by Fabien Archambault
Modified: 2010-12-11 15:38 UTC (History)
3 users (show)

Fixed In Version: 0.8.8
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-12-11 15:38:25 UTC

Attachments (Terms of Use)
File: backtrace (deleted)
2010-06-01 14:14 UTC, Fabien Archambault
no flags Details

Description Fabien Archambault 2010-06-01 14:14:26 UTC
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/bin/gtk-gnash -x 38597954 -j 1 -k 1 -u about:blank -F 84 -U -P id=flash_object_old -P pluginspage= -P quality=high -P src=about:blank -P 'style=position: absolute; top: 1px; left: 1px; height: 1px; width: 1px;' -P type=application/x-shockwave-flash -
component: gnash
crash_function: raise
executable: /usr/bin/gtk-gnash
global_uuid: 6935247624b309d6ca2287949d3fc1f22b918cc9
package: gnash-1:0.8.7-1.fc13
rating: 4
reason: Process /usr/bin/gtk-gnash was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
1. Login or closing tab in gmail

Comment 1 Fabien Archambault 2010-06-01 14:14:30 UTC
Created attachment 418653 [details]
File: backtrace

Comment 2 Fabien Archambault 2010-08-24 07:19:39 UTC
This crash seems to be corrected with the update of gnash to 0.8.8 (in koji)

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