Bug 625847

Summary: [abrt] galeon-2.0.7-30.fc13: Process /usr/bin/galeon was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: John Kissane <john.kissane>
Component: galeonAssignee: Yanko Kaneti <yaneti>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 13CC: yaneti
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:2404f2ceb3a7b3dc8bec1bb0027fa09057fb40dc
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-08-23 08:24:45 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 John Kissane 2010-08-20 15:33:29 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: galeon /home/jkissane/.evolution/cache/tmp/evolution-jkissane-heV6Bi/apns-20100820161756.xml
component: galeon
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/bin/galeon
kernel: 2.6.33.6-147.2.4.fc13.x86_64
package: galeon-2.0.7-30.fc13
rating: 4
reason: Process /usr/bin/galeon was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1282318238
uid: 2283

How to reproduce
-----
1. Double clicked on an xml attachment in evolution & the galeon crash was reported.
2.
3.
Comment 1 John Kissane 2010-08-20 15:33:32 UTC 
Created an attachment (id=439976)
File: backtrace
Comment 2 Yanko Kaneti 2010-08-20 17:03:21 UTC 
It looks like bug 577103
Have you used galeon previously ? i.e. do you have an old galeon profile in ~/.galeon/
Can you try removing ~/.galeon/mozilla/galeon/compreg.dat  and then try the same thing again.
Comment 3 John Kissane 2010-08-23 08:17:50 UTC 
Thanks for the suggestion, it's highly likely I've use Galeon before as my home directory has been used for Fedora 10,11,12 & now 13. Removing that file has stopped the crash in any case.
Comment 4 Yanko Kaneti 2010-08-23 08:24:45 UTC 
Thanks for the feedback

*** This bug has been marked as a duplicate of bug 577103 ***