Latest Greasemonkey breaks Firefox 3.6.2 on Solaris

[laxity]

After upgrading Firefox to 3.6 I found that it would start when
running it for the first time but trying to run it again anytime after
that it would fail. I discovered that the problem was being caused by
greasemonkey addon as disabling it allowed FF2.6 to start every time
without fail. Re-enable greasemonkey and Firefox 3.6 fails to start
again. Seems to only affect the Solaris release though. Looks like a
bug that needs fixing.

[Anthony Lieuallen]

On Tue, Mar 30, 2010 at 5:58 AM, laxity <richar...@sun.com> wrote:

 Seems to only affect the Solaris release though.

Can you provide any more detailed diagnostics?  I can't speak for everyone, but I certainly don't have a machine running Solaris to test this on.

[esquifit]

This is probably related to a similar problem with GM + FF 3.6 on Linux:

http://groups.google.com/group/greasemonkey-users/browse_thread/thread/8b3863f3a3362b00

Maybe some hard-coded file path or something like that?

[Anthony Lieuallen]

On 03/31/10 09:29, esquifit wrote:
> This is probably related to a similar problem with GM + FF 3.6 on Linux:
> http://groups.google.com/group/greasemonkey-users/browse_thread/thread/8b3863f3a3362b00
> Maybe some hard-coded file path or something like that?

The problem described in that thread happens only upon every other
launch (as I read it, assuming a forced-without-gm launch is run) so it
can't be some constantly wrong factor like a file path.

I'm running Firefox 3.6 on Ubuntu and see no such behavior, which
further discounts the possibility of always having a problem on any
unix/linux variant.

To anyone having this problem:
Could you go to www.mozilla.com and download their binary package, not
the one provided by your distribution? It can be extracted and run
completely standalone. Does it exhibit the same behavior?

[Bernd]

On 31 Mrz., 17:07, Anthony Lieuallen <arant...@gmail.com> wrote:
> The problem described in that thread happens only upon every other
> launch (as I read it, assuming a forced-without-gm launch is run) so it
> can't be some constantly wrong factor like a file path.

It sounds like the problem I am having. It will only start the first
time. After closing ff it won't ever start again until you force it to
run without gm. Then you can start it another time with gm, but again
only once.

> Could you go towww.mozilla.comand download their binary package, not

> the one provided by your distribution?  It can be extracted and run
> completely standalone.  Does it exhibit the same behavior?

I am having this problem with the ubuntuzilla script which will
download the original latest ff release from the mozilla site and
install it into /opt/firefox/ while leaving the original installation
of ff by the package manager untouched.

[laxity]

Thanks esquifit. Yes the problem is exactly the same issue as
mentioned in that Linux thread you mention.

Even better is that one post in that thread seems to have stumbled on
the cause which is that if your profile directory is symlinked to a
different location, Greasemonkey doesn't like this AFTER the first
start of Firefox and you have to disable Greasemonkey in order to get
Firefox to start again OR remove the symlink to your profile directory
and move it back to the correct location.

Not sure why Greasemonkey doesn't like symlinks, but clearly its a bug
that needs looking at.

Cheers,
Richard.

On Mar 31, 2:29 pm, esquifit <esqui...@googlemail.com> wrote:
> This is probably related to a similar problem with GM + FF 3.6 on Linux:
>

> http://groups.google.com/group/greasemonkey-users/browse_thread/threa...

[Anthony Lieuallen]

On 04/12/10 04:22, laxity wrote:
> ..

> Even better is that one post in that thread seems to have stumbled on
> the cause which is that if your profile directory is symlinked to a
> different location, Greasemonkey doesn't like this AFTER the first
> start of Firefox and you have to disable Greasemonkey in order to get
> Firefox to start again OR remove the symlink to your profile directory
> and move it back to the correct location.
>
> Not sure why Greasemonkey doesn't like symlinks, but clearly its a bug
> that needs looking at.

>..

To anyone experiencing this: There's no need to put a symlink where
your profile would go. You can edit ~/.mozilla/firefox/profiles.ini and
tell it to put your profile directly at any path you want. I've done
this to put my profile inside an encfs volume, rather than the default
location, for example. (Copy/move the existing profile to the new
location (if any) while Firefox is not running, edit profiles.ini,
restart Firefox, and the transition should be seamless. Or just point
it at an empty directory and it will create a new profile on launch.)