[Linux] Solved: Firefox fails to start

User Help for Mozilla Firefox
Post Reply
IdOp
Posts: 28
Joined: May 16th, 2013, 12:42 pm

[Linux] Solved: Firefox fails to start

Post by IdOp »

For the past several weeks I've had a problem with Firefox crashing immediately at start-up on two of my Slackware Linux systems. In my investigations I found several similar problems reported elsewhere online, but either those reports went unanswered, or the answers they found didn't help me.

I've now found the cause of my Firefox problems, and just want to document the solution here, in case it helps someone else.

The Problems
The exact symptoms depend on which ff binary is used.

(a) Using the binary supplied by mozilla.org, a Crash Reporter window comes up giving the option to re-start or quit. Re-starting never works. The error message in the console is like this:

Code: Select all

ExceptionHandler::GenerateDump cloned child 1524
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...
(b) If I use the Slackware-supplied binary of ff-ESR, a blank browser window comes up, and the console fills with error messages like:

Code: Select all

Crash Annotation GraphicsCriticalError: |[0][GFX1-]: Failed to lock new back buffer. (t=3.49651)
The Solution
After a lot of tests, frustration and dead ends, I found the problem (which was the result of "administrator error" ..., i.e., my bad!). It had to do ultimately with lack of user write permissions on /dev/shm . Normally, Slackware will mount a tmpfs on /dev/shm with the following line in /etc/fstab:

Code: Select all

tmpfs           /dev/shm         tmpfs       defaults         0   0
At one point I'd turned this off, forgotten about it, and much later ff stopped working (I don't use it regularly). As a result of this, the permissions on /dev/shm were those found on the root filesystem:

Code: Select all

drwxr-xr-x 2 root root          40 Dec  3 04:55 /dev/shm
which don't allow users to write to this space. Once the tmpfs is properly mounted again, the permissions look like this:

Code: Select all

drwxrwxrwt 2 root root          40 Dec  4 14:42 /dev/shm
Now users can write there and Firefox is happy.
Post Reply