Timestamp: 4/23/2012 8:09:57 AM
Error: Error installing app: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIWindowsRegKey.open]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: resource:///modules/WebappsInstaller.jsm :: <TOP_LEVEL> :: line 224" data: no]
Source File: resource:///modules/WebappsInstaller.jsm
Which app(s) did you try to install? And from which website (f.e. marketplace-dev.allizom.org)? And while running which nightly build? A bit more information would be most helpful. ;-)
Not getting a reproduction of this bug on Win 7 64-bit with the current nightly. Anant could you clarify the following things:
- What build are you running (e.g. the latest nightly)
- If the problem still reproduces with the current nightly
- Reproduction steps
Sorry, I mostly just wanted to log the error message so we don't forget. The problem occurred on Todd's Windows Laptop this morning, and he will followup with information on his setup shortly.
Windows: Win 7, version 6.1
Nightly: 14.0a1 (2012-04-23)
Tried: Lord of Ultima, Boston Globe, GodFather, Lanyard, etc....
Reproduce: click install on any app. Gives error message "App Installation not allowed"
The error occurs when installing an app from anywhere (I just tried installing one from the mozillalabs appdir). It's the latest nightly from today.
I have a hunch that this has something to do with permissions (the current user being unable to write to the registry), or that the registry is just corrupt.
(In reply to Anant Narayanan [:anant] from comment #5)
> I have a hunch that this has something to do with permissions (the current
> user being unable to write to the registry), or that the registry is just
That's the line of code where the failure is occurring. Does not look like it happens on every machine, only certain Windows machines. I agree with Anant - Sounds like this might be a permissions issue. Tim - Any ideas?
Looking at the code a bit more, it looks like we're checking the registry to see if the app was previously installed and if so, we remove it. I think failure to do so shouldn't raise an error in the install process, or maybe we can punt on it until later on when we try to add a registry key?
Anyway, that's just a band-aid, we still have to figure out the core problem of why that Component is failing on that particular Windows setup.
I just tested this on a Win 7 machine and got an App manifest is invalid error.
This is what I see in the error console when I tried to install the Evernote app:
marketplace-dev.allizom.org : server does not support RFC 5746, see CVE-2009-3555
stage.evernote.com : server does not support RFC 5746, see CVE-2009-3555
According to SUMO, it appears this may be related to some issue with Java? Really? http://support.mozilla.org/en-US/questions/746438
I was able to successfully install Sandglaz, but Evernote and Boston Globe failed.
The CVE messages are just warnings, they are not the cause of the problem.
(In reply to Ragavan S [:rags] from comment #11)
> I was able to successfully install Sandglaz, but Evernote and Boston Globe
Sounds like what you are describing an existing marketplace dev bug - bug 747252.
Hmm. I got an idea for testing that might reveal the root cause of this issue - We had a problem in the past with the extension involving "fresh" builds of windows 7 I think that involved registry keys (bug 723355). As a result, the application could not be installed on the user's machine. However, when they installed Chrome on their machine, a certain registry key was written, which as a result, lead to allowing app installations.
First, do we know if logic behind bug 723355 was taken into account in the new implementation? Checking the diff, I wonder if this is correct. Myk or Tim - Could you take a look at the patch on that bug and comment here on your opinion?
I'll see if I get a fresh build of Windows 7 to test this.
Todd - Could you give me more details on the machine information - Things like how long you've had the windows 7 OS installed, how old the machine is, whether you've installed Chrome on that machine or not, etc.
Followup questions to comment 14:
Myk or Tim - If the registry key in comment 6 doesn't exist, do we ensure we create it to avoid erroring out?
Todd - We might want to look at the windows registry on your machine.
Created attachment 618366 [details] [diff] [review]
Straightforward. The code that _creates_ the key had no problem dealing with the nonexistent key, it's only the code that tries to clean-up a previous installation first that wasn't coping well.
Comment on attachment 618366 [details] [diff] [review]
Review of attachment 618366 [details] [diff] [review]:
Tested locally and chatted with Felipe about the patch. Looks good!
*** Bug 749100 has been marked as a duplicate of this bug. ***
Verified through Todd today in the apps show and tell.