Bug 212548 - Dolphin segfault after spawning terminal on a samba share
Summary: Dolphin segfault after spawning terminal on a samba share
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-10-31 20:42 UTC by Stirling Westrup
Modified: 2009-11-18 02:25 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 Stirling Westrup 2009-10-31 20:42:36 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 unstable (sid)

What I was doing when the application crashed:
I was using dolphin to browse a samba share on a file server, while in split screen mode. I spawned a terminal (via drop-down menu) on the samba share, which succeeded but moments later Dolphin crashed.

Alas, there doesn't seem to be a debian package of debug info for libdbus, so this crash report is as complete as I could make it.

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#5  0x00007fab3471c244 in ?? () from /lib/libdbus-1.so.3
#6  0x00007fab3472dbcd in ?? () from /lib/libdbus-1.so.3
#7  0x00007fab347208bf in ?? () from /lib/libdbus-1.so.3
#8  0x00007fab41308884 in q_dbus_timeout_handle (this=0x23970e0, e=<value optimized out>) at ./qdbus_symbols_p.h:172
#9  QDBusConnectionPrivate::timerEvent (this=0x23970e0, e=<value optimized out>) at qdbusintegrator.cpp:1023
#10 0x00007fab403f8353 in QObject::event (this=0x23970e0, e=0x0) at kernel/qobject.cpp:1074
#11 0x00007fab408b701d in QApplicationPrivate::notify_helper (this=0x23ab580, receiver=0x23970e0, e=0x7fff65e82020) at kernel/qapplication.cpp:4065
#12 0x00007fab408bf07a in QApplication::notify (this=0x7fff65e82360, receiver=0x23970e0, e=0x7fff65e82020) at kernel/qapplication.cpp:4030
#13 0x00007fab41c0a0db in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#14 0x00007fab403e8c9c in QCoreApplication::notifyInternal (this=0x7fff65e82360, receiver=0x23970e0, event=0x7fff65e82020) at kernel/qcoreapplication.cpp:610
#15 0x00007fab404152c6 in QCoreApplication::sendEvent (this=0x23a44d0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#16 QTimerInfoList::activateTimers (this=0x23a44d0) at kernel/qeventdispatcher_unix.cpp:580
#17 0x00007fab40411658 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#18 idleTimerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:231
#19 0x00007fab3c33d12a in g_main_dispatch (context=0x23ab940) at /tmp/buildd/glib2.0-2.22.2/glib/gmain.c:1960
#20 IA__g_main_context_dispatch (context=0x23ab940) at /tmp/buildd/glib2.0-2.22.2/glib/gmain.c:2513
#21 0x00007fab3c340988 in g_main_context_iterate (context=0x23ab940, block=1, dispatch=1, self=<value optimized out>) at /tmp/buildd/glib2.0-2.22.2/glib/gmain.c:2591
#22 0x00007fab3c340b3c in IA__g_main_context_iteration (context=0x23ab940, may_block=1) at /tmp/buildd/glib2.0-2.22.2/glib/gmain.c:2654
#23 0x00007fab4041139c in QEventDispatcherGlib::processEvents (this=0x237c790, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:407
#24 0x00007fab4094df1f in QGuiEventDispatcherGlib::processEvents (this=0x0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#25 0x00007fab403e7562 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#26 0x00007fab403e7934 in QEventLoop::exec (this=0x7fff65e822d0, flags=...) at kernel/qeventloop.cpp:201
#27 0x00007fab403e9ba4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#28 0x000000000043953d in _start ()

Reported using DrKonqi
Comment 1 Dario Andres 2009-11-01 01:21:28 UTC
This is likely to be bug 208921.
- Does Dolphin crash again if you repeat the situation you described ?
Thanks
Comment 2 Stirling Westrup 2009-11-01 09:50:22 UTC
I have tried several times, and have not been able to duplicate this bug. As well, I suspect that my initial bug report may have been in error, and I was not trying to spawn a terminal on the samba share, but on the local side of the operation. I was confused because I ended up taking a large amount of time to install debug packages to augment the backtrace after the crash, during which the details of what, exactly, I was doing became blurred.
Comment 3 Dario Andres 2009-11-18 02:25:37 UTC
Thanks

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