Bugzilla Bug 126309

Hi, I noticed something strange recently when running thunderbird.  I could
click on a link if firefox wasn't running, and firefox would start fine.  If I
clicked on a link once firefox was already running (and it would normally try
to open it in a new tab), if failed with the message "Firefox is already
running, but is not responding.  To open a new window, you must first close the
existing Firefox process, or restart your system."  Strangely liferea still
opened links fine, and there were no other problems.  Once the error dialog
showed up I ran ps aux and tried to replicate the command that was being run. 
This worked fine, so I'm assuming it's something about the environment that
thunderbird uses when making the call to firefox.

Finally I reverted to mozilla-launcher-1.49 and the problem vanished.  I check
the difference and it appears there's one line where previously mozbin had been
run with arguments and now it was being run with the MOZ_NO_REMOTE=1
environment variable and then the arguments.  There was one other minor change,
but I'm assuming this is the cause of it.  The comment says this is because of
bug 114683.  Since it seems such a specific change, I haven't bothered
including my emerge --info.  If it's needed, please ask.

If there's any further information I can provide to try and fix this problem,
please just let me know.  Thanks...

Hmm, indeed. Also I guess the functionality broken in this bug is much more
important than switching between some stupid profiles that are broken by design
anyway. Please, revert the change.

Fixed in 1.51, thanks

Just thought I would point out that bug 114731 reports that this problem was
due to an upstream bug.  That bug
(https://bugzilla.mozilla.org/show_bug.cgi?id=298960) is currently in a
re-opened state.

I see the same behavior reported here with 1.49 of mozilla-launcher even though
the reporter says that version works for him.

This leads me to suspect that there is a version depencency between
mozilla-launcher and firefox and that this bug may not be fixed in 1.51 for all
versions of firefox.  But, this is only speculation because I haven't tested
the combinations.

YMMV.