Bug 361279 - after changing sent/draft/etc.folders in identitys, kmail crashed on next start
Summary: after changing sent/draft/etc.folders in identitys, kmail crashed on next start
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords: drkonqi
Depends on:
Blocks:
 
Reported: 2016-04-01 13:54 UTC by chymian
Modified: 2018-02-01 09:44 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description chymian 2016-04-01 13:54:43 UTC
Application: kontact (4.14.10)
KDE Platform Version: 4.14.14
Qt Version: 4.8.7
Operating System: Linux 4.3.0-1-amd64 x86_64
Distribution: Debian GNU/Linux testing (stretch)

-- Information about the crash:
- What I was doing when the application crashed:
after changing sent/draft/etc.folders in identitys, kmail crashed on next start.
inbetween, akonadictl restart, fsck, vacuum
- Unusual behavior I noticed:
it crahs far to oftn in this days

The crash can be reproduced sometimes.

-- Backtrace:
Application: Kontact (kontact), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f508c47a940 (LWP 10117))]

Thread 7 (Thread 0x7f506c524700 (LWP 10118)):
#0  0x00007f50836bb04f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0
#1  0x00007f5088ba9a4d in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x00007f5088ba9aa9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x00007f50836b5454 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#4  0x00007f5089958edd in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 6 (Thread 0x7f502bc21700 (LWP 10119)):
#0  0x00007f50836bb04f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0
#1  0x00007f50888cd191 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#2  0x00007f5088bd9fe6 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4
#3  0x00007f50836b5454 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#4  0x00007f5089958edd in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 5 (Thread 0x7f501b71e700 (LWP 10124)):
#0  0x00007f508994fe4d in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007f50831cd32c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f50831cd43c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f508a14a326 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x00007f508a118251 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#5  0x00007f508a1185c5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x00007f508a007569 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7  0x00007f508a009e5c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8  0x00007f50836b5454 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#9  0x00007f5089958edd in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 4 (Thread 0x7f5010c03700 (LWP 10323)):
#0  0x00007f50836bb04f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/x86_64-linux-gnu/libpthread.so.0
#1  0x00007f5022ae9cca in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#2  0x00007f5022ae9cf9 in ?? () from /usr/lib/x86_64-linux-gnu/libQtScript.so.4
#3  0x00007f50836b5454 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#4  0x00007f5089958edd in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 3 (Thread 0x7f501946b700 (LWP 29115)):
#0  0x00007f508994fe4d in poll () from /lib/x86_64-linux-gnu/libc.so.6
#1  0x00007f50831cd32c in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f50831cd43c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f508a14a326 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#4  0x00007f508a118251 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#5  0x00007f508a1185c5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x00007f508a007569 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7  0x00007f508a0f82b3 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8  0x00007f508a009e5c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x00007f50836b5454 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#10 0x00007f5089958edd in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 2 (Thread 0x7f4f7ffff700 (LWP 29122)):
#0  0x00007f5083211a94 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007f50831ccd59 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f50831cd2d0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f50831cd43c in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f508a14a326 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#5  0x00007f508a118251 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#6  0x00007f508a1185c5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#7  0x00007f508a007569 in QThread::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#8  0x00007f508a0f82b3 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x00007f508a009e5c in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#10 0x00007f50836b5454 in start_thread () from /lib/x86_64-linux-gnu/libpthread.so.0
#11 0x00007f5089958edd in clone () from /lib/x86_64-linux-gnu/libc.so.6

Thread 1 (Thread 0x7f508c47a940 (LWP 10117)):
[KCrash Handler]
#6  0x00007f50898a3478 in raise () from /lib/x86_64-linux-gnu/libc.so.6
#7  0x00007f50898a48fa in abort () from /lib/x86_64-linux-gnu/libc.so.6
#8  0x00007f5089ffef35 in qt_message_output(QtMsgType, char const*) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#9  0x00007f5089fff391 in ?? () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#10 0x00007f5089fffcb1 in qFatal(char const*, ...) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#11 0x00007f502120b9b7 in MailCommon::Kernel::self() () from /usr/lib/libmailcommon.so.4
#12 0x00007f502125feb3 in MailCommon::FolderCollection::writeConfig() const () from /usr/lib/libmailcommon.so.4
#13 0x00007f5021260762 in MailCommon::FolderCollection::~FolderCollection() () from /usr/lib/libmailcommon.so.4
#14 0x00007f50212607d9 in MailCommon::FolderCollection::~FolderCollection() () from /usr/lib/libmailcommon.so.4
#15 0x00007f502125ecf5 in ?? () from /usr/lib/libmailcommon.so.4
#16 0x00007f50898a5e08 in ?? () from /lib/x86_64-linux-gnu/libc.so.6
#17 0x00007f50898a5e55 in exit () from /lib/x86_64-linux-gnu/libc.so.6
#18 0x00007f508a5d336e in KCmdLineArgs::isSet(QByteArray const&) const () from /usr/lib/libkdecore.so.5
#19 0x0000000000404351 in _start ()

Possible duplicates by query: bug 360524, bug 359607, bug 359461, bug 358650, bug 357924.

Reported using DrKonqi
Comment 1 Denis Kurz 2017-06-23 22:06:45 UTC
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.
Comment 2 Denis Kurz 2018-02-01 09:44:01 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.1 aka 15.12; preferably much more recent), please open a new one unless it already exists. Thank you for all your input.