Bug 208760 - nautilus crashes displaying properties of /home
Summary: nautilus crashes displaying properties of /home
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-09-28 11:11 UTC by Adam Stover
Modified: 2009-09-29 09:51 UTC (History)
1 user (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 Adam Stover 2009-09-28 11:11:35 UTC
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-ARCH x86_64

What I was doing when the application crashed:
Nautilus crashed while displaying the properties of my /home folder.  This has happened only a few times, and I cannot reproduce it on command.  Previously while open I tried to drag a tab-switching button to the toolbar in the 'configure toolbar' menu.

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#5  0x00007f73baed58b0 in KDirModelNode::rowNumber () from /usr/lib/libkio.so.5
#6  0x00007f73baed5951 in KDirModelPrivate::indexForNode () from /usr/lib/libkio.so.5
#7  0x00007f73baeda2f6 in KDirModelPrivate::_k_slotNewItems () from /usr/lib/libkio.so.5
#8  0x00007f73baedb6d6 in KDirModel::qt_metacall () from /usr/lib/libkio.so.5
#9  0x00007f73b7e576bc in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#10 0x00007f73baebf44a in KDirLister::itemsAdded () from /usr/lib/libkio.so.5
#11 0x00007f73baec01fa in KDirLister::Private::emitItems () from /usr/lib/libkio.so.5
#12 0x00007f73baecac78 in KDirListerCache::processPendingUpdates () from /usr/lib/libkio.so.5
#13 0x00007f73baecb5ee in KDirListerCache::slotFilesChanged () from /usr/lib/libkio.so.5
#14 0x00007f73baed1900 in KDirListerCache::qt_metacall () from /usr/lib/libkio.so.5
#15 0x00007f73b7e576bc in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#16 0x00007f73baedcc75 in OrgKdeKDirNotifyInterface::FilesChanged () from /usr/lib/libkio.so.5
#17 0x00007f73baedcde0 in OrgKdeKDirNotifyInterface::qt_metacall () from /usr/lib/libkio.so.5
#18 0x00007f73b8cf5ee4 in ?? () from /usr/lib/libQtDBus.so.4
#19 0x00007f73b8cfd1ef in ?? () from /usr/lib/libQtDBus.so.4
#20 0x00007f73b7e519d9 in QObject::event () from /usr/lib/libQtCore.so.4
#21 0x00007f73b82c30cc in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4
#22 0x00007f73b82ca39e in QApplication::notify () from /usr/lib/libQtGui.so.4
#23 0x00007f73b95ef8d6 in KApplication::notify () from /usr/lib/libkdeui.so.5
#24 0x00007f73b7e425bc in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4
#25 0x00007f73b7e4319a in QCoreApplicationPrivate::sendPostedEvents () from /usr/lib/libQtCore.so.4
#26 0x00007f73b7e6ae13 in ?? () from /usr/lib/libQtCore.so.4
#27 0x00007f73b3b7cdbe in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#28 0x00007f73b3b80568 in g_main_context_iterate () from /usr/lib/libglib-2.0.so.0
#29 0x00007f73b3b80690 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#30 0x00007f73b7e6aa86 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#31 0x00007f73b835607e in ?? () from /usr/lib/libQtGui.so.4
#32 0x00007f73b7e40ec2 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#33 0x00007f73b7e41294 in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#34 0x00007f73b7e43449 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#35 0x0000000000439515 in _start ()

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

Reported using DrKonqi
Comment 1 Frank Reininghaus 2009-09-29 09:51:52 UTC
Thanks for the bug report! This crash (which is really not always easy to reproduce and therefore, unfortunately, difficult to debug) has been reported already.

BTW, KDE's file manager is called 'Dolphin' ;-)

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