On current nightly and aurora builds, Firefox will fail to start with "Couldn't load XPCOM" under these conditions:
1) The executable is loaded from the users PATH,
...and...
2) There is a file called "firefox" in the current working directory
This is because if you pass a relative path to realpath, it will resolve the path if the file exists in the current working directory. This causes mozilla::BinaryPath::Get() to return the wrong path.
This was reported to https://launchpad.net/bugs/809384 by Ben, who experienced this because he has a folder named "firefox" in his home directory. This is enough to prevent a current aurora build from starting
On current nightly and aurora builds, Firefox will fail to start with "Couldn't load XPCOM" under these conditions:
1) The executable is loaded from the users PATH,
...and...
2) There is a file called "firefox" in the current working directory
This is because if you pass a relative path to realpath, it will resolve the path if the file exists in the current working directory. This causes mozilla: :BinaryPath: :Get() to return the wrong path.
This was reported to https:/ /launchpad. net/bugs/ 809384 by Ben, who experienced this because he has a folder named "firefox" in his home directory. This is enough to prevent a current aurora build from starting