[opensuse] [SOLVED] Howto Get Thunderbird to Open Links in Firefox 4
Guys, Hopefully this will save others the grief it caused me. After upgrade to Firefox 4, clicking links in an email to http:// https:// etc... did nothing. It was a complete PITA copying links from email and pasting them into the browser (middle-click paste anywhere in the page) After looking, I found an answer on the Arch Linux bbs. Basically, in tbird, you must: (1) Edit -> Preferences -> Advanced -> Config Editor: search: "network.protocol", locate: network.protocol-handler.warn-external.ftp network.protocol-handler.warn-external.http network.protocol-handler.warn-external.https ** set each to "true" AND restart Thunderbird (2) send yourself an email with a good link for each eg.: http://download.opensuse.org/repositories https://bbs.archlinux.org/viewtopic.php?id=115524&p=1 ftp://mirror.services.wisc.edu/mirrors/mysql/Downloads/ (3) click on the link in your email, the navigate to /usr/bin/firefox and choose "[x] remember my selection" or whatever it says; and then links in Thunderbird emails will once again open in firefox as they should. It looks like some links or something were forgotten as part of the FF4 update. Wolfgang - can FF4 be fixed to do this automatically on update? -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
El 30/03/11 18:22, David C. Rankin escribió:
Guys,
Hopefully this will save others the grief it caused me. After upgrade to Firefox 4, clicking links in an email to http:// https:// etc... did nothing. It was a complete PITA copying links from email and pasting them into the browser (middle-click paste anywhere in the page)
Install thunderbird extension "thunderbrowse", there is no-brainer wizard that ask you if you want to use it to select the browser to use or for more advanced things. No need to mess with anything else. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 03/30/2011 04:48 PM, Cristian Rodríguez wrote:
El 30/03/11 18:22, David C. Rankin escribió:
Guys,
Hopefully this will save others the grief it caused me. After upgrade to Firefox 4, clicking links in an email to http:// https:// etc... did nothing. It was a complete PITA copying links from email and pasting them into the browser (middle-click paste anywhere in the page)
Install thunderbird extension "thunderbrowse", there is no-brainer wizard that ask you if you want to use it to select the browser to use or for more advanced things.
No need to mess with anything else.
Why am I always the last to know... :p -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
* David C. Rankin <drankinatty@suddenlinkmail.com> [03-30-11 18:56]:
Why am I always the last to know... :p
Something like: "Three left turns = one right turn" :^) -- (paka)Patrick Shanahan Plainfield, Indiana, USA HOG # US1244711 http://wahoo.no-ip.org Photo Album: http://wahoo.no-ip.org/gallery2 http://en.opensuse.org openSUSE Community Member Registered Linux User #207535 @ http://counter.li.org -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 03/30/2011 06:53 PM, David C. Rankin wrote:
On 03/30/2011 04:48 PM, Cristian Rodríguez wrote:
El 30/03/11 18:22, David C. Rankin escribió:
Guys,
Hopefully this will save others the grief it caused me. After upgrade to Firefox 4, clicking links in an email to http:// https:// etc... did nothing. It was a complete PITA copying links from email and pasting them into the browser (middle-click paste anywhere in the page)
Install thunderbird extension "thunderbrowse", there is no-brainer wizard that ask you if you want to use it to select the browser to use or for more advanced things.
No need to mess with anything else.
Why am I always the last to know... :p
I have not installed anything unusual, and I do not see the extension 'thunderbrowse" when I look for it in ff. I have Firefox 4. Have Thunderbird 3.1.9. I just tried snapping on an URL in a message in my received tray, and ff opened it without fuss. --doug -- Blessed are the peacemakers...for they shall be shot at from both sides. --A. M. Greeley -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 03/30/2011 06:50 PM, Doug wrote:
I have not installed anything unusual, and I do not see the extension 'thunderbrowse" when I look for it in ff. I have Firefox 4. Have Thunderbird 3.1.9. I just tried snapping on an URL in a message in my received tray, and ff opened it without fuss.
--doug
I think the issue was that I had FF 3 installed on 11.4, then upgraded to FF 4. All my links in emails were dead as door-nails. I can't explain why. But, I do know from googling -- I'm far from the only one that had the problem... -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Hi, Am 30.03.2011 23:22, schrieb David C. Rankin:
It looks like some links or something were forgotten as part of the FF4 update. Wolfgang - can FF4 be fixed to do this automatically on update?
Given how many times I have answered to that problem I'm wondering if it cannot be found with Google :-(. There are several ways to achieve what you want and you found one of them. I can give you some background on what Thunderbird does _by default_. It looks up your default browser in gconf (under every desktop). If you run Firefox in a Gnome environment (or any other but KDE) the setting in gconf is most likely correct (Firefox even will complain by default and set it for you if it runs somewhere but KDE). If you run Firefox under KDE it'll only set the default browser setting in KDE but Thunderbird is not reading from there. Actually the situation is the downside of having Firefox integrated into KDE (while Thunderbird isn't). The simple solution would be running this as user: gconftool-2 --type=string -s /desktop/gnome/url-handlers/http/command \ "firefox %s" gconftool-2 --type=string -s /desktop/gnome/url-handlers/https/command \ "firefox %s" I cannot do this from the Firefox package though. Anyone has an idea where to document that so that people actually can find it? Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 03/31/2011 12:23 AM, Wolfgang Rosenauer wrote:
The simple solution would be running this as user: gconftool-2 --type=string -s /desktop/gnome/url-handlers/http/command \ "firefox %s" gconftool-2 --type=string -s /desktop/gnome/url-handlers/https/command \ "firefox %s"
I cannot do this from the Firefox package though.
Anyone has an idea where to document that so that people actually can find it?
One thing that I have found lacking is a useful *reliable* wiki for openSuSE. I know it has one -- don't get me wrong, this isn't bashing, but it is really hit or miss as to whether you will find anything useful there for any given package or issue. I used to think wikis were pretty much useless -- for that reason (not just suse's). However, of all the distros I've used, Arch has done their wiki right. For virtually every package, there is a current *reliable* wiki with fairly complete information from package install, configuration and current issues. There, you are expected to consult the wiki first before posting to the list, because the devs can be reasonably sure the question has already been answered and that the answer is correct. The package maintainers are responsible for the wiki information and the community fills in the blanks. It works really well. openSuSE does many, many things right, but one area where it could be improved is having a *reliable* wiki that the community can refer to and be reasonably sure that any current issue has already been addressed there by the packager. Also, of all the wikis I have worked with, mediawiki is the only way to go. Foswiki, etc. are usable, but they are such a PITA for the community to contribute to from a formatting standpoint, that they usually don't get used. http://en.opensuse.org/Firefox leaves quite a bit of room for improvement. No flames, this isn't a slam, it is just a recognition that issues like the Thunderbird/Firefox link problem are a perfect candidate for wiki use, and if we built the content and confidence in the opensuse wiki, then the community would know where to go to get distro specific answers to questions like these :) -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
<snip>
No flames, this isn't a slam, it is just a recognition that issues like the Thunderbird/Firefox link problem are a perfect candidate for wiki use, and if we built the content and confidence in the opensuse wiki, then the community would know where to go to get distro specific answers to questions like these :)
Example: http://en.opensuse.org/index.php?title=Thunderbird&stable=0&shownotice=1&fro... -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 03/31/2011 11:06 AM, David C. Rankin wrote: <snip>
No flames, this isn't a slam, it is just a recognition that issues like the Thunderbird/Firefox link problem are a perfect candidate for wiki use, and if we built the content and confidence in the opensuse wiki, then the community would know where to go to get distro specific answers to questions like these :)
Of course, this is another problem with the openSuSE wiki: "Changes will be published once an authorised user reviews them. The draft, shown below, contains 1 pending change. Return to page section named "Current Issues". " So you might not see the information I added until someone gets around to reviewing it and committing the change for real. This isn't the way a wiki is supposed to work. The change should be allowed when made, then reviewed and revised (or deleted) if inappropriate. There are no little martians running around defacing linux distro wikis. Yeah, it does happen, but very, very rarely - and then the offender is simply banned. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 01/04/2011 03:24, David C. Rankin wrote:
On 03/31/2011 11:06 AM, David C. Rankin wrote: <snip>
No flames, this isn't a slam, it is just a recognition that issues like the Thunderbird/Firefox link problem are a perfect candidate for wiki use, and if we built the content and confidence in the opensuse wiki, then the community would know where to go to get distro specific answers to questions like these :)
Of course, this is another problem with the openSuSE wiki:
"Changes will be published once an authorised user reviews them. The draft, shown below, contains 1 pending change.
Return to page section named "Current Issues". "
So you might not see the information I added until someone gets around to reviewing it and committing the change for real.
This isn't the way a wiki is supposed to work. The change should be allowed when made, then reviewed and revised (or deleted) if inappropriate. There are no little martians running around defacing linux distro wikis. Yeah, it does happen, but very, very rarely - and then the offender is simply banned.
Wouldn't it be nice, David, if you could just post what you added here for all to see? :-) . BC -- Any experiment in life will be at your own experience. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 03/31/2011 06:43 PM, Basil Chupin wrote:
This isn't the way a wiki is supposed to work. The change should be allowed when made, then reviewed and revised (or deleted) if inappropriate. There are no little martians running around defacing linux distro wikis. Yeah, it does happen, but very, very rarely - and then the offender is simply banned.
Wouldn't it be nice, David, if you could just post what you added here for all to see? :-) .
BC
With my reputation for being acrimonious on the list, I'm pretty sure my posts get reviewed :p But seriously, with the great group of smart people we have on this list, there is no reason the openSUSE wiki shouldn't be the best wiki of all. With a few changes to make it usable, I see it really moving forward. And... it is already mediawiki based, so it has the backend that anybody can use very simply. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
with the great group of smart people we have on this list, there is no reason the openSUSE wiki shouldn't be the best wiki of all.
+1. I'd happily contribute "how to" and "how it works" bits for stuff I end up figuring out. There's a gap between n00b docs that say "Wave this chicken." and the ongoing conversations of active developers. I'm pretty computer literate, but when the prescribed chicken-waving doesn't work, digging out what's going on (and going wrong) could be a lot easier. It's a lot of work to even to figure out enough to ask useful questions. A "concept of operations" kind of thing would help immensely. There's some good work in this direction with a few pegged threads and intentionally written overview pieces in the discussion groups. Candidates for this treatment are ... - Graphics / Display / GUI, - Networking, - Sound, - Printing, - Partitions and Multiple Booting - Repositories & Associated Support / Testing Expectations - Reporting Bugs - YAST Package Management - Command Line Package Management An alternative to article approval before publication is a reviewers seal of approval. We have plenty of lizard logos. How about a logo, tagged with "Suzy of SUSE says this works as advertised!" With page history, discussion pages, and the option to put critique at the front of pages that need work (a la Wikipedia) that's a lot of context. /Example Meta - Here's a crappy and partially wrong first draft of a NetworkManager overview that would have helped me, and I suspect would help many other people ... "Network Manager is a service, jointly developed and used across multiple Linux Distributions (including <list>), which runs as a daemon managing network devices and events. OpenSuSE uses the <some NM version policy> version of NetworkManager on major release (since <release>). The Network Manager project is here: <URL>, some tech notes on how it works are here: <URL> and in the OpenSUSE build service / repositories it is here: <URL>. Network Manager - the service - <?reads what to do from a configuration file - is this right? I still don't know.?>, or can be managed in real time by a front-end app <?or from the command line - right?>. Real-time GUI front ends supplied in OpenSuSE are KNetworkManager in KDE (KDE <versions>, in OpenSuSE releases <this, that, the other>), the KNetworkManager plasmoid in KDE (KDE <versions>, in OpenSuSE releases <this, that, the other>), and <whatever> in Gnome. The right GUI front-end is installed as part of the <desktop> package group in YAST. In OpenSUSE you can also use YAST to set up the NetworkManager (Yast -> <whatever>). YAST and GUI front-end configuration can interfere with each other, so in general pick one. Since OpenSUSE release <what?>, the GUI front end is preferred to YAST. For more info: - NetworkManagement under KDE is here: http://userbase.kde.org/NetworkManagement - NetworkManagement under Gnome is here: <URL> - Intro to KDE 4.6 is here: <URL> - A step by step guide for newbies is here: <URL> - And an intro to wireless on OpenSuSE is here: <URL> On 04/01/2011 11:06 AM, David C. Rankin wrote:
On 03/31/2011 06:43 PM, Basil Chupin wrote:
This isn't the way a wiki is supposed to work. The change should be allowed when made, then reviewed and revised (or deleted) if inappropriate. There are no little martians running around defacing linux distro wikis. Yeah, it does happen, but very, very rarely - and then the offender is simply banned.
Wouldn't it be nice, David, if you could just post what you added here for all to see? :-) .
BC
With my reputation for being acrimonious on the list, I'm pretty sure my posts get reviewed :p
But seriously, with the great group of smart people we have on this list, there is no reason the openSUSE wiki shouldn't be the best wiki of all. With a few changes to make it usable, I see it really moving forward. And... it is already mediawiki based, so it has the backend that anybody can use very simply.
-- Jim Bullock, Rare Bird Enterprises, "Conscious Development" LinkedIn: http://www.linkedin.com/in/rarebirdenterprises Listen to a round table of experts in these books from Dorset House: Roundtable on Project Management, http://www.dorsethouse.com/books/rpm.html Roundtable on Technical Leadership, http://www.dorsethouse.com/books/rtl.html -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
David C. Rankin wrote:
One thing that I have found lacking is a useful *reliable* wiki for openSuSE. I know it has one -- don't get me wrong, this isn't bashing, but it is really hit or miss as to whether you will find anything useful there for any given package or issue. I used to think wikis were pretty much useless -- for that reason (not just suse's).
However, of all the distros I've used, Arch has done their wiki right. For virtually every package, there is a current *reliable* wiki with fairly complete information from package install, configuration and current issues. There, you are expected to consult the wiki first before posting to the list, because the devs can be reasonably sure the question has already been answered and that the answer is correct.
The package maintainers are responsible for the wiki information and the community fills in the blanks. It works really well.
openSuSE does many, many things right, but one area where it could be improved is having a *reliable* wiki that the community can refer to and be reasonably sure that any current issue has already been addressed there by the packager.
First thought - a wiki-page per package, not a bad idea at all. Second thought - duplication of information? I.e. what does the wiki-page cover that isn't already covered by other easily/publicly accessible information? Usually, a package will have a homepage with some docs, maybe one or two howtos and/or FAQs and plain man pages for the cli utilities and the configuration files.
No flames, this isn't a slam, it is just a recognition that issues like the Thunderbird/Firefox link problem are a perfect candidate for wiki use,
I agree, although I also think that issue really ought to be solved, not just documented. Maybe this thread is best continued on -project? -- Per Jessen, Zürich (0.0°C) -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
On 03/31/2011 12:47 PM, Per Jessen wrote:
First thought - a wiki-page per package, not a bad idea at all.
Exactly - not just rpm -qi info either... A monkey can get that information. The information that is needed is: - distro specific install and config - normal links to rpms, etc. - advanced configuration usage - that we all do, and have to find each time - current issues - packager contact (yes - that's rpm -qi :)
Second thought - duplication of information?
There will be to some degree no matter what format you use. The key here is make it distro relevant - otherwise you can google it. Second point - the package wiki page should pretty much be a "one stop shop" for information on that package as it relates to the distro.
I.e. what does the wiki-page cover that isn't already covered by other easily/publicly accessible information? Usually, a package will have a homepage with some docs, maybe one or two howtos and/or FAQs and plain man pages for the cli utilities and the configuration files.
Couple of examples: Cups: https://wiki.archlinux.org/index.php/Cups Xorg: https://wiki.archlinux.org/index.php/Xorg There is just a loose basic look you are supposed to follow - nothing hard and fast - it is left to the packager or contributor to format the page in an intelligent manner. It works fantastically. Giving the user/community a bit more control of how they add and contribute information really imparts a bit more ownership of the resource on the user and IMHO results in a better product because the user takes that bit of extra effort in making sure their work product is something to community can rely on.
No flames, this isn't a slam, it is just a recognition that issues like the Thunderbird/Firefox link problem are a perfect candidate for wiki use, I agree, although I also think that issue really ought to be solved, not just documented.
Maybe this thread is best continued on -project?
5 hours and twenty minutes later - my contribution to the openSUSE Thunderbird wiki posting Wolfgang's help is still: "Changes will be published once an authorised user reviews them. The draft, shown below, contains 2 pending changes. Return to page section named "Links in Thunderbird do NOT open in Firefox". " It will be yesterday's news by the time the changes are actually reviewed and committed. Christian, all Novell folks -- this policy really has to change. It really leaves the user with the feeling of "what's the point of trying to get info up on the openSUSE wiki? -- it will be days before somebody looks over your shoulder to make sure you did it right...." Talk to the powers that be. Removing the "review before commit restriction" is probably the #1 thing Novell can do to spur community involvement. -- David C. Rankin, J.D.,P.E. -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Am 31.03.2011 23:40, schrieb David C. Rankin:
Christian, all Novell folks -- this policy really has to change. It really leaves the user with the feeling of "what's the point of trying to get info up on the openSUSE wiki? -- it will be days before somebody looks over your shoulder to make sure you did it right...."
I'm not very good in documenting that stuff anyway but now that you pointed out I basically stopped feeding the wiki when it moved to the new one suffering from the above. Actually to me as a non-every-day wiki user the openSUSE wiki is unusable. I usually even search on the old wiki since it had information while the new one has a lot of non-interesting stuff. Probably I just don't get it but my guess is that quite a _lot_ of people have the same issues. Wolfgang -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
Wolfgang Rosenauer wrote:
I'm not very good in documenting that stuff anyway but now that you pointed out I basically stopped feeding the wiki when it moved to the new one suffering from the above. Actually to me as a non-every-day wiki user the openSUSE wiki is unusable. I usually even search on the old wiki since it had information while the new one has a lot of non-interesting stuff. Probably I just don't get it but my guess is that quite a _lot_ of people have the same issues.
+1 -- To unsubscribe, e-mail: opensuse+unsubscribe@opensuse.org For additional commands, e-mail: opensuse+help@opensuse.org
participants (9)
-
Basil Chupin -
Cristian Rodríguez -
Dave Howorth -
David C. Rankin -
Doug -
James Bullock -
Patrick Shanahan -
Per Jessen -
Wolfgang Rosenauer