Bug 238381 - dolphin crashes when I try to reach a shared directory over wireless lan
Summary: dolphin crashes when I try to reach a shared directory over wireless lan
Status: RESOLVED DUPLICATE of bug 213895
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: 2010-05-21 12:44 UTC by Ozer Tayiz
Modified: 2010-06-10 03:37 UTC (History)
0 users

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 Ozer Tayiz 2010-05-21 12:44:14 UTC
Application that crashed: dolphin
Version of the application: 1.3
KDE Version: 4.3.5 (KDE 4.3.5)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-16-generic i686
Distribution: Linux Mint 8 Helena - KDE Community Edition

What I was doing when the application crashed:
I tried to set up a shared directory between my laptop and home computer on the local network using wireless LAN in my home. I do the settings from properties>sharing of the folder, but when I try to reach the folder from dolphin, it crashes.

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#6  QBasicAtomicInt::ref (this=0x9224268, j=0x9b090c8) at /usr/include/qt4/QtCore/qatomic_i386.h:120
#7  QList (this=0x9224268, j=0x9b090c8) at /usr/include/qt4/QtCore/qlist.h:111
#8  KDirListerCache::slotResult (this=0x9224268, j=0x9b090c8) at ../../kio/kio/kdirlister.cpp:1180
#9  0x009cccc7 in KDirListerCache::qt_metacall (this=0x9224268, _c=QMetaObject::InvokeMetaMethod, _id=12, _a=0xbfc35db8) at ./kdirlister_p.moc:99
#10 0x08263263 in QMetaObject::activate (sender=0x9b090c8, from_signal_index=7, to_signal_index=7, argv=0xbfc35db8) at kernel/qobject.cpp:3113
#11 0x08263ec2 in QMetaObject::activate (sender=0x9b090c8, m=0x80b7400, local_signal_index=3, argv=0xbfc35db8) at kernel/qobject.cpp:3187
#12 0x02858353 in KJob::result (this=0x9b090c8, _t1=0x9b090c8) at ./kjob.moc:188
#13 0x028587d9 in KJob::emitResult (this=0x9b090c8) at ../../kdecore/jobs/kjob.cpp:304
#14 0x009989e0 in KIO::SimpleJob::slotFinished (this=0x9b090c8) at ../../kio/kio/job.cpp:477
#15 0x00998b4b in KIO::ListJob::slotFinished (this=0x9b090c8) at ../../kio/kio/job.cpp:2415
#16 0x0099f76e in KIO::ListJob::qt_metacall (this=0x9b090c8, _c=QMetaObject::InvokeMetaMethod, _id=43, _a=0xbfc35fdc) at ./jobclasses.moc:764
#17 0x08263263 in QMetaObject::activate (sender=0x959d400, from_signal_index=8, to_signal_index=8, argv=0x0) at kernel/qobject.cpp:3113
#18 0x08263ec2 in QMetaObject::activate (sender=0x959d400, m=0xb4bf64, local_signal_index=4, argv=0x0) at kernel/qobject.cpp:3187
#19 0x00a63a07 in KIO::SlaveInterface::finished (this=0x959d400) at ./slaveinterface.moc:165
#20 0x00a678fd in KIO::SlaveInterface::dispatch (this=0x959d400, _cmd=104, rawdata=...) at ../../kio/kio/slaveinterface.cpp:175
#21 0x00a63ec3 in KIO::SlaveInterface::dispatch (this=0x959d400) at ../../kio/kio/slaveinterface.cpp:91
#22 0x00a55eba in KIO::Slave::gotInput (this=0x959d400) at ../../kio/kio/slave.cpp:323
#23 0x00a58393 in KIO::Slave::qt_metacall (this=0x959d400, _c=QMetaObject::InvokeMetaMethod, _id=30, _a=0xbfc362bc) at ./slave.moc:76
#24 0x08263263 in QMetaObject::activate (sender=0x93886e8, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113
#25 0x08263ec2 in QMetaObject::activate (sender=0x93886e8, m=0xb488a0, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#26 0x0095f227 in KIO::Connection::readyRead (this=0x93886e8) at ./connection.moc:86
#27 0x00960fee in KIO::ConnectionPrivate::dequeue (this=0x9c16968) at ../../kio/kio/connection.cpp:82
#28 0x0096111e in KIO::Connection::qt_metacall (this=0x93886e8, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0x96589e8) at ./connection.moc:73
#29 0x0825bf0b in QMetaCallEvent::placeMetaCall (this=0x95849a8, object=0x93886e8) at kernel/qobject.cpp:477
#30 0x0825d5fe in QObject::event (this=0x93886e8, e=0x95849a8) at kernel/qobject.cpp:1111
#31 0x0863ff54 in QApplicationPrivate::notify_helper (this=0x9086090, receiver=0x93886e8, e=0x95849a8) at kernel/qapplication.cpp:4056
#32 0x0864767c in QApplication::notify (this=0xbfc36b5c, receiver=0x93886e8, e=0x95849a8) at kernel/qapplication.cpp:3603
#33 0x0116a25a in KApplication::notify (this=0xbfc36b5c, receiver=0x93886e8, event=0x95849a8) at ../../kdeui/kernel/kapplication.cpp:302
#34 0x0824d6cb in QCoreApplication::notifyInternal (this=0xbfc36b5c, receiver=0x93886e8, event=0x95849a8) at kernel/qcoreapplication.cpp:610
#35 0x0824e2b2 in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x9068e48) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#36 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x9068e48) at kernel/qcoreapplication.cpp:1247
#37 0x0824e47d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#38 0x082783ff in QCoreApplication::sendPostedEvents (s=0x908db90) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#39 postEventSourceDispatch (s=0x908db90) at kernel/qeventdispatcher_glib.cpp:210
#40 0x05a69e88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#41 0x05a6d730 in ?? () from /lib/libglib-2.0.so.0
#42 0x05a6d863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#43 0x0827802c in QEventDispatcherGlib::processEvents (this=0x9068a30, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#44 0x086e0be5 in QGuiEventDispatcherGlib::processEvents (this=0x9068a30, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#45 0x0824bc79 in QEventLoop::processEvents (this=0xbfc36ab4, flags=) at kernel/qeventloop.cpp:149
#46 0x0824c0ca in QEventLoop::exec (this=0xbfc36ab4, flags=...) at kernel/qeventloop.cpp:201
#47 0x0824e53f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#48 0x0863fdd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#49 0x0807a6f5 in _start ()

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

Reported using DrKonqi
Comment 1 Christoph Feck 2010-06-10 03:37:44 UTC

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