Bug 212449 - Dolphin crashed after searching for files/folders using control+f
Summary: Dolphin crashed after searching for files/folders using control+f
Status: RESOLVED DUPLICATE of bug 208921
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-30 21:26 UTC by nik8pol
Modified: 2009-12-17 17:31 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 nik8pol 2009-10-30 21:26:28 UTC
Application that crashed: dolphin
Version of the application: 1.3
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-14-generic x86_64
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
Strigi was indexing files since I started the session. I opened dolphin and hit control+f in order to search for a file. The after pressing the search button dolphin crashed (and closed) and the search windows remained opened
System:kubuntu 9.10 

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f3c36049280 in ?? () from /lib/libdbus-1.so.3
#6  0x00007f3c36049299 in ?? () from /lib/libdbus-1.so.3
#7  0x00007f3c3603178d in ?? () from /lib/libdbus-1.so.3
#8  0x00007f3c36040455 in ?? () from /lib/libdbus-1.so.3
#9  0x00007f3c36031ddc in ?? () from /lib/libdbus-1.so.3
#10 0x00007f3c3d50e733 in q_dbus_timeout_handle (this=0x10578a0, e=<value optimized out>) at ./qdbus_symbols_p.h:172
#11 QDBusConnectionPrivate::timerEvent (this=0x10578a0, e=<value optimized out>) at qdbusintegrator.cpp:1023
#12 0x00007f3c3c65cd83 in QObject::event (this=0x10578a0, e=0x100000006) at kernel/qobject.cpp:1075
#13 0x00007f3c3cae0efc in QApplicationPrivate::notify_helper (this=0x106feb0, receiver=0x10578a0, e=0x7fff17585bf0) at kernel/qapplication.cpp:4056
#14 0x00007f3c3cae81ce in QApplication::notify (this=0x7fff17585f40, receiver=0x10578a0, e=0x7fff17585bf0) at kernel/qapplication.cpp:4021
#15 0x00007f3c3de15ab6 in KApplication::notify (this=0x7fff17585f40, receiver=0x10578a0, event=0x7fff17585bf0) at ../../kdeui/kernel/kapplication.cpp:302
#16 0x00007f3c3c64dc2c in QCoreApplication::notifyInternal (this=0x7fff17585f40, receiver=0x10578a0, event=0x7fff17585bf0) at kernel/qcoreapplication.cpp:610
#17 0x00007f3c3c678862 in QCoreApplication::sendEvent (this=0x106f920) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#18 QTimerInfoList::activateTimers (this=0x106f920) at kernel/qeventdispatcher_unix.cpp:572
#19 0x00007f3c3c67625d in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:165
#20 0x00007f3c3816bbbe in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#21 0x00007f3c3816f588 in ?? () from /lib/libglib-2.0.so.0
#22 0x00007f3c3816f6b0 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#23 0x00007f3c3c6761a6 in QEventDispatcherGlib::processEvents (this=0x103cd20, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#24 0x00007f3c3cb754be in QGuiEventDispatcherGlib::processEvents (this=0x105b9d8, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#25 0x00007f3c3c64c532 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#26 0x00007f3c3c64c904 in QEventLoop::exec (this=0x7fff17585e90, flags=) at kernel/qeventloop.cpp:201
#27 0x00007f3c3c64eab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#28 0x0000000000439555 in _start ()

Reported using DrKonqi
Comment 1 Dario Andres 2009-10-31 02:18:03 UTC
This could be related to bug 208921. 
- Can you try to reproduce the crash situation ?
Thanks
Comment 2 Dario Andres 2009-12-17 17:31:12 UTC

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