Application: kontact (4.14.10) KDE Platform Version: 4.14.17 (Compiled from sources) Qt Version: 4.8.6 Operating System: Linux 4.1.15-8-default x86_64 Distribution: "openSUSE Leap 42.1 (x86_64)" -- Information about the crash: I was running my "all filter" and moving a folder from current to archives, looks like Kmail was not able to manage the load. The crash can be reproduced sometimes. -- Backtrace: Application: Kontact (kontact), signal: Aborted Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7f5651e76800 (LWP 1911))] Thread 5 (Thread 0x7f563522c700 (LWP 1912)): #0 0x00007f56493d003f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f564e556eb6 in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib64/libQtWebKit.so.4 #2 0x00007f564e556ee9 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib64/libQtWebKit.so.4 #3 0x00007f56493cc0a4 in start_thread () from /lib64/libpthread.so.0 #4 0x00007f564f346fed in clone () from /lib64/libc.so.6 Thread 4 (Thread 0x7f55f4929700 (LWP 1913)): #0 0x00007f56493d003f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f564e2c9b3d in JSC::BlockAllocator::blockFreeingThreadMain() () from /usr/lib64/libQtWebKit.so.4 #2 0x00007f564e57ea06 in WTF::wtfThreadEntryPoint(void*) () from /usr/lib64/libQtWebKit.so.4 #3 0x00007f56493cc0a4 in start_thread () from /lib64/libpthread.so.0 #4 0x00007f564f346fed in clone () from /lib64/libc.so.6 Thread 3 (Thread 0x7f55e5021700 (LWP 2061)): #0 0x00007f564f33ebbd in poll () from /lib64/libc.so.6 #1 0x00007f5648dffe64 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007f5648dfff7c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x00007f564fb3bfde in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #4 0x00007f564fb0dd4f in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #5 0x00007f564fb0e045 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #6 0x00007f564fa0b4df in QThread::exec() () from /usr/lib64/libQtCore.so.4 #7 0x00007f564fa0dbbf in ?? () from /usr/lib64/libQtCore.so.4 #8 0x00007f56493cc0a4 in start_thread () from /lib64/libpthread.so.0 #9 0x00007f564f346fed in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7f55dd4f4700 (LWP 18832)): #0 0x00007f56493d003f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f55ec61486b in ?? () from /usr/lib64/libQtScript.so.4 #2 0x00007f55ec6148a9 in ?? () from /usr/lib64/libQtScript.so.4 #3 0x00007f56493cc0a4 in start_thread () from /lib64/libpthread.so.0 #4 0x00007f564f346fed in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7f5651e76800 (LWP 1911)): [KCrash Handler] #6 0x00007f564f2970a7 in raise () from /lib64/libc.so.6 #7 0x00007f564f298458 in abort () from /lib64/libc.so.6 #8 0x00007f564fa036d4 in qt_message_output(QtMsgType, char const*) () from /usr/lib64/libQtCore.so.4 #9 0x00007f564fa03859 in ?? () from /usr/lib64/libQtCore.so.4 #10 0x00007f564fa04064 in qFatal(char const*, ...) () from /usr/lib64/libQtCore.so.4 #11 0x00007f55eb132cb8 in ?? () from /usr/lib64/libkmailprivate.so.4 #12 0x00007f55eb131d1d in ?? () from /usr/lib64/libkmailprivate.so.4 #13 0x00007f55eb136a62 in ?? () from /usr/lib64/libkmailprivate.so.4 #14 0x00007f55eb136c68 in ?? () from /usr/lib64/libkmailprivate.so.4 #15 0x00007f55eb05f085 in KMKernel::dumpDeadLetters() () from /usr/lib64/libkmailprivate.so.4 #16 0x00007f55eb060877 in ?? () from /usr/lib64/libkmailprivate.so.4 #17 0x00007f565128d2d0 in KCrash::defaultCrashHandler (sig=6) at /usr/src/debug/kdelibs-4.14.17/kdeui/util/kcrash.cpp:307 #18 <signal handler called> #19 0x00007f564f2970a7 in raise () from /lib64/libc.so.6 #20 0x00007f564f298458 in abort () from /lib64/libc.so.6 #21 0x00007f564fa036d4 in qt_message_output(QtMsgType, char const*) () from /usr/lib64/libQtCore.so.4 #22 0x00007f564fa03859 in ?? () from /usr/lib64/libQtCore.so.4 #23 0x00007f564fa04064 in qFatal(char const*, ...) () from /usr/lib64/libQtCore.so.4 #24 0x00007f55ea9a7d84 in MailCommon::Kernel::self() () from /usr/lib64/libmailcommon.so.4 #25 0x00007f55ea9effd0 in MailCommon::FolderCollection::writeConfig() const () from /usr/lib64/libmailcommon.so.4 #26 0x00007f55ea9f07d2 in MailCommon::FolderCollection::~FolderCollection() () from /usr/lib64/libmailcommon.so.4 #27 0x00007f55ea9f0849 in MailCommon::FolderCollection::~FolderCollection() () from /usr/lib64/libmailcommon.so.4 #28 0x00007f55ea9ef104 in ?? () from /usr/lib64/libmailcommon.so.4 #29 0x00007f564f299b19 in __run_exit_handlers () from /lib64/libc.so.6 #30 0x00007f564f299b65 in exit () from /lib64/libc.so.6 #31 0x00007f564ffb2a4b in KCmdLineArgs::isSet (this=0x162ec450, _opt=...) at /usr/src/debug/kdelibs-4.14.17/kdecore/kernel/kcmdlineargs.cpp:1520 #32 0x0000000000404087 in _start () Possible duplicates by query: bug 321981, bug 313084, bug 306565. Reported using DrKonqi
This bug has never been confirmed for a KDE PIM version that is based on KDE Frameworks, except possibly a Technology Preview version 5.0.x. Those Framework-based versions differ significantly from the old 4.x series. Therefore, I plan to close it in around two or three months. In the meantime, it is set to WAITINGFORINFO to give reporters the opportunity to check if it is still valid. As soon as someone confirms it for a recent version (at least 5.1, ideally even more recent), I'll gladly reopen it. Please understand that we lack the manpower to triage bugs reported for versions almost two years beyond their end of life.
Hi Denis, Thks for your feedback. I've been away from home since February, didn't check my Kontact nore did have any opportunity to update it. I need to plan this update as it will be very complicated, I will have to re-setup all the simlink to the partition where my email database is installed (different HDD) and that takes a long annoying time (compared to Thunderbird which does it with one click) By the time I come back home this will be closed. I will re-open one if necessary Have a great day ! Éric Le 2017-06-23 16:29, Denis Kurz a écrit : > https://bugs.kde.org/show_bug.cgi?id=360524 > > Denis Kurz <kdenis@posteo.de> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |kdenis@posteo.de > Resolution|--- |WAITINGFORINFO > Status|UNCONFIRMED |NEEDSINFO > > --- Comment #1 from Denis Kurz <kdenis@posteo.de> --- > This bug has never been confirmed for a KDE PIM version that is based > on KDE > Frameworks, except possibly a Technology Preview version 5.0.x. Those > Framework-based versions differ significantly from the old 4.x series. > Therefore, I plan to close it in around two or three months. In the > meantime, > it is set to WAITINGFORINFO to give reporters the opportunity to check > if it is > still valid. As soon as someone confirms it for a recent version (at > least 5.1, > ideally even more recent), I'll gladly reopen it. > > Please understand that we lack the manpower to triage bugs reported for > versions almost two years beyond their end of life.
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!