Open Bug 922821 Opened 12 years ago Updated 3 years ago

downloaded file does not launch - (NS_ERROR_FAILURE) [nsIMIMEInfo.launchWithFile]" nsresult: "0x80004005

Categories

(Toolkit :: Downloads API, defect)

x86
Windows 7
defect

Tracking

()

People

(Reporter: wsmwk, Unassigned)

Details

I started seeing this I think a couple weeks ago. using current trunk http://hg.mozilla.org/mozilla-central/rev/5a49762ee832 [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMIMEInfo.launchWithFile]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: resource://gre/modules/DownloadIntegration.jsm :: DI_launchDownload_task :: line 503" data: no] example steps 1. https://ftp.mozilla.org/pub/mozilla.org/thunderbird/nightly/latest-comm-central/ 2. DL exe file and get green arrow 3. click to display list DLs actual results: nothing launched
I may have tested safe mode way back but I don't recall. May try again
Can you try switching the "browser.download.useJSTransfer" preference in about:config, restart the browser, download the file again, and see if you have the same error?
works with browser.download.useJSTransfer = false
(In reply to Wayne Mery (:wsmwk) from comment #1) > I may have tested safe mode way back but I don't recall. May try again Testing with a new profile might help in understanding if there is some type of configuration on your computer or profile to which the new code reacts differently. On a new profile, I haven't seen the issue on my computer.
Same behaviour here, but slightly different location. I think it started with Beta3 of FF26. 11:09:07.464 [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIMIMEInfo.launchWithFile]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: resource://gre/modules/DownloadIntegration.jsm :: DI_launchDownload_task :: line 496" data: no] promise.js:133
Addendum to comment #5: I cannot find "browser.download.useJSTransfer" in "about:config".
Severity: normal → S3
You need to log in before you can comment on or make changes to this bug.