Closed
Bug 481565
Opened 16 years ago
Closed 15 years ago
firefox crash not working at all after autoupdation
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
INCOMPLETE
People
(Reporter: mozilla, Unassigned)
Details
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; SV1; .NET CLR 1.1.4322; .NET CLR 2.0.50727; MS-RTC LM 8) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.0.7) Gecko/2009021910 Firefox/3.0.7 In my firefox, Autoupdation is active, I got a message stating updation complete, click here to install, I clicked, firefox restarted, and its not working at all... Reproducible: Didn't try Error: [Exception... "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIChannel.contentType]" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: file:///C:/Program%20Files/Mozilla%20Firefox/components/FeedProcessor.js :: FP_onStartRequest :: line 1440" data: no] Source File: file:///C:/Program%20Files/Mozilla%20Firefox/components/FeedProcessor.js Line: 1440
Comment 1•16 years ago
|
||
This is not a security-sensitive bug.
Group: core-security
Component: Session Restore → General
QA Contact: session.restore → general
Comment 2•16 years ago
|
||
Does it work in the Firefox safemode ? http://support.mozilla.com/en-US/kb/Safe+Mode
no its not working in safe mode with any options.... see in my firefox autoupdation is selected... so after updating it shows me to restart the firefox... I did the same... but after that no site i"m able to visit ... evenly homepage of firefox also not working ... I don't know which components added that time ...
Comment 4•16 years ago
|
||
It's a little bit unclear for me which issue you have. In the summary you report a crashing Firefox, does it crash on startup or when you visit any other URL or do you mean that it can not connect to any site ?
Comment 5•16 years ago
|
||
You're going to need help from people who know how to help, us developers are not always known for our clear and helpful directions: http://support.mozilla.com They can help you get Firefox running again (try downloading a complete new copy from http://www.mozilla.com and install that; try creating a "new profile"--instructions on the support site). We can't fix a bug until we know what it is, and at this point it could be a conflict with something else on your machine. I can't think of any reason for the FeedProcessor to get "not available" errors unless something is really messed up in your installation so a fresh copy would be a good idea. Let us know what works as that will narrow down where the problem was.
Updated•15 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 15 years ago
Resolution: --- → INCOMPLETE
You need to log in
before you can comment on or make changes to this bug.
Description
•