Bug 592524

Summary: [abrt] crash in gnash-1:0.8.7-1.fc12: raise: Process /usr/bin/gtk-gnash was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: __UNIX_hokum <antenna-5>
Component: gnashAssignee: Kevin Kofler <kevin>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: jreznik, kevin, pertusus, tomeu
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:2745b447edbc3992f9cc190e5883b86a0f3193d4
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-25 09:13:44 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description __UNIX_hokum 2010-05-15 05:08:30 UTC 
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/bin/gtk-gnash -x 0 -j 0 -k 0 -u about:blank -F 12 -U http://wg216.odnoklassniki.ru/dk?st.cmd=userMain&tkn=6408#st.cmd=altGroupMembers&st.groupId=osifdmgbdyznrjelzk0rteazbfiqlitkhbjphu&st.page=673 -P allowscriptaccess=always -P height=0 -P id=StorageMovie -P src=about:blank -P swliveconnect=0 -P type=application/x-shockwave-flash -P width=0 -
component: gnash
crash_function: raise
executable: /usr/bin/gtk-gnash
global_uuid: 2745b447edbc3992f9cc190e5883b86a0f3193d4
kernel: 2.6.32.11-99.fc12.i686.PAE
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 __UNIX_hokum 2010-05-15 05:08:34 UTC 
Created attachment 414215 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 09:13:44 UTC 

*** This bug has been marked as a duplicate of bug 585780 ***
Comment 3 Karel Klíč 2010-05-25 09:13:44 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #585780.

Sorry for the inconvenience.