Bug 270747 - Kontact GUI sometimes is unresponsive for around 30 seconds
Summary: Kontact GUI sometimes is unresponsive for around 30 seconds
Status: RESOLVED WORKSFORME
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: enterprise
Platform: Microsoft Windows Microsoft Windows
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-04-12 10:56 UTC by Andre Heinecke
Modified: 2011-04-15 12:50 UTC (History)
0 users

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 Andre Heinecke 2011-04-12 10:56:07 UTC 
Version:           enterprise (using Devel) 
OS:                MS Windows

On Windows if you use Kontact and do some GUI actions like opening a messagecomposer switching from one Mail directory to another or even switching the selected application (e.g. from KMail to Korganizer) the GUI freezes and you get the Windows "Kontact is not responding" message.

I was not able to obtain decent debug output. This Bug should serve as a starting point to collect more information on this problem.

The current suspicion is that this might be a DBus problem with the 30 seconds beeing the qdbusinterface.call timeout. 

Reproducible: Sometimes
Comment 1 Andre Heinecke 2011-04-15 12:50:42 UTC 
Several users reported this Bug as gone and it can no longer be reproduced.
Changes were that Akonadi is no longer built with the AKONADI_USE_STRIGI_SEARCH build option but instead now uses Nepomuk.

As a test i've disabled Nepomuk and still was not able to reproduce the hangs. So it might have been the STRIGI_SEARCH buildoption that was the problem with a disfunctional strigidaemon. But that is just speculation