Bugzilla – Bug 347116
Firefox not honoring kde default mail program setting
Last modified: 2007-12-08 20:21:01 UTC
if you go into the kde personalization settings, select component chooser and change the default email program to something other than kmail, firefox does not honor this setting and always opens mailto links with kmail. Konqueror is honoring the setting and opening mailto links with the alternat email program.
Basically that's a duplicate of bug #113512. The other bug talks mainly about mapping mime-types of files to proper handlers and therefore is not exactly the same. These protocol handlers (like mailto:) are read from gconf by Firefox. Since KDE isn't used on KDE it's preconfigured to use Gnome applications. I'm not sure what the default is on 10.3 for mailto links. For me it's evolution so I'm not sure why it's kmail for you. It also could be another setting in your Firefox. In case you have gconf-editor installed you can easily change that setting under /desktop/gnome/url-handlers/mailto. You also need to check if you got somehow kmail set up in Firefox directly. Type "about:config" in your url bar and search for "protocol-handler". By default you shouldn't have an entry for "network.protocol-handler.app.mailto" Please let us know if that information is sufficient to solve your issue. If not, please let me know what you find out about the information above.
sorry your right, it is an evolution new message and not kmail. there was no help in the message window for me to triple check what mail client it had opened so I simply assumed it was using the default client listed in the kde component chooser which happened to be kmail. Also, yes firefox does seem to listen to the gnome settings and not KDE so I have it working at least, but overall this is not good. As the #2 browser KDE and opensuse should assume that people are going to be installing it on their kde desktops and therefor have it listen to whatever config kde has set as opposed to hard coding it to use the gnome config files. Since this issue has been brought up in the bug 113512 then close this one and I'll add my complaints over there.
*** This bug has been marked as a duplicate of bug 113512 ***