Bug 218636 - dolphin crash after entering search result folder
Summary: dolphin crash after entering search result folder
Status: RESOLVED DUPLICATE of bug 208921
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Compiled Sources Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-12-14 13:22 UTC by SlashDevDsp
Modified: 2009-12-15 22:22 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 SlashDevDsp 2009-12-14 13:22:04 UTC
Version:            (using Devel)
Compiler:          g++ 4.3 
OS:                Linux
Installed from:    Compiled sources

dolphin crashed after entering search term 'tif' and clicking the resulting folder. At the time the 'Nepomuk Strigi service stub' shows Strigi is still indexing the home folder when the crash happened. bt below:

Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#5  0x00007fdecaca4f54 in ?? () from /lib/libdbus-1.so.3
#6  0x00007fdecacb669d in ?? () from /lib/libdbus-1.so.3
#7  0x00007fdecaca95ef in ?? () from /lib/libdbus-1.so.3
#8  0x00007fded27b0894 in QDBusConnectionPrivate::timerEvent (this=0xa1adb0, e=<value optimized out>) at /home/kde-devel/kdesvn/qt-copy/src/dbus/qdbus_symbols_p.h:172
#9  0x00007fded24aee53 in QObject::event (this=0xa1adb0, e=0x0) at /home/kde-devel/kdesvn/qt-copy/src/corelib/kernel/qobject.cpp:1223
#10 0x00007fded11e548d in QApplicationPrivate::notify_helper (this=0xa27430, receiver=0xa1adb0, e=0x7fff555ec450) at /home/kde-devel/kdesvn/qt-copy/src/gui/kernel/qapplication.cpp:4253
#11 0x00007fded11ecae3 in QApplication::notify (this=0x7fff555ec790, receiver=0xa1adb0, e=0x7fff555ec450) at /home/kde-devel/kdesvn/qt-copy/src/gui/kernel/qapplication.cpp:3663
#12 0x00007fded332bd8b in KApplication::notify (this=0x7fff555ec790, receiver=0xa1adb0, event=0x7fff555ec450) at /home/kde-devel/kdesvn/kdelibs/kdeui/kernel/kapplication.cpp:302
#13 0x00007fded249ff9b in QCoreApplication::notifyInternal (this=0x7fff555ec790, receiver=0xa1adb0, event=0x7fff555ec450) at /home/kde-devel/kdesvn/qt-copy/src/corelib/kernel/qcoreapplication.cpp:704
#14 0x00007fded24c9754 in QTimerInfoList::activateTimers (this=0xa2d7d0) at ../../include/QtCore/../../../../qt-copy/src/corelib/kernel/qcoreapplication.h:215
#15 0x00007fded24c61b8 in idleTimerSourceDispatch (source=<value optimized out>) at /home/kde-devel/kdesvn/qt-copy/src/corelib/kernel/qeventdispatcher_glib.cpp:184
#16 0x00007fdecc61220a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#17 0x00007fdecc6158e0 in ?? () from /usr/lib/libglib-2.0.so.0
#18 0x00007fdecc615a7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#19 0x00007fded24c5e8c in QEventDispatcherGlib::processEvents (this=0xa00240, flags=<value optimized out>) at /home/kde-devel/kdesvn/qt-copy/src/corelib/kernel/qeventdispatcher_glib.cpp:407
#20 0x00007fded12840ef in QGuiEventDispatcherGlib::processEvents (this=0x65006700610072, flags=<value optimized out>) at /home/kde-devel/kdesvn/qt-copy/src/gui/kernel/qguieventdispatcher_glib.cpp:202
#21 0x00007fded249ea82 in QEventLoop::processEvents (this=<value optimized out>, flags={i = 1432274624}) at /home/kde-devel/kdesvn/qt-copy/src/corelib/kernel/qeventloop.cpp:149
#22 0x00007fded249ec1c in QEventLoop::exec (this=0x7fff555ec700, flags={i = 1432274704}) at /home/kde-devel/kdesvn/qt-copy/src/corelib/kernel/qeventloop.cpp:197
#23 0x00007fded24a0f2c in QCoreApplication::exec () at /home/kde-devel/kdesvn/qt-copy/src/corelib/kernel/qcoreapplication.cpp:981
#24 0x000000000043a0b5 in main (argc=5, argv=0x7fff555ecc78) at /home/kde-devel/kdesvn/kdebase/apps/dolphin/src/main.cpp:94

versions:
latest git kde-qt branch: 4.6.1
svn root: 1062220
kdelibs: 1062207
kdebase: 1062214
Comment 1 Frank Reininghaus 2009-12-15 22:22:41 UTC
Thanks for the bug report! This crash has been reported quite a few times already. Note that a patch has recently been attached to the other report - if you can test it, that would help a lot!

*** This bug has been marked as a duplicate of bug 208921 ***