Bug 223980 - dolphin crashes when connecting to network workgroup computer
Summary: dolphin crashes when connecting to network workgroup computer
Status: RESOLVED DUPLICATE of bug 213895
Alias: None
Product: kio
Classification: Frameworks and Libraries
Component: general (show other bugs)
Version: 4.3
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-01-24 00:34 UTC by z01111010
Modified: 2010-01-26 14:59 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 z01111010 2010-01-24 00:34:40 UTC
Application that crashed: dolphin
Version of the application: 1.3
KDE Version: 4.3.4 (KDE 4.3.4)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-18-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
In Dolphin, clicking Network -> Network, then clicking on a computer on my LAN, causes Dolphin to crash. Seems to be repeatable.

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#6  QBasicAtomicInt::ref (this=0x9a3ea08, j=0x9d953b0) at /usr/include/qt4/QtCore/qatomic_i386.h:120
#7  QList (this=0x9a3ea08, j=0x9d953b0) at /usr/include/qt4/QtCore/qlist.h:111
#8  KDirListerCache::slotResult (this=0x9a3ea08, j=0x9d953b0) at ../../kio/kio/kdirlister.cpp:1119
#9  0x0020b9a7 in KDirListerCache::qt_metacall (this=0x9a3ea08, _c=QMetaObject::InvokeMetaMethod, _id=12, _a=0xbf806bb8) at ./kdirlister_p.moc:99
#10 0x03b2f263 in QMetaObject::activate (sender=0x9d953b0, from_signal_index=7, to_signal_index=7, argv=0xbf806bb8) at kernel/qobject.cpp:3113
#11 0x03b2fec2 in QMetaObject::activate (sender=0x9d953b0, m=0x80b7400, local_signal_index=3, argv=0xbf806bb8) at kernel/qobject.cpp:3187
#12 0x0086f353 in KJob::result (this=0x9d953b0, _t1=0x9d953b0) at ./kjob.moc:188
#13 0x0086f7d9 in KJob::emitResult (this=0x9d953b0) at ../../kdecore/jobs/kjob.cpp:304
#14 0x001d9690 in KIO::SimpleJob::slotFinished (this=0x9d953b0) at ../../kio/kio/job.cpp:477
#15 0x001d97fb in KIO::ListJob::slotFinished (this=0x9d953b0) at ../../kio/kio/job.cpp:2408
#16 0x001e041e in KIO::ListJob::qt_metacall (this=0x9d953b0, _c=QMetaObject::InvokeMetaMethod, _id=43, _a=0xbf806ddc) at ./jobclasses.moc:764
#17 0x03b2f263 in QMetaObject::activate (sender=0x9bbb6b0, from_signal_index=8, to_signal_index=8, argv=0x0) at kernel/qobject.cpp:3113
#18 0x03b2fec2 in QMetaObject::activate (sender=0x9bbb6b0, m=0x38af64, local_signal_index=4, argv=0x0) at kernel/qobject.cpp:3187
#19 0x002a3587 in KIO::SlaveInterface::finished (this=0x9bbb6b0) at ./slaveinterface.moc:165
#20 0x002a747d in KIO::SlaveInterface::dispatch (this=0x9bbb6b0, _cmd=104, rawdata=...) at ../../kio/kio/slaveinterface.cpp:175
#21 0x002a3a43 in KIO::SlaveInterface::dispatch (this=0x9bbb6b0) at ../../kio/kio/slaveinterface.cpp:91
#22 0x00295b1a in KIO::Slave::gotInput (this=0x9bbb6b0) at ../../kio/kio/slave.cpp:322
#23 0x00297f13 in KIO::Slave::qt_metacall (this=0x9bbb6b0, _c=QMetaObject::InvokeMetaMethod, _id=30, _a=0xbf8070bc) at ./slave.moc:76
#24 0x03b2f263 in QMetaObject::activate (sender=0x9b43ad0, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113
#25 0x03b2fec2 in QMetaObject::activate (sender=0x9b43ad0, m=0x3878a0, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#26 0x0019ff37 in KIO::Connection::readyRead (this=0x9b43ad0) at ./connection.moc:86
#27 0x001a1cfe in KIO::ConnectionPrivate::dequeue (this=0x9d5def0) at ../../kio/kio/connection.cpp:82
#28 0x001a1e2e in KIO::Connection::qt_metacall (this=0x9b43ad0, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0x9fe9888) at ./connection.moc:73
#29 0x03b27f0b in QMetaCallEvent::placeMetaCall (this=0x9daf918, object=0x9b43ad0) at kernel/qobject.cpp:477
#30 0x03b295fe in QObject::event (this=0x9b43ad0, e=0x9daf918) at kernel/qobject.cpp:1111
#31 0x01001f54 in QApplicationPrivate::notify_helper (this=0x98afe60, receiver=0x9b43ad0, e=0x9daf918) at kernel/qapplication.cpp:4056
#32 0x0100967c in QApplication::notify (this=0xbf80795c, receiver=0x9b43ad0, e=0x9daf918) at kernel/qapplication.cpp:3603
#33 0x00d211aa in KApplication::notify (this=0xbf80795c, receiver=0x9b43ad0, event=0x9daf918) at ../../kdeui/kernel/kapplication.cpp:302
#34 0x03b196cb in QCoreApplication::notifyInternal (this=0xbf80795c, receiver=0x9b43ad0, event=0x9daf918) at kernel/qcoreapplication.cpp:610
#35 0x03b1a2b2 in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x988de48) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#36 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x988de48) at kernel/qcoreapplication.cpp:1247
#37 0x03b1a47d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#38 0x03b443ff in QCoreApplication::sendPostedEvents (s=0x98ac310) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#39 postEventSourceDispatch (s=0x98ac310) at kernel/qeventdispatcher_glib.cpp:210
#40 0x02bdce88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#41 0x02be0730 in ?? () from /lib/libglib-2.0.so.0
#42 0x02be0863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#43 0x03b4402c in QEventDispatcherGlib::processEvents (this=0x988da30, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#44 0x010a2be5 in QGuiEventDispatcherGlib::processEvents (this=0x988da30, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#45 0x03b17c79 in QEventLoop::processEvents (this=0xbf8078b4, flags=) at kernel/qeventloop.cpp:149
#46 0x03b180ca in QEventLoop::exec (this=0xbf8078b4, flags=...) at kernel/qeventloop.cpp:201
#47 0x03b1a53f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#48 0x01001dd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#49 0x0807a6f5 in _start ()

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

Reported using DrKonqi
Comment 1 Frank Reininghaus 2010-01-26 14:59:10 UTC
Thanks for the bug report! This issue has been reported already, and it looks like the cause of the bug might have been found just today.

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