Bug 577103

Summary: [abrt] crash on startup in galeon fc13 after update (old compreg.dat break)
Product: [Fedora] Fedora Reporter: David Le Sage <dlesage>
Component: galeonAssignee: Yanko Kaneti <yaneti>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: high Docs Contact:
Priority: high    
Version: 13CC: dan, dlstripes-fedorabugs, fcbugz, fonya, glandauer, hany, jdragone, john.kissane, marian_ion, pekkas, redhat_bugzilla, tomek.by, waltsaw, yaneti
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:a64d06f7d3236015de12cd8e160c0e184686316d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-06-27 15:18:01 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
Attached again. none

Description David Le Sage 2010-03-26 06:28:49 UTC
abrt 1.0.8 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: galeon
component: galeon
executable: /usr/bin/galeon
kernel: 2.6.33-1.fc13.i686.PAE
package: galeon-2.0.7-25.fc13
rating: 3
reason: Process /usr/bin/galeon was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Tried to launch Galeon

Comment 1 David Le Sage 2010-03-26 06:28:51 UTC
Created attachment 402755 [details]
File: backtrace

Comment 2 David Le Sage 2010-03-26 06:29:17 UTC

How to reproduce
-----
1. Tried to launch Galeon

Comment 3 Yanko Kaneti 2010-03-26 15:12:08 UTC
I can't reproduce this in a F13 testing vm. Tried if it had something to do with prelink but also saw no problems. 
galeon-2.0.7-25.f13.i686
xulrunner-1.9.2.2-1.f13.i686

Maybe somehow you ended up with a different xulrunner? Its quite important that galeon runs on top the exact same xulrunner it was built against.

Can you try 
rpm -V galeon xulrunner

Comment 4 David Le Sage 2010-03-27 05:33:56 UTC
Yes, I can confirm it is definitely xulrunner-1.9.2.2-1.f13.

Comment 5 Yanko Kaneti 2010-03-27 08:47:29 UTC
1) Can you still reproduce this ?
2) if (1) Can you verify that galeon and xulrunner are in tact ?
 rpm -V galeon xullrunner
3) try perlink -ua (unding prelink on all) and then again rpm -V

3) if (2) doesn't help can you move your ~/.galeon somewhere temporarily and see if it fixes the startup ?
4) if (3) fixes the startup, then perhaps you could send me a tarred copy of ~/.galeon (of course sanitized of personal stuff) so that I can try to reproduce this somehow ?

Comment 6 David Le Sage 2010-03-28 22:22:51 UTC
Hello Yanko.


I followed your instructions and once I moved ~/.galeon elsewhere, it finally loaded, so it must be a problem with my personal config settings.


Note that I moved to Fed 13 alpha via running preupdate on F12, so it might be a legacy setting.  I will attach a copy of it for you in a few moments.

Comment 8 Yanko Kaneti 2010-03-29 16:00:11 UTC
Hello, 
I think the attachment didn't make it.

I suspect just removing ~/.galeon/mozilla/galeon/compreg.dat
might be enough to fix the crash.

Comment 9 David Le Sage 2010-03-29 23:38:10 UTC
It is attached but I set it as private.  Perhaps you do not have the security permissions to see it.  Okay, I will attach it again.  It does not contain any confidential data, anyway.

Comment 10 David Le Sage 2010-03-29 23:39:47 UTC
Created attachment 403388 [details]
Attached again.

Comment 11 Yanko Kaneti 2010-03-30 05:05:50 UTC
Thanks. Finally, I am able to reproduce it. And indeed its compreg.dat thats causing it, so just removing ~/.galeon/mozilla/galeon/compreg.dat is enough to  work around it , until the next time when a xulrunner upgrade causes the same thing)

I'll try investigate why the mozilla embedding code fails to deal with this itself or is there something galeon should be doing to force a registry rebuild.
Any help or insight welcome.

Comment 12 Yanko Kaneti 2010-03-30 09:12:55 UTC
*** Bug 570897 has been marked as a duplicate of this bug. ***

Comment 13 Yanko Kaneti 2010-05-26 11:21:53 UTC
*** Bug 596092 has been marked as a duplicate of this bug. ***

Comment 14 Daniel Stripes 2010-05-28 13:33:35 UTC
Package: galeon-2.0.7-27.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


Comment
-----
Attempted to start galeon for first time since upgrade from f12 to f13.

Comment 15 Yanko Kaneti 2010-05-29 12:07:31 UTC
*** Bug 597259 has been marked as a duplicate of this bug. ***

Comment 16 Daniel Stripes 2010-05-29 23:47:43 UTC
(In reply to comment #14)
> Package: galeon-2.0.7-27.fc13
> Architecture: x86_64
> OS Release: Fedora release 13 (Goddard)
> 
> 
> Comment
> -----
> Attempted to start galeon for first time since upgrade from f12 to f13.    

I uninstalled galeon, mv'd ~/.galeon to ~/.galeon_old, reinstalled galeon, and then started galeon without error/fault.

I then checked and found that I have xulrunner-1.9.2.3-1.fc13.x86_64 installed.

Haven't the opportunity to examine my compreg.dat contents yet.

Comment 17 Yanko Kaneti 2010-05-30 19:46:35 UTC
*** Bug 597411 has been marked as a duplicate of this bug. ***

Comment 18 Yanko Kaneti 2010-05-31 05:56:14 UTC
*** Bug 597909 has been marked as a duplicate of this bug. ***

Comment 19 Yanko Kaneti 2010-05-31 06:08:25 UTC
*** Bug 597961 has been marked as a duplicate of this bug. ***

Comment 20 Roger Moore 2010-06-02 04:36:46 UTC
Package: galeon-2.0.7-27.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


Comment
-----
Program crashed on startup

Comment 21 Yanko Kaneti 2010-06-02 06:52:55 UTC
*** Bug 598280 has been marked as a duplicate of this bug. ***

Comment 22 Yanko Kaneti 2010-06-02 06:53:49 UTC
*** Bug 598435 has been marked as a duplicate of this bug. ***

Comment 23 Peter Hanecak 2010-06-17 19:12:14 UTC
Package: galeon-2.0.7-27.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. start Galeon
2. it wont come up, it crashes



Comment
-----
First attampt to dtart Galeon after upgrade from Fedaro 12 to Fedora 13. In Fedora 12, Galeon worked well.

Comment 24 Peter Hanecak 2010-06-20 19:32:02 UTC
Removing ~/.galeon allows the Galeon to start. Be that and ugly solution causing loss of bookmarks and settings.

Removing just ~/.galeon/mozilla/galeon/compreg.dat works too. And bookmarks and settings are there.

Thank you for help. :)

Comment 25 Yanko Kaneti 2010-07-30 21:03:26 UTC
*** Bug 619634 has been marked as a duplicate of this bug. ***

Comment 26 Yanko Kaneti 2010-08-23 08:24:45 UTC
*** Bug 625847 has been marked as a duplicate of this bug. ***

Comment 27 jdragone 2010-09-23 20:38:46 UTC
Package: galeon-2.0.7-30.fc13
Architecture: x86_64
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. solo inicie el galeon y se cayo
2.
3.


Comment
-----
siempre se cae el galeon al arrancar

Comment 28 Yanko Kaneti 2010-10-01 08:54:24 UTC
*** Bug 639242 has been marked as a duplicate of this bug. ***

Comment 29 Bug Zapper 2011-06-02 15:54:37 UTC
This message is a reminder that Fedora 13 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 13.  It is Fedora's policy to close all
bug reports from releases that are no longer maintained.  At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '13'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 13's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we may not be able to fix it before Fedora 13 is end of life.  If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora please change the 'version' of this 
bug to the applicable version.  If you are unable to change the version, 
please add a comment here and someone will do it for you.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 30 Bug Zapper 2011-06-27 15:18:01 UTC
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is 
no longer maintained, which means that it will not receive any further 
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of 
Fedora please feel free to reopen this bug against that version.

Thank you for reporting this bug and we are sorry it could not be fixed.