It had a virus.

OK - it got sick. Where is the replacement that goes with Linux Firefox ver.48? Firefox is basically useless without it.

xpcom is packaged into the installer, it isn't sold separately...

As a Windows user, I don't know the best procedure for a "clean" install on Linux. If there's nothing in the general article (Install Firefox on Linux), hopefully a Linux user can give you more specific advice.

But generally speaking, you would remove just the program directory (not your data), and run the installer again. It should detect your data automatically.

Still, wouldn't hurt to do a backup: Back up and restore information in Firefox profiles.

Norseman01 said

downloaded Linux update ver.48 firefox. fires up - spits out XPCOM not found and terminates. ver.17 had similar problem. it could not find the libxpcom.so in firefox directory. ver.48 - xpcom is no where to be found.

I use 64-bit Linux and 64-bit Firefox and I see you have 32-bit Linux. I tried to run the 32-bit Firefox on my 64-bit Linux and I get the Couldn't load XPCOM error.

So are you trying to run the 64-bit Firefox on 32-bit Linux?

Look at https://www.mozilla.org/en-US/firefox/all/ for the Linux row without the 64 mention as far right row is the 64-bit builds.

James - The location you offer is where I got the problem in the first place. I did get the 32bit part right then. I just double checked. SO-- I get a no XPCOM on the 32bit platform and you get the same trying that same package on the 64bit platform. I assume the 64bit has no such problem? I unpacked and ran grep and got no hits on the 32bit platform. looks as if it got a virus, died and was buried. Guess anf25 is not completely wrong. :)

I have the libxpcom.so from ver.17... Wonder how much havoc it would wreck to try it?

Anybody got a good guess?

The only time I have encountered the Couldn't load XPCOM error is when say accidentally trying to run 32-bit version on 64-bit Linux.

anf25 was just posting short mostly random replies as it is a virus was a common one posted.

Turns out that file was no where near the problem. I got hit with a scam. After chasing in circles for way too long I bought another router of same Manufacturer but a step or two down. Read it's manual, then found and read my make and model manual and simply did the "reset to factory" followed by the Manufacturer's suggested login to the router and reload of the basics and everything is back to normal. Since they live on the other side of the planet there is a good chance I'll never get to deliver them some pain. But I can always wish. :)