Bug 597259

Summary: [abrt] crash in galeon-2.0.7-27.fc13: Process /usr/bin/galeon was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Marian-Nicolae ION <marian_ion>
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: i686   
OS: Linux   
Whiteboard: abrt_hash:c35bcdb154b5376d4ad615573479eed08d1e13d1
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-29 12:07:31 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 Marian-Nicolae ION 2010-05-28 14:14:12 UTC 
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: galeon -n http://fetchyahoo.sf.net
component: galeon
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/bin/galeon
global_uuid: c35bcdb154b5376d4ad615573479eed08d1e13d1
kernel: 2.6.33.4-95.fc13.i686.PAE
package: galeon-2.0.7-27.fc13
rating: 4
reason: Process /usr/bin/galeon was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1.rpm -qi <package> (in a console)
2.click on the link displayed on URL
3.
Comment 1 Marian-Nicolae ION 2010-05-28 14:14:14 UTC 
Created attachment 417624 [details]
File: backtrace
Comment 2 Yanko Kaneti 2010-05-28 14:36:44 UTC 
This looks like bug 577103
can you try removing ~/.galeon/mozilla/galeon/compreg.dat to work around the crash?
Comment 3 Marian-Nicolae ION 2010-05-28 20:18:52 UTC 
Package: galeon-2.0.7-27.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
click on a link in "google gadgets"
Comment 4 Marian-Nicolae ION 2010-05-29 11:18:41 UTC 
Well, Id didn't wait too much - I needed to search something on the net, so I deleted the whole ~/.galeon folder and, of course, it started working again...
Comment 5 Yanko Kaneti 2010-05-29 12:07:31 UTC 
Ok, I'll assume its the same thing. 
Thanks.

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