Bug 217078 - dolphin crashed in a sudden
Summary: dolphin crashed in a sudden
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-12-02 16:14 UTC by julee
Modified: 2009-12-02 22:00 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 julee 2009-12-02 16:14:45 UTC
Application that crashed: dolphin
Version of the application: 1.3
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.3
Operating System: Linux 2.6.31.6-desktop586-1mnb i686
Distribution: "Mandriva Linux 2010.0"

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

Thread 2 (Thread 0xb19b1b70 (LWP 11524)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb5bd8d12 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/i686/libpthread.so.0
#2  0xb5ccd744 in __pthread_cond_timedwait (cond=0x9676f08, mutex=0x9676ef0, abstime=0xb19b1360) at forward.c:152
#3  0xacb30855 in ?? () from /usr/lib/libxine.so.1
#4  0xb5bd4885 in start_thread () from /lib/i686/libpthread.so.0
#5  0xb5cbf57e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130

Thread 1 (Thread 0xb4ff96d0 (LWP 31122)):
[KCrash Handler]
#6  _dbus_connection_lock (connection=0x650000) at dbus-connection.c:355
#7  0xb5069005 in _dbus_pending_call_get_connection_and_lock (pending=0x95fe7c8) at dbus-pending-call.c:307
#8  0xb50598f6 in reply_handler_timeout (data=0x95fe7c8) at dbus-connection.c:3156
#9  0xb506def0 in dbus_timeout_handle (timeout=0x960ef68) at dbus-timeout.c:473
#10 0xb6a4bec0 in QDBusConnectionPrivate::timerEvent (this=0x8a4b020, e=0xbfcd87d0) at ./qdbus_symbols_p.h:172
#11 0xb5fa8dfb in QObject::event (this=0x8a4b020, e=0xbfcd87d0) at kernel/qobject.cpp:1074
#12 0xb619d68c in QApplicationPrivate::notify_helper (this=0x8a5e6c8, receiver=0x8a4b020, e=0xbfcd87d0) at kernel/qapplication.cpp:4065
#13 0xb61a50ce in QApplication::notify (this=0xbfcd8afc, receiver=0x8a4b020, e=0xbfcd87d0) at kernel/qapplication.cpp:3605
#14 0xb6eeba21 in KApplication::notify (this=0xbfcd8afc, receiver=0x8a4b020, event=0xbfcd87d0) at /usr/src/debug/kdelibs-4.3.2/kdeui/kernel/kapplication.cpp:302
#15 0xb5f98c0e in QCoreApplication::notifyInternal (this=0xbfcd8afc, receiver=0x8a4b020, event=0xbfcd87d0) at kernel/qcoreapplication.cpp:610
#16 0xb5fc72c1 in QTimerInfoList::activateTimers (this=0x8a55774) at ../../src/corelib/kernel/qcoreapplication.h:213
#17 0xb5fc4c05 in idleTimerSourceDispatch (source=0x8a557b0) at kernel/qeventdispatcher_glib.cpp:184
#18 0xb54e4b92 in IA__g_main_context_dispatch (context=0x8a55278) at gmain.c:1960
#19 0xb54e8468 in g_main_context_iterate (context=0x8a55278, block=<value optimized out>, dispatch=1, self=0x8a52bf0) at gmain.c:2591
#20 0xb54e858e in IA__g_main_context_iteration (context=0x8a55278, may_block=1) at gmain.c:2654
#21 0xb5fc48f1 in QEventDispatcherGlib::processEvents (this=0x8a5cad8, flags={i = 36}) at kernel/qeventdispatcher_glib.cpp:406
#22 0xb623f4ba in QGuiEventDispatcherGlib::processEvents (this=0x8a5cad8, flags={i = 36}) at kernel/qguieventdispatcher_glib.cpp:202
#23 0xb5f9726d in QEventLoop::processEvents (this=0xbfcd8a54, flags=) at kernel/qeventloop.cpp:149
#24 0xb5f976b9 in QEventLoop::exec (this=0xbfcd8a54, flags={i = 0}) at kernel/qeventloop.cpp:201
#25 0xb5f99b50 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#26 0xb619d504 in QApplication::exec () at kernel/qapplication.cpp:3525
#27 0x08078c25 in main (argc=5, argv=0xbfcd8cd4) at /usr/src/debug/kdebase-4.3.2/apps/dolphin/src/main.cpp:94

Reported using DrKonqi
Comment 1 Frank Reininghaus 2009-12-02 22:00:07 UTC
Thanks for the bug report! A crash of this kind (crash in DBus code, apparently
related to Nepomuk) has been reported quite a few times already.

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