Bug 214952 - dolphin crashed while trying to log on to an SMB share via openvpn
Summary: dolphin crashed while trying to log on to an SMB share via openvpn
Status: RESOLVED DUPLICATE of bug 197851
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-11-17 12:28 UTC by Tim Richardson
Modified: 2009-11-17 12:54 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 Tim Richardson 2009-11-17 12:28:35 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.31-6.slh.1-sidux-686 i686
Distribution: Debian GNU/Linux unstable (sid)

What I was doing when the application crashed:
While on my third attempt to log on to a Windows Server share, Dolphin crashed. Previous attempts failed probably because I didn't give my username in the format domain\user. Anyway, when I tried this, it crashed. 

It is reproducible. 


 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#6  KDirListerCache::slotUpdateResult (this=0x92d1c40, j=0x9205da8) at ../../kio/kio/kdirlister.cpp:1539
#7  0xb76ebda4 in KDirListerCache::qt_metacall (this=0x92d1c40, _c=QMetaObject::InvokeMetaMethod, _id=11, _a=0xbff95b3c) at ./kdirlister_p.moc:102
#8  0xb61cf303 in QMetaObject::activate (sender=0x9205da8, from_signal_index=7, to_signal_index=7, argv=0xbff95b3c) at kernel/qobject.cpp:3112
#9  0xb61cff42 in QMetaObject::activate (sender=0x9205da8, m=0x80b5580, local_signal_index=3, argv=0xbff95b3c) at kernel/qobject.cpp:3186
#10 0xb6db74d3 in KJob::result (this=0x9205da8, _t1=0x9205da8) at ./kjob.moc:188
#11 0xb6db7979 in KJob::emitResult (this=0x9205da8) at ../../kdecore/jobs/kjob.cpp:304
#12 0xb76bcbd5 in KIO::SimpleJob::slotFinished (this=0x9205da8) at ../../kio/kio/job.cpp:477
#13 0xb76bd194 in KIO::ListJob::slotFinished (this=0x9205da8) at ../../kio/kio/job.cpp:2408
#14 0xb76bebd3 in KIO::ListJob::qt_metacall (this=0x9205da8, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0xbff95d28) at ./jobclasses.moc:764
#15 0xb61cf303 in QMetaObject::activate (sender=0x9564f78, from_signal_index=8, to_signal_index=8, argv=0x0) at kernel/qobject.cpp:3112
#16 0xb61cff42 in QMetaObject::activate (sender=0x9564f78, m=0xb7864ba4, local_signal_index=4, argv=0x0) at kernel/qobject.cpp:3186
#17 0xb77827d7 in KIO::SlaveInterface::finished (this=0x9564f78) at ./slaveinterface.moc:165
#18 0xb7786587 in KIO::SlaveInterface::dispatch (this=0x9564f78, _cmd=104, rawdata=...) at ../../kio/kio/slaveinterface.cpp:175
#19 0xb7782cb7 in KIO::SlaveInterface::dispatch (this=0x9564f78) at ../../kio/kio/slaveinterface.cpp:91
#20 0xb7774c9d in KIO::Slave::gotInput (this=0x9564f78) at ../../kio/kio/slave.cpp:322
#21 0xb7777183 in KIO::Slave::qt_metacall (this=0x9564f78, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbff95ff8) at ./slave.moc:76
#22 0xb61cf303 in QMetaObject::activate (sender=0x95fcb50, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3112
#23 0xb61cff42 in QMetaObject::activate (sender=0x95fcb50, m=0xb78614e0, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3186
#24 0xb7680d57 in KIO::Connection::readyRead (this=0x95fcb50) at ./connection.moc:86
#25 0xb7682663 in KIO::ConnectionPrivate::dequeue (this=0x960cee0) at ../../kio/kio/connection.cpp:82
#26 0xb7682a46 in KIO::Connection::qt_metacall (this=0x95fcb50, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0x92c1ec8) at ./connection.moc:73
#27 0xb61c8b0b in QMetaCallEvent::placeMetaCall (this=0x94a9f40, object=0x95fcb50) at kernel/qobject.cpp:477
#28 0xb61ca5e0 in QObject::event (this=0x95fcb50, e=0x94a9f40) at kernel/qobject.cpp:1110
#29 0xb63f2a94 in QApplicationPrivate::notify_helper (this=0x9208770, receiver=0x95fcb50, e=0x94a9f40) at kernel/qapplication.cpp:4065
#30 0xb63fabee in QApplication::notify (this=0xbff967a4, receiver=0x95fcb50, e=0x94a9f40) at kernel/qapplication.cpp:3605
#31 0xb70ed0fd in KApplication::notify (this=0xbff967a4, receiver=0x95fcb50, event=0x94a9f40) at ../../kdeui/kernel/kapplication.cpp:302
#32 0xb61ba1eb in QCoreApplication::notifyInternal (this=0xbff967a4, receiver=0x95fcb50, event=0x94a9f40) at kernel/qcoreapplication.cpp:610
#33 0xb61bae2e in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x91e2830) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#34 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x91e2830) at kernel/qcoreapplication.cpp:1247
#35 0xb61bb00d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#36 0xb61e54cf in QCoreApplication::sendPostedEvents (s=0x9201d10) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#37 postEventSourceDispatch (s=0x9201d10) at kernel/qeventdispatcher_glib.cpp:276
#38 0xb5810e98 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#39 0xb5814623 in ?? () from /lib/libglib-2.0.so.0
#40 0xb58147a8 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#41 0xb61e5041 in QEventDispatcherGlib::processEvents (this=0x91e2370, flags=...) at kernel/qeventdispatcher_glib.cpp:407
#42 0xb6492305 in QGuiEventDispatcherGlib::processEvents (this=0x91e2370, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#43 0xb61b883a in QEventLoop::processEvents (this=0xbff96730, flags=...) at kernel/qeventloop.cpp:149
#44 0xb61b8c82 in QEventLoop::exec (this=0xbff96730, flags=...) at kernel/qeventloop.cpp:201
#45 0xb61bb0d9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#46 0xb63f2917 in QApplication::exec () at kernel/qapplication.cpp:3525
#47 0x0807a945 in main (argc=5, argv=0xbff96954) at ../../../../apps/dolphin/src/main.cpp:94

Reported using DrKonqi
Comment 1 Frank Reininghaus 2009-11-17 12:54:21 UTC
Thanks for the report! This seems to be a crash that has been reported already.

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