Error initializing DeveloperCompanion Extension. Narwhal for XULRunner Extension not installed or enabled!

[PDan]

Hello,
For about one week I get that error when trying to start
DeveloperCompanion.
Before that moment everything worked.
The error is displayed in the first tab in firefox (3.6.12, Windows
Vista 32)
Narwhal for XULRunner - 0.0.0master1011091417
DeveloperCompanion - 0.0.0master1011091424
If you need more info please tell me.

[Christoph Dorn]

Hmm. Could you try uninstalling the Narwhal and DeveloperCompanion
extensions and re-installing the companion:
http://www.christophdorn.com/Tools/

Also make sure they are enabled.

This is the first time this issue has been reported while both
extensions are installed. The only thing I could think of is that the
Narwhal extension is not enabled?

Christoph

--
http://www.ChristophDorn.com/Tools/

[PDan]

Finally I found a solution (uninstall/reinstall didn't work).
I found a file narwhal.json in my profile - after removing the file
everything is in order.
Thank you.

[Christoph Dorn]

Hmm. Thanks for letting me know.

Do you remember when you first installed FirePHP Companion? That file is
no longer auto-generated and only used if present, but it should not
cause the extension to fail. I am wondering what the contents was.

Christoph

--
http://www.ChristophDorn.com/Tools/

[PDan]

I had first FirePHP, then FireConsole Alpha, and then
DeveloperCompanion (I think it was abot 2-3 months ago?)
I believe FireConsole also installed some additional extension.
I think I have the file in the office in a backup.

PDan

On Nov 24, 8:58 pm, Christoph Dorn <christoph...@christophdorn.com>
wrote:

[Christoph Dorn]

On 10-11-24 8:54 PM, PDan wrote:
> I had first FirePHP, then FireConsole Alpha, and then
> DeveloperCompanion (I think it was abot 2-3 months ago?)
> I believe FireConsole also installed some additional extension.
> I think I have the file in the office in a backup.

If you have a spare minute it would be good to look at, but not essential.

I have modified the code that reads that config file to only look for
the debug and verbose flags ignoring the other config values (their
defaults have changed which I think is the reason for the issue you were
having). This will be deployed with the next release and likely save
others the same frustration you went through.

Thanks again for letting me know.

Christoph

--
http://www.ChristophDorn.com/Tools/

[Jochen]

I have this problem, too.
I have installed and deinstalled everything according to the
instructions but no avail.

Bye Jochen

[PDan]

Try to remove the file narwhal.json in your windows user/firefox user
profile.

[Jochen Schäfer]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Am 20.12.2010 19:12, schrieb PDan:
> Try to remove the file narwhal.json in your windows user/firefox user
> profile.

I already searched for that file, but couldn't find it.

Bye Jochen
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.10 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/

iQEcBAEBAgAGBQJND6T9AAoJED1xhplUkdnrs3sH/0DCBly3MzC5+bfvPmyvsBSz
bXOYai+NGRxMFDUx4V+CY3aC3BQiS+dKg49BRu45dRazR2t3qkc0yyoVFhDn/byV
GzkfKcuxpndiEPqx1qBwc2y6FcWU6oxCD1IXbqf3X9FcplQEO+x3E/H04j0iH/jt
61d9iQC9a+NPH/N4bbBEASYyGDVWLFCP/OQz5tqVJIl/G+z7bAQ08wLMJLhgokl7
KQysKTqv9sTxFT+rZCy2d59W2Ij5WvqB2Xd1ljeOTbaHWVejBaAttA4TILCT9mvH
WUUlYnbP12SRQasWJ0NHAhWycs4mYD8+VJ/ODA90RK/wlp9+NC1jxcDFqbxPwac=
=goIc
-----END PGP SIGNATURE-----

[Christoph Dorn]

The narwhal.json file should not affect this any more with recent releases.

I think it's a different issues. I have an install on one of my test
computers that is doing the same thing now. I'll troubleshoot that and
see what is going on. The issue is likely related.

It's probably going to take a couple of days.

As a workaround you could create a new firefox profile and install it
there. That should most definitely fix the issue as it's working on many
other installs.

Christoph

[Christoph Dorn]

I updated companion to the latest version on the install that was not
working before and it is working again now. Still not sure what was
wrong originally but the update seems to have fixed it. I don't think
it's anything in the update specifically but rather the fact that there
was an update and how firefox clears internal caches etc...

If it's still not working for you, can you try with a fresh firefox profile?

I'll be making some changes in January in relation to FF 4 support that
may resolve this issue if we cannot figure it out until then.

Christoph

[nobulart]

Hi Christopher

I'm experiencing the same problem with a clean Firefox profile.
This is my setup, and the extensions are all enabled :

Firefox 4.0b10 (Mac)
Firebug 1.7X.0a9
DeveloperCompanion 0.0.0master1101111422
Narwhal for XULRunner 0.0.0master1012021007

I have no other 3rd party extensions installed. As mentioned above, I
have started with a fresh profile in my efforts to overcome this
problem, but to no avail.

Perhaps you've gained some new insights into the causes of this in the
past month?

Thx. Craig

[Christoph Dorn]

Firefox 4 is not supported at this time.

Please use Firefox 3.6.

I hope to add support for Firefox 4 in February.

Christoph