[Bug 227636] Kontact starting, running, but doesn't show up

Thomas McGuire mcguire at kde.org
Thu Feb 25 15:07:17 GMT 2010


https://bugs.kde.org/show_bug.cgi?id=227636





--- Comment #10 from Thomas McGuire <mcguire kde org>  2010-02-25 16:07:11 ---
BTW: Slow sending is unrelated to this bug report, which is about Kontact not
starting up. Further discussions should take place at bug 219687.

> Well, certainly from a user PoV, it's not the same.  We talked before of 
> delays of up to a minute when sending messages.  As I said here, in this case > it froze so completely that I couldn't do anything at all with KMail, and I 
> waited for more than 10 minutes, by which time it seemed beyond recovery.

The delays depend on how long Nepomuk takes to execute the search. This can
actually be 10 minutes or more, depending on how much Strigi has indexed.
That's also the reason I didn't see this problem before release: I had Strigi
file indexing disabled.

> The reason I asked for priority raising was that using the applications as 
> stand-alone would be a work-around, but in fact the work-around was failing.

I see. In case of the delays when sending or switching messages, running
standalone vs running in Kontact makes no difference.

> but with KMail working, even as stand-alone, I am constantly on
> 98-99% CPU.

Constantly? That sounds wrong. During mail fetch/sync, the CPU usage of course
peeks, but it shouldn't be 100% constantly. Is it really KMail that is using
the CPU or some other process?

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Kdepim-bugs mailing list