Bug 255378 - Krunner crashes randomly while searching strigi
Summary: Krunner crashes randomly while searching strigi
Status: RESOLVED DUPLICATE of bug 241594
Alias: None
Product: krunner
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: unspecified Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-27 09:51 UTC by kranthi
Modified: 2010-11-20 14:17 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 kranthi 2010-10-27 09:51:27 UTC
Application: krunner (0.1)
KDE Platform Version: 4.4.5 (KDE 4.4.5)
Qt Version: 4.6.3
Operating System: Linux 2.6.31.13-131 i686
Distribution: "Pardus 2009.2 Geronticus eremita"

-- Information about the crash:
I'm using pardus 2009 G.E. 
installed nepomuk, indexed the data, and using strigi as query engine. I have also installed akonadi. Now i'm trying to search contacts using krunner and,
1. the results come very slow,
2. Sometimes Krunner Crashes,
3. Sometimes it stalls.


The crash can be reproduced some of the time.

 -- Backtrace:
Application: Run Command Interface (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#6  _dbus_connection_lock (connection=0x753920) at dbus-connection.c:355
#7  0xb56d8b85 in _dbus_pending_call_get_connection_and_lock (pending=0x9df2eb0) at dbus-pending-call.c:309
#8  0xb56ca666 in reply_handler_timeout (data=0x9df2eb0) at dbus-connection.c:3116
#9  0xb56dde70 in dbus_timeout_handle (timeout=0x9faeda8) at dbus-timeout.c:473
#10 0xb5d1e287 in q_dbus_timeout_handle (timeout=<value optimized out>) at qdbus_symbols_p.h:172
#11 QDBusConnectionPrivate::timerEvent (timeout=<value optimized out>) at qdbusintegrator.cpp:1035
#12 0xb6d271c4 in QObject::event (this=0x9993b00, e=0xbf8a6d80) at kernel/qobject.cpp:1212
#13 0xb621fdfc in QApplicationPrivate::notify_helper (this=0x999a558, receiver=0x9993b00, e=0xbf8a6d80) at kernel/qapplication.cpp:4324
#14 0xb622788a in QApplication::notify (this=0x999a358, receiver=0x9993b00, e=0xbf8a6d80) at kernel/qapplication.cpp:3728
#15 0xb6fa3e71 in KApplication::notify (this=0x999a358, receiver=0x9993b00, event=0xbf8a6d80) at /var/pisi/kdelibs-4.4.5-79/work/kdelibs-4.4.5/kdeui/kernel/kapplication.cpp:302
#16 0xb6d15cfe in QCoreApplication::notifyInternal (this=0x999a358, receiver=0x9993b00, event=0xbf8a6d80) at kernel/qcoreapplication.cpp:726
#17 0xb6d46e6c in sendEvent (event=<value optimized out>, receiver=<value optimized out>) at kernel/qcoreapplication.h:215
#18 QTimerInfoList::activateTimers (event=<value optimized out>, receiver=<value optimized out>) at kernel/qeventdispatcher_unix.cpp:617
#19 0xb6d43595 in timerSourceDispatch (source=0x999cfc0) at kernel/qeventdispatcher_glib.cpp:184
#20 idleTimerSourceDispatch (source=0x999cfc0) at kernel/qeventdispatcher_glib.cpp:231
#21 0xb59fe53c in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#22 0x0999c694 in ?? ()
Backtrace stopped: previous frame inner to this frame (corrupt stack?)

Possible duplicates by query: bug 255359, bug 255287, bug 254999, bug 254605, bug 254010.

Reported using DrKonqi
Comment 1 Dario Andres 2010-11-20 14:17:14 UTC
[Comment from a bug triager]
This is an issue in the DBus core technology. It is already fixed in the 1.3.1 version or later. Your distribution should offer that version soon.
The reports were being tracked at bug 241594. Merging.
Thanks

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