Bug 203707 - Dolphin crashes in setting display properties in a folder
Summary: Dolphin crashes in setting display properties in a folder
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
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-13 13:52 UTC by Charles-henri de Blesson
Modified: 2009-09-08 12:31 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Charles-henri de Blesson 2009-08-13 13:52:44 UTC
Application that crashed: dolphin
Version of the application: 1.3
KDE Version: 4.3.00 (KDE 4.3.0)
Qt Version: 4.5.2
Operating System: Linux 2.6.30-ARCH i686

What I was doing when the application crashed:
1. In the folder view, right click and select display settings
2. Just switching tabs one by one
3. Click OK, application crashes

Note : It doesn't happen all times, but frequently even with no changes in properties.

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#6  0xb7e2574d in KDirModelNode::rowNumber () from /usr/lib/libkio.so.5
#7  0xb7e25803 in KDirModelPrivate::indexForNode () from /usr/lib/libkio.so.5
#8  0xb7e2a64b in KDirModelPrivate::_k_slotNewItems () from /usr/lib/libkio.so.5
#9  0xb7e2bb57 in KDirModel::qt_metacall () from /usr/lib/libkio.so.5
#10 0xb690f9ac in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#11 0xb69105e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#12 0xb7e0e269 in KDirLister::itemsAdded () from /usr/lib/libkio.so.5
#13 0xb7e0f2fe in KDirLister::Private::emitItems () from /usr/lib/libkio.so.5
#14 0xb7e1a5e7 in KDirListerCache::processPendingUpdates () from /usr/lib/libkio.so.5
#15 0xb7e1aeaf in KDirListerCache::slotFilesChanged () from /usr/lib/libkio.so.5
#16 0xb7e21685 in KDirListerCache::qt_metacall () from /usr/lib/libkio.so.5
#17 0xb690f9ac in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#18 0xb69105e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#19 0xb7e2d2e3 in OrgKdeKDirNotifyInterface::FilesChanged () from /usr/lib/libkio.so.5
#20 0xb7e2d4b5 in OrgKdeKDirNotifyInterface::qt_metacall () from /usr/lib/libkio.so.5
#21 0xb739e6c7 in ?? () from /usr/lib/libQtDBus.so.4
#22 0xb73a5f87 in ?? () from /usr/lib/libQtDBus.so.4
#23 0xb6909d9e in QObject::event () from /usr/lib/libQtCore.so.4
#24 0xb6b0c994 in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#25 0xb6b1407c in QApplication::notify () from /usr/lib/libQtGui.so.4
#26 0xb7803faa in KApplication::notify () from /usr/lib/libkdeui.so.5
#27 0xb68f9fcb in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#28 0xb68fabb2 in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4
#29 0xb68fad7d in QCoreApplication::sendPostedEvents () from /usr/lib/libQtCore.so.4
#30 0xb6924a9f in ?? () from /usr/lib/libQtCore.so.4
#31 0xb5f8ad98 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#32 0xb5f8e3e0 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#33 0xb5f8e513 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#34 0xb69246cc in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#35 0xb6baa6c5 in ?? () from /usr/lib/libQtGui.so.4
#36 0xb68f8579 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#37 0xb68f89ca in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#38 0xb68fae3f in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#39 0xb6b0c817 in QApplication::exec () from /usr/lib/libQtGui.so.4
#40 0x0807a635 in _start ()

This bug may be a duplicate of or related to bug 202181

Reported using DrKonqi
Comment 1 Frank Reininghaus 2009-08-13 23:29:32 UTC
Thanks for the bug report! Looks like it might be related to bug 190535.
Comment 2 FiNeX 2009-09-08 12:02:46 UTC
It looks more like bug #202714 .
Comment 3 Frank Reininghaus 2009-09-08 12:31:52 UTC
(In reply to comment #2)
> It looks more like bug #202714 .

You're right, but I think that these (and a couple more reports) are probably all related. However, I'm not completely sure. David would probably know that, but I'll mark it as a dup of 202714 anyway because that one clearly looks like it's the same crash.

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