Bug 216572 - remote:/ -> network -> oliniusz.local -> oliniusz [xx:xx:xx:xx:xx] -> segm. fault
Summary: remote:/ -> network -> oliniusz.local -> oliniusz [xx:xx:xx:xx:xx] -> segm. f...
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-28 23:21 UTC by Oliniusz
Modified: 2009-12-01 00:24 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 Oliniusz 2009-11-28 23:21:52 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:
I suppose it's duplicate of bug 213645

remote:/ -> network -> oliniusz.local -> oliniusz [xx:xx:xx:xx:xx] -> segm. fault

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#6  QBasicAtomicInt::ref (this=0x94c87e0, j=0x9af1f40) at /usr/include/qt4/QtCore/qatomic_i386.h:120
#7  QList (this=0x94c87e0, j=0x9af1f40) at /usr/include/qt4/QtCore/qlist.h:111
#8  KDirListerCache::slotResult (this=0x94c87e0, j=0x9af1f40) at ../../kio/kio/kdirlister.cpp:1119
#9  0x0020bac7 in KDirListerCache::qt_metacall (this=0x94c87e0, _c=QMetaObject::InvokeMetaMethod, _id=12, _a=0xbf9ab148) at ./kdirlister_p.moc:99
#10 0x0117f263 in QMetaObject::activate (sender=0x9af1f40, from_signal_index=7, to_signal_index=7, argv=0xbf9ab148) at kernel/qobject.cpp:3113
#11 0x0117fec2 in QMetaObject::activate (sender=0x9af1f40, m=0x80b7400, local_signal_index=3, argv=0xbf9ab148) at kernel/qobject.cpp:3187
#12 0x00ebbff3 in KJob::result (this=0x9af1f40, _t1=0x9af1f40) at ./kjob.moc:188
#13 0x00ebc479 in KJob::emitResult (this=0x9af1f40) at ../../kdecore/jobs/kjob.cpp:304
#14 0x001d97b0 in KIO::SimpleJob::slotFinished (this=0x9af1f40) at ../../kio/kio/job.cpp:477
#15 0x001d991b in KIO::ListJob::slotFinished (this=0x9af1f40) at ../../kio/kio/job.cpp:2408
#16 0x001e053e in KIO::ListJob::qt_metacall (this=0x9af1f40, _c=QMetaObject::InvokeMetaMethod, _id=43, _a=0xbf9ab36c) at ./jobclasses.moc:764
#17 0x0117f263 in QMetaObject::activate (sender=0x966bff8, from_signal_index=8, to_signal_index=8, argv=0x0) at kernel/qobject.cpp:3113
#18 0x0117fec2 in QMetaObject::activate (sender=0x966bff8, m=0x38bf64, local_signal_index=4, argv=0x0) at kernel/qobject.cpp:3187
#19 0x002a36a7 in KIO::SlaveInterface::finished (this=0x966bff8) at ./slaveinterface.moc:165
#20 0x002a759d in KIO::SlaveInterface::dispatch (this=0x966bff8, _cmd=104, rawdata=...) at ../../kio/kio/slaveinterface.cpp:175
#21 0x002a3b63 in KIO::SlaveInterface::dispatch (this=0x966bff8) at ../../kio/kio/slaveinterface.cpp:91
#22 0x00295c3a in KIO::Slave::gotInput (this=0x966bff8) at ../../kio/kio/slave.cpp:322
#23 0x00298033 in KIO::Slave::qt_metacall (this=0x966bff8, _c=QMetaObject::InvokeMetaMethod, _id=30, _a=0xbf9ab64c) at ./slave.moc:76
#24 0x0117f263 in QMetaObject::activate (sender=0x9851870, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3113
#25 0x0117fec2 in QMetaObject::activate (sender=0x9851870, m=0x3888a0, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3187
#26 0x001a0057 in KIO::Connection::readyRead (this=0x9851870) at ./connection.moc:86
#27 0x001a1e1e in KIO::ConnectionPrivate::dequeue (this=0x979e890) at ../../kio/kio/connection.cpp:82
#28 0x001a1f4e in KIO::Connection::qt_metacall (this=0x9851870, _c=QMetaObject::InvokeMetaMethod, _id=5, _a=0x979e408) at ./connection.moc:73
#29 0x01177f0b in QMetaCallEvent::placeMetaCall (this=0x9727b88, object=0x9851870) at kernel/qobject.cpp:477
#30 0x011795fe in QObject::event (this=0x9851870, e=0x9727b88) at kernel/qobject.cpp:1111
#31 0x03bddf54 in QApplicationPrivate::notify_helper (this=0x93bb5a0, receiver=0x9851870, e=0x9727b88) at kernel/qapplication.cpp:4056
#32 0x03be567c in QApplication::notify (this=0xbf9abeec, receiver=0x9851870, e=0x9727b88) at kernel/qapplication.cpp:3603
#33 0x0090214a in KApplication::notify (this=0xbf9abeec, receiver=0x9851870, event=0x9727b88) at ../../kdeui/kernel/kapplication.cpp:302
#34 0x011696cb in QCoreApplication::notifyInternal (this=0xbf9abeec, receiver=0x9851870, event=0x9727b88) at kernel/qcoreapplication.cpp:610
#35 0x0116a2b2 in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x9394e48) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#36 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x9394e48) at kernel/qcoreapplication.cpp:1247
#37 0x0116a47d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#38 0x011943ff in QCoreApplication::sendPostedEvents (s=0x93b4dc0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#39 postEventSourceDispatch (s=0x93b4dc0) at kernel/qeventdispatcher_glib.cpp:210
#40 0x0368de78 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#41 0x03691720 in ?? () from /lib/libglib-2.0.so.0
#42 0x03691853 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#43 0x0119402c in QEventDispatcherGlib::processEvents (this=0x9394a30, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#44 0x03c7ebe5 in QGuiEventDispatcherGlib::processEvents (this=0x9394a30, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#45 0x01167c79 in QEventLoop::processEvents (this=0xbf9abe44, flags=) at kernel/qeventloop.cpp:149
#46 0x011680ca in QEventLoop::exec (this=0xbf9abe44, flags=...) at kernel/qeventloop.cpp:201
#47 0x0116a53f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#48 0x03bdddd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#49 0x0807a6f5 in _start ()

Reported using DrKonqi
Comment 1 Frank Reininghaus 2009-12-01 00:24:27 UTC
Thanks for the bug report!

(In reply to comment #0)
> I suppose it's duplicate of bug 213645

Yes, it seems so.

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