Bug 105050

Version:           3.4.0 (using KDE 3.4.0, Debian Package 4:3.4.0-0pre4 (3.1))
Compiler:          gcc version 3.3.5 (Debian 1:3.3.5-8)
OS:                Linux (i686) release 2.6.8-2-386

Hello,
When I enter into an archive I have two solutions to get out:
 - Parent Directory
 - Precedent
So, if I use Precedent, I get showed the last directory, everything is ok.
But, when I get out from the directory by using Parent Directory (SHIFT+UP as shortcut, or the button) (by walking into the directory or not, just when getting out from the archive) Konqueror crashes.
I tried out from rar, zip, tar, etc... every archive does the same bug. I thought it does it with every kio_slave :/

I have a suggestion:
Maybe the fact that I am in a kio_slave tar: zip: etc... to get a directory up makes it bug because it needs to show file:

++
ps: here is a call stack 

[KCrash handler]
#3  0x40d2ce48 in QGList::first () from /usr/lib/libqt-mt.so.3
#4  0x4047308b in KDirListerCache::slotUpdateResult ()
   from /usr/lib/libkio.so.4
#5  0x40477db4 in KDirListerCache::qt_invoke () from /usr/lib/libkio.so.4
#6  0x40a7471c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#7  0x403c7e3a in KIO::Job::result () from /usr/lib/libkio.so.4
#8  0x403b013c in KIO::Job::emitResult () from /usr/lib/libkio.so.4
#9  0x403b165c in KIO::SimpleJob::slotFinished () from /usr/lib/libkio.so.4
#10 0x403ba6ae in KIO::ListJob::slotFinished () from /usr/lib/libkio.so.4
#11 0x403cb293 in KIO::ListJob::qt_invoke () from /usr/lib/libkio.so.4
#12 0x40a7471c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#13 0x40a74544 in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#14 0x403a634e in KIO::SlaveInterface::finished () from /usr/lib/libkio.so.4
#15 0x403a4eb1 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.4
#16 0x403a43b9 in KIO::SlaveInterface::dispatch () from /usr/lib/libkio.so.4
#17 0x403a1deb in KIO::Slave::gotInput () from /usr/lib/libkio.so.4
#18 0x403a3b08 in KIO::Slave::qt_invoke () from /usr/lib/libkio.so.4
#19 0x40a7471c in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#20 0x40a7487d in QObject::activate_signal () from /usr/lib/libqt-mt.so.3
#21 0x40db4452 in QSocketNotifier::activated () from /usr/lib/libqt-mt.so.3
#22 0x40a90f00 in QSocketNotifier::event () from /usr/lib/libqt-mt.so.3
#23 0x40a17e1f in QApplication::internalNotify () from /usr/lib/libqt-mt.so.3
#24 0x40a1741e in QApplication::notify () from /usr/lib/libqt-mt.so.3
#25 0x40671ac5 in KApplication::notify () from /usr/lib/libkdecore.so.4
#26 0x40a0781a in QEventLoop::activateSocketNotifiers ()
   from /usr/lib/libqt-mt.so.3
#27 0x409c0cb3 in QEventLoop::processEvents () from /usr/lib/libqt-mt.so.3
#28 0x40a2a1d8 in QEventLoop::enterLoop () from /usr/lib/libqt-mt.so.3
#29 0x40a2a088 in QEventLoop::exec () from /usr/lib/libqt-mt.so.3
#30 0x40a18071 in QApplication::exec () from /usr/lib/libqt-mt.so.3
#31 0x416142cc in kdemain () from /usr/lib/libkdeinit_konqueror.so
#32 0x40018786 in kdeinitmain () from /usr/lib/kde3/konqueror.so

Maybe I'm not false with the kio's, because it is named by the different calls.