| Summary: | Dolphin crashes while selecting a File | ||
|---|---|---|---|
| Product: | [Unmaintained] kdelibs | Reporter: | Diego Sanchez <osezno141> |
| Component: | general | Assignee: | kdelibs bugs <kdelibs-bugs> |
| Status: | RESOLVED DUPLICATE | ||
| Severity: | crash | CC: | frank78ac, smithjd15, vinvarma |
| Priority: | NOR | ||
| Version: | unspecified | ||
| Target Milestone: | --- | ||
| Platform: | Mandriva RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Diego Sanchez
2008-10-22 23:55:32 UTC
Thanks for the bug report! If you have a chance to reproduce this, it might help if you could provide a better backtrace, see http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports I'll reassign this to kdelibs because it looks like a Solid/kdelibs problem. Note that bug 169240 and bug 168768 look related - they also have Solid::Device::listFromQuery () in the backtrace. Wasn't able to reproduce the crash. So no backtrace to show. Sorry about that. I only could confirm slow responsiveness when selecting, mousing over or right-clicking the big pdf file (294.4 MiB); it takes 30 seconds or so to react to the command, while the Dolphin window freezes while "thinking" and the whole system gets slow also, but it allows to select other window and work with it (slowly, though). pdf default app is Xpdf. Changing it to Okular didn't help. Changing the location of the file to a bigger and emptier HD partition does not improve the response. Tried to stop the rest of the applications (Amarok, Amule, Firefox) and the results were the same. One thing I was able to do: I think I've isolated the freezing problem; if the "Information" panel is deselected, the speed remains normal, and the selection, mousing over and right-clicking works normally. Some System info: Laptop Acer Aspire 5601. Centrino Duo T2250 @ 1.73GHz, 1 Gb RAM. Mobile 945GM/GMS, 943/940GML Express Integrated Graphics Controller (Module: Card:Intel 810 and later), no 3D effects. OS: Mandriva 2009.0 One. Linux (i686) release 2.6.27-desktop586-0.rc8.2mnb KDE4 as default, but Amarok 1.4.10 (using KDE 3.5.10) installed. *** Bug 186927 has been marked as a duplicate of this bug. *** See my comment in bug 178844 about the problem with XIOErrors exit() behaviour. I had a similar issue. I double clicked on a picture, which opened fine, but while viewing the picture, after a moment Dolphin crashed. Unfortunately there doesn't appear to be debug symbols for libdbus-1.so.3, but I hope this is useful.
Application that crashed: dolphin
Version of the application: 1.3
KDE Version: 4.3.4 (KDE 4.3.4)
Qt Version: 4.5.3
Operating System: Linux 2.6.32-2.slh.4-sidux-amd64 x86_64
Distribution: Debian GNU/Linux unstable (sid)
-- Backtrace:
Application: Dolphin (dolphin), signal: Segmentation fault
The current source language is "auto; currently c".
[KCrash Handler]
#5 0x00007f5b8e026244 in ?? () from /lib/libdbus-1.so.3
#6 0x00007f5b8e037bcd in ?? () from /lib/libdbus-1.so.3
#7 0x00007f5b8e02a8bf in ?? () from /lib/libdbus-1.so.3
#8 0x00007f5b95768884 in q_dbus_timeout_handle (this=0x1c7d170, e=<value optimized out>) at ./qdbus_symbols_p.h:172
#9 QDBusConnectionPrivate::timerEvent (this=0x1c7d170, e=<value optimized out>) at qdbusintegrator.cpp:1023
#10 0x00007f5b94858353 in QObject::event (this=0x1c7d170, e=0x0) at kernel/qobject.cpp:1074
#11 0x00007f5b94d1701d in QApplicationPrivate::notify_helper (this=0x1c91570, receiver=0x1c7d170, e=0x7fffe9f7ed30) at kernel/qapplication.cpp:4065
#12 0x00007f5b94d1f07a in QApplication::notify (this=0x7fffe9f7f090, receiver=0x1c7d170, e=0x7fffe9f7ed30) at kernel/qapplication.cpp:4030
#13 0x00007f5b96070e06 in KApplication::notify (this=0x7fffe9f7f090, receiver=0x1c7d170, event=0x7fffe9f7ed30) at ../../kdeui/kernel/kapplication.cpp:302
#14 0x00007f5b94848c9c in QCoreApplication::notifyInternal (this=0x7fffe9f7f090, receiver=0x1c7d170, event=0x7fffe9f7ed30) at kernel/qcoreapplication.cpp:610
#15 0x00007f5b948752c6 in QCoreApplication::sendEvent (this=0x1c8b2e0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#16 QTimerInfoList::activateTimers (this=0x1c8b2e0) at kernel/qeventdispatcher_unix.cpp:580
#17 0x00007f5b94871658 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 0x00007f5b903738fe in g_main_dispatch (context=0x1c8a120) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:1960
#20 IA__g_main_context_dispatch (context=0x1c8a120) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2513
#21 0x00007f5b903772b8 in g_main_context_iterate (context=0x1c8a120, block=<value optimized out>, dispatch=<value optimized out>, self=<value optimized out>)
at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2591
#22 0x00007f5b903773e0 in IA__g_main_context_iteration (context=0x1c8a120, may_block=1) at /build/buildd/glib2.0-2.22.3/glib/gmain.c:2654
#23 0x00007f5b9487139c in QEventDispatcherGlib::processEvents (this=0x1c62790, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:407
#24 0x00007f5b94dadf1f in QGuiEventDispatcherGlib::processEvents (this=0x0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#25 0x00007f5b94847562 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#26 0x00007f5b94847934 in QEventLoop::exec (this=0x7fffe9f7efe0, flags=...) at kernel/qeventloop.cpp:201
#27 0x00007f5b94849ba4 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#28 0x00000000004394b5 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../../../apps/dolphin/src/main.cpp:94
(In reply to comment #5) Your crash is a different one: bug 208921, fixed in KDE 4.4. This almost looks like the same behaviour as reportedly fixed in the khtml renderer for konq 4.4.1. It might be connected to the QT change made. *** This bug has been marked as a duplicate of bug 178844 *** |