Bug 214771

Summary:	dolphin randomly crashes on dbus operations
Product:	[Applications] dolphin	Reporter:	Vovochka <vovochka13>
Component:	general	Assignee:	Peter Penz <peter.penz19>
Status:	RESOLVED DUPLICATE
Severity:	crash	CC:	andresbajotierra
Priority:	NOR
Version:	16.12.2
Target Milestone:	---
Platform:	Unlisted Binaries
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Vovochka 2009-11-16 09:30:56 UTC

Application that crashed: dolphin
Version of the application: 1.3
KDE Version: 4.3.3 (KDE 4.3.3) "release 1"
Qt Version: 4.5.3
Operating System: Linux 2.6.31.5-0.1-desktop x86_64
Distribution: "openSUSE 11.2 (x86_64)"

What I was doing when the application crashed:
Just after opening dolphin it may crash after some minutes. Or may not. It's realy annoying.

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f92edddc750 (LWP 27290))]

Thread 2 (Thread 0x7f92df187910 (LWP 27768)):
#0  0x00007f92e9e722cd in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007f92dde8b271 in metronom_sync_loop () from /usr/lib64/libxine.so.1
#2  0x00007f92e9e6d65d in start_thread () from /lib64/libpthread.so.0
#3  0x00007f92ea15414d in clone () from /lib64/libc.so.6
#4  0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f92edddc750 (LWP 27290)):
[KCrash Handler]
#5  _dbus_connection_lock (connection=0x772f616b68636f76) at dbus-connection.c:355
#6  0x00007f92e6ad0bfd in _dbus_pending_call_get_connection_and_lock (pending=0x7f92c4008840) at dbus-pending-call.c:307
#7  0x00007f92e6ac2d3e in reply_handler_timeout (data=0x772f616b68636f76) at dbus-connection.c:3158
#8  0x00007f92eb6cba37 in ?? () from /usr/lib64/libQtDBus.so.4
#9  0x00007f92ea83ef63 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#10 0x00007f92eacc02ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#11 0x00007f92eacc757e in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#12 0x00007f92ebfa4f26 in KApplication::notify (this=0x7fff227b9d50, receiver=0x6a32d0, event=0x7fff227b9950) at /usr/src/debug/kdelibs-4.3.3/kdeui/kernel/kapplication.cpp:302
#13 0x00007f92ea82fddc in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#14 0x00007f92ea85b71d in ?? () from /usr/lib64/libQtCore.so.4
#15 0x00007f92ea858678 in ?? () from /usr/lib64/libQtCore.so.4
#16 0x00007f92e6379dde in g_main_dispatch (context=<value optimized out>) at gmain.c:1960
#17 IA__g_main_context_dispatch (context=<value optimized out>) at gmain.c:2513
#18 0x00007f92e637d7a8 in g_main_context_iterate (context=0x6b1120, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2591
#19 0x00007f92e637d8d0 in IA__g_main_context_iteration (context=0x6b1120, may_block=1) at gmain.c:2654
#20 0x00007f92ea8583a3 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#21 0x00007f92ead5331e in ?? () from /usr/lib64/libQtGui.so.4
#22 0x00007f92ea82e712 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#23 0x00007f92ea82eae4 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#24 0x00007f92ea830c99 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#25 0x0000000000439575 in _start ()

This bug may be a duplicate of or related to bug 208921

Reported using DrKonqi

Comment 1 Dario Andres 2009-11-16 13:31:46 UTC

This crash is likely to be related to the bugs reported at bug 208921.
- Do you have Nepomuk(Desktop Search/indexing technology) enabled? (search for it in SystemSettings/Advanced/Desktop Search)

Thanks

Comment 2 Vovochka 2009-11-17 00:25:25 UTC

Yes. Nepomuk was enabled. Now i disable it. Will see what will be.
But in any case, it's not a cool solution. :(
P.S. this bug still exists since 4.3.0

Comment 3 Dario Andres 2009-11-17 22:15:32 UTC

Disabling Nepomuk is not a "solution". It is just a way to test if the issue is related... Thanks

Comment 4 Dario Andres 2009-11-21 16:29:45 UTC

Waiting for feedback after the tests.

Comment 5 Vovochka 2009-11-24 04:59:45 UTC

Looks like everything is ok. But this bug is quite rare. So i'm keep waiting :)

Comment 6 Dario Andres 2009-12-09 23:24:38 UTC

Thanks

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