Bug 7476

Summary:	I've set Chromium as default browser but Thunderbird opens the links with firefox
Product:	Mageia	Reporter:	Marcello Anni <marcello.anni>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	stblack, stormi-mageia
Version:	2	Keywords:	Triaged, UPSTREAM
Target Milestone:	---
Hardware:	i586
OS:	Linux
Whiteboard:
Source RPM:	thunderbird	CVE:
Status comment:

Description Marcello Anni 2012-09-14 09:50:47 CEST

Description of problem:

as written in the summary, the problem is nearly simple. can you help me to fix it? thank you


cheers,
Marcello

Thierry Vignaud 2012-09-14 15:12:44 CEST

Source RPM: (none) => thunderbird, xdg-utils

Comment 1 Stefano Negro 2012-10-04 08:50:05 CEST

Hi Marcello,
you can do it manually following the page on the Mozillazine.

http://kb.mozillazine.org/Default_browser#Setting_the_browser_that_opens_in_Thunderbird_-_Linux

Ciao
Stblack

CC: (none) => stblack

Comment 2 Marcello Anni 2012-10-04 11:59:19 CEST

hi stefano,

thank you for the reply :) i've added the file user.js to the Thunderbird folder, and i've added these strings:

user_pref("network.protocol-handler.app.http", "/usr/bin/chromium");
user_pref("network.protocol-handler.app.https", "/usr/bin/chromium");
user_pref("network.protocol-handler.app.ftp", "/usr/bin/chromium");


but it doesn't work. did i make any mistakes? should i do anything else? thank you



cheers,
Marcello

Comment 3 Marcello Anni 2012-10-04 12:01:24 CEST

i've also added these strings in prefs.js but it doesn't work too...

Comment 4 Samuel Verschelde 2013-08-29 16:53:43 CEST

I think this is an upstream bug.

Keywords: (none) => Triaged, UPSTREAM
CC: (none) => stormi
Source RPM: thunderbird, xdg-utils => thunderbird

Comment 5 Marcello Anni 2013-08-29 18:42:11 CEST

do i fill the bug in thunderbird bugillza?

Comment 6 Samuel Verschelde 2013-08-29 18:53:39 CEST

First I'd search the internet for similar bug reports in other distributions (maybe they have a patch), and also search for an existing bug in thunderbird's bugzilla. I'm quite sure it exists already. If it doesn't, then yes please open a bug upstream.

Comment 7 Manuel Hiebel 2013-10-22 12:20:05 CEST

This message is a reminder that Mageia 2 is nearing its end of life.
Approximately one month from now Mageia will stop maintaining and issuing updates for Mageia 2. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '2'.

Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 2's end of life.

Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 2 is end of life.  If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia.

Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete.

-- 
The Mageia Bugsquad

Comment 8 Manuel Hiebel 2013-11-23 16:16:12 CET

Mageia 2 changed to end-of-life (EOL) status on ''22 November''. Mageia 2 is no
longer maintained, which means that it will not receive any further security or
bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD