Bug 624010 - [abrt] crash in galeon-2.0.7-30.fc13: Process /usr/bin/galeon was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in galeon-2.0.7-30.fc13: Process /usr/bin/galeon was killed by s...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: galeon
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Yanko Kaneti
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:312bed850d5f5af5851b502a3f0...
: 624015 624024 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-13 12:28 UTC by James DeCambra
Modified: 2010-09-28 09:40 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-09-28 09:40:58 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (62.77 KB, text/plain)
2010-08-13 12:28 UTC, James DeCambra
no flags Details

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


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