Bug 108227

Summary:	Thunderbird will not open when sending emails in Digikam
Product:	[Applications] digikam	Reporter:	Jostein Berntsen <jbernts>
Component:	Plugin-Generic-SendByMail	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	normal	CC:	ainsaur
Priority:	NOR
Version:	5.6.0
Target Milestone:	---
Platform:	unspecified
OS:	Linux
Latest Commit:		Version Fixed In:	0.1.0
Sentry Crash Report:

Description Jostein Berntsen 2005-06-27 17:22:50 UTC

Version:           0.1.1 (using KDE 3.4.1 Level "a" , SUSE 9.2 UNSUPPORTED)
Compiler:          gcc version 3.3.4 (pre 3.3.5 20040809)
OS:                Linux (i686) release 2.6.8-747.inotify.2-default

When selecting thunderbird as the mail client in Digikam the "Preparing images to send" dialog box hangs at "Starting mailer agent..." and Thunderbird is not opened. No error messages. Other mail clients like kmail and mozilla works. The thunderbird path is /usr/bin/thunderbird, and works from the command line as wellas Alt-F2.

Comment 1 Tom Albers 2005-09-03 17:22:50 UTC

SVN commit 456755 by toma:

Thunderbird does not return the dot in this error message, so thunderbird was not started and the composer can not be started in that case. 
Also replaced the 'contains' with a 'find' which is faster, I learned that from Ingo, which is pretty funny in this case ;-)

BUGS: 108227
CCMAIL: oliver@doerr-privat.de 


 M  +1 -1      sendimages.cpp  


--- trunk/extragear/libs/kipi-plugins/sendimages/sendimages.cpp #456754:456755
@@ -637,7 +637,7 @@
 
 void SendImages::slotMozillaExited(KProcess*)
 {
-    if ( m_mozillaStdErr.contains("No running window found.") == true )   // No remote Mozilla | Netscape |
+    if ( m_mozillaStdErr.find("No running window found") != -1 )   // No remote Mozilla | Netscape |
        {                                                                  // Thunderbird env. loaded !
        m_mailAgentProc2 = new KProcess;                                   // Init a new env.

Comment 2 Tom Albers 2006-04-30 01:25:45 UTC

*** Bug 126493 has been marked as a duplicate of this bug. ***