Application: kmail (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: - What I was doing when the application crashed: Entered a character in the search box above the message list. I'm using POP3 only (not IMAP) and have several folders. The crash occurs whether or not the current folder is empty. After starting kmail from konsole, these messages are displayed when the crash occurs: 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 'Xapian::DatabaseOpeningError' *** KMail got signal 6 (Exiting) *** Dead letters dumped. The crash can be reproduced every time. -- Backtrace: Application: KMail (kmail), signal: Aborted Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1". [Current thread is 1 (Thread 0x7f0073dd7800 (LWP 6764))] Thread 5 (Thread 0x7f004cedc700 (LWP 6767)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007f00656d01cd in WTF::TCMalloc_PageHeap::scavengerThread() () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x00007f00656d0209 in WTF::TCMalloc_PageHeap::runScavengerThread(void*) () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x00007f006e9fdf6e in start_thread (arg=0x7f004cedc700) at pthread_create.c:311 #4 0x00007f00711399cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 4 (Thread 0x7f000bd4a700 (LWP 6768)): #0 pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:185 #1 0x00007f0065410bbd in JSC::BlockAllocator::blockFreeingThreadMain() () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #2 0x00007f00656ffa76 in WTF::wtfThreadEntryPoint(void*) () from /usr/lib/x86_64-linux-gnu/libQtWebKit.so.4 #3 0x00007f006e9fdf6e in start_thread (arg=0x7f000bd4a700) at pthread_create.c:311 #4 0x00007f00711399cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 3 (Thread 0x7f000aeaa700 (LWP 6769)): #0 0x00007f00691ee0e0 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x00007f00691ee399 in g_mutex_lock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f00691ae798 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f0071acbaf6 in QEventDispatcherGlib::processEvents (this=0x7efffc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #4 0x00007f0071a9d30f in QEventLoop::processEvents (this=this@entry=0x7f000aea9d70, flags=...) at kernel/qeventloop.cpp:149 #5 0x00007f0071a9d605 in QEventLoop::exec (this=this@entry=0x7f000aea9d70, flags=...) at kernel/qeventloop.cpp:204 #6 0x00007f0071999c4f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:537 #7 0x00007f007199c31f in QThreadPrivate::start (arg=0x15b8170) at thread/qthread_unix.cpp:349 #8 0x00007f006e9fdf6e in start_thread (arg=0x7f000aeaa700) at pthread_create.c:311 #9 0x00007f00711399cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 2 (Thread 0x7f00094fc700 (LWP 6775)): #0 0x00007f00691ee0f9 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #1 0x00007f00691ee3c9 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #2 0x00007f00691add40 in g_main_context_prepare () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #3 0x00007f00691ae5c3 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #4 0x00007f00691ae7ac in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0 #5 0x00007f0071acbaf6 in QEventDispatcherGlib::processEvents (this=0x7f00000008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #6 0x00007f0071a9d30f in QEventLoop::processEvents (this=this@entry=0x7f00094fbd30, flags=...) at kernel/qeventloop.cpp:149 #7 0x00007f0071a9d605 in QEventLoop::exec (this=this@entry=0x7f00094fbd30, flags=...) at kernel/qeventloop.cpp:204 #8 0x00007f0071999c4f in QThread::exec (this=this@entry=0x1b702d0) at thread/qthread.cpp:537 #9 0x00007f0071a7ea33 in QInotifyFileSystemWatcherEngine::run (this=0x1b702d0) at io/qfilesystemwatcher_inotify.cpp:265 #10 0x00007f007199c31f in QThreadPrivate::start (arg=0x1b702d0) at thread/qthread_unix.cpp:349 #11 0x00007f006e9fdf6e in start_thread (arg=0x7f00094fc700) at pthread_create.c:311 #12 0x00007f00711399cd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:113 Thread 1 (Thread 0x7f0073dd7800 (LWP 6764)): [KCrash Handler] #6 0x00007f0071075f77 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #7 0x00007f00710795e8 in __GI_abort () at abort.c:90 #8 0x00007f007167d6e5 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #9 0x00007f007167b856 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #10 0x00007f007167b883 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #11 0x00007f007167baf6 in __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6 #12 0x00007f0071a9d7f6 in QEventLoop::exec (this=this@entry=0x7fffd35fdf70, flags=...) at kernel/qeventloop.cpp:218 #13 0x00007f0071aa2deb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225 #14 0x00007f0071fce3cc in QApplication::exec () at kernel/qapplication.cpp:3828 #15 0x0000000000402d18 in main (argc=<optimized out>, argv=<optimized out>) at ../../kmail/main.cpp:146 Possible duplicates by query: bug 333253, bug 332942, bug 332891, bug 332890, bug 332769. Reported using DrKonqi
Created attachment 86043 [details] New crash information added by DrKonqi kmail (4.13 rc) on KDE Platform 4.12.97 using Qt 4.8.6 - What I was doing when the application crashed: Entering any character into quick search box instantly crashes kmail, whether it runs on its own or in kontact shell. Folder and account type make no difference - it happens with IMAP and POP accounts and large and empty mail folders. I watched debug screens in akonadiconsole (debugger/query debugger,job tracker) and none of them showed any activity at a moment of the crash. -- Backtrace (Reduced): #6 0x00007f85e1814f77 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56 #7 0x00007f85e18185e8 in __GI_abort () at abort.c:90 [...] #12 0x00007f85e223c7f6 in QEventLoop::exec (this=this@entry=0x7fff42085780, flags=...) at kernel/qeventloop.cpp:218 #13 0x00007f85e2241deb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225 #14 0x00007f85e276d3cc in QApplication::exec () at kernel/qapplication.cpp:3828
Update to 4.13 final. (when package will be available) it's a baloo crash. it fixed.
Installing package "baloo" resolved the problem. Hopefully there will be some notice for users logging in kde 4.13 to let them know that baloo package is replacing nepomuk More info about new search: http://community.kde.org/Baloo
(In reply to comment #3) > Installing package "baloo" resolved the problem. Are you running Kubuntu?
(In reply to comment #4) > (In reply to comment #3) > > Installing package "baloo" resolved the problem. > > Are you running Kubuntu? kubuntu 13.10 kde packages are from kubuntu-ppa/beta
Yes, same here. I had the Baloo libraries installed, but not the baloo package itself. After installing it, quick search works fine (even better than before, with the extra buttons that appear for filtering). The Find Messages dialog doesn't work, but that's the subject of another bug. Maybe it'll be OK in Trusty. I've confirmed that the baloo package is present in Trusty beta, anyway.
I'm still seeing the "same" crash with 4.13 final packages from kubuntu 14.04. However I have baloo installed and instead of "terminate called after throwing an instance of 'Xapian::DatabaseOpeningError'" on the terminal, I do see terminate called after throwing an instance of 'std::logic_error' what(): basic_string::_S_construct null not valid Any ideas what that could be?
(In reply to comment #7) I expect it would be best if you opened a new bug report for this.
(In reply to comment #8) > (In reply to comment #7) > > I expect it would be best if you opened a new bug report for this. Laurent, you ok with that? :)
Yes please open a new one :)