Bug 216198 - Dolphin crashes when trying to enter my own computer in my own network
Summary: Dolphin crashes when trying to enter my own computer in my own network
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: 2009-11-26 02:24 UTC by Jeroen
Modified: 2009-11-26 08:36 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 Jeroen 2009-11-26 02:24:11 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-15-generic i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
Dolphin crashes when trying to enter /Network/'my computer name'.local/ and clicking on my own computer

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#6  QBasicAtomicInt::ref (this=0x9016b90, j=0x92ed238) at /usr/include/qt4/QtCore/qatomic_i386.h:120
#7  QList (this=0x9016b90, j=0x92ed238) at /usr/include/qt4/QtCore/qlist.h:111
#8  KDirListerCache::slotResult (this=0x9016b90, j=0x92ed238) at ../../kio/kio/kdirlister.cpp:1119
#9  0x00c85ac7 in KDirListerCache::qt_metacall (this=0x9016b90, _c=QMetaObject::InvokeMetaMethod, _id=12, _a=0xbf90eef8) at ./kdirlister_p.moc:99
#10 0x01560263 in QMetaObject::activate (sender=0x92ed238, from_signal_index=7, to_signal_index=7, argv=0xbf90eef8) at kernel/qobject.cpp:3113
#11 0x01560ec2 in QMetaObject::activate (sender=0x92ed238, m=0x80b7400, local_signal_index=3, argv=0xbf90eef8) at kernel/qobject.cpp:3187
#12 0x007b4ff3 in KJob::result (this=0x92ed238, _t1=0x92ed238) at ./kjob.moc:188
#13 0x007b5479 in KJob::emitResult (this=0x92ed238) at ../../kdecore/jobs/kjob.cpp:304
#14 0x00c537b0 in KIO::SimpleJob::slotFinished (this=0x92ed238) at ../../kio/kio/job.cpp:477
#15 0x00c5391b in KIO::ListJob::slotFinished (this=0x92ed238) at ../../kio/kio/job.cpp:2408
#16 0x00c5a53e in KIO::ListJob::qt_metacall (this=0x92ed238, _c=QMetaObject::InvokeMetaMethod, _id=43, _a=0xbf90f11c) at ./jobclasses.moc:764
#17 0x01560263 in QMetaObject::activate (sender=0x9611b50, from_signal_index=8, to_signal_index=8, argv=0x0) at kernel/qobject.cpp:3113
#18 0x01560ec2 in QMetaObject::activate (sender=0x9611b50, m=0xe05f64, local_signal_index=4, argv=0x0) at kernel/qobject.cpp:3187
#19 0x00d1d6a7 in KIO::SlaveInterface::finished (this=0x9611b50) at ./slaveinterface.moc:165
#20 0x00d2159d in KIO::SlaveInterface::dispatch (this=0x9611b50, _cmd=104, rawdata=...) at ../../kio/kio/slaveinterface.cpp:175
#21 0x00d1db63 in KIO::SlaveInterface::dispatch (this=0x9611b50) at ../../kio/kio/slaveinterface.cpp:91
#22 0x00d0fc3a in KIO::Slave::gotInput (this=0x9611b50) at ../../kio/kio/slave.cpp:322
#23 0x00d12033 in KIO::Slave::qt_metacall (this=0x9611b50, _c=QMetaObject::InvokeMetaMethod, _id=30, _a=0xbf90f3fc) at ./slave.moc:76
#24 0x01560263 in QMetaObject::activate (sender=0x91d0810, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113
#25 0x01560ec2 in QMetaObject::activate (sender=0x91d0810, m=0xe028a0, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#26 0x00c1a057 in KIO::Connection::readyRead (this=0x91d0810) at ./connection.moc:86
#27 0x00c1be1e in KIO::ConnectionPrivate::dequeue (this=0x9617dd8) at ../../kio/kio/connection.cpp:82
#28 0x00c1bf4e in KIO::Connection::qt_metacall (this=0x91d0810, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0x9678108) at ./connection.moc:73
#29 0x01558f0b in QMetaCallEvent::placeMetaCall (this=0x9384b80, object=0x91d0810) at kernel/qobject.cpp:477
#30 0x0155a5fe in QObject::event (this=0x91d0810, e=0x9384b80) at kernel/qobject.cpp:1111
#31 0x03c9ef54 in QApplicationPrivate::notify_helper (this=0x8ea5990, receiver=0x91d0810, e=0x9384b80) at kernel/qapplication.cpp:4056
#32 0x03ca667c in QApplication::notify (this=0xbf90fc9c, receiver=0x91d0810, e=0x9384b80) at kernel/qapplication.cpp:3603
#33 0x00fe114a in KApplication::notify (this=0xbf90fc9c, receiver=0x91d0810, event=0x9384b80) at ../../kdeui/kernel/kapplication.cpp:302
#34 0x0154a6cb in QCoreApplication::notifyInternal (this=0xbf90fc9c, receiver=0x91d0810, event=0x9384b80) at kernel/qcoreapplication.cpp:610
#35 0x0154b2b2 in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x8e87e48) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#36 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8e87e48) at kernel/qcoreapplication.cpp:1247
#37 0x0154b47d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#38 0x015753ff in QCoreApplication::sendPostedEvents (s=0x8ea7710) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#39 postEventSourceDispatch (s=0x8ea7710) at kernel/qeventdispatcher_glib.cpp:210
#40 0x011d9e78 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#41 0x011dd720 in ?? () from /lib/libglib-2.0.so.0
#42 0x011dd853 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#43 0x0157502c in QEventDispatcherGlib::processEvents (this=0x8e87a30, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#44 0x03d3fbe5 in QGuiEventDispatcherGlib::processEvents (this=0x8e87a30, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#45 0x01548c79 in QEventLoop::processEvents (this=0xbf90fbf4, flags=) at kernel/qeventloop.cpp:149
#46 0x015490ca in QEventLoop::exec (this=0xbf90fbf4, flags=...) at kernel/qeventloop.cpp:201
#47 0x0154b53f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#48 0x03c9edd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#49 0x0807a6f5 in _start ()

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

Reported using DrKonqi
Comment 1 Frank Reininghaus 2009-11-26 08:36:29 UTC
Thanks for the bug report! This crash has been reported already.

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