1236816 - Add-on file cannot be installed from network folder with NS_ERROR_FILE_ACCESS_DENIED: Component returned failure code: 0x80520015

Status: RESOLVED INACTIVE

(Toolkit :: Add-ons Manager, defect, P2)

Description

[magicp]

User Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:46.0) Gecko/20100101 Firefox/46.0
Build ID: 20160104030217

Steps to reproduce:

1. Save any add-ons (e.g. Adblock Plus) xpi file from AMO to network folder.
2. Run Nightly 46.0a1
3. Select Menu > File > Open File... (or Ctrl+O)
4. Open the add-on file in network folder


Actual results:

No response after step 4. The following error is displayed in Browser Console.

NS_ERROR_FILE_ACCESS_DENIED: Component returned failure code: 0x80520015 (NS_ERROR_FILE_ACCESS_DENIED) [nsIWebNavigation.loadURIWithOptions]1 browser-child.js:306:0

However it works fine with below steps.
1. Open Add-ons Manager
2. Select menu "Install Add-ons From File..." in header-util-button
3. Open the add-on file in network folder


Expected results:

Add-on could be installed from accessible network folder without any errors.

Comment 1

[Dave Townsend [:mossop]]

Can you open html files from the network drive in the same way?

Comment 2

[Dave Townsend [:mossop]]

What URL is loaded in the tab when you do this?

Do you have e10s enabled?

Comment 3

[magicp]

(In reply to Dave Townsend [:mossop] from comment #1)
> Can you open html files from the network drive in the same way?

No, I can't any html files.

Comment 4

[magicp]

(In reply to Dave Townsend [:mossop] from comment #2)
> What URL is loaded in the tab when you do this?
> 
> Do you have e10s enabled?

"about:home", "https://bugzilla.mozilla.org" etc...
Good question! I have e10s enabled. It works in non-e10s window.

Comment 5

[magicp]

inbound regression window
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=c1795d9a7b427da6f9b699015a52dece05ce221d&tochange=56e6914c51a78ed06d3f949127ccf20df08665a6

Comment 6

[Andy McKay]

QA can you reproduce this?

Comment 7

[magicp]

Reconfirm regression range:
https://hg.mozilla.org/integration/mozilla-inbound/pushloghtml?fromchange=5118292ae7f3f3a2c007a6f9a844b22f68026da7&tochange=56e6914c51a78ed06d3f949127ccf20df08665a6

Comment 8

[Vasilica Tamas, QA [:vtamas]]

I was able to reproduce the initial issue on Firefox 46.0a1 (2016-01-05) under Windows 10 64-bit. 


Tested on Firefox 51.0a1 (2016-08-29), Firefox 50.0a2 (2016-08-29), Firefox 49.0b7 and Firefox 48.0.2 (20160823121617) under Windows 10 64-bit and noticed the following:

   1. The add-on is successfully installed from a network folder under Firefox 50.0a2, Firefox 49.0b7 and Firefox 48.0.2 
   2. “Access to the file was denied” error is displayed using Firefox 51.0a1 (2016-08-29): http://screencast.com/t/kitVjwHRJ but the add-on is successfully installed in a non-e10s window.
Is this some nightly specific error? Because the first build where I encountered is Firefox 49.0a1 from 2016-04-12 but it seems that is not reproducible across the other branches. 


Pushlog:
https://hg.mozilla.org/mozilla-central/pushloghtml?fromchange=49d7fb650c9dde7cf6e4b2c7aa578a4a11e83f83&tochange=fb125ff927eae1b7adb8d0e3db798c341d71d8ab


Any thoughts about this issue?

Comment 9

[Dave Townsend [:mossop]]

 Sounds like an e10s only bug to me.

Comment 10

[Julien Cristau [:jcristau]]

Mass wontfix for bugs affecting firefox 52.

Comment 11

[BMO Automation]

Per policy at https://wiki.mozilla.org/Bug_Triage/Projects/Bug_Handling/Bug_Husbandry#Inactive_Bugs. If this bug is not an enhancement request or a bug not present in a supported release of Firefox, then it may be reopened.