Bug 624010

Summary: [abrt] crash in galeon-2.0.7-30.fc13: Process /usr/bin/galeon was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: James DeCambra <fedora>
Component: galeonAssignee: Yanko Kaneti <yaneti>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: yaneti
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:312bed850d5f5af5851b502a3f0b1997f8eaf714
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-09-28 09:40:58 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 James DeCambra 2010-08-13 12:28:25 UTC 
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: galeon
component: galeon
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/bin/galeon
global_uuid: 312bed850d5f5af5851b502a3f0b1997f8eaf714
kernel: 2.6.33.3-85.fc13.i686.PAE
package: galeon-2.0.7-30.fc13
rating: 4
reason: Process /usr/bin/galeon was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. not sure which bug this is for.  if for galeon then i was just playing scrabble on facebook
2.
3.
Comment 1 James DeCambra 2010-08-13 12:28:26 UTC 
Created attachment 438669 [details]
File: backtrace
Comment 2 Yanko Kaneti 2010-08-13 12:49:36 UTC 
glibc complaints like this one are usually caused by the java plugin but I can't tell for sure from the trace. We'll need a reproducible testcase not requiring logging into facebook or smiliar...

Thanks
Comment 3 Yanko Kaneti 2010-08-13 12:56:50 UTC 
*** Bug 624015 has been marked as a duplicate of this bug. ***
Comment 4 Yanko Kaneti 2010-08-13 13:10:22 UTC 
*** Bug 624024 has been marked as a duplicate of this bug. ***