Bug 246291 - Dolphin crashed after splitting the view and moving a file
Summary: Dolphin crashed after splitting the view and moving a file
Status: RESOLVED DUPLICATE of bug 226725
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-07-30 18:00 UTC by Bernd Schmidt
Modified: 2010-08-02 13:04 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 Bernd Schmidt 2010-07-30 18:00:14 UTC
Application: dolphin (1.5)
KDE Platform Version: 4.4.95 (KDE 4.4.95 (KDE 4.5 >= 20100723))
Qt Version: 4.6.3
Operating System: Linux 2.6.34-12-desktop x86_64
Distribution: "openSUSE 11.3 (x86_64)"

-- Information about the crash:
I have split the view and moved one file from the left to the right. 
I have done it very often and sometimes dolphin crashed. In the last time it crashed many times.

The crash can be reproduced some of the time.

-- Backtrace:
Application: Dolphin (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#6  _dbus_connection_lock (connection=0x5f006e006f006e) at dbus-connection.c:355
#7  0x00007f216d05bb1d in _dbus_pending_call_get_connection_and_lock (pending=0xb1d410) at dbus-pending-call.c:307
#8  0x00007f216d04dfce in reply_handler_timeout (data=0xb1d410) at dbus-connection.c:3163
#9  0x00007f2170306cef in q_dbus_timeout_handle (this=0x687380, e=0x7fff475798e0) at qdbus_symbols_p.h:172
#10 QDBusConnectionPrivate::timerEvent (this=0x687380, e=0x7fff475798e0) at qdbusintegrator.cpp:1035
#11 0x00007f2172ed522e in QObject::event (this=0x687380, e=0x7fff475798e0) at kernel/qobject.cpp:1212
#12 0x00007f21720984d4 in QApplicationPrivate::notify_helper (this=0x68fe60, receiver=0x687380, e=0x7fff475798e0) at kernel/qapplication.cpp:4302
#13 0x00007f21720a0aca in QApplication::notify (this=<value optimized out>, receiver=0x687380, e=0x7fff475798e0) at kernel/qapplication.cpp:4185
#14 0x00007f2173b29096 in KApplication::notify (this=0x7fff47579d30, receiver=0x687380, event=0x7fff475798e0) at /usr/src/debug/kdelibs-4.4.95/kdeui/kernel/kapplication.cpp:309
#15 0x00007f2172ec3e4c in QCoreApplication::notifyInternal (this=0x7fff47579d30, receiver=0x687380, event=0x7fff475798e0) at kernel/qcoreapplication.cpp:726
#16 0x00007f2172eef0c9 in sendEvent (this=0x693a10) at kernel/qcoreapplication.h:215
#17 QTimerInfoList::activateTimers (this=0x693a10) at kernel/qeventdispatcher_unix.cpp:618
#18 0x00007f2172eebff8 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#19 idleTimerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:231
#20 0x00007f216ea4ca93 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#21 0x00007f216ea4d270 in ?? () from /usr/lib64/libglib-2.0.so.0
#22 0x00007f216ea4d510 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#23 0x00007f2172eec67f in QEventDispatcherGlib::processEvents (this=0x68f450, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#24 0x00007f217213914e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#25 0x00007f2172ec3292 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#26 0x00007f2172ec3495 in QEventLoop::exec (this=0x7fff47579c70, flags=...) at kernel/qeventloop.cpp:201
#27 0x00007f2172ec788b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1003
#28 0x00007f216513d085 in kdemain (argc=5, argv=0x66b1f0) at /usr/src/debug/kdebase-4.4.95/apps/dolphin/src/main.cpp:98
#29 0x00000000004074a9 in _start ()

Possible duplicates by query: bug 246208, bug 246017, bug 245976, bug 245682, bug 245205.

Reported using DrKonqi
Comment 1 Frank Reininghaus 2010-08-02 13:04:20 UTC
Thanks for the bug report! This crash has been reported already. It's a bug in
the D-Bus library.

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