Where did you install Firefox from? Help Mozilla uncover 3rd party websites that offer problematic Firefox installation by taking part in our campaign. There will be swag, and you'll be featured in our blog if you manage to report at least 10 valid reports!

Avatar for Username

Sykje yn Support

Mij stipescams. Wy sille jo nea freegje in telefoannûmer te beljen, der in sms nei ta te stjoeren of persoanlike gegevens te dielen. Meld fertochte aktiviteit mei de opsje ‘Misbrûk melde’.

Learn More

Dizze konversaasje is argivearre. Stel in nije fraach as jo help nedich hawwe.

I keep getting two error messages and I'm not sure how to get rid of them. Help.

  • 1 antwurd
  • 22 hawwe dit probleem
  • 1 werjefte
  • Lêste antwurd fan cor-el

hobenjane
hobenjane
more options

Here are the two error messages: [Exception... "Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIFileInputStream.init]" nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame :: chrome://1clickweather/content/js/utils/filemanager.js :: <TOP_LEVEL> :: line 233" data: no]


[Exception... "Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIFileInputStream.init]" nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame :: chrome://1clickweather/content/js/utils/filemanager.js :: <TOP_LEVEL> :: line 133" data: no]

Here are the two error messages: [Exception... "Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIFileInputStream.init]" nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame :: chrome://1clickweather/content/js/utils/filemanager.js :: <TOP_LEVEL> :: line 233" data: no] [Exception... "Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIFileInputStream.init]" nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame :: chrome://1clickweather/content/js/utils/filemanager.js :: <TOP_LEVEL> :: line 133" data: no]

Alle antwurden (1)

cor-el
cor-el
  • Moderator
  • Top 10 Contributor
more options

This is caused by an extension (in this case: 1clickweather) that isn't working properly.