Closed Bug 542046 Opened 16 years ago Closed 14 years ago

Suddenly clicking on links in a message results in an error.

Categories

(Thunderbird :: Mail Window Front End, defect)

x86_64
Windows Vista
defect
Not set
major

Tracking

(Not tracked)

RESOLVED DUPLICATE of bug 535940

People

(Reporter: thesamim, Unassigned)

Details

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.7) Gecko/20100111 Error Console: Error: uncaught exception: [Exception... "Component returned failure code: 0x80004005 (NS_ERROR_FAILURE) [nsIExternalProtocolService.loadUrl]" nsresult: "0x80004005 (NS_ERROR_FAILURE)" location: "JS frame :: chrome://communicator/content/contentAreaClick.js :: openLinkExternally :: line 188" data: no] Happens with all links from all messages. Reproducible: Always Steps to Reproduce: 1. Click on link in an open mail message. 2. nothing happens 3. check error console. 4. See above error. Actual Results: Never opens browser. Never goes to browser page. (ie: doesn't matter if browser is open or closed. Result is same) Expected Results: browser opens, page is displayed. Tried restarting thunderbird and firefox. Tried starting in different sequences (t-bird first, f-fox first...) This was working just fine yesterday. Started happening today. I have not downloaded or installed any new software. I do have lightning installed: Lightning/1.0b1 Thunderbird/3.0.1 Firefox version: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.7) Gecko/20091221 Firefox/3.5.7 (.NET CLR 3.5.30729)
Apologies, just noticed that periodically this error also shows up on click: Error: [Exception... "Component returned failure code: 0x80004001 (NS_ERROR_NOT_IMPLEMENTED) [nsIRequest.name]" nsresult: "0x80004001 (NS_ERROR_NOT_IMPLEMENTED)" location: "JS frame :: file:///C:/Program%20Files%20(x86)/Mozilla%20Thunderbird/components/nsLoginManager.js :: anonymous :: line 328" data: no] Source File: file:///C:/Program%20Files%20(x86)/Mozilla%20Thunderbird/components/nsLoginManager.js Line: 328
can you try to start thunderbird in -safe-mode (http://kb.mozillazine.org/Safe_mode) and see if the issue is still present ?
Problem seems to have gone away. If it happens again, I'll try safe mode.
I'm seeing a very similar symptom on WinXP 64 -- click an http: link in TB, and the link does not open; this appears in the console: Error: uncaught exception: [Exception... "Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIExternalProtocolService.loadUrl]" nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame :: chrome://communicator/content/contentAreaClick.js :: openLinkExternally :: line 188" data: no] Same symptom in safe mode. network.protocol-handler prefs for http: and https: are identical. Registry settings that handle these protocols appear to be set up correctly. Default browser is Fx 3.6.2. I've got other outstanding XP64-related bugs which seem to be due to my running on AMD processor (dual-core Athlon 4850e); Sami, is your system Intel or AMD? This is with: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.1.9) Gecko/20100328 Shredder/3.0.5pre
Trying to open the link from the context menu yields: Error: uncaught exception: [Exception... "Component returned failure code: 0x80520012 (NS_ERROR_FILE_NOT_FOUND) [nsIExternalProtocolService.loadURI]" nsresult: "0x80520012 (NS_ERROR_FILE_NOT_FOUND)" location: "JS frame :: chrome://messenger/content/nsContextMenu.js :: CM_openLinkInBrowser :: line 830" data: no]
Mike: Mine's an Intel processor. But FYI: I have not seen that error again...
(In reply to comment #4) > Same symptom in safe mode. network.protocol-handler prefs for http: and https: > are identical. Registry settings that handle these protocols appear to be set > up correctly. Default browser is Fx 3.6.2. I'm not sure we still use the pref.
Sami, do you have started TB with -no-remote option?
(In reply to Sami Mikhail from comment #6) > But FYI: I have not seen that error again... The problem was probably that the default browser wasn't set correctly, and Thunderbird couldn't find it, which would explain why your problem is now gone. Reopen if that's not the root cause (I'm talking about the error message from comment 0, not the one from comment 5).
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.