Firefox 3.0.1 Crashes

alkos333 · 08-28-2008, 09:54 AM

Firefox randomly crashes with the following message:

Code:

/usr/lib/firefox-3.0.1/crashreporter: error while loading shared libraries: libgconf-2.so.4: cannot open shared object file: No such file or directory
/usr/lib/firefox-3.0.1/run-mozilla.sh: line 131: 14522 Segmentation fault      "$prog" ${1+"$@"}

I also got the following in the dmesg:

Code:

Aug 28 09:51:44 localhost kernel: firefox-bin[14523] general protection eip:af7e3344 esp:b60fec48 error:70

adriv · 08-28-2008, 10:29 AM

Have you tried a new profile?

alkos333 · 08-28-2008, 11:34 AM

Yes, there was a patch that came along with 3.0.1 update for -current provided by Pat.

adriv · 08-28-2008, 03:24 PM

That's not the same.

Try a brand new profile, it'll probabbly work fine. Later on (if everything is OK) you can copy your bookmarks file from the old to the new profile.

shadowsnipes · 08-30-2008, 10:38 PM

I've never seen that error in using Firefox 3 on various profiles/machines/configurations.

Hopefully a new profile should fix that for you. Even if it doesn't, it takes almost zero time to create a new profile to check it out...
The firefox 3 package for Slackware is not significantly patched. The newest patch just makes sure that mailto links are handled properly (FF 3 style).

If a new profile isn't the fix then either you consistently corrupt your profiles, or your firefox installation was messed up (unlikely if using Pat's package), or you messed around with some libraries that are giving FF grief.

Speaking of profiles and such, there is a lot more useful information that you might want to transfer from an old profile besides bookmarks. A whole thread could be devoted to that subject, however.

alkos333 · 09-11-2008, 09:02 AM

Well, I tried disabled FireGPG plug-in and guess what, it's been over a week and haven't had a single crash yet.

shadowsnipes · 09-11-2008, 02:34 PM

Quote:

Originally Posted by alkos333

Well, I tried disabled FireGPG plug-in and guess what, it's been over a week and haven't had a single crash yet.

Good to hear that it looks like you found the source of the problem. That is still an experimental addon, by the way.

I would contact the addon author about your problems to see if they can be resolved.