Application: kontact (4.14.3) KDE Platform Version: 4.14.3 (Compiled from sources) Qt Version: 4.8.5 Operating System: Linux 3.19.2-gentoo x86_64 Distribution (Platform): Gentoo Packages -- Information about the crash: - What I was doing when the application crashed: I was login into my session after a boot up. Kontact automatically starts as it was running the last time I shutdown the computer. If I enter directly my masterpassword for the kdewallet everything's fine. PB happens if I am not in front of my PC while the session is started, like when I enter that masterpassword 10mins after I logged in. - Unusual behavior I noticed: 1. Behind the kdewallet "pop up" for entering the masterpassword, a Manage Sieve password "pop-up" from Kontact asking for the ManageSieve account password is shown. I believed like for the rest the password of ManageSieve is also stored in KDEWallet but I am not so sure anymore... 2. When I finally enter the masterpassword in the KDEWallet pop-up and then the ManageSieve password in the Kontact pop up, I get this crash of Kontact. This has been systematically happening. Not a big issue are restart the soft works very fine but it is not right either. - Custom settings of the application: Manage Sieve protocol configure connecting to a ManageSieve server integrated in a Dovecot IMAP install. net-mail/dovecot-2.2.13-r1 The crash can be reproduced every time. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault Using host libthread_db library "/lib64/libthread_db.so.1". [Current thread is 1 (Thread 0x7fd3ffc037c0 (LWP 3680))] Thread 3 (Thread 0x7fd3df770700 (LWP 3682)): #0 0x00007fd3f7a4b53f in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007fd3faa9af6a in ?? () from /usr/lib64/qt4/libQtWebKit.so.4 #2 0x00007fd3faa9afa9 in ?? () from /usr/lib64/qt4/libQtWebKit.so.4 #3 0x00007fd3f7a47204 in start_thread () from /lib64/libpthread.so.0 #4 0x00007fd3fd1d65bd in clone () from /lib64/libc.so.6 Thread 2 (Thread 0x7fd3dee6f700 (LWP 3684)): #0 0x00007fd3fd1cd96d in poll () from /lib64/libc.so.6 #1 0x00007fd3f6e2c724 in ?? () from /usr/lib64/libglib-2.0.so.0 #2 0x00007fd3f6e2c82c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #3 0x00007fd3fe5c5ebe in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4 #4 0x00007fd3fe5974bf in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4 #5 0x00007fd3fe5977b5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4 #6 0x00007fd3fe493abf in QThread::exec() () from /usr/lib64/qt4/libQtCore.so.4 #7 0x00007fd3fe4961ff in ?? () from /usr/lib64/qt4/libQtCore.so.4 #8 0x00007fd3f7a47204 in start_thread () from /lib64/libpthread.so.0 #9 0x00007fd3fd1d65bd in clone () from /lib64/libc.so.6 Thread 1 (Thread 0x7fd3ffc037c0 (LWP 3680)): [KCrash Handler] #5 0x00007fd3fe54f847 in QUrl::setUserName(QString const&) () from /usr/lib64/qt4/libQtCore.so.4 #6 0x00007fd39254a4d8 in ?? () from /usr/lib64/libkmanagesieve.so.4 #7 0x00007fd39254a9cc in ?? () from /usr/lib64/libkmanagesieve.so.4 #8 0x00007fd39254b4e9 in ?? () from /usr/lib64/libkmanagesieve.so.4 #9 0x00007fd39254c224 in ?? () from /usr/lib64/libkmanagesieve.so.4 #10 0x00007fd3fe5ac97a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4 #11 0x00007fd3feab61a2 in ?? () from /usr/lib64/libkdecore.so.5 #12 0x00007fd3fe5ac97a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4 #13 0x00007fd3f89f593f in ?? () from /usr/lib64/qt4/libQtNetwork.so.4 #14 0x00007fd3f89ef539 in ?? () from /usr/lib64/qt4/libQtNetwork.so.4 #15 0x00007fd3fe5ac97a in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/qt4/libQtCore.so.4 #16 0x00007fd3f89cf92d in ?? () from /usr/lib64/qt4/libQtNetwork.so.4 #17 0x00007fd3f89d8b0d in ?? () from /usr/lib64/qt4/libQtNetwork.so.4 #18 0x00007fd3fd95338c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #19 0x00007fd3fd959b40 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/qt4/libQtGui.so.4 #20 0x00007fd3ff00f30a in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #21 0x00007fd3fe59889d in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/qt4/libQtCore.so.4 #22 0x00007fd3fe5c6be6 in ?? () from /usr/lib64/qt4/libQtCore.so.4 #23 0x00007fd3f6e2c544 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #24 0x00007fd3f6e2c788 in ?? () from /usr/lib64/libglib-2.0.so.0 #25 0x00007fd3f6e2c82c in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #26 0x00007fd3fe5c5e9e in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4 #27 0x00007fd3fd9f18b6 in ?? () from /usr/lib64/qt4/libQtGui.so.4 #28 0x00007fd3fe5974bf in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4 #29 0x00007fd3fe5977b5 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/qt4/libQtCore.so.4 #30 0x00007fd3fe59ca89 in QCoreApplication::exec() () from /usr/lib64/qt4/libQtCore.so.4 #31 0x00000000004035d2 in ?? () #32 0x00007fd3fd110aa5 in __libc_start_main () from /lib64/libc.so.6 #33 0x0000000000403a79 in _start () Possible duplicates by query: bug 320127. Reported using DrKonqi
This bug has never been confirmed for a Kontact version that is based on KDE Frameworks (5.x). Those 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 oportunity 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.
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.