Thunderbird now plays well with Firefox

  • user warning: Table 'cache' is marked as crashed and should be repaired query: SELECT data, created, headers, expire FROM cache WHERE cid = 'filter:1:81be5718a32a0befed8d169d59baf1a8' in /home/dowdle/public_html/montanalinux/includes/database.mysql.inc on line 121.
  • user warning: Table 'cache' is marked as crashed and should be repaired query: UPDATE cache SET data = '<p>I had been a non-conformist in many ways with regard to installing my own tarball of Thunderbird and Firefox instead of using the packaged RPMs Fedora already built. I mainly did this because they are considered stable by Mozilla yet one version ahead of RPMs.</p>\n<p>Late last year I had run into problems with my system dieing for various reasons and I had suspected Firefox. I knelt down and installed the RPM leaving the tarball version in place and changing my app links to point to the correct bin. Soon to follow was Thunderbird as well.</p>\n<p>Well today I discovered I had been starting Firefox in a variety of ways. I noticed that Firefox was upgrading to 2.0.0.12 but failed due to incompatible extensions I guess. Then I started wondering why the RPM would allow me to be upgrading in this fashion anyway. I looked at my processes and noticed Firefox running from <i>/usr/lib/firefox/firefox-bin</i> which is where I put my tarball installation.</p>\n<p>I double checked my link to Firefox and it says it is linked to <i>/usr/bin/firefox</i> which is actually <i>/usr/lib/firefox-2.0.0.10/firefox-bin</i>. So how the heck was the old (newer) Firefox getting started?</p>\n<p>In process list I noticed it also had some reference to a website I had clicked on from an email and from there I remembered I launched Firefox via Thunderbird.</p>\n<p>I proceeded to remove the <i>/usr/lib/firefox</i> directory. Then from Thunderbird I hit a link form email. Nothing happened. Ugh! Well I have experienced this before but never really fixed it. Mainly just dragged the link into Firefox to get around it. This time I looked around and read many different offers to the problem but only tired one. I believe this fix works the same way depending on your packagers file names; either <i>user.js</i> or <i>prefs.js</i> in your Thunderbird profile directory. Add these lines to the <i>.js</i> file:</p>\n<blockquote>\n<pre>user_pref(\"network.protocol-handler.app.http\", \"/usr/bin/firefox\");\nuser_pref(\"network.protocol-handler.app.https\", \"/usr/bin/firefox\");\nuser_pref(\"network.protocol-handler.app.ftp\", \"/usr/bin/firefox\");</pre></p></blockquote>\n<p>Now, one trick to this... and be advised... don\'t make edits while Thunderbird is still open. Once you close TB, your changes are flushed back to the current TB session. Edit your <i>.js</i> file after you close TB.</p>\n<br class=\"clear\" />', created = 1410746464, expire = 1410832864, headers = '' WHERE cid = 'filter:1:81be5718a32a0befed8d169d59baf1a8' in /home/dowdle/public_html/montanalinux/includes/database.mysql.inc on line 121.
  • user warning: Table 'cache' is marked as crashed and should be repaired query: SELECT data, created, headers, expire FROM cache WHERE cid = 'filter:1:5da8c78415499ab3904614c46cfbe6fc' in /home/dowdle/public_html/montanalinux/includes/database.mysql.inc on line 121.
  • user warning: Table 'cache' is marked as crashed and should be repaired query: UPDATE cache SET data = '<p>Thanks for the heads up</p>\n<br class=\"clear\" />', created = 1410746464, expire = 1410832864, headers = '' WHERE cid = 'filter:1:5da8c78415499ab3904614c46cfbe6fc' in /home/dowdle/public_html/montanalinux/includes/database.mysql.inc on line 121.
|

I had been a non-conformist in many ways with regard to installing my own tarball of Thunderbird and Firefox instead of using the packaged RPMs Fedora already built. I mainly did this because they are considered stable by Mozilla yet one version ahead of RPMs.

Late last year I had run into problems with my system dieing for various reasons and I had suspected Firefox. I knelt down and installed the RPM leaving the tarball version in place and changing my app links to point to the correct bin. Soon to follow was Thunderbird as well.

Well today I discovered I had been starting Firefox in a variety of ways. I noticed that Firefox was upgrading to 2.0.0.12 but failed due to incompatible extensions I guess. Then I started wondering why the RPM would allow me to be upgrading in this fashion anyway. I looked at my processes and noticed Firefox running from /usr/lib/firefox/firefox-bin which is where I put my tarball installation.

I double checked my link to Firefox and it says it is linked to /usr/bin/firefox which is actually /usr/lib/firefox-2.0.0.10/firefox-bin. So how the heck was the old (newer) Firefox getting started?

In process list I noticed it also had some reference to a website I had clicked on from an email and from there I remembered I launched Firefox via Thunderbird.

I proceeded to remove the /usr/lib/firefox directory. Then from Thunderbird I hit a link form email. Nothing happened. Ugh! Well I have experienced this before but never really fixed it. Mainly just dragged the link into Firefox to get around it. This time I looked around and read many different offers to the problem but only tired one. I believe this fix works the same way depending on your packagers file names; either user.js or prefs.js in your Thunderbird profile directory. Add these lines to the .js file:

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

Now, one trick to this... and be advised... don't make edits while Thunderbird is still open. Once you close TB, your changes are flushed back to the current TB session. Edit your .js file after you close TB.


Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.

Thanks for the heads up

Thanks for the heads up


Comment viewing options

Select your preferred way to display the comments and click "Save settings" to activate your changes.