Bug 209862 - crash occured when wanting to set icon for /home/user
Summary: crash occured when wanting to set icon for /home/user
Status: RESOLVED DUPLICATE of bug 202714
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
Depends on:
Reported: 2009-10-08 13:10 UTC by m.wege
Modified: 2009-10-08 17:42 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Note You need to log in before you can comment on or make changes to this bug.
Description m.wege 2009-10-08 13:10:24 UTC
Application that crashed: dolphin
Version of the application: 1.3
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.30-02063003-generic i686
Distribution: Ubuntu 9.04

What I was doing when the application crashed:
crash occured when I want to set an icon for /home/user, via right click on user, properties, setting the icon and ok. Might be the problem that I did not have the rights for doing that, but stil dolphin should not crash.

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#6  0xb7ece1e8 in KDirModelNode::rowNumber (this=0x0) at /build/buildd/kde4libs-4.3.2/kio/kio/kdirmodel.cpp:120
#7  0xb7ece290 in KDirModelPrivate::indexForNode (this=0x8a1ce00, node=0x0, rowNumber=-1) at /build/buildd/kde4libs-4.3.2/kio/kio/kdirmodel.cpp:284
#8  0xb7ed2d6e in KDirModelPrivate::_k_slotNewItems (this=0x8a1ce00, directoryUrl=@0x8932288, items=@0x8932290) at /build/buildd/kde4libs-4.3.2/kio/kio/kdirmodel.cpp:377
#9  0xb7ed410c in KDirModel::qt_metacall (this=0x8a0ed88, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbf95c608) at /build/buildd/kde4libs-4.3.2/obj-i486-linux-gnu/kio/kdirmodel.moc:82
#10 0xb68331b8 in QMetaObject::activate (sender=0x8a1d2a0, from_signal_index=14, to_signal_index=14, argv=0xbf95c608) at kernel/qobject.cpp:3113
#11 0xb6833e42 in QMetaObject::activate (sender=0x8a1d2a0, m=0x80b6410, local_signal_index=10, argv=0xbf95c608) at kernel/qobject.cpp:3187
#12 0xb7eb6b99 in KDirLister::itemsAdded (this=0x8a1d2a0, _t1=@0x8932288, _t2=@0x8932290) at /build/buildd/kde4libs-4.3.2/obj-i486-linux-gnu/kio/kdirlister.moc:268
#13 0xb7eb7ab6 in KDirLister::Private::emitItems (this=0x8a129e0) at /build/buildd/kde4libs-4.3.2/kio/kio/kdirlister.cpp:2303
#14 0xb7eba604 in KDirListerCache::processPendingUpdates (this=0x89b3570) at /build/buildd/kde4libs-4.3.2/kio/kio/kdirlister.cpp:1796
#15 0xb7ec966d in KDirListerCache::slotFilesChanged (this=0x89b3570, fileList=@0x9190398) at /build/buildd/kde4libs-4.3.2/kio/kio/kdirlister.cpp:850
#16 0xb7eca222 in KDirListerCache::qt_metacall (this=0x89b3570, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbf95c88c) at /build/buildd/kde4libs-4.3.2/obj-i486-linux-gnu/kio/kdirlister_p.moc:93
#17 0xb68331b8 in QMetaObject::activate (sender=0x89b9748, from_signal_index=8, to_signal_index=8, argv=0xbf95c88c) at kernel/qobject.cpp:3113
#18 0xb6833e42 in QMetaObject::activate (sender=0x89b9748, m=0xb8042274, local_signal_index=3, argv=0xbf95c88c) at kernel/qobject.cpp:3187
#19 0xb7ed5cc3 in OrgKdeKDirNotifyInterface::FilesChanged (this=0x89b9748, _t1=@0x9190398) at /build/buildd/kde4libs-4.3.2/obj-i486-linux-gnu/kio/kdirnotify.moc:118
#20 0xb7ed5e8a in OrgKdeKDirNotifyInterface::qt_metacall (this=0x89b9748, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0xbf95ca28)
    at /build/buildd/kde4libs-4.3.2/obj-i486-linux-gnu/kio/kdirnotify.moc:82
#21 0xb72dae5a in QDBusConnectionPrivate::deliverCall (this=0x8854658, object=0x89b9748, msg=@0x8ec4d84, metaTypes=@0x8ec4d88, slotIdx=8) at qdbusintegrator.cpp:891
#22 0xb72e2eb7 in QDBusCallDeliveryEvent::placeMetaCall (this=0x8ec4d58, object=0x89b9748) at qdbusintegrator_p.h:101
#23 0xb682e3b0 in QObject::event (this=0x89b9748, e=0x8ec4d58) at kernel/qobject.cpp:1111
#24 0xb6a34d3c in QApplicationPrivate::notify_helper (this=0x88642b8, receiver=0x89b9748, e=0x8ec4d58) at kernel/qapplication.cpp:4056
#25 0xb6a3d03e in QApplication::notify (this=0xbf95d144, receiver=0x89b9748, e=0x8ec4d58) at kernel/qapplication.cpp:3603
#26 0xb777c49d in KApplication::notify (this=0xbf95d144, receiver=0x89b9748, event=0x8ec4d58) at /build/buildd/kde4libs-4.3.2/kdeui/kernel/kapplication.cpp:302
#27 0xb681dbcb in QCoreApplication::notifyInternal (this=0xbf95d144, receiver=0x89b9748, event=0x8ec4d58) at kernel/qcoreapplication.cpp:610
#28 0xb681e825 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x883db38) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#29 0xb681ea1d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#30 0xb68496af in postEventSourceDispatch (s=0x885db10) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#31 0xb5f7ab88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#32 0xb5f7e0eb in ?? () from /usr/lib/libglib-2.0.so.0
#33 0xb5f7e268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#34 0xb68492f8 in QEventDispatcherGlib::processEvents (this=0x883dd10, flags={i = -1080700888}) at kernel/qeventdispatcher_glib.cpp:327
#35 0xb6ad6a75 in QGuiEventDispatcherGlib::processEvents (this=0x883dd10, flags={i = -1080700840}) at kernel/qguieventdispatcher_glib.cpp:202
#36 0xb681c1fa in QEventLoop::processEvents (this=0xbf95d0d0, flags={i = -1080700776}) at kernel/qeventloop.cpp:149
#37 0xb681c642 in QEventLoop::exec (this=0xbf95d0d0, flags={i = -1080700712}) at kernel/qeventloop.cpp:201
#38 0xb681eae9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#39 0xb6a34bb7 in QApplication::exec () at kernel/qapplication.cpp:3525
#40 0x0807aaef in main (argc=6, argv=0xbf95d2f4) at /build/buildd/kdebase-4.3.2/apps/dolphin/src/main.cpp:94

Reported using DrKonqi
Comment 1 Frank Reininghaus 2009-10-08 14:58:29 UTC
Thanks for the bug report! This crash is known already, but unfortunately, it's difficult to debug because it's not always easy to reproduce.

*** This bug has been marked as a duplicate of bug 202714 ***
Comment 2 m.wege 2009-10-08 15:23:44 UTC
@Frank: I can 100% reproduce this bug on my Kubuntu system. When I do the same thing again, it will crash in the same way.
Comment 3 Frank Reininghaus 2009-10-08 16:10:21 UTC
Thanks for the info! Sometimes, I've also been able to reproduce this very reliably on my Kubuntu system, but one cannot debug this properly in a binary package. What would help more would be a way to reproduce this every time in a trunk build from source, but that never really worked for me (and AFAIK neither for David Faure, who has a much better insight into the relevant code than anyone else).

But thanks for your help anyway! I'll also keep trying to find better ways to reproduce the crash...
Comment 4 m.wege 2009-10-08 16:52:42 UTC
additional information:
- The first time the crash occured plasma crash first. Unfortunately I clicked it away, so there is not debug and this part does not repeat itself.
- The change (changing the folder icon) has actually worked.
-> For me this seems like Dolphin and may be Plasma too crashed when they were informed about the change.
-> If Plasma crashed for the same reason, may be others had that too and there may be crash reports with backtrace for plasma which might help to find the common reason for the crash.
Comment 5 Frank Reininghaus 2009-10-08 17:13:42 UTC
> -> For me this seems like Dolphin and may be Plasma too crashed when they were
> informed about the change.

You're right - it seems that a KDirModel owned by either application is informed about a change of an item that is actually not inside the model, and this leads to the crash.

> -> If Plasma crashed for the same reason, may be others had that too and there
> may be crash reports with backtrace for plasma which might help to find the
> common reason for the crash.

Other users (including myself) have indeed seen this crash in other applications (in my case, Amarok). The backtraces seem to be the same though because the code that gets executed (D-Bus/KDirLister/KDirModel) is exactly the same.
Comment 6 m.wege 2009-10-08 17:28:52 UTC
Ok, that is interesting. I am not programmer, but if the bug is not reproducable with svn, wouldn't it make sense to try to trace it down via some extra debug code in the upcoming 4.3.3, so that crash reports are more useful then?
Comment 7 Frank Reininghaus 2009-10-08 17:42:25 UTC
I can't say much about that because I'm not involved in the development of KDirLister/KDirModel either.

The bug is certainly also in the trunk version from SVN (I've seen it a few times). If the crash occurs or not seems to depend on some outer influences, but it's still unknown how :-(