Comment 25 for bug 93546

Might it be possible to have an interim 'solution' that would keep both sides
happy?

For sites where Mozilla is used by technically unsavvy users, the prompt to
setup a new profile leads to headaches for support staff, and everyone I've
asked would settle for a message that says "Close the other Mozilla first"
instead of the new profile setup prompt.

Another solution would be a simple prefs.js setting to disable the locking.
Those of us following this and related bug reports that have a problem with
the new locking behaviour are fully aware of the risk of profile corruption
and yet are willing to take that risk (primarily because the alternative
really isn't an alternative), and a means to disable it would make us happy
campers again.