Description of problem: After updating the installed mozilla and galeon components to errata versions, galeon hangs before drawing any windows. Five galeon-bin processes sit in a sleep state until killed with CTRL-C. The packages were upgraded to: nautilus-1.0.6-16 mozilla-nspr-1.0.1-2.7.3 mozilla-1.0.1-2.7.3 nautilus-mozilla-1.0.6-16 mozilla-nss-1.0.1-2.7.3 mozilla-psm-1.0.1-2.7.3 galeon-1.2.6-0.7.3 If started from a console, the following messages are displayed: [richard@holly richard]$ galeon ** CRITICAL **: file mozilla.cpp: line 134 (gboolean mozilla_preference_set (const char *, const char *)): assertion `new_value != NULL' failed. ** CRITICAL **: file mozilla.cpp: line 134 (gboolean mozilla_preference_set (const char *, const char *)): assertion `new_value != NULL' failed. ** CRITICAL **: file mozilla.cpp: line 134 (gboolean mozilla_preference_set (const char *, const char *)): assertion `new_value != NULL' failed. ** CRITICAL **: file mozilla.cpp: line 134 (gboolean mozilla_preference_set (const char *, const char *)): assertion `new_value != NULL' failed. ** CRITICAL **: file mozilla.cpp: line 134 (gboolean mozilla_preference_set (const char *, const char *)): assertion `new_value != NULL' failed. ** CRITICAL **: file mozilla.cpp: line 134 (gboolean mozilla_preference_set (const char *, const char *)): assertion `new_value != NULL' failed. Version-Release number of selected component (if applicable): galeon-1.2.6-0.7.3 How reproducible: Every time. Steps to Reproduce: 1. Update packages 2. Run Galeon 3. Actual results: No browser window. Expected results: A running browser. Additional info: I have noticed that if the ~/.galeon directory is moved to another name, galeon will draw all the initial preference setting windows but will still print the above critical errors before displaying the initial preference setting windows and fail to draw a browser window after clicking 'Finish'. I can supply an 'strace -ff' if it will help (~ 95k gzipped).
Do you have any plugins installed? Maybe the Java plugin, in particular? Try removing them or moving them to another location so they don't get picked up. Also, try re-running the mozilla-rebuild-databases.pl script to see if that helps.
Thanks for the suggestion. It was indeed the Java plugin that was stopping the browser window from appearing. Updating the rpms (The IBM ones) from 1.3-10.0 to 1.4-0.0 means I am now able to use galeon to submit this comment. I still get the above 'CRITICAL' errors, but so far their claimed seriousness seems somewhat exagerated.