Bug 190535

Thanks Ken. Being you using a compiled from source version. You could re-compile dolphin enabling debug messages in order to provide a more useful backtrace.

I reproduced this in 4.2.2 (Kubuntu 9.04) by right-clicking in my home dir (in the white area, not on a file), clicking "Properties", modifying the permissions and clicking OK. Not 100% reproducible, maybe it depends on files getting changed or added while the Properties dialog is open.

Probably a duplicate of bug 181536 (and quite a few more which can be found by searching crashes with "OrgKdeKDirNotifyInterface" in a comment).

Application: Dolphin (dolphin), signal SIGSEGV

Thread 1 (Thread 0xb5c12700 (LWP 6679)):
[KCrash Handler]
#6  0xb7dcf848 in KDirModelNode::rowNumber (this=0x0) at /build/buildd/kde4libs-4.2.2/kio/kio/kdirmodel.cpp:115
#7  0xb7dcf8f0 in KDirModelPrivate::indexForNode (this=0xa1d3ef8, node=0x0, rowNumber=-1) at /build/buildd/kde4libs-4.2.2/kio/kio/kdirmodel.cpp:279
#8  0xb7dd422e in KDirModelPrivate::_k_slotNewItems (this=0xa1d3ef8, directoryUrl=@0xa40e968, items=@0xa40e970) at /build/buildd/kde4libs-4.2.2/kio/kio/kdirmodel.cpp:372
#9  0xb7dd55cc in KDirModel::qt_metacall (this=0xa1de918, _c=QMetaObject::InvokeMetaMethod, _id=1, _a=0xbfe836b8) at /build/buildd/kde4libs-4.2.2/obj-i486-linux-gnu/kio/kdirmodel.moc:78
#10 0xb6730ca8 in QMetaObject::activate (sender=0xa1de800, from_signal_index=14, to_signal_index=14, argv=0xbfe836b8) at kernel/qobject.cpp:3069
#11 0xb6731932 in QMetaObject::activate (sender=0xa1de800, m=0x80a92b0, local_signal_index=10, argv=0xbfe836b8) at kernel/qobject.cpp:3143
#12 0xb7db8ae9 in KDirLister::itemsAdded (this=0xa1de800, _t1=@0xa40e968, _t2=@0xa40e970) at /build/buildd/kde4libs-4.2.2/obj-i486-linux-gnu/kio/kdirlister.moc:268
#13 0xb7db9ce6 in KDirLister::Private::emitItems (this=0xa1de858) at /build/buildd/kde4libs-4.2.2/kio/kio/kdirlister.cpp:2274
#14 0xb7dbbcbf in KDirListerCache::emitRefreshItem (this=0xa020ee8, oldItem=@0xbfe83814, fileitem=@0xa087454) at /build/buildd/kde4libs-4.2.2/kio/kio/kdirlister.cpp:960
#15 0xb7dca0a5 in KDirListerCache::slotFilesChanged (this=0xa020ee8, fileList=@0xab49fe8) at /build/buildd/kde4libs-4.2.2/kio/kio/kdirlister.cpp:834
#16 0xb7dcacc2 in KDirListerCache::qt_metacall (this=0xa020ee8, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfe8392c) at /build/buildd/kde4libs-4.2.2/obj-i486-linux-gnu/kio/kdirlister_p.moc:93
#17 0xb6730ca8 in QMetaObject::activate (sender=0x9f3a898, from_signal_index=8, to_signal_index=8, argv=0xbfe8392c) at kernel/qobject.cpp:3069
#18 0xb6731932 in QMetaObject::activate (sender=0x9f3a898, m=0xb7f442d4, local_signal_index=3, argv=0xbfe8392c) at kernel/qobject.cpp:3143
#19 0xb7dd7073 in OrgKdeKDirNotifyInterface::FilesChanged (this=0x9f3a898, _t1=@0xab49fe8) at /build/buildd/kde4libs-4.2.2/obj-i486-linux-gnu/kio/kdirnotify.moc:118
#20 0xb7dd723a in OrgKdeKDirNotifyInterface::qt_metacall (this=0x9f3a898, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0xbfe83ac8)
    at /build/buildd/kde4libs-4.2.2/obj-i486-linux-gnu/kio/kdirnotify.moc:82
#21 0xb7223d7a in QDBusConnectionPrivate::deliverCall (this=0x9e5c520, object=0x9f3a898, msg=@0xa499224, metaTypes=@0xa499228, slotIdx=8) at qdbusintegrator.cpp:891
#22 0xb722c187 in QDBusCallDeliveryEvent::placeMetaCall (this=0xa4991f8, object=0x9f3a898) at qdbusintegrator_p.h:101
#23 0xb672b3a0 in QObject::event (this=0x9f3a898, e=0xa4991f8) at kernel/qobject.cpp:1118
#24 0xb6952f2c in QApplicationPrivate::notify_helper (this=0x9e645e8, receiver=0x9f3a898, e=0xa4991f8) at kernel/qapplication.cpp:4084
#25 0xb695b22e in QApplication::notify (this=0xbfe841e4, receiver=0x9f3a898, e=0xa4991f8) at kernel/qapplication.cpp:3631
#26 0xb76af94d in KApplication::notify (this=0xbfe841e4, receiver=0x9f3a898, event=0xa4991f8) at /build/buildd/kde4libs-4.2.2/kdeui/kernel/kapplication.cpp:307
#27 0xb671aa3b in QCoreApplication::notifyInternal (this=0xbfe841e4, receiver=0x9f3a898, event=0xa4991f8) at kernel/qcoreapplication.cpp:602
#28 0xb671b695 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x9e45b38) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#29 0xb671b88d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1132
#30 0xb67467ef in postEventSourceDispatch (s=0x9e72cd0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#31 0xb5e98b88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#32 0xb5e9c0eb in ?? () from /usr/lib/libglib-2.0.so.0
#33 0xb5e9c268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#34 0xb6746438 in QEventDispatcherGlib::processEvents (this=0x9e498a0, flags={i = -1075298104}) at kernel/qeventdispatcher_glib.cpp:323
#35 0xb69f43f5 in QGuiEventDispatcherGlib::processEvents (this=0x9e498a0, flags={i = -1075298056}) at kernel/qguieventdispatcher_glib.cpp:202
#36 0xb671906a in QEventLoop::processEvents (this=0xbfe84170, flags={i = -1075297992}) at kernel/qeventloop.cpp:149
#37 0xb67194aa in QEventLoop::exec (this=0xbfe84170, flags={i = -1075297928}) at kernel/qeventloop.cpp:200
#38 0xb671b959 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880
#39 0xb6952da7 in QApplication::exec () at kernel/qapplication.cpp:3553
#40 0x080856ef in main (argc=5, argv=0xbfe84394) at /build/buildd/kdebase-4.2.2/apps/dolphin/src/main.cpp:94

@Frank: could bug 192770 also be related to this? (it seems to be non-reproducible on a updated trunk build) Thanks

(In reply to comment #3)
> @Frank: could bug 192770 also be related to this?

It seems so, but right now I can't reproduce any of these issues in trunk. They never seemed 100% reproducible for me though, so I don't know if this is really fixed or if I'm just unlucky today ;-)

I also got this: bug 193818

Bug 192594 seems to be also related (save dialog on fish using KMail)

*** Bug 200411 has been marked as a duplicate of this bug. ***

*** Bug 200526 has been marked as a duplicate of this bug. ***

To everyone who can still reproduce this crash (I couldn't reproduce it today): there might be some output before the crash which starts with "Items emitted in directory". If you're not running the crashing application from Konsole, this output is in ~/.xsession-errors. It might help if you could paste this output here. Thanks!

[I think bug 181536, where I've once hit the Q_ASSERT(result) in KDirModelPrivate::_k_slotNewItems(), is a duplicate. Probably the segfault occurs if asserts are disabled, but the error output should be there anyway.]

*** Bug 202181 has been marked as a duplicate of this bug. ***

*** Bug 192594 has been marked as a duplicate of this bug. ***

*** Bug 202164 has been marked as a duplicate of this bug. ***

*** Bug 199556 has been marked as a duplicate of this bug. ***

*** Bug 198320 has been marked as a duplicate of this bug. ***

*** Bug 207408 has been marked as a duplicate of this bug. ***

*** Bug 207992 has been marked as a duplicate of this bug. ***

SVN commit 1029200 by dfaure:

Don't assert if dataChanged(root, root) is emitted, e.g. when changing permissions for the current dir.
CCBUG: 190535
CCMAIL: Peter Penz <peter.penz@gmx.at>


 M  +4 -0      kfilepreviewgenerator.cpp  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1029200

My fix gets rid of the assert (or crash like in bug 193466) in KFilePreviewGenerator, but that seems unrelated to all the backtraces here mentionning _k_slotNewItems / indexForNode. I still need to find a way to reproduce that crash.

*** Bug 181536 has been marked as a duplicate of this bug. ***

*** Bug 204952 has been marked as a duplicate of this bug. ***

*** Bug 209228 has been marked as a duplicate of this bug. ***

Dario Andres wrote:
> https://bugs.kde.org/show_bug.cgi?id=190535
>
> --- Comment #21 from Dario Andres <andresbajotierra gmail com>  2009-10-03 19:52:04 ---
> - Does Dolphin crash every time you repeat the situation ?
>
> **
>   
Sorry, Sir, I've been unable to replicate the crash. There were four
similar segfaults prior to my bug report, according to the crash logs I
found. I switched to Thunar for the rest of the day. However, Fedora did
release a glibc update (glibc-2.10.1-5) the following day (2009-10-03). 
The message log is peppered with gvfs-gdu-volume segfaults in libgdu.so
with no visible effects. Don't know why I get Gnome stuff in KDE, but
that's Fedora.

These might be relevant...
http://www.kerneloops.org/submitresult.php?number=771593
http://www.kerneloops.org/submitresult.php?number=771760

I wouldn't consider this a high priority. This instance of Fedora 11 was
upgraded from 8, 9, and 10 all using yum. It's scheduled for conversion
from reiserfs to ext4 with a clean install as soon as I can find enough
room to back up my project files.

Thanks for the reply. You have obviously done your best.
regards,
Ken
(who wrote an operating system in 1966)

Application that crashed: dolphin
Version of the application: 1.3
KDE Version: 4.3.1 (KDE 4.3.1)
Qt Version: 4.5.2
Operating System: Linux 2.6.30.8-64.fc11.x86_64 x86_64
Distribution: "Fedora release 11 (Leonidas)"

What I was doing when the application crashed:
<In detail, tell us what you were doing  when the application crashed.>

Simply changed directory from one to another. Caught me by surprise.
[The previous 'thread' comment was from Drkonqi starting up.]
(All I did in 1966 was write a fortran program to solve the Pythagoren Theorem for positive roots on a roll of paper tape.)

 -- Backtrace:
Application: Dolphin (dolphin), signal: Aborted
[KCrash Handler]
#5  0x0000003a6d8332f5 in *__GI_raise (sig=<value optimized out>) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
#6  0x0000003a6d834b20 in *__GI_abort () at abort.c:88
#7  0x0000003a70cc35f5 in __gnu_cxx::__verbose_terminate_handler () at ../../../../libstdc++-v3/libsupc++/vterminate.cc:93
#8  0x0000003a70cc1a36 in __cxxabiv1::__terminate (handler=0xc21) at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:38
#9  0x0000003a70cc1a63 in std::terminate () at ../../../../libstdc++-v3/libsupc++/eh_terminate.cc:48
#10 0x0000003a70cc1ae6 in __cxxabiv1::__cxa_rethrow () at ../../../../libstdc++-v3/libsupc++/eh_throw.cc:116
#11 0x0000003a7853e3f5 in QEventLoop::exec (this=<value optimized out>, flags=<value optimized out>) at kernel/qeventloop.cpp:214
#12 0x0000003a78540439 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#13 0x0000000000437085 in _start ()
Warning: the current language does not match this frame.

Report to https://bugs.kde.org

I'm fishing for dolphin in gdb. My first guess is that my Fedora
installation is not quite right. Although dolphin is running, it started
with the following errors in the same thread:
org.freedesktop.DBus.Error.ServiceUnknown - The name
org.kde.nepomuk.services.nepomukstorage was not provided by any .service
files
  QLocalSocket::connectToServer: Invalid name

Program exited normally. -- Yet dolphin is running. It suggests
debug-install about a dozen programs, including gamin. Gamin is not in
the process tree, nor is nepomuk, which may be the source of these
recent crashes.  Perhaps you might want to close this instance of the
bug due to a corrupt Fedora 11 setup that omitted things that dolphin
occasionally requires and assumes should be already installed. IBK

(In reply to comment #25)
> I'm fishing for dolphin in gdb.

When debugging Dolphin with gdb, it may help to close all Dolphin windows first and then start gdb with

gdb --args dolphin --nofork

Without the --nofork argument, a new process is forked off the one you're seeing in gdb, or another window is opened within an already existing process because Dolphin is a KUniqueApplication.

*** Bug 205852 has been marked as a duplicate of this bug. ***

*** Bug 209142 has been marked as a duplicate of this bug. ***

*** Bug 210251 has been marked as a duplicate of this bug. ***

*** Bug 202714 has been marked as a duplicate of this bug. ***

I have reproced the plasma crash which happened on the same occasion, described in https://bugs.kde.org/show_bug.cgi?id=209862
What I also noticed that after I had changed the icon of /home/user in Dolphin the icon does not get updated in the view. Instead of this "user" (the directory name) gets replaced by a "." That in fact everything went as expected can only be seen after the restart of Dolphin.

Application: Plasma Workspace (kdeinit4), signal: Segmentation fault
[Current thread is 0 (LWP 3209)]

Thread 2 (Thread 0xa7e47b90 (LWP 3211)):
#0  0xb809f430 in __kernel_vsyscall ()
#1  0xb65930e5 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0
#2  0xb67732ed in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0xb7e99172 in QWaitCondition::wait (this=0x8c67680, mutex=0x8c6767c, time=4294967295) at thread/qwaitcondition_unix.cpp:87
#4  0xb77d5ac2 in QHostInfoAgent::run (this=0x8c67670) at kernel/qhostinfo.cpp:260
#5  0xb7e98132 in QThreadPrivate::start (arg=0x8c67670) at thread/qthread_unix.cpp:188
#6  0xb658f4ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#7  0xb676449e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb609ca20 (LWP 3209)):
[KCrash Handler]
#6  0xb79691e8 in KDirModelNode::rowNumber (this=0x0) at /build/buildd/kde4libs-4.3.2/kio/kio/kdirmodel.cpp:120
#7  0xb7969290 in KDirModelPrivate::indexForNode (this=0x8816b78, node=0x0, rowNumber=-1) at /build/buildd/kde4libs-4.3.2/kio/kio/kdirmodel.cpp:284
#8  0xb796dd6e in KDirModelPrivate::_k_slotNewItems (this=0x8816b78, directoryUrl=@0x9037e08, items=@0x9037e10) at /build/buildd/kde4libs-4.3.2/kio/kio/kdirmodel.cpp:377
#9  0xb796f10c in KDirModel::qt_metacall (this=0x87d9b68, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfef93c8) at /build/buildd/kde4libs-4.3.2/obj-i486-linux-gnu/kio/kdirmodel.moc:82
#10 0xb7fa21b8 in QMetaObject::activate (sender=0x8defe90, from_signal_index=14, to_signal_index=14, argv=0xbfef93c8) at kernel/qobject.cpp:3113
#11 0xb7fa2e42 in QMetaObject::activate (sender=0x8defe90, m=0xb7add01c, local_signal_index=10, argv=0xbfef93c8) at kernel/qobject.cpp:3187
#12 0xb7951b99 in KDirLister::itemsAdded (this=0x8defe90, _t1=@0x9037e08, _t2=@0x9037e10) at /build/buildd/kde4libs-4.3.2/obj-i486-linux-gnu/kio/kdirlister.moc:268
#13 0xb7952ab6 in KDirLister::Private::emitItems (this=0x8de4508) at /build/buildd/kde4libs-4.3.2/kio/kio/kdirlister.cpp:2303
#14 0xb7955604 in KDirListerCache::processPendingUpdates (this=0x880b330) at /build/buildd/kde4libs-4.3.2/kio/kio/kdirlister.cpp:1796
#15 0xb796466d in KDirListerCache::slotFilesChanged (this=0x880b330, fileList=@0x902b960) at /build/buildd/kde4libs-4.3.2/kio/kio/kdirlister.cpp:850
#16 0xb7965222 in KDirListerCache::qt_metacall (this=0x880b330, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbfef964c) at /build/buildd/kde4libs-4.3.2/obj-i486-linux-gnu/kio/kdirlister_p.moc:93
#17 0xb7fa21b8 in QMetaObject::activate (sender=0x880b398, from_signal_index=8, to_signal_index=8, argv=0xbfef964c) at kernel/qobject.cpp:3113
#18 0xb7fa2e42 in QMetaObject::activate (sender=0x880b398, m=0xb7add274, local_signal_index=3, argv=0xbfef964c) at kernel/qobject.cpp:3187
#19 0xb7970cc3 in OrgKdeKDirNotifyInterface::FilesChanged (this=0x880b398, _t1=@0x902b960) at /build/buildd/kde4libs-4.3.2/obj-i486-linux-gnu/kio/kdirnotify.moc:118
#20 0xb7970e8a in OrgKdeKDirNotifyInterface::qt_metacall (this=0x880b398, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0xbfef97e8)
    at /build/buildd/kde4libs-4.3.2/obj-i486-linux-gnu/kio/kdirnotify.moc:82
#21 0xb7342e5a in QDBusConnectionPrivate::deliverCall (this=0x84da320, object=0x880b398, msg=@0x95db394, metaTypes=@0x95db398, slotIdx=8) at qdbusintegrator.cpp:891
#22 0xb734aeb7 in QDBusCallDeliveryEvent::placeMetaCall (this=0x95db368, object=0x880b398) at qdbusintegrator_p.h:101
#23 0xb7f9d3b0 in QObject::event (this=0x880b398, e=0x95db368) at kernel/qobject.cpp:1111
#24 0xb6a48d3c in QApplicationPrivate::notify_helper (this=0x84df260, receiver=0x880b398, e=0x95db368) at kernel/qapplication.cpp:4056
#25 0xb6a5103e in QApplication::notify (this=0x84d96f8, receiver=0x880b398, e=0x95db368) at kernel/qapplication.cpp:3603
#26 0xb755949d in KApplication::notify (this=0x84d96f8, receiver=0x880b398, event=0x95db368) at /build/buildd/kde4libs-4.3.2/kdeui/kernel/kapplication.cpp:302
#27 0xb7f8cbcb in QCoreApplication::notifyInternal (this=0x84d96f8, receiver=0x880b398, event=0x95db368) at kernel/qcoreapplication.cpp:610
#28 0xb7f8d825 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8473b38) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#29 0xb7f8da1d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#30 0xb7fb86af in postEventSourceDispatch (s=0x84e1310) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#31 0xb65dcb88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#32 0xb65e00eb in ?? () from /usr/lib/libglib-2.0.so.0
#33 0xb65e0268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#34 0xb7fb82f8 in QEventDispatcherGlib::processEvents (this=0x84ded30, flags={i = -1074815512}) at kernel/qeventdispatcher_glib.cpp:327
#35 0xb6aeaa75 in QGuiEventDispatcherGlib::processEvents (this=0x84ded30, flags={i = -1074815464}) at kernel/qguieventdispatcher_glib.cpp:202
#36 0xb7f8b1fa in QEventLoop::processEvents (this=0xbfef9e90, flags={i = -1074815400}) at kernel/qeventloop.cpp:149
#37 0xb7f8b642 in QEventLoop::exec (this=0xbfef9e90, flags={i = -1074815336}) at kernel/qeventloop.cpp:201
#38 0xb7f8dae9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#39 0xb6a48bb7 in QApplication::exec () at kernel/qapplication.cpp:3525
#40 0xb4bee2f0 in kdemain (argc=1, argv=0x8475cb8) at /build/buildd/kdebase-workspace-4.3.2/plasma/shells/desktop/main.cpp:50
#41 0x0804e27d in launch (argc=1, _name=0x84916c4 "/usr/bin/plasma-desktop", args=0x84916dc "", cwd=0x0, envc=0, envs=0x84916e0 "", reset_env=false, tty=0x0, avoid_loops=false, 
    startup_id_str=0x805136d "0") at /build/buildd/kde4libs-4.3.2/kinit/kinit.cpp:677
#42 0x0804ea5d in handle_launcher_request (sock=7, who=<value optimized out>) at /build/buildd/kde4libs-4.3.2/kinit/kinit.cpp:1169
#43 0x0804efe5 in handle_requests (waitForPid=0) at /build/buildd/kde4libs-4.3.2/kinit/kinit.cpp:1362
#44 0x0804fbca in main (argc=2, argv=0xbfefa684, envp=0xbfefa690) at /build/buildd/kde4libs-4.3.2/kinit/kinit.cpp:1793

*** Bug 210523 has been marked as a duplicate of this bug. ***

*** Bug 210533 has been marked as a duplicate of this bug. ***

*** Bug 210538 has been marked as a duplicate of this bug. ***

I'm going away now. Analysis of the message log documents the gradual
degradation of my entire system caused by failed upgrade attempts. The
libdbus segfaults in hal-acl and the gvfs-gdu-volume libgdu segfaults
produced nothing noticeable in KDE at the time. (What if gnome wasn't
installed? Why does KDE invoke those gnome apps?) I had given up
upgrading Fedora fc11 to rawhide because of yum's dependency hell. I
thought perhaps that the most recent version of gcc and its associated
libraries and utilities would fix some libc problems which presented
themselves. I used that partial compiler upgrade to build a 2.6.30.3
kernel, since the Fedora developers were probably frantically preparing
for next month's fc12 rollout ... and thereby hangs a tale. I noticed
the libselinux problems when I set selinux from disabled to permissive,
then couldn't log in. I eventually booted into my 64-bit Slackware
partition, downloaded a few packages and manually installed them in
order to get login, yum, and rpm to work via chroot, then booted the
partially-repaired fc11 and fixed the rest of the problems by forcing
rpm to delete the fc12 packages and installing their fc11 versions via
yum (including rebuilding the kernel with the repaired tool chain). Much
ado over nothing. You wouldn't have been involved if it weren't for the
automatic bug reports. This verbose babbling might help someone else
with similar issues. Lesson? Keep your entire compiler toolchain and
library dependencies in a consistent state, don't do partial package
upgrades. Gcc, g++ and all which that entails has a bizarre and deep
dependency forest. For example, glibc itself has over 3500 dependencies.
It helps to have the same version used to compile each of them.

Thanks to the entire KDE team for their tireless efforts in maintaining
programming excellence throughout such a well-designed, complex user
environment. I've been using it since the late-nineties.

Colonel Panic, Probationary Kandalf Apprentice #22060.

*** Bug 211520 has been marked as a duplicate of this bug. ***

*** Bug 211780 has been marked as a duplicate of this bug. ***

*** Bug 211827 has been marked as a duplicate of this bug. ***

*** Bug 212655 has been marked as a duplicate of this bug. ***

*** Bug 212697 has been marked as a duplicate of this bug. ***

*** Bug 212773 has been marked as a duplicate of this bug. ***

*** Bug 213030 has been marked as a duplicate of this bug. ***

*** Bug 213310 has been marked as a duplicate of this bug. ***

From bug 213952:
---
What I was doing when the application crashed:
1. I got the warning that disk space is low
2. I move a big file (~4.7G) from /home/$USER to another partation
3. df still says low space
4. I ringht click on my home foler and counter and calculate its size 
5. when finished, I cliked OK
6. dolphin crashed.

*** Bug 213952 has been marked as a duplicate of this bug. ***

*** Bug 214164 has been marked as a duplicate of this bug. ***

*** Bug 214625 has been marked as a duplicate of this bug. ***

*** Bug 214626 has been marked as a duplicate of this bug. ***

*** Bug 214938 has been marked as a duplicate of this bug. ***

*** Bug 215319 has been marked as a duplicate of this bug. ***

*** Bug 215479 has been marked as a duplicate of this bug. ***

*** Bug 215442 has been marked as a duplicate of this bug. ***

*** Bug 215433 has been marked as a duplicate of this bug. ***

*** Bug 215555 has been marked as a duplicate of this bug. ***

*** Bug 215689 has been marked as a duplicate of this bug. ***

*** Bug 216032 has been marked as a duplicate of this bug. ***

*** Bug 216228 has been marked as a duplicate of this bug. ***

*** Bug 216229 has been marked as a duplicate of this bug. ***

*** Bug 216189 has been marked as a duplicate of this bug. ***

*** Bug 216340 has been marked as a duplicate of this bug. ***

*** Bug 216360 has been marked as a duplicate of this bug. ***

*** Bug 216644 has been marked as a duplicate of this bug. ***

*** Bug 216612 has been marked as a duplicate of this bug. ***

*** Bug 216565 has been marked as a duplicate of this bug. ***

*** Bug 216705 has been marked as a duplicate of this bug. ***

*** Bug 217518 has been marked as a duplicate of this bug. ***

@David: This crash occurs mainly in two situations:

1. Open the Properties dialog, change something (icon, permissions), close it.
2. Click in action in Konqueror's context menu (like open a terminal in the current folder, run some kdesvn actions). There are no crashes for actions run from Dolphin's context menu AFAIK. Don't know if that helps...

I can reproduce the crash quite reliably using the following steps:

a. Open Dolphin, create a folder, enter the new folder
b. When inside the folder, open its Properties dialog (e.g., by pressing Alt+Return)
c. Change the icon of the folder and close the dialog.
d. If it hasn't crashed yet, go back to step b.

It usually crashes after 2 or 3 iterations.

@Frank: Wow, you got steps to reproduce this little monster
I can reproduce the crash using your second set of steps here:

Qt: 4.6.0 (kde-qt master commit cd8595efe9aace2afdaa5db37af7cfe82b87e4aa
        Date:   Wed Nov 18 01:33:21 2009 +0100)
KDE Development Platform: 4.3.80 (KDE 4.3.80 (KDE 4.4 Beta1))
kdelibs svn rev. 1058633 / kdebase svn rev. 1058634
on ArchLinux i686 - Kernel 2.6.31.6

Shell output (may be useful):

dolphin(8601)/kio (KDirListerCache) KDirListerCache::processPendingUpdates: "file:///home/kde-devel/a/New%20Folder"
dolphin(8601)/kio (KDirModel): Items emitted in directory KUrl("file:///home/kde-devel/a") but that directory isn't in KDirModel! Root directory: KUrl("file:///home/kde-devel/a/New Folder")
KCrash: Application 'dolphin' crashing...

*** Bug 217645 has been marked as a duplicate of this bug. ***

Created attachment 38910 [details]
Return early on error in the KDirModelPrivate::_k_slotNewItems()

*** Bug 217924 has been marked as a duplicate of this bug. ***

*** Bug 216121 has been marked as a duplicate of this bug. ***

*** Bug 217783 has been marked as a duplicate of this bug. ***

Reproduced, thanks for the precise steps; one needs to change the icon twice indeed, and for the current directory.

The first icon change works but sets refreshItemWasFiltered to true in KDirLister (due to the .directory file being hidden).

And then the second icon change misbehaves because of multiple bugs; wrong directory url emitted (fixed here), in addition refreshItemWasFiltered is still true (aboutToRefreshItem not called) which makes it "add" the item under itself. Fun.
I see, KDirListerCache::aboutToRefreshItem assumes it should go up but this is not true for root items. I think the right fix is to get rid of aboutToRefreshItem altogether, now that we have oldItem+newItem.
Added to my TODO list - no more time today.

Another note to myself: debugging is easier in konqueror otherwise in dolphin there are two kdirlisters involved.

*** Bug 218311 has been marked as a duplicate of this bug. ***

SVN commit 1061513 by dfaure:

Fix crash when changing the icon of the current directory twice.
(for more details about what happened, see bug 190535 comment #74).
The fix was to replace the fragile aboutToRefreshItem stuff with a simple
local var based on the more recently added "oldItem".
The crash is fixed for: 4.4 beta2
CCBUG: 190535

One bug remains though: the dir becomes "." in the dolphin treeview.


 M  +8 -32     kio/kdirlister.cpp  
 M  +0 -5      kio/kdirlister_p.h  
 M  +85 -27    tests/kdirlistertest.cpp  
 M  +3 -0      tests/kdirlistertest.h  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1061513

SVN commit 1061529 by dfaure:

Fix the subdir being renamed to "." in the dolphin treeview when changing its icon.
 We have to let findByUrl do like slotEntries, and prefer a subdir item with a name
 over a root item with ".". The name doesn't matter for root items, but it matters
 for child items.
Fixed for: 4.4-beta2
BUG: 190535


 M  +19 -12    kio/kdirlister.cpp  
 M  +39 -9     tests/kdirlistertest.cpp  
 M  +3 -1      tests/kdirlistertest.h  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1061529

*** Bug 218379 has been marked as a duplicate of this bug. ***

*** Bug 218454 has been marked as a duplicate of this bug. ***

*** Bug 218550 has been marked as a duplicate of this bug. ***

*** Bug 218704 has been marked as a duplicate of this bug. ***

*** Bug 215920 has been marked as a duplicate of this bug. ***

*** Bug 220607 has been marked as a duplicate of this bug. ***

*** Bug 220162 has been marked as a duplicate of this bug. ***

Still happens in beta 2, see bug 220162.

I wonder if those crashes were the same backtrace but different steps to reproduce can be fixed with the same commit.. may be there are still special cases that cause the crash...

*** Bug 220950 has been marked as a duplicate of this bug. ***

*** Bug 221955 has been marked as a duplicate of this bug. ***

*** Bug 222021 has been marked as a duplicate of this bug. ***

*** Bug 222068 has been marked as a duplicate of this bug. ***

(In reply to comment #90)
> *** Bug 222068 has been marked as a duplicate of this bug. ***

What I was doing when the application crashed:
This crash happens in any KDE application with an open file dialog. For example
Okular: I click  File -> Open -> Network -> Network Services -> FTP Servers
(url bar shows zeroconf: > _ftp._tcp) -> click on a server named TSW-1(FTP) ->
it shortly shows in url bar: "ftp | tsw-1.local:21" then "ftp | tsw-1.local"
and then crashes immediately.

This looks like a new way to trigger this same bug ?

*** Bug 222374 has been marked as a duplicate of this bug. ***

*** Bug 222360 has been marked as a duplicate of this bug. ***

SVN commit 1078174 by dfaure:

Backporting all remaining fixes from 4.4 to 4.3 branch; (in fact ended up copying the files
after backporting all and checking up the remaining diff).

This backports the fixes for the bugs below to the upcoming 4.3.5 release.
Svn revisions backported: 1061529, 1062515, 1065297, 1065291, 1071530, 1061513
Fixed for: 4.3.5
CCBUG: 190535 219547


 M  +101 -89   kio/kdirlister.cpp  
 M  +16 -15    kio/kdirlister_p.h  
 M  +320 -302  tests/kdirlistertest.cpp  
 M  +60 -2     tests/kdirlistertest.h  


WebSVN link: http://websvn.kde.org/?view=rev&revision=1078174

*** Bug 224496 has been marked as a duplicate of this bug. ***

*** Bug 224903 has been marked as a duplicate of this bug. ***

*** Bug 225226 has been marked as a duplicate of this bug. ***

*** Bug 225884 has been marked as a duplicate of this bug. ***

*** Bug 226589 has been marked as a duplicate of this bug. ***

*** Bug 227145 has been marked as a duplicate of this bug. ***

*** Bug 227700 has been marked as a duplicate of this bug. ***

*** Bug 227874 has been marked as a duplicate of this bug. ***

*** Bug 224725 has been marked as a duplicate of this bug. ***

*** Bug 230273 has been marked as a duplicate of this bug. ***

*** Bug 230561 has been marked as a duplicate of this bug. ***

*** Bug 230698 has been marked as a duplicate of this bug. ***

*** Bug 232553 has been marked as a duplicate of this bug. ***

*** Bug 235811 has been marked as a duplicate of this bug. ***

*** Bug 237036 has been marked as a duplicate of this bug. ***

*** Bug 240941 has been marked as a duplicate of this bug. ***

*** Bug 245165 has been marked as a duplicate of this bug. ***

is this bug still valid under kde 4.4 or 4.5  ?

Yes

*** Bug 199902 has been marked as a duplicate of this bug. ***

*** Bug 250874 has been marked as a duplicate of this bug. ***

*** Bug 262425 has been marked as a duplicate of this bug. ***

*** Bug 275295 has been marked as a duplicate of this bug. ***

*** Bug 275102 has been marked as a duplicate of this bug. ***

*** Bug 285415 has been marked as a duplicate of this bug. ***

*** Bug 295702 has been marked as a duplicate of this bug. ***

Bug #295702 reports this in KDE 4.8.0.

Can someone here please confirm if this bug is still valid for KDE 4.10 or higher?

This backtrace appeared again in bug #390288 in KDE Frameworks 5.43.

Dear Bug Submitter,

This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days, the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information.

For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging

If you have already provided the requested information, please set the bug status as REPORTED so that the KDE team knows that the bug is ready to be confirmed.

Thank you for helping us make KDE software even better for everyone!