Problem opening links in Thunderbird on dual-headed desktop

[eskwayrd]

Binary package hint: mozilla-thunderbird

In a dual-head desktop scenario, if Thunderbird is running on one head and Firefox is running on the other, clicking links in Thunderbird results in the error message "Firefox is already running, but is not responding." If Thunderbird is quit and started on the Firefox head, or if Firefox is quit and started on the Thunderbird head, then there is no problem, but defeats the purpose of using dual-head.

Using Ubuntu Gutsy (7.10), Gnome 2.20.1, Thunderbird 2.0.0.6, Firefox 2.0.0.12, on Intel Core 2 box.

[Ruben Verweij (ruben-verweij)]

I can not confirm this bug using Hardy (8.04), Firefox 3.0.3, Thunderbird 2.0.0.17 and nVidia driver 169.12. Could you upgrade to Hardy to see if the problem still persists on your system?

[eskwayrd (eskwayrd)]

On Sat, Oct 11, 2008 at 3:13 AM, Ruben Verweij <email address hidden>wrote:

> I can not confirm this bug using Hardy (8.04), Firefox 3.0.3,
> Thunderbird 2.0.0.17 and nVidia driver 169.12. Could you upgrade to
> Hardy to see if the problem still persists on your system?

I can confirm that the problem persists while running Hardy 8.04, Firefox
3.0.3, and Thunderbird 2.0.0.17 with nvidia-glx-new 169.12.

If further details would help, such as my current xorg.conf, please let me
know.

>
> ** Changed in: mozilla-thunderbird (Ubuntu)
> Status: New => Incomplete
>
> --
> Problem opening links in Thunderbird on dual-headed desktop
> https://bugs.launchpad.net/bugs/194061
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in "mozilla-thunderbird" source package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: mozilla-thunderbird
>
> In a dual-head desktop scenario, if Thunderbird is running on one head and
> Firefox is running on the other, clicking links in Thunderbird results in
> the error message "Firefox is already running, but is not responding." If
> Thunderbird is quit and started on the Firefox head, or if Firefox is quit
> and started on the Thunderbird head, then there is no problem, but defeats
> the purpose of using dual-head.
>
> Using Ubuntu Gutsy (7.10), Gnome 2.20.1, Thunderbird 2.0.0.6, Firefox
> 2.0.0.12, on Intel Core 2 box.
>

--
Ewan Edwards, <email address hidden>

[John Vivirito (gnomefreak)]

eskwayrd wrote:
> On Sat, Oct 11, 2008 at 3:13 AM, Ruben Verweij
> <email address hidden>wrote:
>
>
>> I can not confirm this bug using Hardy (8.04), Firefox 3.0.3,
>> Thunderbird 2.0.0.17 and nVidia driver 169.12. Could you upgrade to
>> Hardy to see if the problem still persists on your system?
>>
>
>
> I can confirm that the problem persists while running Hardy 8.04, Firefox
> 3.0.3, and Thunderbird 2.0.0.17 with nvidia-glx-new 169.12.
>
> If further details would help, such as my current xorg.conf, please let me
> know.
>
>
>
>> ** Changed in: mozilla-thunderbird (Ubuntu)
>> Status: New => Incomplete
>>
>> --
>> Problem opening links in Thunderbird on dual-headed desktop
>> https://bugs.launchpad.net/bugs/194061
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>> Status in "mozilla-thunderbird" source package in Ubuntu: Incomplete
>>
>> Bug description:
>> Binary package hint: mozilla-thunderbird
>>
>> In a dual-head desktop scenario, if Thunderbird is running on one head and
>> Firefox is running on the other, clicking links in Thunderbird results in
>> the error message "Firefox is already running, but is not responding." If
>> Thunderbird is quit and started on the Firefox head, or if Firefox is quit
>> and started on the Thunderbird head, then there is no problem, but defeats
>> the purpose of using dual-head.
>>
>> Using Ubuntu Gutsy (7.10), Gnome 2.20.1, Thunderbird 2.0.0.6, Firefox
>> 2.0.0.12, on Intel Core 2 box.
>>
>>
>
>
Everyone seeing this issue is using Kubuntu or Ubuntu?

--
Sincerely Yours,
    John Vivirito

https://launchpad.net/~gnomefreak
https://wiki.ubuntu.com/JohnVivirito
Linux User# 414246

"How can i get lost, if i have no where to go"
    -- Metallica from UnforgivenIII

[Ruben Verweij (ruben-verweij)]

I am using Ubuntu and I can't reproduce this bug. (see my previous post)

John Vivirito schreef:
> eskwayrd wrote:
>
>> On Sat, Oct 11, 2008 at 3:13 AM, Ruben Verweij
>> <email address hidden>wrote:
>>
>>
>>
>>> I can not confirm this bug using Hardy (8.04), Firefox 3.0.3,
>>> Thunderbird 2.0.0.17 and nVidia driver 169.12. Could you upgrade to
>>> Hardy to see if the problem still persists on your system?
>>>
>>>
>> I can confirm that the problem persists while running Hardy 8.04, Firefox
>> 3.0.3, and Thunderbird 2.0.0.17 with nvidia-glx-new 169.12.
>>
>> If further details would help, such as my current xorg.conf, please let me
>> know.
>>
>>
>>
>>
>>> ** Changed in: mozilla-thunderbird (Ubuntu)
>>> Status: New => Incomplete
>>>
>>> --
>>> Problem opening links in Thunderbird on dual-headed desktop
>>> https://bugs.launchpad.net/bugs/194061
>>> You received this bug notification because you are a direct subscriber
>>> of the bug.
>>>
>>> Status in "mozilla-thunderbird" source package in Ubuntu: Incomplete
>>>
>>> Bug description:
>>> Binary package hint: mozilla-thunderbird
>>>
>>> In a dual-head desktop scenario, if Thunderbird is running on one head and
>>> Firefox is running on the other, clicking links in Thunderbird results in
>>> the error message "Firefox is already running, but is not responding." If
>>> Thunderbird is quit and started on the Firefox head, or if Firefox is quit
>>> and started on the Thunderbird head, then there is no problem, but defeats
>>> the purpose of using dual-head.
>>>
>>> Using Ubuntu Gutsy (7.10), Gnome 2.20.1, Thunderbird 2.0.0.6, Firefox
>>> 2.0.0.12, on Intel Core 2 box.
>>>
>>>
>>>
>>
>>
> Everyone seeing this issue is using Kubuntu or Ubuntu?
>
>

[Ruben Verweij (ruben-verweij)]

I can also not confirm this bug on Intrepid (8.10), Thunderbird 2.0.0.17, Firefox 3.0.3, NVIDIA accelerated graphics driver version 177 (enabled via jockey).

[Alexander Sack (asac)]

i think there was an upstream bug for this in bugzilla.mozilla.org ... please find it for me again :).

[Victor Vargas (kamus)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!