Bug 223650 - crash after closing the properties pop-up for a folder
Summary: crash after closing the properties pop-up for a folder
Status: RESOLVED WAITINGFORINFO
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: 2010-01-21 10:03 UTC by paolog
Modified: 2018-03-14 11:52 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description paolog 2010-01-21 10:03:14 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.31-17-generic-pae i686
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
the folder contained > 3 GB data and > 20 k files
on closing the properties pop-up after it had reported the size

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#6  0xb76fc98d in ?? () from /usr/lib/libkio.so.5
#7  0xb76fca43 in ?? () from /usr/lib/libkio.so.5
#8  0xb770186b in ?? () from /usr/lib/libkio.so.5
#9  0xb7702d77 in KDirModel::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5
#10 0xb61df263 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4
#11 0xb61dfec2 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#12 0xb76e5469 in KDirLister::itemsAdded(KUrl const&, KFileItemList const&) () from /usr/lib/libkio.so.5
#13 0xb76e64fe in KDirLister::Private::emitItems() () from /usr/lib/libkio.so.5
#14 0xb76f17e7 in ?? () from /usr/lib/libkio.so.5
#15 0xb76f20af in ?? () from /usr/lib/libkio.so.5
#16 0xb76f88a5 in ?? () from /usr/lib/libkio.so.5
#17 0xb61df263 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4
#18 0xb61dfec2 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4
#19 0xb7704503 in OrgKdeKDirNotifyInterface::FilesChanged(QStringList const&) () from /usr/lib/libkio.so.5
#20 0xb77046d5 in OrgKdeKDirNotifyInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libkio.so.5
#21 0xb6c7d7b4 in ?? () from /usr/lib/libQtDBus.so.4
#22 0xb6c85197 in ?? () from /usr/lib/libQtDBus.so.4
#23 0xb61d95fe in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4
#24 0xb63def54 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#25 0xb63e667c in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4
#26 0xb70e8bfa in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#27 0xb61c96cb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4
#28 0xb61ca2b2 in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib/libQtCore.so.4
#29 0xb61ca47d in QCoreApplication::sendPostedEvents(QObject*, int) () from /usr/lib/libQtCore.so.4
#30 0xb61f43ff in ?? () from /usr/lib/libQtCore.so.4
#31 0xb57d5e88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#32 0xb57d9730 in ?? () from /lib/libglib-2.0.so.0
#33 0xb57d9863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#34 0xb61f402c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#35 0xb647fbe5 in ?? () from /usr/lib/libQtGui.so.4
#36 0xb61c7c79 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#37 0xb61c80ca in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#38 0xb61ca53f in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4
#39 0xb63dedd7 in QApplication::exec() () from /usr/lib/libQtGui.so.4
#40 0x0807a745 in _start ()

Reported using DrKonqi
Comment 1 Dario Andres 2010-01-21 13:33:24 UTC
- If you can reproduce the crash at will (or you experience this regularly), can you install the "kdelibs5-dbg" package and post a complete backtrace here? (you can get more information at http://techbase.kde.org/User:DarioAndres/Basic_Guide_about_Crash_Reporting ) Thanks
Comment 2 Julian Steinmann 2018-03-14 11:52:23 UTC
Probably resolved, closing for inactivity. Please reopen this bug with a backtrace attached if you still experience this crash.