Bug 229555 - Kontact freezes after initial syncing with Kolab
Summary: Kontact freezes after initial syncing with Kolab
Status: RESOLVED FIXED
Alias: None
Product: Akonadi
Classification: Frameworks and Libraries
Component: Kolab Resource (show other bugs)
Version: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-05 15:36 UTC by Fabian Köster
Modified: 2012-06-08 12:40 UTC (History)
3 users (show)

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

Attachments
gdb output & backtrace (18.93 KB, text/plain)
2010-03-05 15:37 UTC, Fabian Köster 		Details
View All Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Fabian Köster 2010-03-05 15:36:23 UTC 
Version:            (using KDE 4.4.1)
OS:                Linux
Installed from:    Ubuntu Packages

I am currently testing Kolab support of Kubuntu Lucid. Currently Lucid contains KDE 4.4.1, the version of the kdepim-package is 4:4.4.1a-0ubuntu1 the corresponding debug-packages are installed.

What I did:

1) Purge .kde directory completely
2) Run kolabwizard (Configuring a corporate Kolab server)
3) Start gdb kontact
4) Execute run --nofork

In KMail I start syncing of E-Mails and after all folders and messages are downloaded completely, Kontact crashes. Attaching the backtrace of gdb.

I do not know the exact version of the Kolab server running at my company, but I could determine this. If you need more information just let me know.
Comment 1 Fabian Köster 2010-03-05 15:37:17 UTC 
Created attachment 41353 [details]
gdb output & backtrace
Comment 2 Fabian Köster 2010-03-05 16:23:21 UTC 
I have to correct my first description, Kontact does not crash but it freezes and consumes ~100% CPU time. Looks like an infinite loop.

Sorry for the noise.
Comment 3 Christophe Marin 2010-03-26 14:33:53 UTC 
Changing from crash to normal.
Comment 4 Christophe Marin 2011-10-01 00:05:09 UTC 
Reassign, but I doubt this report is still valid in kdepim > 4.6
Comment 5 Christian Mollekopf 2012-06-08 12:40:43 UTC 
accountwizard works, and the backtrace is for sure invalid against kdepim > 4.6. So consider it fixed.