Firefox Requires Reinstall to Access Internet Each Time I Close It
I recently had my laptop fail, but I had my profile folder backed up to a remote location so I've been trying to move it to a replacement system. I followed the instructions found here: https://support.mozilla.org/en-US/kb/back-and-restore-information-firefox-profiles . Both were Windows 7 machines running FF 44.0.
After backing up the existing profile information, I replaced the contents of my existing profile directory with my profile, and it worked great. Then I closed Firefox, did some things, and tried to restart it. No connection. Any external pages hang forever rather than load. I repeated in safe mode, restarted my PC, checked proxy settings, and used the Refresh Firefox feature under about:support. No change. I even tried restoring the original profile and the problem persisted.
Then I tried reinstalling Firefox and it worked fine, and even had my restored profile. But as soon as I restarted, there was no connection. Through trial and error, I've found simply running the installer without first uninstalling works as well. I have to assume it's a config issue between the systems. The only major difference I can find is that the old version of FF was installed on drive C while this is on drive D (though I've tried installing it on C without any success).
Any assistance would be appreciated, especially some that keeps my history. Worst case I can nuke the profile and restart with just restore with bookmarks and passwords, but I'd prefer to avoid that.
Выбранное решение
It appears this was related to issue 124098 and fixed in 44.0.2.
I think.
Hopefully.
I'm really tired of this bug.
Прочитайте этот ответ в контексте 👍 0Все ответы (12)
As a test, disable your protection programs.
Create a new, blank profile and use it as is. Still a problem? https://support.mozilla.org/en-US/kb/profile-manager-create-and-remove-firefox-profiles
https://support.mozilla.org/en-US/kb/how-run-firefox-when-profile-missing-inaccessible
Okay, this is odd. Disabling my firewall and antivirus didn't help. And I used the profile creator to create a blank test profile which had the same issues. But when I switched back from the test profile, the pages started loading. Deleted the test profile and it continued to work. So not sure exactly what solved it, except that launching the profile creator may run some compatibility fixes on existing profiles.
Edit: See below
Изменено radius
Well, the problem reared its head again. I'm also noticing multiple instances of FIrefox in my process explorer that persist if I run with the -P option.
I've called the big guys to help you. Good luck.
Thanks. I have a feeling it's an issue deep in some config files. Maybe the Windows Registry. I had to do some odd stuff to get it to handle programs being installed on two different drives.
Update: No improvement in the 44.0.1 update
Install an older version of Firefox {web link}
Okay, it 43.0.4 works, but if I try to upgrade from it to latest the problem comes back. I've disabled automated updates for now, but I'd like to eventually get back up to date.
Until the issue is fixed, at least you are on-line.
Just got an odd error from Netflix as well. The error code indicates says it is likely corrupted data. A quick google search for the error code brings up this tracker:
Got a chance to start looking through the logs as well, and here's the output prom the browser console when the issue occurs. Googling isn't much help.
Could not read chrome manifest 'file:///D:/Program%20Files%20(x86)/Mozilla%20Firefox/chrome.manifest'. While creating services from category 'profile-after-change', could not create service for entry 'Sapi Speech Synth', contract ID '@mozilla.org/synthsapi;1' "DevToolsUtils.dbg_assert is deprecated! Use DevToolsUtils.assert instead! dbg_assert@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/DevToolsUtils.js:449:13 TabActor.prototype.sources@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/server/actors/webbrowser.js:897:7 ThreadActor.prototype.sources@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/server/actors/script.js:509:5 ThreadActor.prototype.onAttach@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/server/actors/script.js:627:5 DSC_onPacket@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/server/main.js:1599:15 LocalDebuggerTransport.prototype.send/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/transport/transport.js:569:11 makeInfallible/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/DevToolsUtils.js:87:14 makeInfallible/<@resource://gre/modules/commonjs/toolkit/loader.js -> resource://devtools/shared/DevToolsUtils.js:87:14 " DevToolsUtils.js:452 1455164240869 Toolkit.Telemetry WARN TelemetryStorage::_scanArchive - have seen this id before: beeb9dac-7cfb-4127-b0e5-de350e422bae, overwrite: false 1455164261283 addons.productaddons WARN Failed downloading XML, status: 0, reason: timeout 1455164261284 Toolkit.GMP ERROR GMPInstallManager.simpleCheckAndInstall Could not check for addons: Error: Failed downloading XML, status: 0, reason: timeout (resource://gre/modules/addons/ProductAddonChecker.jsm:103:16) JS Stack trace: downloadXML/</fail@ProductAddonChecker.jsm:103:16 Log.jsm:751:0 1455164330827 Toolkit.Telemetry ERROR TelemetrySend::_doPing - error making request to https://incoming.telemetry.mozilla.org/submit/telemetry/beeb9dac-7cfb-4127-b0e5-de350e422bae/crash/Firefox/44.0.1/release/20160205155049?v=4: timeout Log.jsm:751:0 1455164330827 Toolkit.Telemetry ERROR TelemetrySend::sendPersistedPings - failed to send ping beeb9dac-7cfb-4127-b0e5-de350e422bae: {"isTrusted":true} Log.jsm:751:0 1455164330827 Toolkit.Telemetry ERROR TelemetrySend::_doPing - error making request to https://incoming.telemetry.mozilla.org/submit/telemetry/afc014d1-9adb-4bf6-a6fe-04c88b0bf6e5/main/Firefox/44.0.1/release/20160205155049?v=4: timeout Log.jsm:751:0 1455164330827 Toolkit.Telemetry ERROR TelemetrySend::sendPersistedPings - failed to send ping afc014d1-9adb-4bf6-a6fe-04c88b0bf6e5: {"isTrusted":true} Log.jsm:751:0 1455164330828 Toolkit.Telemetry ERROR TelemetrySend::_doPing - error making request to https://incoming.telemetry.mozilla.org/submit/telemetry/bc5a9314-2df4-4363-a03e-54cf09c7980f/main/Firefox/44.0.1/release/20160205155049?v=4: timeout Log.jsm:751:0 1455164330828 Toolkit.Telemetry ERROR TelemetrySend::sendPersistedPings - failed to send ping bc5a9314-2df4-4363-a03e-54cf09c7980f: {"isTrusted":true} Log.jsm:751:0 1455164330835 Toolkit.Telemetry ERROR TelemetrySend::_doPing - error making request to https://incoming.telemetry.mozilla.org/submit/telemetry/476a046f-6cd6-4301-9cf2-5181467b0728/main/Firefox/43.0.4/release/20160105164030?v=4: timeout Log.jsm:751:0 1455164330835 Toolkit.Telemetry ERROR TelemetrySend::sendPersistedPings - failed to send ping 476a046f-6cd6-4301-9cf2-5181467b0728: {"isTrusted":true} Log.jsm:751:0 1455164540859 Toolkit.Telemetry ERROR TelemetrySend::_doPing - error making request to https://incoming.telemetry.mozilla.org/submit/telemetry/beeb9dac-7cfb-4127-b0e5-de350e422bae/crash/Firefox/44.0.1/release/20160205155049?v=4: timeout Log.jsm:751:0 1455164540859 Toolkit.Telemetry ERROR TelemetrySend::sendPersistedPings - failed to send ping beeb9dac-7cfb-4127-b0e5-de350e422bae: {"isTrusted":true} Log.jsm:751:0 1455164540860 Toolkit.Telemetry ERROR TelemetrySend::_doPing - error making request to https://incoming.telemetry.mozilla.org/submit/telemetry/afc014d1-9adb-4bf6-a6fe-04c88b0bf6e5/main/Firefox/44.0.1/release/20160205155049?v=4: timeout Log.jsm:751:0 1455164540860 Toolkit.Telemetry ERROR TelemetrySend::sendPersistedPings - failed to send ping afc014d1-9adb-4bf6-a6fe-04c88b0bf6e5: {"isTrusted":true} Log.jsm:751:0 1455164540860 Toolkit.Telemetry ERROR TelemetrySend::_doPing - error making request to https://incoming.telemetry.mozilla.org/submit/telemetry/bc5a9314-2df4-4363-a03e-54cf09c7980f/main/Firefox/44.0.1/release/20160205155049?v=4: timeout Log.jsm:751:0 1455164540860 Toolkit.Telemetry ERROR TelemetrySend::sendPersistedPings - failed to send ping bc5a9314-2df4-4363-a03e-54cf09c7980f: {"isTrusted":true} Log.jsm:751:0 1455164540860 Toolkit.Telemetry ERROR TelemetrySend::_doPing - error making request to https://incoming.telemetry.mozilla.org/submit/telemetry/476a046f-6cd6-4301-9cf2-5181467b0728/main/Firefox/43.0.4/release/20160105164030?v=4: timeout Log.jsm:751:0 1455164540860 Toolkit.Telemetry ERROR TelemetrySend::sendPersistedPings - failed to send ping 476a046f-6cd6-4301-9cf2-5181467b0728: {"isTrusted":true} </p>
Выбранное решение
It appears this was related to issue 124098 and fixed in 44.0.2.
I think.
Hopefully.
I'm really tired of this bug.