Bug 213792

Summary: Dolphin crash while working with two sftp connections
Product: [Applications] dolphin Reporter: iferca
Component: generalAssignee: Peter Penz <peter.penz19>
Status: RESOLVED DUPLICATE    
Severity: crash CC: echidnaman
Priority: NOR    
Version: 16.12.2   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:

Description iferca 2009-11-09 02:14:28 UTC
Application that crashed: dolphin
Version of the application: 1.3
KDE Version: 4.3.3 (KDE 4.3.3)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-14-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
Having two different connections with sftp(ssh) servers dolphin crashed. I saved the password for both connections and the application was asking the password several times, just clicking OK mades the dialog disapears but sudently it crashed.
I was unable to repeat the crash, in fact the next time I was able to copy all the stuff without any issue.

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#6  0x00000000 in ?? ()
#7  0x001f495f in ~JobPrivate (this=0x9a42374, __in_chrg=<value optimized out>) at ../../kio/kio/job_p.h:35
#8  ~FileCopyJobPrivate (this=0x9a42374, __in_chrg=<value optimized out>) at ../../kio/kio/job.cpp:1656
#9  0x00655774 in ~KJob (this=0x9cc3678, __in_chrg=<value optimized out>) at ../../kdecore/jobs/kjob.cpp:69
#10 0x006545e8 in ~KCompositeJob (this=0x9cc3678, __in_chrg=<value optimized out>) at ../../kdecore/jobs/kcompositejob.cpp:44
#11 0x001e49f8 in ~Job (this=0x9cc3678, __in_chrg=<value optimized out>) at ../../kio/kio/job.cpp:91
#12 0x001e4a2d in ~FileCopyJob (this=0x9cc3678, __in_chrg=<value optimized out>) at ../../kio/kio/job.cpp:1811
#13 0x08334135 in qDeleteInEventHandler (o=0xa0e6770) at kernel/qobject.cpp:3815
#14 0x0833562b in QObject::event (this=0x9cc3678, e=0x9a42378) at kernel/qobject.cpp:1094
#15 0x01247f54 in QApplicationPrivate::notify_helper (this=0x98ad998, receiver=0x9cc3678, e=0x9fdbdb0) at kernel/qapplication.cpp:4056
#16 0x0124f67c in QApplication::notify (this=0xbfb9e42c, receiver=0x9cc3678, e=0x9fdbdb0) at kernel/qapplication.cpp:3603
#17 0x00f6714a in KApplication::notify (this=0xbfb9e42c, receiver=0x9cc3678, event=0x9fdbdb0) at ../../kdeui/kernel/kapplication.cpp:302
#18 0x083256cb in QCoreApplication::notifyInternal (this=0xbfb9e42c, receiver=0x9cc3678, event=0x9fdbdb0) at kernel/qcoreapplication.cpp:610
#19 0x083262b2 in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x9888e48) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#20 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x9888e48) at kernel/qcoreapplication.cpp:1247
#21 0x0832647d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#22 0x083503ff in QCoreApplication::sendPostedEvents (s=0x98a7f30) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#23 postEventSourceDispatch (s=0x98a7f30) at kernel/qeventdispatcher_glib.cpp:210
#24 0x0331de78 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#25 0x03321720 in ?? () from /lib/libglib-2.0.so.0
#26 0x03321853 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#27 0x0835002c in QEventDispatcherGlib::processEvents (this=0x9888a30, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#28 0x012e8be5 in QGuiEventDispatcherGlib::processEvents (this=0x9888a30, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#29 0x08323c79 in QEventLoop::processEvents (this=0xbfb9e384, flags=) at kernel/qeventloop.cpp:149
#30 0x083240ca in QEventLoop::exec (this=0xbfb9e384, flags=...) at kernel/qeventloop.cpp:201
#31 0x0832653f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#32 0x01247dd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#33 0x0807a6f5 in main (argc=6, argv=0xbfb9e604) at ../../../../apps/dolphin/src/main.cpp:94

This bug may be a duplicate of or related to bug 213283

Reported using DrKonqi
Comment 1 Jonathan Thomas 2009-11-10 00:32:37 UTC
Thanks. This is most likely bug 188387.

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