User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:126.96.36.199) Gecko/20061208 Firefox/188.8.131.52 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:184.108.40.206) Gecko/20061208 Firefox/220.127.116.11 Clicking on a link of the type href="mailto:firstname.lastname@example.org" fails to open email MUA, this whether MUA is currently running or not. Reproducible: Always Steps to Reproduce: 1. Ascertain that MUA functions properly, e.g., run "thunderbird -compose mailto:email@example.com". Do this with thunderbird currently running and not currently running. (All this works fine for me.) 2. Open an html document with a mailto link in it. 3. Clink on that mailto link. Actual Results: Step #1 works fine. Nothing happens after step #3. Expected Results: Should open MUA in compose mode, e.g., thunderbird Compose window, with mailto's URI plugged into relevant fields (e.g., To, Subject). Other folks are talking about this same problem at http://forums.mozillazine.org/viewtopic.php?t=511496&sid=58214636af026e08708d08d390729bb0. This problem was discussed a couple years ago (see https://bugzilla.mozilla.org/show_bug.cgi?id=56478). about:buildconfig ::::::::::: Build platform target i686-pc-linux-gnu Build tools Compiler Version Compiler flags gcc gcc version 3.3.2 20031022 (Red Hat Linux 3.3.2-1) -Wall -W -Wno-unused -Wpointer-arith -Wcast-align -Wno-long-long -pedantic -pthread -pipe c++ gcc version 3.3.2 20031022 (Red Hat Linux 3.3.2-1) -fno-rtti -fno-exceptions -Wall -Wconversion -Wpointer-arith -Wcast-align -Woverloaded-virtual -Wsynth -Wno-ctor-dtor-privacy -Wno-non-virtual-dtor -Wno-long-long -pedantic -fshort-wchar -pthread -pipe -I/usr/X11R6/include Configure arguments --enable-application=browser --enable-update-channel=release --enable-update-packaging --enable-official-branding --disable-debug '--enable-optimize=-Os -freorder-blocks -fno-reorder-functions -gstabs+' --disable-tests --enable-default-toolkit=gtk2 --enable-xft --disable-freetype2 --enable-svg --enable-canvas --enable-static --disable-shared
Out of curiousity, does this work with Firefox 2.0.0?
As stated in the fourth line in the description, this bug is found in Firefox/18.104.22.168.
Keywords: mail4, useless-UI
That doesn't answer my question. Is it a problem in 22.214.171.124 but NOT in 2.0.0, or is it a problem in both? That is, is this something that broke due to a change in the security release, or something that broke between 1.5 and 2.0?
WFM on windows... is this happening to only a handful of people, but all platforms? or only on Linux but to everyone on Linux?
Can't block on an unconfirmed bug -- can we get an answer to comment 4? Anyone besides the reporter seeing this problem?
juanb/tony: Can either of you please test this on linux and report back whether you are seeing this or not? Thanks!
FWIW, it works fine with my self-compiled Firefox 126.96.36.199pre and Thunderbird 2 beta 1-ish, on SuSE 10.1. The distro's FF 1.5.0.x and Thunderbird are also installed and may be part of it (mozilla/mozilla-x-remote scripts and friends in /usr/bin/ etc.).
Running: Fedora linux Thunderbird v 2 beta 2 (20070116) Firefox 188.8.131.52: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:184.108.40.206) Gecko/20061208 Firefox/220.127.116.11 Unable to repro original problem. i was able to open thunderbird compose via terminal. also created a html document with mailto link and clicking it in Firefox 18.104.22.168 will launch thunderbird compose window.
Tony, What value do you have in (about:config) network.protocol-handler.app.mailto ? And isn't this value (whatever it is) supposed to be a command which is executed when a mailto link is clicked?
(In reply to comment #4) > WFM on windows... is this happening to only a handful of people, but all > platforms? or only on Linux but to everyone on Linux? > Other folks are talking about this same problem at http://forums.mozillazine.org/viewtopic.php?t=511496&sid=58214636af026e08708d08d390729bb0.
Same problem talked about at: http://help.lockergnome.com/linux/mailto-Firefox-Thunderbird-ftopict387604.html
> What value do you have in (about:config) network.protocol-handler.app.mailto ? Well, what value do *you* have there, and how did it get there? I don't have *any* network.protocol-handler.app.* . I do have: network.protocol-handler.expose.mailto default false network.protocol-handler.external.mailto default true network.protocol-handler.warn-external.mailto default false
(In reply to comment #12) > > What value do you have in (about:config) network.protocol-handler.app.mailto ? > > Well, what value do *you* have there, and how did it get there? > > I don't have *any* network.protocol-handler.app.* . I do have: > > network.protocol-handler.expose.mailto default false > network.protocol-handler.external.mailto default true > network.protocol-handler.warn-external.mailto default false > I have those *also*. In network.protocol-handler.app I have thunderbird, but I've had all those that are mentioned on the forums cited *above*, plus a dozen or so *more* variations of those. The network.protocol-handler.app was *there* when I first went into it, so the firefox install must have put it there or it picked it up from the *previous version* of FF I had installed. Are you running *gnome*? If so, what does gconf-editor show for /schemas/desktop/gnome/url-handlers/mailto and /desktop/gnome/url-handlers/mailto *??* *Thanks*
Please just tell us which prefs (related to this, and surely everything matching "mailto") your have set, and particularly which ones are not default. If there are any non-default ones, set all of them back to default and try again, if you haven't done so yet. > I've had all those that are mentioned on the forums cited *above* Please don't assume that we'll have through the forum threads, but *summarize* the *outcome*.
Guys, how about we try seeing what's going on instead of just asking questions? ;) kf, can you please do the following? 1) Set the NSPR_LOG_MODULES environment variable to the value "HelperAppService:5". 2) Set the NSPR_LOG_FILE environment variable to an absolute path of your choice. 3) Start Firefox in whatever shell you set those in. 4) Reproduce the problem once. 5) Quite Firefox. 6) Attach the resulting log file to this bug. That'll give us a starting point to work with, at least.
This only appears to affect a few people, until we get more info that suggests something worse we're not going to hold 22.214.171.124 for it. Has anyone investigated whether the people seeing this bug are all using the same distro, or KDE vs Gnome, or some other commonality?
Flags: blocking126.96.36.199? → blocking188.8.131.52?
kf, have you had a chance to get a log file per comment 15?
This is not going to block the next release at this point - kf never answered the question in comment 3 (regression or not). That will tell us a lot about whether to look for config issues on his machine or things in Firefox. - kf never got the requested debug logs which would tell us what's going on on his system. Until this gets confirmed and we know what we're dealing with blocking is unrealistic.
no more reaction from kf. Is this a candidate for WFM or INVALID?
Hi All, I am having the problem with Linux Firefox (firefox-184.108.40.206-1.fc4.remi.i386.rpm) under CentOS 5.0 (Red Hat Enterprise Linux 5.0 clone). My settings are: grep -i mailto prefs.js user_pref("network.protocol-handler.app.mailto", "/usr/bin/thunderbird --compose %s"); user_pref("network.protocol-handler.expose.mailto", true); user_pref("network.protocol-handler.warn-external.mailto", true); When I click on a MailTo: link, I get the pop up (External Protocol Request) that tells me it is about to start "/usr/bin/thunderbird --compose %s". When I click on "Launch Application", the box disappears and nothing else happens. As a test, I can run "/usr/bin/thunderbird --compose mailto:firstname.lastname@example.org" from the command line. Please let me know how I can assist with this bug. It may take me three or four days to respond, but I will respond. Many thanks, -T
wfm on Mac OS X + FF 220.127.116.11. So this plus #5, can we agree this is linux-only?
No symptom change under firefox-18.104.22.168-1.fc6.remi.i386
Isn't this duplicate of bug 296635
This bug was reported on Firefox 2.x or older, which is no longer supported and will not be receiving any more updates. I strongly suggest that you update to Firefox 3.6.3 or later, update your plugins (flash, adobe, etc.), and retest in a new profile. If you still see the issue with the updated Firefox, please post here. Otherwise, please close as RESOLVED > WORKSFORME http://www.mozilla.com http://support.mozilla.com/kb/Managing+profiles http://support.mozilla.com/kb/Safe+mode
Whiteboard: [CLOSEME 5-15-2010]
Version: unspecified → 2.0 Branch
No reply, INCOMPLETE. Please retest with Firefox 3.6.x or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 8 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.