Bug 224083 - Dolphin delayed crash after click to open PDF
Summary: Dolphin delayed crash after click to open PDF
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-24 21:23 UTC by Martin
Modified: 2010-01-26 15:02 UTC (History)
1 user (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 Martin 2010-01-24 21:23:32 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:
Dolphin chrashes after clicking on icons of files or directories. Opening the PDF was simply the first one when I actually knew exacly which action caused it.
Delay between clicking and crash during which Dolphin remains frozen.
Happens about every 20th click on average.

 -- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
[KCrash Handler]
#5  _dbus_connection_lock (connection=0x57002d00450044) at dbus-connection.c:355
#6  0x00007fc1c8a29bfd in _dbus_pending_call_get_connection_and_lock (pending=0x80bcf0) at dbus-pending-call.c:307
#7  0x00007fc1c8a1bd3e in reply_handler_timeout (data=0x57002d00450044) at dbus-connection.c:3158
#8  0x00007fc1cd624a37 in q_dbus_timeout_handle (timeout=<value optimized out>) at ./qdbus_symbols_p.h:172
#9  QDBusConnectionPrivate::timerEvent (timeout=<value optimized out>) at qdbusintegrator.cpp:1023
#10 0x00007fc1cc797f63 in QObject::event (this=0x6a32c0, e=0x6a7210) at kernel/qobject.cpp:1075
#11 0x00007fc1ccc192ac in QApplicationPrivate::notify_helper (this=0x6b9890, receiver=0x6a32c0, e=0x7fffae1f9de0) at kernel/qapplication.cpp:4065
#12 0x00007fc1ccc2057e in QApplication::notify (this=0x7fffae1fa1e0, receiver=0x6a32c0, e=0x7fffae1f9de0) at kernel/qapplication.cpp:4030
#13 0x00007fc1cdefd8d6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5
#14 0x00007fc1cc788ddc in QCoreApplication::notifyInternal (this=0x7fffae1fa1e0, receiver=0x6a32c0, event=0x7fffae1f9de0) at kernel/qcoreapplication.cpp:610
#15 0x00007fc1cc7b471d in sendEvent (event=<value optimized out>, receiver=<value optimized out>) at kernel/qcoreapplication.h:213
#16 QTimerInfoList::activateTimers (event=<value optimized out>, receiver=<value optimized out>) at kernel/qeventdispatcher_unix.cpp:594
#17 0x00007fc1cc7b1678 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 0x00007fc1c82d2dde in g_main_dispatch (context=<value optimized out>) at gmain.c:1960
#20 IA__g_main_context_dispatch (context=<value optimized out>) at gmain.c:2513
#21 0x00007fc1c82d67a8 in g_main_context_iterate (context=0x6b51f0, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>) at gmain.c:2591
#22 0x00007fc1c82d68d0 in IA__g_main_context_iteration (context=0x6b51f0, may_block=1) at gmain.c:2654
#23 0x00007fc1cc7b13a3 in QEventDispatcherGlib::processEvents (this=0x689730, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:407
#24 0x00007fc1cccac31e in QGuiEventDispatcherGlib::processEvents (this=0x57002d00450044, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#25 0x00007fc1cc787712 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#26 0x00007fc1cc787ae4 in QEventLoop::exec (this=0x7fffae1fa130, flags=) at kernel/qeventloop.cpp:201
#27 0x00007fc1cc789c99 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#28 0x0000000000439575 in _start ()

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

Reported using DrKonqi
Comment 1 Frank Reininghaus 2010-01-26 15:02:51 UTC
Thanks for the bug report! This will be fixed in KDE 4.3.5 and later.

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