Bug 260723

Summary: Dolphin crashes when moving files from memory stick to a harddisk
Product: [Applications] dolphin Reporter: Dominik <dominik>
Component: generalAssignee: Peter Penz <peter.penz19>
Status: RESOLVED DUPLICATE    
Severity: crash CC: andresbajotierra
Priority: NOR    
Version: 16.12.2   
Target Milestone: ---   
Platform: Compiled Sources   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description Dominik 2010-12-19 17:55:16 UTC
Application: dolphin (1.4)
KDE Platform Version: 4.4.5 (KDE 4.4.5) (Compiled from sources)
Qt Version: 4.6.3
Operating System: Linux 2.6.34-gentoo-r6-07 i686
Distribution (Platform): Gentoo Packages

-- Information about the crash:
Dolphin crashes when moving files from memory stick to a harddisk

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

Thread 2 (Thread 0xb3187b70 (LWP 5578)):
#0  0xffffe424 in __kernel_vsyscall ()
#1  0xb53be342 in pthread_cond_timedwait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/i386/i686/../i486/pthread_cond_timedwait.S:179
#2  0xb59cc6b4 in __pthread_cond_timedwait (cond=0x85d07b8, mutex=0x85d07a0, abstime=0xb3187320) at forward.c:152
#3  0xb267647b in metronom_sync_loop (this=0x85d0758) at metronom.c:870
#4  0xb53b997e in start_thread (arg=0xb3187b70) at pthread_create.c:297
#5  0xb59bf69e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:133

Thread 1 (Thread 0xb4ba0710 (LWP 5567)):
[KCrash Handler]
#6  _dbus_connection_lock (connection=0x7325c0) at dbus-connection.c:355
#7  0xb52e7e56 in _dbus_pending_call_get_connection_and_lock (pending=0x8bfea58) at dbus-pending-call.c:307
#8  0xb52d67f6 in reply_handler_timeout (data=0x8bfea58) at dbus-connection.c:3163
#9  0xb52ed2a2 in dbus_timeout_handle (timeout=0x8b4dde8) at dbus-timeout.c:473
#10 0xb6950d80 in q_dbus_timeout_handle (this=0x80f8ec8, e=0xbfead9f8) at qdbus_symbols_p.h:172
#11 QDBusConnectionPrivate::timerEvent (this=0x80f8ec8, e=0xbfead9f8) at qdbusintegrator.cpp:1035
#12 0xb682c39c in QObject::event (this=0x80f8ec8, e=0x8bfea58) at kernel/qobject.cpp:1204
#13 0xb5ca45d4 in QApplicationPrivate::notify_helper (this=0x8101718, receiver=0x80f8ec8, e=0xbfead9f8) at kernel/qapplication.cpp:4302
#14 0xb5ca47cb in QApplication::notify (this=0xbfeadd64, receiver=0x80f8ec8, e=0xbfead9f8) at kernel/qapplication.cpp:3706
#15 0xb6e31d3b in KApplication::notify (this=0xbfeadd64, receiver=0x80f8ec8, event=0xbfead9f8) at /var/tmp/portage/kde-base/kdelibs-4.4.5/work/kdelibs-4.4.5/kdeui/kernel/kapplication.cpp:302
#16 0xb6812c22 in QCoreApplication::notifyInternal (this=0xbfeadd64, receiver=0x80f8ec8, event=0xbfead9f8) at kernel/qcoreapplication.cpp:726
#17 0xb68471ae in QCoreApplication::sendEvent (this=0x810407c) at kernel/qcoreapplication.h:215
#18 QTimerInfoList::activateTimers (this=0x810407c) at kernel/qeventdispatcher_unix.cpp:603
#19 0xb68442f8 in timerSourceDispatch (source=0x81040b0) at kernel/qeventdispatcher_glib.cpp:184
#20 idleTimerSourceDispatch (source=0x81040b0) at kernel/qeventdispatcher_glib.cpp:231
#21 0xb51fb0a1 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#22 0xb51fb988 in ?? () from /usr/lib/libglib-2.0.so.0
#23 0x08103890 in ?? ()
#24 0x000000c8 in ?? ()
#25 0x087a2538 in ?? ()
#26 0x0000000d in ?? ()
#27 0x00000013 in ?? ()
#28 0x00000000 in ?? ()

This bug may be a duplicate of or related to bug 258132, bug 251769.

Possible duplicates by query: bug 259316, bug 258880, bug 258373, bug 258134, bug 258132.

Reported using DrKonqi
Comment 1 Dario Andres 2010-12-19 19:00:47 UTC
[Comment from a bug triager]
- What is your DBus version ?
Regards
Comment 2 Dominik 2010-12-19 19:37:24 UTC
I am using dbus-1.2.24, qt-dbus-4.6.3 and dbus-glib-0.86
Comment 3 Dario Andres 2010-12-19 19:38:42 UTC
This is an issue in the D-Bus library which has been reported already.
It is fixed in D-Bus 1.3.1 and later:

http://bugreports.qt.nokia.com/browse/QTBUG-7475
https://bugs.freedesktop.org/show_bug.cgi?id=17754

If you cannot update to D-Bus 1.3.1 or later, you can disable tool tips and the
Information Panel as a workaround.

Regards

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