Am 29.07.2012 19:48, schrieb Je...@nospam.fake:
> On 7/29/12 10:23 AM, Christian Riechers wrote:
>> On 07/29/2012 03:21 PM, Je...@nospam.fake wrote:
>>> All of a sudden links in emails no longer open in my browser. When I
>>> click on them the desktop flashes but nothing else happens.
>>> Am using TB 14.0 and the latest Firefox in Windows 7 64 bit.
>>>
>>> What is happening and how to fix? Thanks.
>>>
>>> Jeff
>>
>>
http://support.mozillamessaging.com/en-US/kb/Hyperlinks-in-Messages-Not-Working
>>
>
> I followed all the instructions on that web page and they did not solve
> the problem.
>
> a) Firefox is the default browser.
>
> b) Restarting TB in safe mode does not solve the problem: links still
> will not open in browser.
>
Eight days ago I had a very similar problem (cf. my thread in the
Firefox Support group "FF 14.0.1 doesn't open Thunderbird 14 links like
it used to"). Let me quote from that thread:
"I am on VistaSP2 32-bit, and Firefox 14.0.1 is my default browser.
I've been using Thunderbird as my mail client for about 5 years now.
Up until the last updates to FF version 14.0.1 and TB version 14 (a
couple of days ago) the interaction between TB and FF was fine.
Today - all of a sudden - whenever I click a link in Thunderbird, a
little Firefox-box will pop up saying that Firefox is already running
but is not responding and that I have to end the running process or
restart my computer before I can open a new window [i.e. the link in
TB].
Following this advice lets me open just one(!) link; trying to open
further links makes the little Firefox-box pop up again...
All this applies to four independent TB-profiles.
The fact that the little box is a FF-box lets me assume that this is a
Firefox issue...
And I am obviously not alone in my misery:
http://support.mozilla.org/de/questions/932461 offers a very good
description of this issue."
The most plausible answer I got:
"What you describe is a windows registry problem, windows has forgotten
FF is your default browser."
This certainly does not exclude that the last updates of FF and/or TB
could have provoked this issue.
But whatever the reason was, after booting up my machine the next
morning everything was miraculously back to normal again.
I am still mystified and don't know if this was due to some act of
self-correction of the Windows registry??
-rebro