Bug 226458 - clicking zeroconf host in dolphin caused crash
Summary: clicking zeroconf host in dolphin caused crash
Status: RESOLVED DUPLICATE of bug 213895
Alias: None
Product: kio
Classification: Unmaintained
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-02-12 06:40 UTC by ben.l.gardiner
Modified: 2010-02-12 13:55 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description ben.l.gardiner 2010-02-12 06:40:45 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-19-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
I believe this is a duplicate of bug 221750. I browse to a host running avahi and ssh using dolphin and then click on the icon that has 'host [MAC]' and dolphin segfaults.

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#6  QBasicAtomicInt::ref (this=0xa17a9b0, j=0xa1eb3d8) at /usr/include/qt4/QtCore/qatomic_i386.h:120
#7  QList (this=0xa17a9b0, j=0xa1eb3d8) at /usr/include/qt4/QtCore/qlist.h:111
#8  KDirListerCache::slotResult (this=0xa17a9b0, j=0xa1eb3d8) at ../../kio/kio/kdirlister.cpp:1180
#9  0x00c2fcc7 in KDirListerCache::qt_metacall (this=0xa17a9b0, _c=QMetaObject::InvokeMetaMethod, _id=12, _a=0xbfd407c8) at ./kdirlister_p.moc:99
#10 0x014a5263 in QMetaObject::activate (sender=0xa1eb3d8, from_signal_index=7, to_signal_index=7, argv=0xbfd407c8) at kernel/qobject.cpp:3113
#11 0x014a5ec2 in QMetaObject::activate (sender=0xa1eb3d8, m=0x80b7400, local_signal_index=3, argv=0xbfd407c8) at kernel/qobject.cpp:3187
#12 0x001ea353 in KJob::result (this=0xa1eb3d8, _t1=0xa1eb3d8) at ./kjob.moc:188
#13 0x001ea7d9 in KJob::emitResult (this=0xa1eb3d8) at ../../kdecore/jobs/kjob.cpp:304
#14 0x00bfb9e0 in KIO::SimpleJob::slotFinished (this=0xa1eb3d8) at ../../kio/kio/job.cpp:477
#15 0x00bfbb4b in KIO::ListJob::slotFinished (this=0xa1eb3d8) at ../../kio/kio/job.cpp:2415
#16 0x00c0276e in KIO::ListJob::qt_metacall (this=0xa1eb3d8, _c=QMetaObject::InvokeMetaMethod, _id=43, _a=0xbfd409ec) at ./jobclasses.moc:764
#17 0x014a5263 in QMetaObject::activate (sender=0xa509f10, from_signal_index=8, to_signal_index=8, argv=0x0) at kernel/qobject.cpp:3113
#18 0x014a5ec2 in QMetaObject::activate (sender=0xa509f10, m=0xdaef64, local_signal_index=4, argv=0x0) at kernel/qobject.cpp:3187
#19 0x00cc6a07 in KIO::SlaveInterface::finished (this=0xa509f10) at ./slaveinterface.moc:165
#20 0x00cca8fd in KIO::SlaveInterface::dispatch (this=0xa509f10, _cmd=104, rawdata=...) at ../../kio/kio/slaveinterface.cpp:175
#21 0x00cc6ec3 in KIO::SlaveInterface::dispatch (this=0xa509f10) at ../../kio/kio/slaveinterface.cpp:91
#22 0x00cb8eba in KIO::Slave::gotInput (this=0xa509f10) at ../../kio/kio/slave.cpp:323
#23 0x00cbb393 in KIO::Slave::qt_metacall (this=0xa509f10, _c=QMetaObject::InvokeMetaMethod, _id=30, _a=0xbfd40ccc) at ./slave.moc:76
#24 0x014a5263 in QMetaObject::activate (sender=0xa590b90, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113
#25 0x014a5ec2 in QMetaObject::activate (sender=0xa590b90, m=0xdab8a0, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#26 0x00bc2227 in KIO::Connection::readyRead (this=0xa590b90) at ./connection.moc:86
#27 0x00bc3fee in KIO::ConnectionPrivate::dequeue (this=0xa511fd8) at ../../kio/kio/connection.cpp:82
#28 0x00bc411e in KIO::Connection::qt_metacall (this=0xa590b90, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0xa52a588) at ./connection.moc:73
#29 0x0149df0b in QMetaCallEvent::placeMetaCall (this=0xa439790, object=0xa590b90) at kernel/qobject.cpp:477
#30 0x0149f5fe in QObject::event (this=0xa590b90, e=0xa439790) at kernel/qobject.cpp:1111
#31 0x0902cf54 in QApplicationPrivate::notify_helper (this=0x9f80310, receiver=0xa590b90, e=0xa439790) at kernel/qapplication.cpp:4056
#32 0x0903467c in QApplication::notify (this=0xbfd4156c, receiver=0xa590b90, e=0xa439790) at kernel/qapplication.cpp:3603
#33 0x0109e25a in KApplication::notify (this=0xbfd4156c, receiver=0xa590b90, event=0xa439790) at ../../kdeui/kernel/kapplication.cpp:302
#34 0x0148f6cb in QCoreApplication::notifyInternal (this=0xbfd4156c, receiver=0xa590b90, event=0xa439790) at kernel/qcoreapplication.cpp:610
#35 0x014902b2 in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x9f5de48) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#36 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x9f5de48) at kernel/qcoreapplication.cpp:1247
#37 0x0149047d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#38 0x014ba3ff in QCoreApplication::sendPostedEvents (s=0x9f7e310) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#39 postEventSourceDispatch (s=0x9f7e310) at kernel/qeventdispatcher_glib.cpp:210
#40 0x07234e88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#41 0x07238730 in ?? () from /lib/libglib-2.0.so.0
#42 0x07238863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#43 0x014ba02c in QEventDispatcherGlib::processEvents (this=0x9f5da30, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#44 0x090cdbe5 in QGuiEventDispatcherGlib::processEvents (this=0x9f5da30, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#45 0x0148dc79 in QEventLoop::processEvents (this=0xbfd414c4, flags=) at kernel/qeventloop.cpp:149
#46 0x0148e0ca in QEventLoop::exec (this=0xbfd414c4, flags=...) at kernel/qeventloop.cpp:201
#47 0x0149053f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#48 0x0902cdd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#49 0x0807a6f5 in main (argc=6, argv=0xbfd41744) at ../../../../apps/dolphin/src/main.cpp:94

Reported using DrKonqi
Comment 1 Dario Andres 2010-02-12 13:55:00 UTC
Those crashes are being tracked at bug 213895. Regards

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