Bug 273622 - Open composer from kontact application if kmail runs from cli with mailto argument
Summary: Open composer from kontact application if kmail runs from cli with mailto arg...
Status: RESOLVED FIXED
Alias: None
Product: kmail2
Classification: Applications
Component: composer (show other bugs)
Version: Git (master)
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-19 10:41 UTC by Murz
Modified: 2011-07-19 09:04 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 4.7.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Murz 2011-05-19 10:41:09 UTC
Version:           Git (master) (using KDE 4.6.3) 
OS:                Linux

I use kontact every time. mailto: links from browser and other apps try to start kmail with arguments, like this:
/usr/bin/kmail mailto:user@example.com?subject=Message

So, if I use kmail, this works normally.
But if I use kontact and have it loaded, I got the message:
Kontact seems to be running on another display on this machine. Running Kontact and KMail at the same time can cause the loss of mail. You should not start KMail unless you are sure that Kontact is not running.
http://i.imgur.com/E9sny.png

kontact didn't accepts any cli arguments, so I don't know how to solve this problem.

Will be good that kmail check the command line and if they have arguments, connects to the kontact and do the action instead of showing this window.

Reproducible: Always
Comment 1 Thomas Tanghus 2011-06-24 07:27:05 UTC
Same issue here.
KDE SC 4.6.4
KDEPIM 4.6.0
KMail 2.1.0
Comment 2 Yngve Levinsen 2011-07-19 07:40:30 UTC
I can confirm this after recent upgrade to KMail 2. Not having mailto: links working is of course not a problem as such for me, but I think it is an important bug that should be fixed soon. If you want to convince your family members to switch to KDE, these things have to work.
Comment 3 Christophe Marin 2011-07-19 09:04:50 UTC
Fixed 5 days ago. Also see bug 265491