Closed Bug 433605 Opened 12 years ago Closed 2 years ago
Exception thrown when trying to reload a live bookmark [@ FP
_on Start Request][@ ns IChannel .content Type]
Seen while testing Mozilla/5.0 (Macintosh; U; PPC Mac OS X 10.5; en-US; rv:1.9) Gecko/2008051202 Firefox/3.0. STR: 1. Load a new profile to test RC1 2. Import some data from Safari. I see this error in the console: Error: [Exception... "Component returned failure code: 0x80040111 (NS_ERROR_NOT_AVAILABLE) [nsIChannel.contentType]" nsresult: "0x80040111 (NS_ERROR_NOT_AVAILABLE)" location: "JS frame :: file:///Users/marcia/Desktop/RC1%20candidate/Firefox.app/Contents/MacOS/components/FeedProcessor.js :: FP_onStartRequest :: line 1440" data: no] Source File: file:///Users/marcia/Desktop/RC1%20candidate/Firefox.app/Contents/MacOS/components/FeedProcessor.js Line: 1440
I got the same error in the console on first launch using a new profile, no migration, but while I had no internet connection.
Confirmed on XP too, i saw this when i was out of range from wlan connections and have no internet connection
OS: Mac OS X → All
Hardware: Macintosh → All
On XP it'S this line which throws the exception: channel.contentType = "application/vnd.mozilla.maybe.feed";
I was person who developed Comment #3 in Vista. Interested to notice Gavin Sharp's patch. I cannot use Firefox in Vista at present, because it seems best to uninstall it, after it always does as described. I wonder if patch could get it installed?
Occured on my PC too. Windows XP SP3
Any update on this bug so far? Gavin, what happened with the patch you attached half a year ago? Is it something we can use?
Summary: NS_ERROR_NOT_AVAILABLE [nsIChannel.contentType] → Exception thrown when trying to reload a live bookmark [@ FP_onStartRequest][@ nsIChannel.contentType]
It likely fixes the bug. Confirmation would be useful, I don't think I've tested it. Someone taking this bug would be even better!
While running Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b3pre) Gecko/20090128 Shiretoko/3.1b3pre I am still seeing this error. But as Gavin notes in Comment 12, an owner is needed.
(In reply to comment #12) > It likely fixes the bug. Confirmation would be useful, I don't think I've > tested it. Someone taking this bug would be even better! Robert, could this be a possible fix for the problem? It would be nice when we can eliminate the clutter from the Error Console.
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.
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.