Bug 255619 - Dolphin crashes after displaying pdf preview
Summary: Dolphin crashes after displaying pdf preview
Status: RESOLVED DUPLICATE of bug 226725
Alias: None
Product: dolphin
Classification: Applications
Component: general (show other bugs)
Version: 16.12.2
Platform: Arch Linux Linux
: NOR crash
Target Milestone: ---
Assignee: Peter Penz
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-29 23:03 UTC by FabioLima
Modified: 2010-11-03 01:21 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 FabioLima 2010-10-29 23:03:13 UTC
Application: dolphin (1.5)
KDE Platform Version: 4.5.2 (KDE 4.5.2)
Qt Version: 4.7.0
Operating System: Linux 2.6.35-CHAKRA i686
Distribution (Platform): Archlinux Packages

-- Information about the crash:
- What I was doing when the application crashed:
after you put the mouse cursor over a PDF file, dolphin crashes with no notice

The crash can be reproduced every time.

-- Backtrace:
Application: Dolphin (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#7  0xb335d594 in _dbus_pthread_mutex_lock () from /usr/lib/libdbus-1.so.3
#8  0xb3350de8 in _dbus_mutex_lock () from /usr/lib/libdbus-1.so.3
#9  0xb3336c85 in _dbus_connection_lock () from /usr/lib/libdbus-1.so.3
#10 0xb334b665 in _dbus_pending_call_get_connection_and_lock () from /usr/lib/libdbus-1.so.3
#11 0xb333afa5 in reply_handler_timeout () from /usr/lib/libdbus-1.so.3
#12 0xb3350bb2 in dbus_timeout_handle () from /usr/lib/libdbus-1.so.3
#13 0xb5fe8984 in q_dbus_timeout_handle (this=0x8458d28, e=0xbff713d0) at qdbus_symbols_p.h:174
#14 QDBusConnectionPrivate::timerEvent (this=0x8458d28, e=0xbff713d0) at qdbusintegrator.cpp:1050
#15 0xb6f5da04 in QObject::event (this=0x8458d28, e=0xbff713d0) at kernel/qobject.cpp:1183
#16 0xb64ae6a4 in QApplicationPrivate::notify_helper (this=0x845e6c8, receiver=0x8458d28, e=0xbff713d0) at kernel/qapplication.cpp:4397
#17 0xb64b31ee in QApplication::notify (this=0xbff71730, receiver=0x8458d28, e=0xbff713d0) at kernel/qapplication.cpp:3799
#18 0xb75e4d4a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5
#19 0xb6f4880b in QCoreApplication::notifyInternal (this=0xbff71730, receiver=0x8458d28, event=0xbff713d0) at kernel/qcoreapplication.cpp:732
#20 0xb6f7897e in QCoreApplication::sendEvent (this=0x8461e94) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#21 QTimerInfoList::activateTimers (this=0x8461e94) at kernel/qeventdispatcher_unix.cpp:602
#22 0xb6f756c4 in timerSourceDispatch (source=0x8461e60) at kernel/qeventdispatcher_glib.cpp:184
#23 0xb5d7eb72 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#24 0xb5d7f350 in ?? () from /usr/lib/libglib-2.0.so.0
#25 0xb5d7f604 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#26 0xb6f75e47 in QEventDispatcherGlib::processEvents (this=0x845eef0, flags=...) at kernel/qeventdispatcher_glib.cpp:417
#27 0xb655ef25 in QGuiEventDispatcherGlib::processEvents (this=0x845eef0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204
#28 0xb6f479c9 in QEventLoop::processEvents (this=0xbff71674, flags=...) at kernel/qeventloop.cpp:149
#29 0xb6f47c6a in QEventLoop::exec (this=0xbff71674, flags=...) at kernel/qeventloop.cpp:201
#30 0xb6f4c69f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1009
#31 0xb64ac527 in QApplication::exec () at kernel/qapplication.cpp:3673
#32 0xb30ce0d5 in kdemain () from /usr/lib/libkdeinit4_dolphin.so
#33 0x0804dec9 in _start ()

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

Possible duplicates by query: bug 254880, bug 252329, bug 249556, bug 249348, bug 248534.

Reported using DrKonqi
Comment 1 Frank Reininghaus 2010-11-03 01:21:15 UTC
Thanks for the bug report! This is an issue in the D-Bus library which
has been reported already. It is fixed in D-Bus 1.3.1 and later:

http://bugreports.qt.nokia.com/browse/QTBUG-7475
https://bugs.freedesktop.org/show_bug.cgi?id=17754

If you cannot update to D-Bus 1.3.1 or later, you can disable tool tips and the
Information Panel as a workaround.

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