Bug 422199

Summary: Akonadi crashes while KMail fetches IMAP-Servers
Product: [Frameworks and Libraries] Akonadi Reporter: Peter Huyoff <peter.huyoff>
Component: serverAssignee: kdepim bugs <kdepim-bugs>
Status: RESOLVED DUPLICATE    
Severity: crash CC: dvratil, peter.huyoff
Priority: NOR Keywords: drkonqi
Version: unspecified   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed In:

Description Peter Huyoff 2020-05-28 21:03:10 UTC
Application: akonadiserver (5.14.1 (20.04.0))

Qt Version: 5.14.1
Frameworks Version: 5.70.0
Operating System: Linux 5.6.12-1-default x86_64
Windowing system: X11
Distribution: "openSUSE Tumbleweed"

-- Information about the crash:
- What I was doing when the application crashed:

System powered on, KMail starts and begins fetching IMAP-Servers. Then Akonadi crashes, but runs fine after restarting it.

-- Backtrace (Reduced):
#4  0x00007fccf0f55b19 in qHash (key=..., seed=608053022) at ../../include/QtCore/../../src/corelib/text/qstring.h:266
#5  0x000056376fa81a3b in QHash<QString, Akonadi::Server::AbstractItemRetrievalJob*>::findNode (this=this@entry=0x56376fbef338, akey=..., ahp=ahp@entry=0x0) at /usr/include/qt5/QtCore/qhash.h:950
#6  0x000056376fa83f3e in QHash<QString, Akonadi::Server::AbstractItemRetrievalJob*>::remove (akey=..., this=0x56376fbef338) at /usr/include/qt5/QtCore/qrefcount.h:102
#7  Akonadi::Server::ItemRetrievalManager::retrievalJobFinished (this=0x56376fbef300, request=0x7fcca0481830, errorMsg=...) at /usr/src/debug/akonadi-server-20.04.1-1.1.x86_64/src/server/storage/itemretrievalmanager.cpp:179
#8  0x00007fccf11259de in QtPrivate::QSlotObjectBase::call (a=0x7fcce6ffc810, r=0x56376fbef300, this=0x7fccdc00d890) at ../../include/QtCore/../../src/corelib/kernel/qobjectdefs_impl.h:394


The reporter indicates this bug may be a duplicate of or related to bug 421077.

Possible duplicates by query: bug 422092, bug 421820, bug 421812, bug 421681, bug 421668.

Reported using DrKonqi
Comment 1 Daniel Vrátil 2020-06-14 11:47:32 UTC

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