Dolphin Crashes - How to Get Backtrace?

English Applications
1

OS 11.2x86_64, KDE 4.3.1 desktop.

The Dolphin file manager crashes on me randomly. It does not seem to be connected to any particular operation, but just “goes away” with no warning & nothing in the system logs. Starting Dolphin in a terminal window gives nothing upon crashing, just the prompt comes back (so far, anyway.)

I’ve found one thread on Dolphin crashes here: Frequent Dolphin Crashes - openSUSE Forums But I have no idea what nepomuk does, or how to disable it to see if that’s part of my problem.

The KDE crash window comes up, but I have no idea what packages I need to load in order to generate a proper backtrace. Anyone have any idea which -debug packages to load?

2

4.3.1 is old, upgrade to 4.3.4 via the STABLE repository:

http://download.opensuse.org/repositories/KDE:/KDE4:/STABLE:/Desktop/openSUSE_11.2/

](http://download.opensuse.org/repositories/KDE:/KDE4:/STABLE:/Desktop/openSUSE_11.2/)
It has received several fixes which may help with your Dolphin issues.

3

Thank you, I will give that a try. :slight_smile:

4

Hey Guy’s and Heidilol!

Try this; System Settings - Display (Computer Admin Section)

What Happens?

5

Installed the KDE 4.3.4 packages as above, then gave your suggestion a try. :slight_smile:

The KDE Crash Handler came up after the menu vanished . . . with a seg fault (signal 11) & the following:

Application: System Settings (systemsettings), signal: Segmentation fault
[KCrash Handler]
#5  0x00007fae3e2855fc in QGraphicsScene::removeItem(QGraphicsItem*) () from /usr/lib64/libQtGui.so.4
#6  0x00007fae3e285f20 in QGraphicsScene::addItem(QGraphicsItem*) () from /usr/lib64/libQtGui.so.4
#7  0x00007fae2f3fb1d1 in ?? () from /usr/lib64/kde4/kcm_randr.so
#8  0x00007fae2f3e8eb9 in ?? () from /usr/lib64/kde4/kcm_randr.so
#9  0x00007fae3e997f01 in KCModule::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkdeui.so.5
#10 0x00007fae3d1852d9 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#11 0x00007fae3dd4348f in QWidget::event(QEvent*) () from /usr/lib64/libQtGui.so.4
#12 0x00007fae3dcf52ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#13 0x00007fae3dcfc57e in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4
#14 0x00007fae3e8eff26 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#15 0x00007fae3d175ddc in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#16 0x00007fae3d1769ea in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () from /usr/lib64/libQtCore.so.4
#17 0x00007fae3d19e803 in ?? () from /usr/lib64/libQtCore.so.4
#18 0x00007fae39dc3dde in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#19 0x00007fae39dc77a8 in ?? () from /usr/lib64/libglib-2.0.so.0
#20 0x00007fae39dc78d0 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#21 0x00007fae3d19e3a3 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#22 0x00007fae3dd8831e in ?? () from /usr/lib64/libQtGui.so.4
#23 0x00007fae3d174712 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#24 0x00007fae3d174ae4 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#25 0x00007fae3d176c99 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#26 0x000000000040cbd9 in _start ()
6

Well duh, it indeed seems to croak. How annoying.

7

Beineri was nice enough to point me to a bug report about it already;
https://bugzilla.novell.com/561164

8

Why not add to the comments in that Bug report. I did a while ago.

9

I hate Bugzilla, incidentally I also hate Wikis so I never fill up the HCL even if I would have hundreds of entries to it.

10

So much hate Heidi
Scary Babe!rotfl!

It is rather tedious I agree