After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 86312 - Galeon crash just after first window appears
Galeon crash just after first window appears
Status: RESOLVED OBSOLETE
Product: galeon
Classification: Deprecated
Component: Mozilla interaction
1.2.5
Other All
: Normal critical
: ---
Assigned To: Philip Langdale
Yanko Kaneti
: 77278 92315 105529 107034 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2002-06-24 08:10 UTC by Gyles Harvey
Modified: 2003-09-10 23:01 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Gyles Harvey 2002-06-24 08:10:45 UTC
I'm seeing the following assert failure fairly regularly:

** ERROR **: file main.c: line 789 (galeon_exit): assertion failed:
(g_list_length (all_embeds) == 0)
aborting...

I'm building Galeon agains GNOME 1.4 and Mozilla 1.0

Thanks.
Comment 1 Ben FrantzDale 2002-07-02 21:14:04 UTC
I get the same behavior sometimes. It's just after starting galeon;
the window opens, but then it crashes. Removing the .galeon directory
fixes the problem, but it develops again from time to time.

I think it has always happened after a *normal* exit, but I'm not sure.
Comment 2 Gyles Harvey 2002-07-03 07:54:14 UTC
That sounds about right. I tried just removing the session* files
this time and that seemed to work too.
Comment 3 Ben FrantzDale 2002-07-18 00:22:20 UTC
I changed the summary to be more clear.

I'm still getting this. I have the contents of three .galeon
directories which cause this problem if someone want's to have a go at
them.
Comment 4 Ben FrantzDale 2002-08-02 20:42:30 UTC
I've discovered that deleting ~/.galeon/mozilla cures the problem
(narrowed down from just ~/.galeon).

I've tried to narrow the problem down more but have had marginal luck.
I think ~/.galeon/mozilla/galeon/prefs.js is doing it, althoguh it
doesn't look corrupted.

The following prefs.js is what is generated when none exists. It works
properly:

# Mozilla User Preferences
// This is a generated file!

user_pref("helpers.global_mailcap_file", "");
user_pref("helpers.global_mime_types_file", "");
user_pref("helpers.private_mailcap_file", "");
user_pref("helpers.private_mime_types_file", "");
user_pref("keyword.URL", "http://www.google.com/search?q=");
user_pref("keyword.enabled", true);
user_pref("mozilla.widget.raise-on-setfocus", false);
user_pref("network.dir.generate_html", true);
user_pref("security.checkloaduri", false);
user_pref("wallet.captureForms", false);
user_pref("xpinstall.enabled", false);

The following, however, breaks:

# Mozilla User Preferences
// This is a generated file!

user_pref("browser.anchor_color", "#0000FF");
user_pref("browser.display.use_document_fonts", 0);
user_pref("browser.download.dir", "~");
user_pref("browser.visited_color", "#FF0000");
user_pref("dom.disable_open_during_load", true);
user_pref("font.default", "sans-serif");
user_pref("general.useragent.override", "Mozilla/5.0 Galeon/1.2.5
(X11; Linux i
86; U;) Gecko/20020610 Debian/1.2.5-1");
user_pref("helpers.global_mailcap_file", "");
user_pref("helpers.global_mime_types_file", "");
user_pref("helpers.private_mailcap_file", "");
user_pref("helpers.private_mime_types_file", "");
user_pref("intl.charset.default", "ISO-8859-1");
user_pref("intl.charset.detector", "");
user_pref("keyword.URL", "http://www.google.com/search?q=");
user_pref("keyword.enabled", true);
user_pref("mousewheel.withaltkey.sysnumlines", true);
user_pref("mousewheel.withcontrolkey.action", 3);
user_pref("mousewheel.withshiftkey.action", 1);
user_pref("mousewheel.withshiftkey.sysnumlines", true);
user_pref("mozilla.widget.raise-on-setfocus", false);
user_pref("network.cookie.cookieBehavior", 0);
user_pref("network.dir.generate_html", true);
user_pref("plugin.soname.list", "libXt.so:libXext.so");
user_pref("security.checkloaduri", false);
user_pref("signon.SignonFileName", "28316193.s");
user_pref("wallet.captureForms", false);
user_pref("xpinstall.enabled", false);

However, after trying to figure it out I went through commenting out
lines and couldn't narrow it down.

Can someone test the above prefs.js and see if it works?
I'm using galeon 1.2.5 from debian.
Comment 5 Ben FrantzDale 2002-08-16 22:50:44 UTC
OK. I'm now getting this even after running (from ~/.galeon):
rm -rf mozilla/ session_crashed.xml session*

What did make it work was
rm -rf mozilla/ session_crashed.xml session* images/

Which then caused it to start up as though I had never used it before.

Am I the only one getting this?
Comment 6 Yanko Kaneti 2002-09-02 10:35:49 UTC
*** Bug 92315 has been marked as a duplicate of this bug. ***
Comment 7 Yanko Kaneti 2002-12-11 14:16:49 UTC
*** Bug 77278 has been marked as a duplicate of this bug. ***
Comment 8 Yanko Kaneti 2003-02-07 21:51:54 UTC
*** Bug 105529 has been marked as a duplicate of this bug. ***
Comment 9 Yanko Kaneti 2003-02-26 04:36:46 UTC
*** Bug 107034 has been marked as a duplicate of this bug. ***
Comment 10 Philip Langdale 2003-04-22 21:07:25 UTC
It has been suggested to me that this is caused by history.xml
corruption, as reported by James Slorach ( jrs47 at janx dot org ).

>I have encountered this bug (with Galeon 1.2.6), and was able to work 
>around it by removing .galeon/history.xml (the history had grown quite 
>large (5711078 bytes), and removing it also cut the start up time 
>sigificantly)

On the one hand, this is a good diagnosis and work around if valid. On
the other, we really shouldn't be corrupting the history, or at least
should handle corruption more elegantly.
Comment 11 Crispin Flowerday (not receiving bugmail) 2003-09-10 23:01:40 UTC
Mass close of gnome 1.[0-2] bugs (search for "galeon 1.x bug closeathon")

It has been decided that there will be no future bug fixes for versions prior to
the current 1.3. Although I have tried not to close still relevant bugs, if you
can reproduce this bug with the current galeon version (1.3.8 or later) and
mozilla 1.4 or later please do the following:

Search on bugzilla.gnome.org for galeon bugs, there may be another bug that is
still open.

Failing that please re-open this bug and add the steps to reproduce, and a small
testcase (along with the versions of galeon and mozilla you tested it with)