Bug 247665 - Dolphin crashed while navigating path
Summary: Dolphin crashed while navigating path
Status: RESOLVED DUPLICATE of bug 226725
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
: 248257 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-08-13 16:42 UTC by chaz1011
Modified: 2010-08-18 19:54 UTC (History)
5 users (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments
kcrash file (2.45 KB, text/plain)
2010-08-13 16:42 UTC, chaz1011
Details
New crash information added by DrKonqi (3.12 KB, text/plain)
2010-08-16 07:16 UTC, Ruchir Brahmbhatt
Details
New crash information added by DrKonqi (5.65 KB, text/plain)
2010-08-18 16:24 UTC, dawid.m
Details

Note You need to log in before you can comment on or make changes to this bug.
Description chaz1011 2010-08-13 16:42:56 UTC
Created attachment 50134 [details]
kcrash file

Version:           unspecified (using KDE 4.5.0) 
OS:                Linux

Dolphin crashed while navigating path.  One instance was in home, the other in a USB drive.

Reproducible: Didn't try




Attached is a kcrash report.  The KDE Crash Handler failed to connect to submit the report so its attached

pplication: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#6  _dbus_connection_lock (connection=0x373030322f736569) at dbus-connection.c:355
#7  0x00007fdd06183b1d in _dbus_pending_call_get_connection_and_lock (pending=0x7fdcf4009d10) at dbus-pending-call.c:307
#8  0x00007fdd06175fce in reply_handler_timeout (data=0x7fdcf4009d10) at dbus-connection.c:3163
#9  0x00007fdd0b447cef in q_dbus_timeout_handle (this=0x626260, e=0x7fffc4580ed0) at qdbus_symbols_p.h:172
#10 QDBusConnectionPrivate::timerEvent (this=0x626260, e=0x7fffc4580ed0) at qdbusintegrator.cpp:1035
#11 0x00007fdd0b12322e in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4
#12 0x00007fdd0a5034d4 in QApplicationPrivate::notify_helper (this=0x63b500, receiver=0x626260, e=0x7fffc4580ed0) at kernel/qapplication.cpp:4302
#13 0x00007fdd0a50baca in QApplication::notify (this=<value optimized out>, receiver=0x626260, e=0x7fffc4580ed0) at kernel/qapplication.cpp:4185
#14 0x00007fdd0bcad0b6 in KApplication::notify (this=0x7fffc4581320, receiver=0x626260, event=0x7fffc4580ed0) at /usr/src/debug/kdelibs-4.5.0/kdeui/kernel/kapplication.cpp:310
#15 0x00007fdd0b111e4c in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4
#16 0x00007fdd0b13d0c9 in ?? () from /usr/lib64/libQtCore.so.4
#17 0x00007fdd0b139ff8 in ?? () from /usr/lib64/libQtCore.so.4
#18 0x00007fdd058b0a93 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#19 0x00007fdd058b1270 in ?? () from /usr/lib64/libglib-2.0.so.0
#20 0x00007fdd058b1510 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#21 0x00007fdd0b13a67f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#22 0x00007fdd0a5a414e in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#23 0x00007fdd0b111292 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#24 0x00007fdd0b111495 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#25 0x00007fdd0b11588b in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4
#26 0x00007fdd0e23d085 in kdemain (argc=5, argv=0x7fffc4581848) at /usr/src/debug/kdebase-4.5.0/apps/dolphin/src/main.cpp:98
#27 0x00007fdd0deb4b7d in __libc_start_main () from /lib64/libc.so.6
#28 0x0000000000400699 in _start () at ../sysdeps/x86_64/elf/start.S:113
Comment 1 Ruchir Brahmbhatt 2010-08-16 07:16:17 UTC
Created attachment 50596 [details]
New crash information added by DrKonqi

dolphin (1.5) on KDE Platform 4.5.00 (KDE 4.5.0) using Qt 4.6.3

- What I was doing when the application crashed:
Opened dolphin. Navigated to one folder and opened a spreadsheet(xls).

-- Backtrace (Reduced):
#6  _dbus_connection_lock (connection=0x0) at dbus-connection.c:355
#7  0x00007fb7169f4b1d in _dbus_pending_call_get_connection_and_lock (pending=0xa00d90) at dbus-pending-call.c:307
#8  0x00007fb7169e6fce in reply_handler_timeout (data=0xa00d90) at dbus-connection.c:3163
#9  0x00007fb719c9fcef in q_dbus_timeout_handle (this=0x685c70, e=0x7ffff54444a0) at qdbus_symbols_p.h:172
#10 QDBusConnectionPrivate::timerEvent (this=0x685c70, e=0x7ffff54444a0) at qdbusintegrator.cpp:1035
Comment 2 Ruchir Brahmbhatt 2010-08-16 07:19:51 UTC
It is reproducible often for me on opensuse 11.3 x86_64 in kde 4.5.
Comment 3 Nicolas L. 2010-08-18 16:11:39 UTC
*** Bug 248257 has been marked as a duplicate of this bug. ***
Comment 4 dawid.m 2010-08-18 16:24:38 UTC
Created attachment 50702 [details]
New crash information added by DrKonqi

I was navigating trough my external HD to add Music to Amaroks Playlist as Dolphin crashed.
Comment 5 Frank Reininghaus 2010-08-18 19:54:58 UTC
Thanks for reporting! This is a bug in the D-Bus library.

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