Bug 221127 - Dolphin crashes randomly.
Summary: Dolphin crashes randomly.
Status: RESOLVED DUPLICATE of bug 208921
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-03 17:45 UTC by Shannon
Modified: 2010-01-03 18:02 UTC (History)
1 user (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 Shannon 2010-01-03 17:45:59 UTC
Application that crashed: dolphin
Version of the application: 1.3
KDE Version: 4.3.4 (KDE 4.3.4)
Qt Version: 4.6.0
Operating System: Linux 2.6.32-gentoo x86_64

What I was doing when the application crashed:
Dolphin crashes randomly. This particular time it crashed after I opened a pdf file useing the context menu -> open with -> other...  and typing kate. The file opened fine in kate. I reported the bug this time because I finally got a useful backtrace.

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#5  _dbus_connection_lock (connection=0x6e0077006f006e) at /var/tmp/portage/sys-apps/dbus-1.3.0-r1/work/dbus-1.3.0/dbus/dbus-connection.c:361
#6  0x00007f6514e0118d in _dbus_pending_call_get_connection_and_lock (pending=0x25cd880) at /var/tmp/portage/sys-apps/dbus-1.3.0-r1/work/dbus-1.3.0/dbus/dbus-pending-call.c:307
#7  0x00007f6514df315e in reply_handler_timeout (data=0x6e0077006f006e) at /var/tmp/portage/sys-apps/dbus-1.3.0-r1/work/dbus-1.3.0/dbus/dbus-connection.c:3237
#8  0x00007f651a1ad477 in q_dbus_timeout_handle (this=0x2323560, e=0x7fff575d6ba0) at ./qdbus_symbols_p.h:172
#9  QDBusConnectionPrivate::timerEvent (this=0x2323560, e=0x7fff575d6ba0) at qdbusintegrator.cpp:1038
#10 0x00007f6519e91be3 in QObject::event (this=0x2323560, e=0x7fff575d6ba0) at kernel/qobject.cpp:1216
#11 0x00007f65191588fc in QApplicationPrivate::notify_helper (this=0x2330860, receiver=0x2323560, e=0x7fff575d6ba0) at kernel/qapplication.cpp:4242
#12 0x00007f651916106a in QApplication::notify (this=0x7fff575d6f00, receiver=<value optimized out>, e=0x7fff575d6ba0) at kernel/qapplication.cpp:4125
#13 0x00007f651acd57c6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#14 0x00007f6519e825db in QCoreApplication::notifyInternal (this=0x7fff575d6f00, receiver=0x2323560, event=0x7fff575d6ba0) at kernel/qcoreapplication.cpp:704
#15 0x00007f6519eae6aa in QCoreApplication::sendEvent (this=0x233b8e0) at kernel/qcoreapplication.h:215
#16 QTimerInfoList::activateTimers (this=0x233b8e0) at kernel/qeventdispatcher_unix.cpp:603
#17 0x00007f6519eab578 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#18 idleTimerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:231
#19 0x00007f6515a9b8eb in g_main_dispatch (context=0x233a120) at gmain.c:1960
#20 IA__g_main_context_dispatch (context=0x233a120) at gmain.c:2513
#21 0x00007f6515a9f1f0 in g_main_context_iterate (context=0x233a120, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2591
#22 0x00007f6515a9f320 in IA__g_main_context_iteration (context=0x233a120, may_block=1) at gmain.c:2654
#23 0x00007f6519eab253 in QEventDispatcherGlib::processEvents (this=0x230b280, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:407
#24 0x00007f65191f358e in QGuiEventDispatcherGlib::processEvents (this=0x6e0077006f006e, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#25 0x00007f6519e80f72 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#26 0x00007f6519e8134d in QEventLoop::exec (this=0x7fff575d6e50, flags=) at kernel/qeventloop.cpp:201
#27 0x00007f6519e84f93 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#28 0x0000000000438818 in _start ()

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

Reported using DrKonqi
Comment 1 Dario Andres 2010-01-03 18:02:39 UTC
Those crashes are being tracked at bug 208921. Thanks

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