175474 - Failure with javascript when trying to add new search plugin

Status: RESOLVED DUPLICATE of bug 171441

(Core :: XPCOM, defect)

Description

[Paul Millar]

Using mozilla 1.2beta

When you click the javascript link on http://mycroft.mozdev.org to add a new
search plugin to Mozilla the following error comes up in the javascript console:

Error: uncaught exception: [Exception... "Component returned failure code:
0x80040154 (NS_ERROR_FACTORY_NOT_REGISTERED) [nsIDOMWindowInternal.sidebar]" 
nsresult: "0x80040154 (NS_ERROR_FACTORY_NOT_REGISTERED)"  location: "JS frame ::
http://mycroft.mozdev.org/ :: addEngine :: line 112"  data: no]

Also occurs on my own site http://www.edazzle.net/noogle/noogle.asp when trying
to detect Mozilla browser in javascript usinf window.sidebar. Following error
shows up in javascript console:

Error: uncaught exception: [Exception... "Component returned failure code:
0x80040154 (NS_ERROR_FACTORY_NOT_REGISTERED) [nsIDOMWindowInternal.sidebar]" 
nsresult: "0x80040154 (NS_ERROR_FACTORY_NOT_REGISTERED)"  location: "JS frame ::
http://www.edazzle.net/noogle/noogle.asp :: <TOP_LEVEL> :: line 124"  data: no]

Comment 1

[Phil Schwartau]

---> Sidebar

Comment 2

[Erich 'Ricky' Iseli]

Unable to reproduce on Mozilla 1.2beta, Linux. I've successfully installed the
Kuro5hin plugin, while keeping an eye on the JavaScript console: no message in
there.

Reporter, I suggest you make a new profile and try to see if you can reproduce
that. Also, if you can tell what plugin you tried to install, maybe the
situation will be different.

Also, I haven't been able to reproduce the second javascript error message on
the noogle website.

Comment 3

[Phil Schwartau]

Note these bugs mentioned the same kind of error:

bug 171612 
"mozilla 2002092808 has javascript problems when searching..."
bug 172475
"quicksearch no longer works after mozilla 1.2a "


They both were fixed by the technique discovered in:

bug 171441
"Unable to download files - 2002092804 [installer] build for Windows"


That techique was to delete a file called "compreg.dat" and 
re-starting Mozilla. See, for example, bug 171441 comment #103.

Paul, does that solve the problem for you?
On this theory, reassigning to XPCOM Registry component -

Comment 4

[Phil Schwartau]

Really reassigning -

Comment 5

[Paul Millar]

Deleting 'compreg.dat' has solved the problem.

Thanks.

Comment 6

[Phil Schwartau]

Paul: thanks for trying that. Resolving this bug as a duplicate of bug 171441.

*** This bug has been marked as a duplicate of 171441 ***