Bug 78599

Oop. The header appears misleading. KDElibs was compiled from sources. Konqueror is the binary release packaged by Redhat for Fedora.

I couldn't get a backtrace at the ASSERT, but this is the trace from when it hits the assert line after the first click. I'm betting that it just blows when the same call is made in too short a time.

#0  KDirListerCache::slotResult(KIO::Job*) (this=0x853c198, j=0x85fd748) at kdirlister.cpp:941
#1  0x4efe99b7 in KDirListerCache::qt_invoke(int, QUObject*) (this=0x853c198, _id=7, _o=0xbfffead0) at kdirlister_p.moc:132
#2  0x4f634467 in QObject::activate_signal(QConnectionList*, QUObject*) (this=0x85fd748, clist=0x83c1e48, o=0xbfffead0) at kernel/qobject.cpp:2356
#3  0x4ef56992 in KIO::Job::result(KIO::Job*) (this=0x85fd748, t0=0x85fd748) at jobclasses.moc:156
#4  0x4ef44ad5 in KIO::Job::emitResult() (this=0x85fd748) at job.cpp:207
#5  0x4ef46043 in KIO::SimpleJob::slotFinished() (this=0x85fd748) at job.cpp:524
#6  0x4ef4bf52 in KIO::ListJob::slotFinished() (this=0x85fd748) at job.cpp:1809
#7  0x4ef59c4c in KIO::ListJob::qt_invoke(int, QUObject*) (this=0x85fd748, _id=16, _o=0xbfffed40) at jobclasses.moc:1370
#8  0x4f634467 in QObject::activate_signal(QConnectionList*, QUObject*) (this=0x85a60e0, clist=0x855f3a8, o=0xbfffed40) at kernel/qobject.cpp:2356
#9  0x4f634306 in QObject::activate_signal(int) (this=0x85a60e0, signal=6) at kernel/qobject.cpp:2325
#10 0x4ef379d1 in KIO::SlaveInterface::finished() (this=0x85a60e0) at slaveinterface.moc:226
#11 0x4ef3611d in KIO::SlaveInterface::dispatch(int, QMemArray<char> const&) (this=0x85a60e0, _cmd=104, rawdata=@0xbfffef00) at slaveinterface.cpp:255
#12 0x4ef35d74 in KIO::SlaveInterface::dispatch() (this=0x85a60e0) at slaveinterface.cpp:191
#13 0x4ef3388b in KIO::Slave::gotInput() (this=0x85a60e0) at slave.cpp:294
#14 0x4ef352b7 in KIO::Slave::qt_invoke(int, QUObject*) (this=0x85a60e0, _id=4, _o=0xbffff040) at slave.moc:113
#15 0x4f634467 in QObject::activate_signal(QConnectionList*, QUObject*) (this=0x84ec710, clist=0x8462598, o=0xbffff040) at kernel/qobject.cpp:2356
#16 0x4f6347d9 in QObject::activate_signal(int, int) (this=0x84ec710, signal=2, param=16) at kernel/qobject.cpp:2449
#17 0x4f9890c5 in QSocketNotifier::activated(int) (this=0x84ec710, t0=16) at .moc/debug-shared-mt/moc_qsocketnotifier.cpp:85
#18 0x4f654398 in QSocketNotifier::event(QEvent*) (this=0x84ec710, e=0xbffff2b0) at kernel/qsocketnotifier.cpp:280
#19 0x4f5d257f in QApplication::internalNotify(QObject*, QEvent*) (this=0xbffff880, receiver=0x84ec710, e=0xbffff2b0) at kernel/qapplication.cpp:2618
#20 0x4f5d1a4e in QApplication::notify(QObject*, QEvent*) (this=0xbffff880, receiver=0x84ec710, e=0xbffff2b0) at kernel/qapplication.cpp:2341
#21 0x4e942947 in KApplication::notify(QObject*, QEvent*) (this=0xbffff880, receiver=0x84ec710, event=0xbffff2b0) at kapplication.cpp:506
#22 0x4f2e8f17 in QApplication::sendEvent(QObject*, QEvent*) (receiver=0x84ec710, event=0xbffff2b0) at qapplication.h:491
#23 0x4f5c0a3e in QEventLoop::activateSocketNotifiers() (this=0x8119d50) at kernel/qeventloop_unix.cpp:580
#24 0x4f57afde in QEventLoop::processEvents(unsigned) (this=0x8119d50, flags=4) at kernel/qeventloop_x11.cpp:383
#25 0x4f5e65aa in QEventLoop::enterLoop() (this=0x8119d50) at kernel/qeventloop.cpp:198
#26 0x4f5e64c6 in QEventLoop::exec() (this=0x8119d50) at kernel/qeventloop.cpp:145
#27 0x4f5d26f5 in QApplication::exec() (this=0xbffff880) at kernel/qapplication.cpp:2741
#28 0x4fba1b9c in kdemain () from /usr/lib/libkdeinit_konqueror.so
#29 0x080485db in ?? ()
#30 0x00000001 in ?? ()
#31 0xbffff9d8 in ?? ()
#32 0x00733eb3 in __libc_start_main () from /lib/tls/libc.so.6

Interesting. It appears this bug does not occur if you have more than one instance of Konqueror running but occurs reliably if there is only one. Just another data point.

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