Bug 216969 - Dolphin crashed after opening two tabs (one with a fish location, another with local filesystem browsing)
Summary: Dolphin crashed after opening two tabs (one with a fish location, another wit...
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-01 18:49 UTC by glaubermd
Modified: 2009-12-17 17:25 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description glaubermd 2009-12-01 18:49:40 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.30-2-amd64 x86_64
Distribution: Debian GNU/Linux testing (squeeze)

What I was doing when the application crashed:
Dolphin crashed after opening two tabs (one with a fish location, another with local filesystem browsing).
I was trying to copy a file to a remote server, using fish protocol (ssh).
I browsed left panel to Network -> Remote_Server_Something, then opened another tab, clicked Desktop folder then Dolphin crashed.

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f425752bcb9 in ?? () from /lib/libdbus-1.so.3
#6  0x00007f425750d24d in ?? () from /lib/libdbus-1.so.3
#7  0x00007f425751ebcd in ?? () from /lib/libdbus-1.so.3
#8  0x00007f42575118bf in ?? () from /lib/libdbus-1.so.3
#9  0x00007f425e968884 in q_dbus_timeout_handle (this=0x1cd30e0, e=<value optimized out>) at ./qdbus_symbols_p.h:172
#10 QDBusConnectionPrivate::timerEvent (this=0x1cd30e0, e=<value optimized out>) at qdbusintegrator.cpp:1023
#11 0x00007f425da58353 in QObject::event (this=0x1cd30e0, e=0x0) at kernel/qobject.cpp:1074
#12 0x00007f425df1701d in QApplicationPrivate::notify_helper (this=0x1ce7640, receiver=0x1cd30e0, e=0x7fffaf5128f0) at kernel/qapplication.cpp:4065
#13 0x00007f425df1f07a in QApplication::notify (this=0x7fffaf512c30, receiver=0x1cd30e0, e=0x7fffaf5128f0) at kernel/qapplication.cpp:4030
#14 0x00007f425f26a0db in KApplication::notify (this=0x7fffaf512c30, receiver=0x1cd30e0, event=0x7fffaf5128f0) at ../../kdeui/kernel/kapplication.cpp:302
#15 0x00007f425da48c9c in QCoreApplication::notifyInternal (this=0x7fffaf512c30, receiver=0x1cd30e0, event=0x7fffaf5128f0) at kernel/qcoreapplication.cpp:610
#16 0x00007f425da752c6 in QCoreApplication::sendEvent (this=0x1ce0e30) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#17 QTimerInfoList::activateTimers (this=0x1ce0e30) at kernel/qeventdispatcher_unix.cpp:580
#18 0x00007f425da71658 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 0x00007f425999b12a in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#21 0x00007f425999e988 in ?? () from /lib/libglib-2.0.so.0
#22 0x00007f425999eb3c in g_main_context_iteration () from /lib/libglib-2.0.so.0
#23 0x00007f425da7139c in QEventDispatcherGlib::processEvents (this=0x1cb8790, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:407
#24 0x00007f425dfadf1f in QGuiEventDispatcherGlib::processEvents (this=0x1, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#25 0x00007f425da47562 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#26 0x00007f425da47934 in QEventLoop::exec (this=0x7fffaf512ba0, flags=...) at kernel/qeventloop.cpp:201
#27 0x00007f425da49ba4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#28 0x000000000043953d in _start ()

Reported using DrKonqi
Comment 1 Dario Andres 2009-12-04 00:45:27 UTC

*** This bug has been marked as a duplicate of bug 215328 ***
Comment 2 Dario Andres 2009-12-04 00:45:51 UTC
Wrong bug number.. reopening
Comment 3 Dario Andres 2009-12-17 17:25:41 UTC
Fixed recently: bug 208921. Thanks

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