Bug 227919 - Kontact freezes when a special e-mail is clicked
Summary: Kontact freezes when a special e-mail is clicked
Status: RESOLVED UNMAINTAINED
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: 4.3.2
Platform: Unlisted Binaries Linux
: NOR normal
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-02-21 12:05 UTC by Manuela
Modified: 2017-01-07 22:44 UTC (History)
0 users

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 Manuela 2010-02-21 12:05:01 UTC
Application that crashed: kontact
Version of the application: 4.3.2
KDE Version: 4.3.2 (KDE 4.3.2)
Qt Version: 4.5.2
Operating System: Linux 2.6.31-19-generic x86_64
Distribution: Ubuntu 9.10

What I was doing when the application crashed:
- using disconnected imap
- removed some mails, moved so to other folders
- did this serveral times and after some time kontact always freezes completly
- after some times I've the suspicion that it always happens with a special mail
- I guess it is not related to the removing or moving the mails before, because I could reproduce it without that now

I'll keep the suspicious mail at the moment, just in case you have further questions.

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
The current source language is "auto; currently c".
[KCrash Handler]
#17 0x00007f077c92ddcf in qobject_cast<QWidget*> (this=<value optimized out>, sourceRegion=<value optimized out>, hasDirtySiblingsAbove=<value optimized out>, alsoNonOpaque=<value optimized out>)
    at ../../include/QtGui/../../src/gui/kernel/qwidget.h:876
#18 QWidgetPrivate::subtractOpaqueSiblings (this=<value optimized out>, sourceRegion=<value optimized out>, hasDirtySiblingsAbove=<value optimized out>, alsoNonOpaque=<value optimized out>)
    at kernel/qwidget.cpp:1826
#19 0x00007f077c92e552 in QWidget::raise (this=0x18ac4e0) at kernel/qwidget.cpp:10411
#20 0x00007f077cd1b81b in QAbstractScrollAreaPrivate::layoutChildren (this=0x18ab470) at widgets/qabstractscrollarea.cpp:443
#21 0x00007f077cd1bfdb in QAbstractScrollArea::qt_metacall (this=0x18ab410, _c=QMetaObject::InvokeMetaMethod, _id=30990128, _a=0x2812a20) at .moc/release-shared/moc_qabstractscrollarea.cpp:80
#22 0x00007f077cee8bc5 in QScrollArea::qt_metacall (this=0x3, _c=1126559544, _id=32006768, _a=0x3) at .moc/release-shared/moc_qscrollarea.cpp:63
#23 0x00007f077abf4e90 in KHTMLView::qt_metacall (this=0x3, _c=1126559544, _id=32006768, _a=0x3) at ./khtmlview.moc:84
#24 0x00007f077bfd10f9 in QObject::event (this=0x18ab410, e=0x2812a80) at kernel/qobject.cpp:1111
#25 0x00007f077c93015f in QWidget::event (this=0x18ab410, event=0x2812a80) at kernel/qwidget.cpp:7946
#26 0x00007f077cc8c2a6 in QFrame::event (this=0x18ab410, e=0x2812a80) at widgets/qframe.cpp:559
#27 0x00007f077cd1bbc9 in QAbstractScrollArea::event (this=0x18ab410, e=0x2812a80) at widgets/qabstractscrollarea.cpp:918
#28 0x00007f077abf6dd7 in KHTMLView::event (this=0x18ab410, e=<value optimized out>) at ../../khtml/khtmlview.cpp:546
#29 0x00007f077c8e1efc in QApplicationPrivate::notify_helper (this=0x10003b0, receiver=0x18ab410, e=0x2812a80) at kernel/qapplication.cpp:4056
#30 0x00007f077c8e91ce in QApplication::notify (this=0x7fff4325ffc0, receiver=0x18ab410, e=0x2812a80) at kernel/qapplication.cpp:4021
#31 0x00007f077d518ab6 in KApplication::notify (this=0x7fff4325ffc0, receiver=0x18ab410, event=0x2812a80) at ../../kdeui/kernel/kapplication.cpp:302
#32 0x00007f077bfc1c2c in QCoreApplication::notifyInternal (this=0x7fff4325ffc0, receiver=0x18ab410, event=0x2812a80) at kernel/qcoreapplication.cpp:610
#33 0x00007f077bfc280a in QCoreApplication::sendEvent (receiver=0x0, event_type=<value optimized out>, data=0xfc8080) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#34 QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=<value optimized out>, data=0xfc8080) at kernel/qcoreapplication.cpp:1247
#35 0x00007f077bfea533 in QCoreApplication::sendPostedEvents (s=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:218
#36 postEventSourceDispatch (s=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:210
#37 0x00007f077583bbce in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#38 0x00007f077583f598 in ?? () from /lib/libglib-2.0.so.0
#39 0x00007f077583f6c0 in g_main_context_iteration () from /lib/libglib-2.0.so.0
#40 0x00007f077bfea1a6 in QEventDispatcherGlib::processEvents (this=0xfc7cb0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:327
#41 0x00007f077c9764be in QGuiEventDispatcherGlib::processEvents (this=0x3, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:202
#42 0x00007f077bfc0532 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#43 0x00007f077bfc0904 in QEventLoop::exec (this=0x7fff4325ff00, flags=) at kernel/qeventloop.cpp:201
#44 0x00007f077bfc2ab9 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888
#45 0x0000000000403f47 in main (argc=<value optimized out>, argv=<value optimized out>) at ../../../kontact/src/main.cpp:218

Reported using DrKonqi
Comment 1 Manuela 2010-02-21 12:11:34 UTC
FYI: When creating this ticket I killed the kontact process because of the freezing.
Comment 2 Christophe Marin 2010-03-27 11:47:55 UTC
(In reply to comment #1)
> FYI: When creating this ticket I killed the kontact process because of the
> freezing.

Changing status then. The backtrace won't show anything useful.

maybe you can run kontact from a console and look at the debug output.
Comment 3 Denis Kurz 2016-09-24 19:27:13 UTC
This bug has only been reported for versions before 4.14, which have been unsupported for at least two years now. Can anyone tell if this bug still present?

If noone confirms this bug for a Framework-based version of kontact (version 5.0 or later, as part of KDE Applications 15.08 or later), it gets closed in about three months.
Comment 4 Denis Kurz 2017-01-07 22:44:15 UTC
Just as announced in my last comment, I close this bug. If you encounter it again in a recent version (at least 5.0 aka 15.08), please open a new one unless it already exists. Thank you for all your input.