Bug 210195 - crash on closing history viewer
Summary: crash on closing history viewer
Status: RESOLVED DUPLICATE of bug 209960
Alias: None
Product: kopete
Classification: Applications
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Kopete Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-10-11 15:46 UTC by Richard Homonnai
Modified: 2009-10-11 18:53 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 Richard Homonnai 2009-10-11 15:46:44 UTC
Application that crashed: kopete
Version of the application: 0.80.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.30-gentoo-r6-richBOOK i686

What I was doing when the application crashed:
I was looking up something in the history viewer, pasted it into a message, and closed the history viewer afterwards. Then kopete crashed on me.

 -- Backtrace:
Application: Kopete (kopete), signal: Segmentation fault
[Current thread is 0 (LWP 13937)]

Thread 3 (Thread 0xb1f16b90 (LWP 14055)):
#0  0xb80d4424 in __kernel_vsyscall ()
#1  0xb65b1417 in poll () from /lib/libc.so.6
#2  0xb60398d8 in g_poll () from /usr/lib/libglib-2.0.so.0
#3  0x00000001 in ?? ()
#4  0xffffffff in ?? ()
#5  0xb60c2ff4 in ?? () from /usr/lib/libglib-2.0.so.0
#6  0xb60c3398 in ?? () from /usr/lib/libglib-2.0.so.0
#7  0x00000001 in ?? ()
#8  0xb60c2ff4 in ?? () from /usr/lib/libglib-2.0.so.0
#9  0xb602ceeb in ?? () from /usr/lib/libglib-2.0.so.0
#10 0x0953c948 in ?? ()
#11 0x00000001 in ?? ()
#12 0xffffffff in ?? ()
#13 0x0953c948 in ?? ()
#14 0x00000001 in ?? ()
#15 0x00000000 in ?? ()

Thread 2 (Thread 0xb1715b90 (LWP 14059)):
#0  0xb6f2f545 in pthread_mutex_lock () from /lib/libpthread.so.0
#1  0xb602c8f2 in g_main_context_prepare () from /usr/lib/libglib-2.0.so.0
#2  0xb60c3398 in ?? () from /usr/lib/libglib-2.0.so.0
#3  0xb60c33c0 in ?? () from /usr/lib/libglib-2.0.so.0
#4  0x00000000 in ?? ()

Thread 1 (Thread 0xb5cf0700 (LWP 13937)):
[KCrash Handler]
#6  ~KHTMLPart (this=0x9678070) at /usr/include/qt4/QtGui/qwidget.h:477
#7  0xb7a8c875 in KParts::Part::slotWidgetDestroyed (this=0x9678070) at /tmp/portage/kde-base/kdelibs-4.3.2-r1/work/kdelibs-4.3.2/kparts/part.cpp:354
#8  0xb7a8c974 in KParts::Part::qt_metacall (this=0x9678070, _c=QMetaObject::InvokeMetaMethod, _id=2, _a=0xbff48e3c)
    at /tmp/portage/kde-base/kdelibs-4.3.2-r1/work/kdelibs-4.3.2_build/kparts/part.moc:76
#9  0xb7a8c9bf in KParts::ReadOnlyPart::qt_metacall (this=0x9678070, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbff48e3c)
    at /tmp/portage/kde-base/kdelibs-4.3.2-r1/work/kdelibs-4.3.2_build/kparts/part.moc:154
#10 0xb3015717 in KHTMLPart::qt_metacall (this=0x9678070, _c=QMetaObject::InvokeMetaMethod, _id=6, _a=0xbff48e3c)
    at /tmp/portage/kde-base/kdelibs-4.3.2-r1/work/kdelibs-4.3.2_build/khtml/khtml_part.moc:246
#11 0xb7094069 in QMetaObject::activate (sender=0x9797158, from_signal_index=<value optimized out>, to_signal_index=1, argv=0x0) at kernel/qobject.cpp:3101
#12 0xb7094391 in QMetaObject::activate (sender=0x9797158, m=0x807eb10, from_local_signal_index=0, to_local_signal_index=1, argv=0xbff48e3c) at kernel/qobject.cpp:3198
#13 0xb7094414 in QObject::destroyed (this=0x9797158, _t1=0x9797158) at .moc/release-shared/moc_qobject.cpp:143
#14 0xb7095ded in ~QObject (this=0x9797158) at kernel/qobject.cpp:757
#15 0xb68adae9 in ~QWidget (this=0x9797158) at kernel/qwidget.cpp:1380
#16 0xb708fcf7 in QObjectPrivate::deleteChildren (this=0x940f110) at kernel/qobject.cpp:1838
#17 0xb68ad940 in ~QWidget (this=0x97c1958) at kernel/qwidget.cpp:1367
#18 0xb708fcf7 in QObjectPrivate::deleteChildren (this=0xa108c20) at kernel/qobject.cpp:1838
#19 0xb68acd8a in ~QWidget (this=0x91f9f60) at kernel/qwidget.cpp:1367
#20 0xb6be2c54 in ~QFrame (this=0x91f9f60) at widgets/qframe.cpp:243
#21 0xb6c3d140 in ~QSplitter (this=0x91f9f60) at widgets/qsplitter.cpp:1008
#22 0xb708fcf7 in QObjectPrivate::deleteChildren (this=0x924b100) at kernel/qobject.cpp:1838
#23 0xb68ad940 in ~QWidget (this=0x966b128) at kernel/qwidget.cpp:1367
#24 0xb708fcf7 in QObjectPrivate::deleteChildren (this=0x9683060) at kernel/qobject.cpp:1838
#25 0xb68acd8a in ~QWidget (this=0x9576e10) at kernel/qwidget.cpp:1367
#26 0xb6cabb4e in ~QDialog (this=0x9576e10) at dialogs/qdialog.cpp:298
#27 0xb74d2ff5 in ~KDialog (this=0x9576e10) at /tmp/portage/kde-base/kdelibs-4.3.2-r1/work/kdelibs-4.3.2/kdeui/dialogs/kdialog.cpp:197
#28 0xb2dc733f in ~HistoryDialog (this=0x9576e10) at /tmp/portage/kde-base/kopete-4.3.2/work/kopete-4.3.2/kopete/plugins/history/historydialog.cpp:187
#29 0xb708fa27 in qDeleteInEventHandler (o=0x9678070) at kernel/qobject.cpp:3806
#30 0xb709152c in QObject::event (this=0x9576e10, e=0x9628940) at kernel/qobject.cpp:1085
#31 0xb68b5109 in QWidget::event (this=0x9576e10, event=0x9628940) at kernel/qwidget.cpp:7946
#32 0xb6867b7b in QApplicationPrivate::notify_helper (this=0x8e82638, receiver=0x9576e10, e=0x9628940) at kernel/qapplication.cpp:4056
#33 0xb686f5b2 in QApplication::notify (this=0xbff49938, receiver=0x9576e10, e=0x9628940) at kernel/qapplication.cpp:4021
#34 0xb7564ccc in KApplication::notify (this=0xbff49938, receiver=0x9576e10, event=0x9628940) at /tmp/portage/kde-base/kdelibs-4.3.2-r1/work/kdelibs-4.3.2/kdeui/kernel/kapplication.cpp:302
#35 0xb7082e3d in QCoreApplication::notifyInternal (this=0xbff49938, receiver=0x9576e10, event=0x9628940) at kernel/qcoreapplication.cpp:606
#36 0xb7083663 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8e618e8) at kernel/qcoreapplication.h:213
#37 0xb7083820 in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140
#38 0xb70a83b8 in postEventSourceDispatch (s=0x8e84390) at kernel/qcoreapplication.h:218
#39 0xb6029d57 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0

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

Reported using DrKonqi
Comment 1 Dario Andres 2009-10-11 18:53:20 UTC
Merging with bug 209960. Thanks

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