Bug 165390 - Kmail sorts mail on IMAP folder wrongly, then crashes
Summary: Kmail sorts mail on IMAP folder wrongly, then crashes
Status: RESOLVED WORKSFORME
Alias: None
Product: kmail
Classification: Applications
Component: IMAP (show other bugs)
Version: unspecified
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: kdepim bugs
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-06-30 08:05 UTC by Arne Schmitz
Modified: 2009-04-04 11:33 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In:


Attachments
Backtrace of crashing Kontact, while reading wrongly sorted emails. (3.79 KB, text/plain)
2008-06-30 08:06 UTC, Arne Schmitz
Details
Better backtrace, with line number information (4.09 KB, text/plain)
2008-06-30 08:27 UTC, Arne Schmitz
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Arne Schmitz 2008-06-30 08:05:42 UTC
Version:            (using KDE 3.5.9)
Installed from:    SuSE RPMs

When I looked into my Spam folder on my IMAP account today, I noticed, that KMail sorts the messages wrongly. I sort via arrival date, but the sorting was jumbled. However, I tried to mark all messages as read, which did not work. When I now select each message to be marked as read, KMail will crash very soon. I will attach a backtrace of this.
Comment 1 Arne Schmitz 2008-06-30 08:06:46 UTC
Created attachment 25718 [details]
Backtrace of crashing Kontact, while reading wrongly sorted emails.
Comment 2 Arne Schmitz 2008-06-30 08:27:02 UTC
Created attachment 25720 [details]
Better backtrace, with line number information
Comment 3 Christophe Marin 2008-06-30 12:18:15 UTC
Please paste backtraces in the description, this makes finding duplicates in the future easier for us.

Using host libthread_db library "/lib/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread 0xb5f726d0 (LWP 6836)]
[New Thread 0xb3461b90 (LWP 6840)]
[New Thread 0xb3c62b90 (LWP 6839)]
[New Thread 0xb4463b90 (LWP 6838)]
[New Thread 0xb4c64b90 (LWP 6837)]
[KCrash handler]
#6  0xffffe410 in __kernel_vsyscall ()
#7  0xb67718f5 in raise () from /lib/libc.so.6
#8  0xb67731e1 in abort () from /lib/libc.so.6
#9  0xb6937380 in __gnu_cxx::__verbose_terminate_handler ()
   from /usr/lib/libstdc++.so.6
#10 0xb6934c25 in ?? () from /usr/lib/libstdc++.so.6
#11 0xb6934c62 in std::terminate () from /usr/lib/libstdc++.so.6
#12 0xb6935505 in __cxa_pure_virtual () from /usr/lib/libstdc++.so.6
#13 0xb5118ecf in KMReaderWin::setMsg (this=0x83aeb30, aMsg=0x8a7f908, 
    force=false) at /usr/src/debug/kdepim-3.5.9/kmail/kmreaderwin.cpp:1207
#14 0xb529202e in KMMainWidget::slotMsgSelected (this=0x869ee38, msg=0x8a7f908)
    at /usr/src/debug/kdepim-3.5.9/kmail/kmmainwidget.cpp:2115
#15 0xb52a2c0d in KMMainWidget::qt_invoke (this=0x869ee38, _id=55, 
    _o=0xbfc575a4) at /usr/src/debug/kdepim-3.5.9/kmail/kmmainwidget.moc:498
#16 0xb6c0597d in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#17 0xb50bd70e in KMHeaders::selected (this=0x86a8958, t0=0x8a7f908)
    at /usr/src/debug/kdepim-3.5.9/kmail/kmheaders.moc:260
#18 0xb50c5f3b in KMHeaders::highlightMessage (this=0x86a8958, lvi=0x8a42580, 
    markitread=false) at /usr/src/debug/kdepim-3.5.9/kmail/kmheaders.cpp:2072
#19 0xb50c637c in KMHeaders::highlightMessage (this=0x86a8958, i=0x8a42580)
    at /usr/src/debug/kdepim-3.5.9/kmail/kmheaders.cpp:2351
#20 0xb50cfc4a in KMHeaders::qt_invoke (this=0x86a8958, _id=107, _o=0xbfc576e4)
    at /usr/src/debug/kdepim-3.5.9/kmail/kmheaders.moc:305
#21 0xb6c0597d in QObject::activate_signal ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#22 0xb6f4d021 in QListView::currentChanged ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#23 0xb6ce590e in QListView::setCurrentItem ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#24 0xb6ce8896 in QListView::contentsMousePressEventEx ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#25 0xb6ce9244 in QListView::contentsMousePressEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#26 0xb741472d in KListView::contentsMousePressEvent (this=0x86a8958, 
    e=0xbfc579e4) at ./kdeui/klistview.cpp:805
#27 0xb50c64a5 in KMHeaders::contentsMousePressEvent (this=0x86a8958, 
    e=0xbfc579e4) at /usr/src/debug/kdepim-3.5.9/kmail/kmheaders.cpp:2235
#28 0xb6d1a7a1 in QScrollView::viewportMousePressEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#29 0xb6d17b36 in QScrollView::eventFilter ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#30 0xb6ce66e6 in QListView::eventFilter () from /usr/lib/qt3/lib/libqt-mt.so.3
#31 0xb50c2a49 in KMHeaders::eventFilter (this=0x86a8958, o=0xbfc579e4, 
    e=0xbfc57e60) at /usr/src/debug/kdepim-3.5.9/kmail/kmheaders.cpp:250
#32 0xb6c0519c in QObject::activate_filters ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#33 0xb6c0520b in QObject::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#34 0xb6c3e69c in QWidget::event () from /usr/lib/qt3/lib/libqt-mt.so.3
#35 0xb6ba716c in QApplication::internalNotify ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#36 0xb6ba8093 in QApplication::notify () from /usr/lib/qt3/lib/libqt-mt.so.3
#37 0xb7252632 in KApplication::notify (this=0xbfc5834c, receiver=0x86a9210, 
    event=0xbfc57e60) at ./kdecore/kapplication.cpp:552
#38 0xb6b4666a in QETWidget::translateMouseEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#39 0xb6b45436 in QApplication::x11ProcessEvent ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#40 0xb6b56240 in QEventLoop::processEvents ()
   from /usr/lib/qt3/lib/libqt-mt.so.3
#41 0xb6bbdcf0 in QEventLoop::enterLoop () from /usr/lib/qt3/lib/libqt-mt.so.3
#42 0xb6bbdb86 in QEventLoop::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#43 0xb6ba6cdf in QApplication::exec () from /usr/lib/qt3/lib/libqt-mt.so.3
#44 0x0805bf33 in main (argc=)
    at /usr/src/debug/kdepim-3.5.9/kontact/src/main.cpp:163
#45 0xb675dfe0 in __libc_start_main () from /lib/libc.so.6
#46 0x0805b601 in _start ()
Comment 4 Jaime Torres 2009-04-04 11:26:33 UTC
In kmail 1.11.x (kde 4.2.x), the new message list sorts the messages (allways) as desired.

Have you experienced the crash again? If so, Are you able to produce it at will?
Comment 5 Arne Schmitz 2009-04-04 11:33:50 UTC
No, I think it works for now. I will reopen, if I ever encounter it again.