Here using:

Qt: 4.4.3
KDE: 4.1.85 (KDE 4.1.85 (KDE 4.2 Beta2))
kdelibs svn rev. 898705 / kdebase svn rev. 898705

I can't reproduce this bug.
Can you start Dolphin from a shell and then paste the Dolphin output (after the crash) here? (mainly the "ASSERT" line). Thanks :)

I've tried to do what you asked but when I launch dolphin from a konsole and repeat my sequence that causes the crash, dolphin doesn't crash ! I can still cause the crash when I launch dolphin from the K menu or from a panel icon.

Cannot reproduce the crash too.

I removed my icons that launch Dolphin from the K menu and from the panel, I then setup the icons again without using any arguments on the command line in the icon settings, previously the command line was: dolphin %i -caption "%c" "%u", now I've just left the command as: dolphin and dolphin does not crash when I use the sequence that I previously described, so I'm closing the bug. 
For information, if I put the arguments back on the command line then the crash situation comes back.

i  think there is a issue as we hit an assert, on mandriva bugzilla this user pasted an interesting  Backtrace :  

Application: Dolphin (dolphin), signal SIGABRT
[Current thread is 1 (Thread 0xb5da28e0 (LWP 8535))]

Thread 1 (Thread 0xb5da28e0 (LWP 8535)):
[KCrash Handler]
#6  0xffffe424 in __kernel_vsyscall ()
#7  0xb6655d90 in raise () from /lib/i686/libc.so.6
#8  0xb66577f8 in abort () from /lib/i686/libc.so.6
#9  0xb68c3445 in qt_message_output (msgType=QtFatalMsg, buf=0xbffd3fd0
"ASSERT: \"listers.isEmpty() || killed\" in file
/home/mandrake/rpm/BUILD/kdelibs-4.1.85/kio/kio/kdirlister.cpp, line 613")
    at global/qglobal.cpp:2102
#10 0xb68c3535 in qFatal (msg=0xb6a16b78 "ASSERT: \"%s\" in file %s, line %d")
at global/qglobal.cpp:2303
#11 0xb68c35e5 in qt_assert (assertion=0xb7f29945 "listers.isEmpty() ||
killed", file=0xb7f29990
"/home/mandrake/rpm/BUILD/kdelibs-4.1.85/kio/kio/kdirlister.cpp", line=613) at
global/qglobal.cpp:1872
#12 0xb7df8cdd in KDirListerCache::updateDirectory (this=0x81f7740,
_dir=@0xbffd6200) at /usr/src/debug/kdelibs-4.1.85/kio/kio/kdirlister.cpp:613
#13 0xb7dfa1f1 in KDirListerCache::slotFileDirty (this=0x81f7740,
path=@0xbffd63b8) at /usr/src/debug/kdelibs-4.1.85/kio/kio/kdirlister.cpp:957
#14 0xb7dfae0b in KDirListerCache::qt_metacall (this=0x81f7740,
_c=QMetaObject::InvokeMetaMethod, _id=4, _a=0xbffd6320) at
/usr/src/debug/kdelibs-4.1.85/build/kio/kdirlister_p.moc:94
#15 0xb69d9c8d in QMetaObject::activate (sender=0x8247230, from_signal_index=4,
to_signal_index=4, argv=0xbffd6320) at kernel/qobject.cpp:3031
#16 0xb69daa95 in QMetaObject::activate (sender=0x8247230, m=0xb7f9f3e4,
local_signal_index=0, argv=0xbffd6320) at kernel/qobject.cpp:3101
#17 0xb7e0ce65 in KDirWatch::dirty (this=0x8247230, _t1=@0xbffd63b8) at
/usr/src/debug/kdelibs-4.1.85/build/kio/kdirwatch.moc:81
#18 0xb7e0d182 in KDirWatch::setDirty (this=0x8247230, _file=@0xbffd63b8) at
/usr/src/debug/kdelibs-4.1.85/kio/kio/kdirwatch.cpp:1662
#19 0xb7e0e694 in KDirWatchPrivate::emitEvent (this=0x81eaa20, e=0x8407d84,
event=1, fileName=@0xbffd6450) at
/usr/src/debug/kdelibs-4.1.85/kio/kio/kdirwatch.cpp:1145
#20 0xb7e11de6 in KDirWatchPrivate::slotRescan (this=0x81eaa20) at
/usr/src/debug/kdelibs-4.1.85/kio/kio/kdirwatch.cpp:1223
#21 0xb7e12fe8 in KDirWatchPrivate::qt_metacall (this=0x81eaa20,
_c=QMetaObject::InvokeMetaMethod, _id=0, _a=0xbffd6518) at
/usr/src/debug/kdelibs-4.1.85/build/kio/kdirwatch_p.moc:72
#22 0xb69d9c8d in QMetaObject::activate (sender=0x81eaa64, from_signal_index=4,
to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3031
#23 0xb69daa95 in QMetaObject::activate (sender=0x81eaa64, m=0xb6aabce4,
local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3101
#24 0xb6a15ef5 in QTimer::timeout (this=0x81eaa64) at
.moc/release-shared/moc_qtimer.cpp:126
#25 0xb69e0946 in QTimer::timerEvent (this=0x81eaa64, e=0xbffd698c) at
kernel/qtimer.cpp:257
#26 0xb69d451b in QObject::event (this=0x81eaa64, e=0xbffd698c) at
kernel/qobject.cpp:1120
#27 0xb6bd4fac in QApplicationPrivate::notify_helper (this=0x8148858,
receiver=0x81eaa64, e=0xbffd698c) at kernel/qapplication.cpp:3803
#28 0xb6bdd1d5 in QApplication::notify (this=0xbffd6c0c, receiver=0x81eaa64,
e=0xbffd698c) at kernel/qapplication.cpp:3393
#29 0xb78359b0 in KApplication::notify (this=0xbffd6c0c, receiver=0x81eaa64,
event=0xbffd698c) at
/usr/src/debug/kdelibs-4.1.85/kdeui/kernel/kapplication.cpp:307
#30 0xb69c4853 in QCoreApplication::notifyInternal (this=0xbffd6c0c,
receiver=0x81eaa64, event=0xbffd698c) at kernel/qcoreapplication.cpp:587
#31 0xb69f3a8d in QTimerInfoList::activateTimers (this=0x813dbbc) at
kernel/qcoreapplication.h:209
#32 0xb69f03ee in timerSourceDispatch (source=0x813db88) at
kernel/qeventdispatcher_glib.cpp:160
#33 0xb60afcba in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#34 0xb60b33d8 in ?? () from /usr/lib/libglib-2.0.so.0
#35 0xb60b3598 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#36 0xb69f034a in QEventDispatcherGlib::processEvents (this=0x813f9d0, flags={i
= -1073911048}) at kernel/qeventdispatcher_glib.cpp:319
#37 0xb6c7192a in QGuiEventDispatcherGlib::processEvents (this=0x813f9d0,
flags={i = -1073911000}) at kernel/qguieventdispatcher_glib.cpp:198
#38 0xb69c2ec3 in QEventLoop::processEvents (this=0xbffd6ba0, flags={i =
-1073910936}) at kernel/qeventloop.cpp:143
#39 0xb69c3081 in QEventLoop::exec (this=0xbffd6ba0, flags={i = -1073910872})
at kernel/qeventloop.cpp:194
#40 0xb69c57f2 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:845
#41 0xb6bd4e14 in QApplication::exec () at kernel/qapplication.cpp:3331
#42 0x08080803 in main (argc=-1073910332, argv=0xbffd6c24) at
/usr/src/debug/kdebase-4.1.85/apps/dolphin/src/main.cpp:94

@Nicolas: that backtrace in comment 5 seems to be the same as the one I posted in bug 178897 (also related to dolphin and shells, but in a different situation)

ah yes   this is exactly the same

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