Application: kontact (4.13 rc) KDE Platform Version: 4.12.97 Qt Version: 4.8.6 Operating System: Linux 3.11.0-19-generic x86_64 Distribution: Ubuntu 13.10 -- Information about the crash: I typed a search term in the search box in Kmail. The problem promptly quit. This happend three sucessive times. The crash can be reproduced every time. -- 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 0x7f6a39793800 (LWP 26997))] Thread 5 (Thread 0x7f6a18dca700 (LWP 26998)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007f6a345421cd in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x00007f6a34542209 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x00007f6a30c61f6e in start_thread (arg=0x7f6a18dca700) at pthread_create.c:311 #4 0x00007f6a36d169cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 4 (Thread 0x7f69d84c7700 (LWP 26999)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007f6a34282bbd in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x00007f6a34571a76 in ?? () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x00007f6a30c61f6e in start_thread (arg=0x7f69d84c7700) at pthread_create.c:311 #4 0x00007f6a36d169cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 3 (Thread 0x7f69c44c6700 (LWP 27002)): #0 0x00007f6a36d086bd in read () at ../sysdeps/unix/syscall-template.S:81 #1 0x00007f6a307c8670 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f6a307891cc in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f6a3078963b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007f6a307897ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x00007f6a37492af6 in QEventDispatcherGlib::processEvents (this=0x7f69bc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #6 0x00007f6a3746430f in QEventLoop::processEvents (this=this@entry=0x7f69c44c5d70, flags=...) at kernel/qeventloop.cpp:149 #7 0x00007f6a37464605 in QEventLoop::exec (this=this@entry=0x7f69c44c5d70, flags=...) at kernel/qeventloop.cpp:204 #8 0x00007f6a37360c4f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:537 #9 0x00007f6a3736331f in QThreadPrivate::start (arg=0x1627fe0) at thread/qthread_unix.cpp:349 #10 0x00007f6a30c61f6e in start_thread (arg=0x7f69c44c6700) at pthread_create.c:311 #11 0x00007f6a36d169cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 2 (Thread 0x7f69c1be4700 (LWP 27006)): #0 0x00007f6a36d09f7d in poll () at ../sysdeps/unix/syscall-template.S:81 #1 0x00007f6a307896a4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f6a307897ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f6a37492af6 in QEventDispatcherGlib::processEvents (this=0x7f69b80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #4 0x00007f6a3746430f in QEventLoop::processEvents (this=this@entry=0x7f69c1be3d30, flags=...) at kernel/qeventloop.cpp:149 #5 0x00007f6a37464605 in QEventLoop::exec (this=this@entry=0x7f69c1be3d30, flags=...) at kernel/qeventloop.cpp:204 #6 0x00007f6a37360c4f in QThread::exec (this=this@entry=0x2608af0) at thread/qthread.cpp:537 #7 0x00007f6a37445a33 in QInotifyFileSystemWatcherEngine::run (this=0x2608af0) at io/qfilesystemwatcher_inotify.cpp:265 #8 0x00007f6a3736331f in QThreadPrivate::start (arg=0x2608af0) at thread/qthread_unix.cpp:349 #9 0x00007f6a30c61f6e in start_thread (arg=0x7f69c1be4700) at pthread_create.c:311 #10 0x00007f6a36d169cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 1 (Thread 0x7f6a39793800 (LWP 26997)): [KCrash Handler] #6 0x00007f6a36c52f77 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #7 0x00007f6a36c565e8 in __GI_abort () at abort.c:90 #8 0x00007f6a370446e5 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #9 0x00007f6a37042856 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #10 0x00007f6a37042883 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #11 0x00007f6a37042af6 in __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #12 0x00007f6a374647f6 in QEventLoop::exec (this=this@entry=0x7fff43e05bc0, flags=...) at kernel/qeventloop.cpp:218 #13 0x00007f6a37469deb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225 #14 0x00007f6a37e563cc in QApplication::exec () at kernel/qapplication.cpp:3828 #15 0x0000000000403660 in main (argc=1, argv=0x7fff43e05e08) at ../../../kontact/src/main.cpp:219 Possible duplicates by query: bug 333332, bug 333327, bug 333318, bug 333253, bug 333141. Reported using DrKonqi
Created attachment 86546 [details] New crash information added by DrKonqi kontact (4.13) on KDE Platform 4.13.0 using Qt 4.8.6 - What I was doing when the application crashed: KDE 4.13 Kontact's search in e-mails crashed reproduceably every time when used. -- Backtrace (Reduced): #6 0x00007f0ecc456f79 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #7 0x00007f0ecc45a388 in __GI_abort () at abort.c:89 [...] #12 0x00007f0eccc66596 in QEventLoop::exec (this=this@entry=0x7fffc294ed80, flags=...) at kernel/qeventloop.cpp:218 #13 0x00007f0eccc6bb79 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225 #14 0x00007f0ecd65837c in QApplication::exec () at kernel/qapplication.cpp:3828
Created attachment 86547 [details] New crash information added by DrKonqi kontact (4.13) on KDE Platform 4.13.0 using Qt 4.8.6 - What I was doing when the application crashed: KDE 4.13 Kontact's search in e-mails crashed again after typing a few letters into the search field. -- Backtrace (Reduced): #6 0x00007f2bbb707f79 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #7 0x00007f2bbb70b388 in __GI_abort () at abort.c:89 [...] #12 0x00007f2bbbf17596 in QEventLoop::exec (this=this@entry=0x7fffa42b1f80, flags=...) at kernel/qeventloop.cpp:218 #13 0x00007f2bbbf1cb79 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225 #14 0x00007f2bbc90937c in QApplication::exec () at kernel/qapplication.cpp:3828
Created attachment 86548 [details] New crash information added by DrKonqi kontact (4.13) on KDE Platform 4.13.0 using Qt 4.8.6 - What I was doing when the application crashed: It crashed again after typing something into the search field. -- Backtrace (Reduced): #6 0x00007ffa681f1f79 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #7 0x00007ffa681f5388 in __GI_abort () at abort.c:89 [...] #12 0x00007ffa68a01596 in QEventLoop::exec (this=this@entry=0x7fff294af1d0, flags=...) at kernel/qeventloop.cpp:218 #13 0x00007ffa68a06b79 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225 #14 0x00007ffa693f337c in QApplication::exec () at kernel/qapplication.cpp:3828
Created attachment 86549 [details] New crash information added by DrKonqi kontact (4.13) on KDE Platform 4.13.0 using Qt 4.8.6 - What I was doing when the application crashed: It crashed again after typing something into the search field. -- Backtrace (Reduced): #6 0x00007f4aa1c0bf79 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #7 0x00007f4aa1c0f388 in __GI_abort () at abort.c:89 [...] #12 0x00007f4aa241b596 in QEventLoop::exec (this=this@entry=0x7fff1d6a3db0, flags=...) at kernel/qeventloop.cpp:218 #13 0x00007f4aa2420b79 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225 #14 0x00007f4aa2e0d37c in QApplication::exec () at kernel/qapplication.cpp:3828
Created attachment 86552 [details] New crash information added by DrKonqi kontact (4.13) on KDE Platform 4.13.0 using Qt 4.8.6 - What I was doing when the application crashed: Typed in some text into the search field -> crash. -- Backtrace (Reduced): #6 0x00007fa043198f79 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #7 0x00007fa04319c388 in __GI_abort () at abort.c:89 [...] #12 0x00007fa0439a8596 in QEventLoop::exec (this=this@entry=0x7fff5ca37070, flags=...) at kernel/qeventloop.cpp:218 #13 0x00007fa0439adb79 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225 #14 0x00007fa04439a37c in QApplication::exec () at kernel/qapplication.cpp:3828
Created attachment 86553 [details] New crash information added by DrKonqi kontact (4.13) on KDE Platform 4.13.0 using Qt 4.8.6 - What I was doing when the application crashed: Typed text into search field. The IMAP account was different from the account causing the problem before. However, the same behaviour occurs: crash. -- Backtrace (Reduced): #6 0x00007ff8d7f16f79 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #7 0x00007ff8d7f1a388 in __GI_abort () at abort.c:89 [...] #12 0x00007ff8d8726596 in QEventLoop::exec (this=this@entry=0x7fff6f998b80, flags=...) at kernel/qeventloop.cpp:218 #13 0x00007ff8d872bb79 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225 #14 0x00007ff8d911837c in QApplication::exec () at kernel/qapplication.cpp:3828
Created attachment 86622 [details] New crash information added by DrKonqi kontact (4.13) on KDE Platform 4.13.0 using Qt 4.8.6 - What I was doing when the application crashed: It crashed again on search. Same as before. -- Backtrace (Reduced): #6 0x00007f2366f67f79 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #7 0x00007f2366f6b388 in __GI_abort () at abort.c:89 [...] #12 0x00007f2367777596 in QEventLoop::exec (this=this@entry=0x7fffcb2177a0, flags=...) at kernel/qeventloop.cpp:218 #13 0x00007f236777cb79 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225 #14 0x00007f236816937c in QApplication::exec () at kernel/qapplication.cpp:3828
Kontact/Kmail reproduceably crashes at all times anything is entered into the search field. Search within mails is currently completely unusable.
This neither works from the "Find Messages" dialogue window, although in this latter case the application does not crash, just returns no results. HINT: There could be a general problem with the SEARCH, as event the plasma search runner is returning no results. Maybe some underlying library stack has changed...? The only "extra" error I can find is in the console output. When starting kontact (or kmail) from the command line, I then type something in the search bar and after one second from the last typed letter the app crashes and I get this log: -------------------------------------- Qt has caught an exception thrown from an event handler. Throwing exceptions from an event handler is not supported in Qt. You must reimplement QApplication::notify() and catch all exceptions there. terminate called after throwing an instance of 'std::logic_error' what(): basic_string::_S_construct null not valid *** KMail got signal 6 (Exiting) *** Dead letters dumped. -------------------------------------- (using KDE 4.13.2 on Manjaro Linux/KDE, testing)
Update: it does not happen with a fresh user (empty user directory), where everything works fine. So, now: how to find out which file in ~/.kde4 is the bad guy?!
Try next 4.13.3 I fixed some problem in baloo package. I hope that it will fix your problem.
It reproduced in KDE Plasma 5.2.2 (Kubuntu 15.04 Beta 2, x64 version); I think with some updates. Previously everything was OK on fresh system (install date - 30.03.2015), using POP3 protocol.
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present? If noone confirms this bug for a Framework-based version of kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.