Bug 224046 - Dolphin crah when checking out mapp info
Summary: Dolphin crah when checking out mapp info
Status: RESOLVED NOT A BUG
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-24 15:40 UTC by reaper
Modified: 2018-03-11 19:43 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 reaper 2010-01-24 15:40:45 UTC
Application that crashed: dolphin
Version of the application: 1.3
KDE Version: 4.3.1 (KDE 4.3.1) "release 6"
Qt Version: 4.5.3
Operating System: Linux 2.6.31.8-0.1-desktop x86_64
Distribution: "openSUSE 11.2 (x86_64)"

What I was doing when the application crashed:
Was checking mapp properties

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#5  0x00007fe2688b22d0 in ?? () from /usr/lib64/libkio.so.5
#6  0x00007fe2688b2371 in ?? () from /usr/lib64/libkio.so.5
#7  0x00007fe2688b6d16 in ?? () from /usr/lib64/libkio.so.5
#8  0x00007fe2688b80f6 in KDirModel::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkio.so.5
#9  0x00007fe265897fbc in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
#10 0x00007fe26889be3a in KDirLister::itemsAdded(KUrl const&, KFileItemList const&) () from /usr/lib64/libkio.so.5
#11 0x00007fe26889cbea in KDirLister::Private::emitItems() () from /usr/lib64/libkio.so.5
#12 0x00007fe2688a7688 in ?? () from /usr/lib64/libkio.so.5
#13 0x00007fe2688a7ffe in ?? () from /usr/lib64/libkio.so.5
#14 0x00007fe2688ae320 in ?? () from /usr/lib64/libkio.so.5
#15 0x00007fe265897fbc in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4
#16 0x00007fe2688b9695 in OrgKdeKDirNotifyInterface::FilesChanged(QStringList const&) () from /usr/lib64/libkio.so.5
#17 0x00007fe2688b9800 in OrgKdeKDirNotifyInterface::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkio.so.5
#18 0x00007fe266728b78 in ?? () from /usr/lib64/libQtDBus.so.4
#19 0x00007fe26673016f in ?? () from /usr/lib64/libQtDBus.so.4
#20 0x00007fe2658922d9 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#21 0x00007fe265d132ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#22 0x00007fe265d1a57e in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#23 0x00007fe266ff78d6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#24 0x00007fe265882ddc in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#25 0x00007fe2658839ea in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4
#26 0x00007fe2658ab803 in ?? () from /usr/lib64/libQtCore.so.4
#27 0x00007fe2613ccdde in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#28 0x00007fe2613d07a8 in ?? () from /usr/lib64/libglib-2.0.so.0
#29 0x00007fe2613d08d0 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#30 0x00007fe2658ab3a3 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#31 0x00007fe265da631e in ?? () from /usr/lib64/libQtGui.so.4
#32 0x00007fe265881712 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#33 0x00007fe265881ae4 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#34 0x00007fe265883c99 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#35 0x0000000000439575 in _start ()

Reported using DrKonqi
Comment 1 Dario Andres 2010-01-24 20:08:53 UTC
- If you can reproduce the crash at will (or you experience this regularly),
can you install the "kdelibs4-debuginfo" 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-11 19:43:23 UTC
There is a lot of information missing here. I am closing this bug for inactivity, please open a new bug if you experience a crash again. Thanks :)