Hi
I am encountering serious problems at the moment.
I am using SuSe 10.1, but it looks as if the problem is not necessarily distribution depended, as I found some messages about my error in Ubuntu forums as well.
So, my problem is, when I try to start firefox and thunderbird, I receive the following error message:
in the case of thunderbird:
/opt/thunderbird/run-mozilla.sh: line 131: 6637 Segmentation fault "$prog" ${1+"$@"}
and with firefox
/opt/firefox/run-mozilla.sh: line 131: 6701 Segmentation fault "$prog" ${1+"$@"}

I have started firefox with a missing ".mozilla" in my home directory to make sure that no extensions are responsible. Besides that, I have reinstalled firefox but still have the same messages.

Apparantly, I am having the same or a similiar problem as the one dealt with in an old thread
http://www.linuxquestions.org/questi...d.php?t=302759
but unforturtunately there is no solution described.

As a result to all my googling, I am pessimistic. It looks as if the problem is widely known, but no solution!

Still, I am full of hope that somebody might be able to help me!

Regards

Bernard

Hmm - do you have Windows on that machine? Does it run its apps fine? Do OTHER apps in Linux run fine?

What version of Thunderbird and Firefox are you trying to get going? The newest ones? Older ones?

Have you run memchk68 on your system? A seg fault is sometimes the result of a bad RAM chip, although the more common cause is (of course) a programming error.

You could try the "pull out and reseat" trick with your RAM to see if that helps. Sometimes "bad RAM" is really just "badly seated RAM" with poor contact to the mother board.

Caution: Be sure to ground yourself (e.g., Touch the computer case if it's metal) before removing and reinserting the RAM board(s). A static discharge through a board can cause extreme problems.

Yesterday evening, I installed hundreds of new fonts. I never thought that this might effect some applications in such a way. One font was the culprit, it's "Amabile". So, don't trust such lovely names
Taking it out of the fonts pool and starting the following two commands again fixed everything:
fc-cache -f -v /usr/share/fonts
fonts-config