Bug 226750 - Ark crashed unexpectedly when closing a preview of an image.
Summary: Ark crashed unexpectedly when closing a preview of an image.
Status: RESOLVED DUPLICATE of bug 209960
Alias: None
Product: ark
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Harald Hvaal
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-14 01:04 UTC by Josef
Modified: 2010-02-14 01:12 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 Josef 2010-02-14 01:04:54 UTC
Application that crashed: ark
Version of the application: 2.13
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-19-generic i686
Distribution: Ubuntu 9.10

 -- Backtrace:
Application: Ark (ark), signal: Segmentation fault
[KCrash Handler]
#6  0x06534a6d in KHTMLImage::disposeImage (this=0x87b6a28) at ../../khtml/khtmlimage.cpp:288
#7  0x0653530e in ~KHTMLImage (this=0x87b6a28, __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at ../../khtml/khtmlimage.cpp:115
#8  0x00abfe2e in KParts::Part::slotWidgetDestroyed (this=0x87b6a28) at ../../kparts/part.cpp:354
#9  0x00abff4b in KParts::Part::qt_metacall (this=0x87b6a28, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfc71d38) at ./part.moc:76
#10 0x00abffba in KParts::ReadOnlyPart::qt_metacall (this=0x87b6a28, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfc71d38) at ./part.moc:154
#11 0x065350ea in KHTMLImage::qt_metacall (this=0x87b6a28, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbfc71d38) at ./khtmlimage.moc:115
#12 0x021c2263 in QMetaObject::activate (sender=0x87e2488, from_signal_index=0, to_signal_index=1, argv=0xbfc71d38) at kernel/qobject.cpp:3113
#13 0x021c26d8 in QMetaObject::activate (sender=0x87e2488, m=0x22991a8, from_local_signal_index=0, to_local_signal_index=1, argv=0xbfc71d38) at kernel/qobject.cpp:3207
#14 0x021c276b in QObject::destroyed (this=0x87e2488, _t1=0x87e2488) at .moc/release-shared/moc_qobject.cpp:143
#15 0x021c3536 in ~QObject (this=0x87e2488, __in_chrg=<value optimized out>) at kernel/qobject.cpp:757
#16 0x00f209cf in ~QWidget (this=0x87e2488, __in_chrg=<value optimized out>) at kernel/qwidget.cpp:1380
#17 0x012d4961 in ~QFrame (this=0x87e2488, __in_chrg=<value optimized out>) at widgets/qframe.cpp:243
#18 0x0081a301 in ~KHBox (this=0x87e2488, __in_chrg=<value optimized out>) at ../../kdeui/widgets/khbox.cpp:51
#19 0x00872795 in ~KVBox (this=0x87e2488, __in_chrg=<value optimized out>) at ../../kdeui/widgets/kvbox.cpp:29
#20 0x021bb46f in QObjectPrivate::deleteChildren (this=0x879b480) at kernel/qobject.cpp:1847
#21 0x00f2085b in ~QWidget (this=0x858c270, __in_chrg=<value optimized out>) at kernel/qwidget.cpp:1367
#22 0x012d4961 in ~QFrame (this=0x858c270, __in_chrg=<value optimized out>) at widgets/qframe.cpp:243
#23 0x0081a301 in ~KHBox (this=0x858c270, __in_chrg=<value optimized out>) at ../../kdeui/widgets/khbox.cpp:51
#24 0x00872795 in ~KVBox (this=0x858c270, __in_chrg=<value optimized out>) at ../../kdeui/widgets/kvbox.cpp:29
#25 0x021bb46f in QObjectPrivate::deleteChildren (this=0x87997b0) at kernel/qobject.cpp:1847
#26 0x00f2085b in ~QWidget (this=0xbfc72098, __in_chrg=<value optimized out>) at kernel/qwidget.cpp:1367
#27 0x013bc184 in ~QDialog (this=0xbfc72098, __in_chrg=<value optimized out>) at dialogs/qdialog.cpp:298
#28 0x006b24c4 in ~KDialog (this=0xbfc72098, __in_chrg=<value optimized out>) at ../../kdeui/dialogs/kdialog.cpp:197
#29 0x050aac4e in ?? () from /usr/lib/kde4/libarkpart.so
#30 0x050abbb4 in ?? () from /usr/lib/kde4/libarkpart.so
#31 0x050a46bb in ?? () from /usr/lib/kde4/libarkpart.so
#32 0x0509d28b in ?? () from /usr/lib/kde4/libarkpart.so
#33 0x021baf0b in QMetaCallEvent::placeMetaCall (this=0x8328428, object=0x8459d78) at kernel/qobject.cpp:477
#34 0x021bc5fe in QObject::event (this=0x8459d78, e=0x8328428) at kernel/qobject.cpp:1111
#35 0x00ecff54 in QApplicationPrivate::notify_helper (this=0x82da950, receiver=0x8459d78, e=0x8328428) at kernel/qapplication.cpp:4056
#36 0x00ed767c in QApplication::notify (this=0xbfc729b0, receiver=0x8459d78, e=0x8328428) at kernel/qapplication.cpp:3603
#37 0x0074cbfa in KApplication::notify (this=0xbfc729b0, receiver=0x8459d78, event=0x8328428) at ../../kdeui/kernel/kapplication.cpp:302
#38 0x021ac6cb in QCoreApplication::notifyInternal (this=0xbfc729b0, receiver=0x8459d78, event=0x8328428) at kernel/qcoreapplication.cpp:610
#39 0x021ad2b2 in QCoreApplication::sendEvent (receiver=0x0, event_type=0, data=0x82c3800) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#40 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x82c3800) at kernel/qcoreapplication.cpp:1247
#41 0x021ad47d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#42 0x021d73ff in QCoreApplication::sendPostedEvents (s=0x82dcd10) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#43 postEventSourceDispatch (s=0x82dcd10) at kernel/qeventdispatcher_glib.cpp:210
#44 0x02be5e88 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#45 0x02be9730 in ?? () from /lib/libglib-2.0.so.0
#46 0x02be9863 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#47 0x021d702c in QEventDispatcherGlib::processEvents (this=0x82c39d8, flags=...) at kernel/qeventdispatcher_glib.cpp:327
#48 0x00f70be5 in QGuiEventDispatcherGlib::processEvents (this=0x82c39d8, flags=...) at kernel/qguieventdispatcher_glib.cpp:202
#49 0x021aac79 in QEventLoop::processEvents (this=0xbfc72914, flags=) at kernel/qeventloop.cpp:149
#50 0x021ab0ca in QEventLoop::exec (this=0xbfc72914, flags=...) at kernel/qeventloop.cpp:201
#51 0x021ad53f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#52 0x00ecfdd7 in QApplication::exec () at kernel/qapplication.cpp:3525
#53 0x08050184 in _start ()

Reported using DrKonqi
Comment 1 Raphael Kubo da Costa 2010-02-14 01:12:36 UTC
This has been fixed a few releases ago - please consider updating your system.

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