Bug 227447 - kmail interaction with nepomuk slows sending mail
Summary: kmail interaction with nepomuk slows sending mail
Status: RESOLVED DUPLICATE of bug 219687
Alias: None
Product: kmail
Classification: Unmaintained
Component: general (show other bugs)
Version: 1.13.0
Platform: unspecified Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-17 23:52 UTC by Danny Auble
Modified: 2010-02-19 13:22 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Danny Auble 2010-02-17 23:52:04 UTC 
Version:           1.13.0 (using 4.4.00 (KDE 4.4.0), Kubuntu packages)
Compiler:          cc
OS:                Linux (x86_64) release 2.6.31-19-generic

When sending a message with kmail it takes multiple seconds, sometimes minutes before the letter begins to send.  If you run nepomukserver in the foreground you get an outrageous number of messages like...

[/usr/bin/nepomukservicestub] nepomukqueryservice(25571)/nepomuk (query service) Nepomuk::Query::SearchThread::sparqlQuery: Found result:  QUrl( "akonadi:?item=31263" )

It appears to go through this list 3 times before the send of the message.

This happens any time I send a message.  If I don't specify the subject this happens before that also.  Please contact me if you need any more information since this is really annoying, and didn't happen before KDE 4.4.
Comment 1 Basti 2010-02-18 13:14:06 UTC 
Here KMail slows down everytime it receives a mail when nepomuk is active. How do I start nepomukserver in the foreground to see the messages?
Comment 2 Danny Auble 2010-02-18 17:32:48 UTC 
All you have to do is kill the nepomukeserver

qdbus org.kde.NepomukServer /nepomukserver quit

and then run nepomuksever

My experience is all the output is fed to the term.
Comment 3 Thomas McGuire 2010-02-19 13:22:02 UTC 

*** This bug has been marked as a duplicate of bug 219687 ***