Version: unspecified (using KDE 4.7.2) OS: Linux Purely randomly. But yet always when I had at least so important work to do, that I could not use the crash handler (that opens) to file a report. Kmail2 is not even open. Reproducible: Sometimes Steps to Reproduce: no clue, sorry. it happens randomly, but more than once, so might not be a coincidence Actual Results: crash handler, kmail does still work when you start it Expected Results: no crash handler
Oops, sorry I wanted to ask what debug packages are needed for the (let's hope never) next crash.
the kdepim-runtime and kdepimlibs ones
Created attachment 65951 [details] New crash information added by DrKonqi akonadi_imap_resource (4.7) on KDE Platform 4.7.3 (4.7.3) using Qt 4.7.4 - What I was doing when the application crashed: Putting computer out of suspend mode. Happend once with hibernation, but that time it was another imap folder. (https://bugzilla.novell.com/show_bug.cgi?id=731558) Once while doing something with LibreOffice Writer, minutes (about 5-10) after suspend(!). And I do not remember the times before. -- Backtrace (Reduced): #6 0x0809b376 in takeFirst (this=0x8222e94) at /usr/include/QtCore/qlist.h:477 #7 SessionPool::declareSessionReady (this=0x8222e70, session=0x86a9f68) at /usr/src/debug/kdepim-runtime-4.7.2/resources/imap/sessionpool.cpp:207 #8 0x0809ce79 in SessionPool::onLoginDone (this=0x8222e70, job=0x8282910) at /usr/src/debug/kdepim-runtime-4.7.2/resources/imap/sessionpool.cpp:348 #9 0x0809d1d9 in SessionPool::qt_metacall (this=0x8222e70, _c=QMetaObject::InvokeMetaMethod, _id=10, _a=0xbffe1df8) at /usr/src/debug/kdepim-runtime-4.7.2/build/resources/imap/sessionpool.moc:118 #10 0xb74eb7dd in metacall (argv=0xbffe1df8, idx=14, cl=QMetaObject::InvokeMetaMethod, object=0x8222e70) at kernel/qmetaobject.cpp:237
The IMAP resource has a new maintainer, reassigning to him.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!