Bug 333465

Summary: Dolphin crashes during open home folder
Product: [Unmaintained] Baloo Reporter: Anatoly <anatrof>
Component: GeneralAssignee: Vishesh Handa <me>
Status: RESOLVED FIXED    
Severity: crash CC: frank78ac, kde
Priority: NOR Keywords: drkonqi
Version First Reported In: unspecified   
Target Milestone: ---   
Platform: Ubuntu   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: New crash information added by DrKonqi

Description Anatoly 2014-04-15 13:32:06 UTC 
Application: dolphin (4.13.0)
KDE Platform Version: 4.13.0
Qt Version: 4.8.6
Operating System: Linux 3.13.0-24-generic x86_64
Distribution: Ubuntu 14.04 LTS

-- Information about the crash:
- What I was doing when the application crashed:

just clicking on start icon from main menu or running by alt+f2 and typing command "dolphin"

The crash can be reproduced every time.

-- Backtrace:
Application: Dolphin (dolphin), signal: Aborted
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f09e779c7c0 (LWP 32608))]

Thread 4 (Thread 0x7f09c9669700 (LWP 32609)):
#0  0x00007f09e705ffbd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f09ddfd0fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f09ddfd10ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f09e30d07be in QEventDispatcherGlib::processEvents (this=0x7f09c40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#4  0x00007f09e30a20af in QEventLoop::processEvents (this=this@entry=0x7f09c9668de0, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f09e30a23a5 in QEventLoop::exec (this=this@entry=0x7f09c9668de0, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007f09e2f9ec5f in QThread::exec (this=this@entry=0x16d6d70) at thread/qthread.cpp:537
#7  0x00007f09e3083823 in QInotifyFileSystemWatcherEngine::run (this=0x16d6d70) at io/qfilesystemwatcher_inotify.cpp:265
#8  0x00007f09e2fa132f in QThreadPrivate::start (arg=0x16d6d70) at thread/qthread_unix.cpp:349
#9  0x00007f09de4b0182 in start_thread (arg=0x7f09c9669700) at pthread_create.c:312
#10 0x00007f09e706d30d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 3 (Thread 0x7f09c8d09700 (LWP 32610)):
#0  0x00007f09de4b37ee in __pthread_mutex_unlock_usercnt (decr=1, mutex=0x7f09bc000a60) at pthread_mutex_unlock.c:57
#1  __GI___pthread_mutex_unlock (mutex=0x7f09bc000a60) at pthread_mutex_unlock.c:310
#2  0x00007f09de0129c1 in g_mutex_unlock () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f09ddfd0a59 in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f09ddfd0f7b in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f09ddfd10ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#6  0x00007f09e30d07be in QEventDispatcherGlib::processEvents (this=0x7f09bc0008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#7  0x00007f09e30a20af in QEventLoop::processEvents (this=this@entry=0x7f09c8d08e20, flags=...) at kernel/qeventloop.cpp:149
#8  0x00007f09e30a23a5 in QEventLoop::exec (this=this@entry=0x7f09c8d08e20, flags=...) at kernel/qeventloop.cpp:204
#9  0x00007f09e2f9ec5f in QThread::exec (this=<optimized out>) at thread/qthread.cpp:537
#10 0x00007f09e2fa132f in QThreadPrivate::start (arg=0x178aa00) at thread/qthread_unix.cpp:349
#11 0x00007f09de4b0182 in start_thread (arg=0x7f09c8d09700) at pthread_create.c:312
#12 0x00007f09e706d30d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 2 (Thread 0x7f09c3dad700 (LWP 32611)):
#0  0x00007f09e705ffbd in poll () at ../sysdeps/unix/syscall-template.S:81
#1  0x00007f09ddfd0fe4 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f09ddfd10ec in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f09e30d07be in QEventDispatcherGlib::processEvents (this=0x7f09b80008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:436
#4  0x00007f09e30a20af in QEventLoop::processEvents (this=this@entry=0x7f09c3dacde0, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f09e30a23a5 in QEventLoop::exec (this=this@entry=0x7f09c3dacde0, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007f09e2f9ec5f in QThread::exec (this=this@entry=0x1d39b60) at thread/qthread.cpp:537
#7  0x00007f09e3083823 in QInotifyFileSystemWatcherEngine::run (this=0x1d39b60) at io/qfilesystemwatcher_inotify.cpp:265
#8  0x00007f09e2fa132f in QThreadPrivate::start (arg=0x1d39b60) at thread/qthread_unix.cpp:349
#9  0x00007f09de4b0182 in start_thread (arg=0x7f09c3dad700) at pthread_create.c:312
#10 0x00007f09e706d30d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:111

Thread 1 (Thread 0x7f09e779c7c0 (LWP 32608)):
[KCrash Handler]
#6  0x00007f09e6fa8f79 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#7  0x00007f09e6fac388 in __GI_abort () at abort.c:89
#8  0x00007f09e2a076b5 in __gnu_cxx::__verbose_terminate_handler() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#9  0x00007f09e2a05836 in ?? () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#10 0x00007f09e2a05863 in std::terminate() () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#11 0x00007f09e2a05af6 in __cxa_rethrow () from /usr/lib/x86_64-linux-gnu/libstdc++.so.6
#12 0x00007f09e30a2596 in QEventLoop::exec (this=this@entry=0x7fffa4212c60, flags=...) at kernel/qeventloop.cpp:218
#13 0x00007f09e30a7b79 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1225
#14 0x00007f09e73884f7 in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_dolphin.so
#15 0x00007f09e6f93ec5 in __libc_start_main (main=0x4006d0, argc=5, argv=0x7fffa4212ec8, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7fffa4212eb8) at libc-start.c:287
#16 0x00000000004006fe in _start ()

Possible duplicates by query: bug 333332, bug 333327, bug 333253, bug 333185, bug 332942.

Reported using DrKonqi
Comment 1 Frank Reininghaus 2014-04-15 13:36:11 UTC 
Thanks for the bug report. This crash is caused by an unhandled exception. Please follow

http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_when_an_uncaught_exception_is_causing_a_crash

to provide more detailed information. Thanks for your help.
Comment 2 Kai Uwe Broulik 2014-04-20 15:52:35 UTC 
Created attachment 86184 [details]
New crash information added by DrKonqi

dolphin (4.13.0) on KDE Platform 4.13.0 using Qt 4.8.6

- What I was doing when the application crashed:
I just started Dolphin after upgrading to SC 4.13.0 and it crashes every time as soon as I enter my home directory

-- Backtrace (Reduced):
#5  0x0000003e00836f79 in __GI_raise (sig=sig@entry=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:56
#6  0x0000003e0083a388 in __GI_abort () at abort.c:89
[...]
#11 0x00007fa1592b4596 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#12 0x00007fa1592b9b79 in QCoreApplication::exec() () from /usr/lib/x86_64-linux-gnu/libQtCore.so.4
#13 0x00007fa15d2044f7 in kdemain () from /usr/lib/kde4/libkdeinit/libkdeinit4_dolphin.so
Comment 3 Kai Uwe Broulik 2014-04-20 17:41:13 UTC 
The console output shows the application crashes due to an unhandled Xapian::DatabaseCorruptError, when I deleted the ~/.local/share/baloo folder the error went away so it appears it crashes because Baloo doesn't handle a corrupt database properly.
Comment 4 Frank Reininghaus 2014-04-21 12:11:59 UTC 
Some of these crashes should be fixed already. See, e.g., bug 332403. That one is supposed to be fixed in 4.13.0 AFAIK though, so I'm not sure if your crash is fixed or not.
Comment 5 Vishesh Handa 2014-07-21 09:56:07 UTC 
This was a case of the DB getting corrupted, an exception being thrown and us crashing. We now no longer crash because of the exception, but this still is not gracefully handled.

This is being tracked over here - https://bugs.kde.org/show_bug.cgi?id=333930

Closing this bug as FIXED since the exact crash reported over here no longer occurs.