LinuxQuestions.org - Clicking a link in Thunderbird does not open Firefox

- Slackware (https://www.linuxquestions.org/questions/slackware-14/)

- - Clicking a link in Thunderbird does not open Firefox (https://www.linuxquestions.org/questions/slackware-14/clicking-a-link-in-thunderbird-does-not-open-firefox-4175443587/)

Clicking a link in Thunderbird does not open Firefox

This is on a new install of Slackware 14 64-bit with latest browser/client. How can this be fixed?

In Thunderbird, go to Edit=>Preferences=>Attachments Tab and see which program is specified for http and https

In my recent installations, it has taken a center click, rather than a left click to open a link in Firefox.
Regards,
Bill

If none of the other work try=
Edit,Preferences,Advanced, tick "Always check to see if Thunderbird is Mail client".
Regards
Trev

Doesn't seem to work

There seems to be two tabs for that screen, one says incoming the other outgoing. I see nothing in them and nothing that would seem to indicate that this is the answer. Would love to hear more, because I am still out of luck.

Quote:

Originally Posted by sycamorex (Post 4860079)

In Thunderbird, go to Edit=>Preferences=>Attachments Tab and see which program is specified for http and https

set Mimetypes(taken from https://wiki.archlinux.org/index.php...t_Applications)
/usr/share/applications/defaults.list (global)
~/.local/share/applications/defaults.list (per user, overrides global)

add something like
[Default Applications]
text/html=mozilla-firefox.desktop
x-scheme-handler/http=mozilla-firefox.desktop

In Thunderbird click the link, open it with
/usr/bin/xdg-open

I had the same problem on Slack 14-32 bit. I have Slack 13.37 64 bit on the same system. On 13.37, I can click a link in TB, and it opens in FF. The interesting thing is TB and FF are the same release on both systems.

So, why does it work on 13.37, and not on 14. As franzen has suggested, this appears to be a mimetype problem. I spent some time and found out there is a mimeType.rdf file in your profiles directory. This is true for both FF and TB. I copied the mimeType.rdf file from my 13.37 install into the profiles dir for TB on 14. I started TB, and now I have things showing under Attachments. I can click a link on 14 TB, it opens now in FF.

Did some more googling, trying to find out the "correct way" to edit mimeType.rdf. I can not find a correct way. MozillaZine indicates you should not manually edit the file because of its complexity. They state you click Tools-->Options... which is not in the menu scheme on either of my TB installations. So, at this point I don't know the correct way. If you are interested, I can post the mimeType.rdf file I have. It works with http links.

I suspect there was a way to edit this file in older versions of TB. My 13.37 /home dir has not been formatted for a long time, so older versions probably had a valid method for the user to edit this file.

If anyone has knowledge of the correct way to edit the mimeTypes file, please post it.

FWIW, here is a link to MozillaZine, and the information they have on momeType.rdf file.

-->http://kb.mozillazine.org/MimeTypes.rdf

Thunderbird slackbuilds of slackware 13.37 and 14.0:

http://slackware.osuosl.org/slackwar...ird.SlackBuild

Code:

( cd $PKG/usr/lib${LIBDIRSUFFIX}/thunderbird-$VERSION

  cp -a defaults/profile/mimeTypes.rdf defaults/profile/mimeTypes.rdf.orig

  zcat $CWD/mimeTypes.rdf > defaults/profile/mimeTypes.rdf || exit 1

) || exit 1

http://slackware.osuosl.org/slackwar...ird.SlackBuild

Code:

# Thunderbird 3.x cruft?

# If we still need something like this (and you know what we need :), let me know.

#( cd $PKG/usr/lib${LIBDIRSUFFIX}/thunderbird-$VERSION

#  cp -a defaults/profile/mimeTypes.rdf defaults/profile/mimeTypes.rdf.orig

#  zcat $CWD/mimeTypes.rdf > defaults/profile/mimeTypes.rdf || exit 1

#) || exit 1

=======
slackware 13.37 mimeTypes.rdf

Code:

<?xml version="1.0"?>  



<!--

 This file is used as a persistent data store for helper application

 information about both MIME type and protocol scheme helpers.



 The root of the data are the two containers

 <RDF:Seq about="urn:mimetypes:root"/> and <RDF:Seq about="urn:schemes:root"/>.



 These contain one <RDF:li/> entry per MIME type/protocol.  Each <RDF:li/> entry

 corresponds to a "urn:<class>:<type>" resource, where <class> is either

 "mimetype" or "scheme" and <type> is either a MIME type in "major/minor" format

 or a scheme.  For example, for HTML we would have "urn:mimetype:text/html",

 while for mailto: we would have "urn:scheme:mailto".



 Typically, this resource will be in the <RDF:Description/> node which has the

 corresponding "about" attribute.



 Each "urn:<class>:<type>" resource can have the following properties:



  NC:Value - the MIME type or scheme string

  NC:editable - a "true" or "false" depending on whether this entry is

                editable

  NC:description - a description of the type ("HTML Document" for text/html)

  NC:fileExtensions - for MIME types, there will be one of these properties

                      per extension that corresponds to this MIME type,

                      each one having a single extension as its value.

  NC:handlerProp - the way the type should be handled.  This corresponds to a

                    "urn:<class>:handler:<type>" resource.  Eg, the way HTML is

                    handled would be stored in the

                    "urn:mimetype:handler:text/html" resource.



 Each "urn:<class>:handler:<type>" resource can have the following properties:



  NC:useSystemDefault - "true" if we should handle per default OS setting,

                          "false" or not set otherwise

  NC:saveToDisk - "true" if the data should be saved to disk, "false" or not

                  set otherwise.

    (Note - if both of these are false, that means "open in helper app")

  NC:alwaysAsk - "true" if the user should always be prompted before handling

                  data of this type, false otherwise.

  NC:externalApplication - the preferred helper application to use for this

                            type.  This corresponds to a

                            "urn:<class>:externalApplication:<type>" resource.

  NC:possibleApplication - a helper application that can be used for this type.

                            Since there can be multiple possible applications,

                            there can be multiple assertions in the graph with

                            this property for a given handler resource.



 Each "urn:<class>:externalApplication:<type>" resource, and each resource

 that represents a possible application, can have the following property:



  NC:prettyName - the "pretty name" of the application ("Acrobat Reader" for

                  /usr/bin/acroread, eg).



 If the resource represents a local application, then it can have the following

 property:



  NC:path - the path to the application on the local filesystem, for example

            /usr/bin/test or C:\windows\system32\cmd.exe.



 If the resource represents a web application, then it can have the following

 property:



  NC:uriTemplate - a URI pointing to the web application to which the type

                    should be handed off, with %s in the template representing

                    the place where the content should be inserted. For example,

                    here is a URI template for a service that lets you email

                    an address in a mailto: link:

                      http://www.example.com/sendmail?link=%s

-->



<RDF:RDF xmlns:RDF="http://www.w3.org/1999/02/22-rdf-syntax-ns#"

        xmlns:NC="http://home.netscape.com/NC-rdf#">



  <RDF:Description about="urn:mimetypes"> 

    <NC:MIME-types> 

      <RDF:Seq about="urn:mimetypes:root"> 

      </RDF:Seq>

    </NC:MIME-types> 

  </RDF:Description> 



  <RDF:Description RDF:about="urn:scheme:handler:http"

                  NC:alwaysAsk="false">

    <NC:externalApplication RDF:resource="urn:scheme:externalApplication:http"/>

  </RDF:Description>

  <RDF:Description RDF:about="urn:scheme:externalApplication:http"

                  NC:prettyName="firefox"

                  NC:path="/usr/bin/firefox" />

  <RDF:Description RDF:about="urn:schemes">

    <NC:Protocol-Schemes RDF:resource="urn:schemes:root"/>

  </RDF:Description>

  <RDF:Description RDF:about="urn:scheme:http"

                  NC:value="http">

    <NC:handlerProp RDF:resource="urn:scheme:handler:http"/>

  </RDF:Description>



  <RDF:Description RDF:about="urn:scheme:handler:https"

                  NC:alwaysAsk="false">

    <NC:externalApplication RDF:resource="urn:scheme:externalApplication:https"/>

  </RDF:Description>

  <RDF:Description RDF:about="urn:scheme:externalApplication:https"

                  NC:prettyName="firefox"

                  NC:path="/usr/bin/firefox" />

  <RDF:Description RDF:about="urn:schemes">

    <NC:Protocol-Schemes RDF:resource="urn:schemes:root"/>

  </RDF:Description>

  <RDF:Description RDF:about="urn:scheme:https"

                  NC:value="https">

    <NC:handlerProp RDF:resource="urn:scheme:handler:https"/>

  </RDF:Description>



</RDF:RDF>

I spent some time messing with this a while ago.

I believe what fixed it for me was going into the Config Editor in Thunderbird (Edit|Preferences|Advanced|Config Editor...) and changing the value of helpers.global_mime_types_file from /etc/mime.types to /etc/httpd/mime.types because /etc/mime.types doesn't seem to exist.

Dave