Bugzilla will be upgraded to version 5.0. The upgrade date is tentatively scheduled for 2 December 2018, pending final testing and feedback.
Bug 596092 - [abrt] crash in galeon-2.0.7-27.fc13: Process /usr/bin/galeon was killed by signal 11 (SIGSEGV)
[abrt] crash in galeon-2.0.7-27.fc13: Process /usr/bin/galeon was killed by s...
Status: CLOSED DUPLICATE of bug 577103
Product: Fedora
Classification: Fedora
Component: galeon (Show other bugs)
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Yanko Kaneti
Fedora Extras Quality Assurance
Depends On:
  Show dependency treegraph
Reported: 2010-05-26 05:57 EDT by Dan Horák
Modified: 2010-05-26 07:21 EDT (History)
1 user (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2010-05-26 07:21:53 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
File: backtrace (43.19 KB, text/plain)
2010-05-26 05:58 EDT, Dan Horák
no flags Details

  None (edit)
Description Dan Horák 2010-05-26 05:57:58 EDT
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: galeon
component: galeon
crash_function: nsProfileLock::FatalSignalHandler
executable: /usr/bin/galeon
global_uuid: df821c99d49f293e7bd5256c4b7b2642a8726a8b
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. try to start Galeon
Comment 1 Dan Horák 2010-05-26 05:58:02 EDT
Created attachment 416745 [details]
File: backtrace
Comment 2 Yanko Kaneti 2010-05-26 06:47:46 EDT
Most likely a dup of bug 577103.
Could you try if removing 
~/.galeon/mozilla/galeon/compreg.dat  works around it ?
Comment 3 Dan Horák 2010-05-26 07:00:57 EDT
yes, after removing the file galeon can start
Comment 4 Yanko Kaneti 2010-05-26 07:21:53 EDT
Thanks. This needs chasing up in mozilla land, for which I don't really have the capacity right now. Insight and patches welcome.

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

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