Bug 247163 - Kontact/Kmail crashing when deleting several unread messages
Summary: Kontact/Kmail crashing when deleting several unread messages
Status: RESOLVED DUPLICATE of bug 219964
Alias: None
Product: kontact
Classification: Applications
Component: general (show other bugs)
Version: 4.4.2
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
: 247489 (view as bug list)
Depends on:
Blocks:
 
Reported: 2010-08-09 19:17 UTC by Irene Korff
Modified: 2010-08-12 15:13 UTC (History)
2 users (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 Irene Korff 2010-08-09 19:17:51 UTC
Application: kontact (4.4.2)
KDE Platform Version: 4.4.2 (KDE 4.4.2)
Qt Version: 4.6.2
Operating System: Linux 2.6.32-24-generic x86_64
Distribution: Ubuntu 10.04.1 LTS

-- Information about the crash:
Kmail within Kontact crashes sometimes when I remove several unread messages at once. The messages are on a remote Gmail server, and are read through IMAP. The problem seems to occur with just one of my several Gmail-accounts, which I have all set up to exclusively use IMAP. The mail for this particular account keeps recurring, no matter if I permanently delete them, even through the Gmail web interface. This is also true for really old mail from years ago. These mails keep returning in my inbox as if they have just been sent. This started a few weeks ago.

Of course, this could be a problem with Gmail, so I changed my pass and tightened my security settings. The thing is that certain mails keep coming back only in  Kmail and not in my Maemo mail program in my phone, where I configured the same account as well.

Some other strange behavior as of lately is that Kmail finds a few hundred new messages in the aforementioned Gmail account, and then starts eliminating them from my inbox until there are just a few left. The mails are still appearing in the remote "all messages" folder. A crash had not happened to me before, but the strange behaviour has been going on for several weeks now. 

 -- Backtrace:
Application: Kontact (kontact), signal: Segmentation fault
[Current thread is 1 (Thread 0x7fa8d3d24780 (LWP 1814))]

Thread 2 (Thread 0x7fa8af5f6710 (LWP 2083)):
#0  0xffffffffff60017b in ?? ()
#1  0x00007fa8af5f5a80 in ?? ()
#2  0x00007fff161ff852 in ?? ()
Backtrace stopped: previous frame identical to this frame (corrupt stack?)

Thread 1 (Thread 0x7fa8d3d24780 (LWP 1814)):
[KCrash Handler]
#5  0x00007fa8b813e684 in MessageList::Core::Item::parent() const () from /usr/lib/libmessagelist.so.4
#6  0x00007fa8b8151c03 in MessageList::Core::Model::parent(QModelIndex const&) const () from /usr/lib/libmessagelist.so.4
#7  0x00007fa8d1add821 in QModelIndex::parent (this=0x2a212c0, index=<value optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qabstractitemmodel.h:389
#8  QTreeView::indexRowSizeHint (this=0x2a212c0, index=<value optimized out>) at itemviews/qtreeview.cpp:2817
#9  0x00007fa8d1addf9e in QTreeViewPrivate::itemHeight (this=0x3137f00, item=2) at itemviews/qtreeview.cpp:3238
#10 0x00007fa8d1ade1df in QTreeViewPrivate::updateScrollBars (this=0x3137f00) at itemviews/qtreeview.cpp:3483
#11 0x00007fa8d1ade614 in QTreeView::updateGeometries (this=0x2a212c0) at itemviews/qtreeview.cpp:2745
#12 0x00007fa8b8159f46 in ?? () from /usr/lib/libmessagelist.so.4
#13 0x00007fa8b815a733 in ?? () from /usr/lib/libmessagelist.so.4
#14 0x00007fa8b815c59e in MessageList::Core::Model::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib/libmessagelist.so.4
#15 0x00007fa8d21d5e3f in QMetaObject::activate (sender=0x2c65258, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x0) at kernel/qobject.cpp:3293
#16 0x00007fa8d21d2a63 in QObject::event (this=0x2c65258, e=0x7fff160f1e50) at kernel/qobject.cpp:1212
#17 0x00007fa8d157c22c in QApplicationPrivate::notify_helper (this=0x23b1680, receiver=0x2c65258, e=0x7fff160f1e50) at kernel/qapplication.cpp:4300
#18 0x00007fa8d15826fb in QApplication::notify (this=0x7fff160f21b0, receiver=0x2c65258, e=0x7fff160f1e50) at kernel/qapplication.cpp:4183
#19 0x00007fa8d2bab526 in KApplication::notify (this=0x7fff160f21b0, receiver=0x2c65258, event=0x7fff160f1e50) at ../../kdeui/kernel/kapplication.cpp:302
#20 0x00007fa8d21c306c in QCoreApplication::notifyInternal (this=0x7fff160f21b0, receiver=0x2c65258, event=0x7fff160f1e50) at kernel/qcoreapplication.cpp:704
#21 0x00007fa8d21efd42 in QCoreApplication::sendEvent (this=0x23cbaa0) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215
#22 QTimerInfoList::activateTimers (this=0x23cbaa0) at kernel/qeventdispatcher_unix.cpp:603
#23 0x00007fa8d21ec824 in timerSourceDispatch (source=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:184
#24 0x00007fa8c99318c2 in g_main_context_dispatch () from /lib/libglib-2.0.so.0
#25 0x00007fa8c9935748 in ?? () from /lib/libglib-2.0.so.0
#26 0x00007fa8c99358fc in g_main_context_iteration () from /lib/libglib-2.0.so.0
#27 0x00007fa8d21ec513 in QEventDispatcherGlib::processEvents (this=0x2386d70, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412
#28 0x00007fa8d162c46e in QGuiEventDispatcherGlib::processEvents (this=0x394e9f0, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204
#29 0x00007fa8d21c1992 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149
#30 0x00007fa8d21c1d6c in QEventLoop::exec (this=0x7fff160f20f0, flags=) at kernel/qeventloop.cpp:201
#31 0x00007fa8d21c5aab in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981
#32 0x0000000000403e8e in _start ()

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

Possible duplicates by query: bug 246820, bug 243398, bug 242767, bug 238828, bug 232152.

Reported using DrKonqi
Comment 1 Irene Korff 2010-08-09 19:20:22 UTC
I forgot to mention that it's my default mailbox.
Comment 2 Nicolas L. 2010-08-10 11:07:22 UTC

*** This bug has been marked as a duplicate of bug 219964 ***
Comment 3 Nicolas L. 2010-08-12 15:13:17 UTC
*** Bug 247489 has been marked as a duplicate of this bug. ***