Closed Bug 388990 Opened 18 years ago Closed 10 years ago

problem with loading chrome from extension gives little or no information

Categories

(Toolkit :: Startup and Profile System, defect)

x86
macOS
defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: ray, Unassigned)

Details

(Keywords: testcase-wanted)

I am having a problem with the packaging of an extension I am creating. I can run it in "developer" mode, ie using a file in the extensions directory to point to the development directory. When I jar up the chrome, create an xpi and install it that way, it does not load. All I see that (as far as I can tell) points to the problem is a single line of output. If I turn on logging and see the 1000+ lines of output one then gets, I see: WARNING: NS_ENSURE_TRUE(NS_SUCCEEDED(rv)) failed: file nsChromeRegistry.cpp, line 1249 Hm. Not extremely helpful. I am not, in this bug, asking for help with getting this extension to load. I am saying that there has got to be a little bit more information here that can be written out so that one can have a hope of seeing what is going on. Throw us a bone, please! Is the problem with a bad format of one of the XML files? Is the problem that the jar referred to in the chrome.manifest is in the wrong place? Is the problem that the jar contains the wrong stuff? Is the problem that the install.rdf is incomplete or points to missing files? Just give us a hint. Any information at all would be more helpful than what I am seeing now.
if not proper component, please adjust
Component: Embedding: Packaging → Startup and Profile System
Product: Core → Toolkit
QA Contact: packaging → startup
Ray do you still see this problem? If you do, please attach testcase. If you do not, please close the bug. Thanks
Flags: needinfo?(ray)
Keywords: testcase-wanted
Whiteboard: [closeme 2015-12-23]
Resolved per whiteboard
Status: NEW → RESOLVED
Closed: 10 years ago
Flags: needinfo?(ray)
Resolution: --- → INCOMPLETE
Whiteboard: [closeme 2015-12-23]
You need to log in before you can comment on or make changes to this bug.