Bug 161844

Summary:	folder mis-sorted, messages not shown
Product:	[Unmaintained] kmail	Reporter:	Andras Georgy Bekes <bekesa>
Component:	IMAP	Assignee:	kdepim bugs <pim-bugs-null>
Status:	RESOLVED FIXED
Severity:	crash	CC:	christophe, lemma
Priority:	NOR	Keywords:	triaged
Version First Reported In:	1.9.9
Target Milestone:	---
Platform:	Debian testing
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:
Attachments:	KMail crashed.

Description Andras Georgy Bekes 2008-05-09 13:28:57 UTC

Version:            (using KDE 3.5.9)
Installed from:    Debian testing/unstable Packages

While reading mails in an IMAP folder (reading, deleting, reading next, etc, periodic reloads), the sorting of messages suddenly gets screwed up. The unread messages get to the top of the list (while they should be in the bottom of the list, my folders are sorted according to "Order of Arrival"). After this event, the unread messages can't be read, if I select them, their message body remains blank.

Switching to other folder and switching back doesn't help, neither restarting kmail. When switching from the screwed up folder to another and back, kmail crashes with some probability, but not always.

The only workaround I've found is deleting 
~/.kde/share/apps/kmail/imap/.$WHEIRD_NUMBER.directory/.$FOLDERNAME.index.*
files.

I can't reproduce the bug intentionally, but it happens like once or twice a week, so it's getting annoying. The problem appeared about a month ago I think.

Comment 1 Andras Georgy Bekes 2008-06-04 15:56:58 UTC

For I don't know why but this bug shows up more frequently, now I meet with it several times a day.

Comment 2 Christophe Marin 2008-08-05 14:00:01 UTC

> For I don't know why but this bug shows up more frequently, now I meet with it several times a day.

If kmail crashes, can you install the package that contains the debug symbols and post a backtrace ?

You will find instructions on this page: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Comment 3 Andras Georgy Bekes 2008-08-13 10:41:26 UTC

Created attachment 26819 [details]
KMail crashed.

Comment 4 Andras Georgy Bekes 2008-08-13 10:42:18 UTC

I'm using debian and have installed kdepim-dbg and kdelibs-dbg (there is no kmail-dbg package).

The kcrash file is attached.

Comment 5 Christophe Marin 2008-08-13 10:58:46 UTC

[Thread debugging using libthread_db enabled]
[New Thread 0xb5e666c0 (LWP 18194)]
[New Thread 0xb3367b90 (LWP 18199)]
[New Thread 0xb3b68b90 (LWP 18198)]
[New Thread 0xb4369b90 (LWP 18197)]
[New Thread 0xb4b6ab90 (LWP 18196)]
[KCrash handler]
#6  0xb4e66f89 in KMFolder::open (this=0x0, owner=0xb51b206a "kmmovecommand")
    at /tmp/buildd/kdepim-3.5.9/./kmail/kmfolder.cpp:476
#7  0xb4ffbfe9 in KMMoveCommand::execute (this=0x8eb33e8)
    at /tmp/buildd/kdepim-3.5.9/./kmail/kmcommands.cpp:2158
#8  0xb4fec3d8 in KMCommand::slotPostTransfer (this=0x8eb33e8, 
    result=KMCommand::OK)
    at /tmp/buildd/kdepim-3.5.9/./kmail/kmcommands.cpp:263
#9  0xb5001b14 in KMCommand::qt_invoke (this=0x8eb33e8, _id=5, _o=0xbf851934)
    at ./kmcommands.moc:148
#10 0xb5001f4b in KMMenuCommand::qt_invoke (this=0x8eb33e8, _id=5, 
    _o=0xbf851934) at ./kmcommands.moc:2801
#11 0xb5001fab in KMMoveCommand::qt_invoke (this=0x8eb33e8, _id=5, 
    _o=0xbf851934) at ./kmcommands.moc:2987
#12 0xb500204b in KMDeleteMsgCommand::qt_invoke (this=0x8eb33e8, _id=5, 
    _o=0xbf851934) at ./kmcommands.moc:3062
#13 0xb6f6ef6d in QObject::activate_signal (this=0x8eb33e8, clist=0x8c6c110, 
    o=0xbf851934) at kernel/qobject.cpp:2359
#14 0xb4fea5ce in KMCommand::messagesTransfered (this=0x8eb33e8, 
    t0=KMCommand::OK) at ./kmcommands.moc:126
#15 0xb50030bc in KMCommand::transferSelectedMsgs (this=0x8eb33e8)
    at /tmp/buildd/kdepim-3.5.9/./kmail/kmcommands.cpp:358
#16 0xb5003208 in KMCommand::slotStart (this=0x8eb33e8)
    at /tmp/buildd/kdepim-3.5.9/./kmail/kmcommands.cpp:255
#17 0xb5001af0 in KMCommand::qt_invoke (this=0x8eb33e8, _id=4, _o=0xbf851ae4)
    at ./kmcommands.moc:147
#18 0xb5001f4b in KMMenuCommand::qt_invoke (this=0x8eb33e8, _id=4, 
    _o=0xbf851ae4) at ./kmcommands.moc:2801
#19 0xb5001fab in KMMoveCommand::qt_invoke (this=0x8eb33e8, _id=4, 
    _o=0xbf851ae4) at ./kmcommands.moc:2987
#20 0xb500204b in KMDeleteMsgCommand::qt_invoke (this=0x8eb33e8, _id=4, 
    _o=0xbf851ae4) at ./kmcommands.moc:3062
#21 0xb6f6ef6d in QObject::activate_signal (this=0x8678ec8, clist=0x8b1dfb8, 
    o=0xbf851ae4) at kernel/qobject.cpp:2359
#22 0xb729905e in QSignal::signal (this=0x8678ec8, t0=@0x8678ef0)
    at .moc/release-shared-mt/moc_qsignal.cpp:100
#23 0xb6f8a8c7 in QSignal::activate (this=0x8678ec8) at kernel/qsignal.cpp:215
#24 0xb6f91993 in QSingleShotTimer::event (this=0x8678ea0)
    at kernel/qtimer.cpp:289
#25 0xb6f1118a in QApplication::internalNotify (this=0xbf8520f8, 
    receiver=0x8678ea0, e=0xbf851de4) at kernel/qapplication.cpp:2638
#26 0xb6f11f76 in QApplication::notify (this=0xbf8520f8, receiver=0x8678ea0, 
    e=0xbf851de4) at kernel/qapplication.cpp:2361
#27 0xb75c1c22 in KApplication::notify (this=0xbf8520f8, receiver=0x8678ea0, 
    event=0xbf851de4)
    at /tmp/buildd/kdelibs-3.5.9.dfsg.1/./kdecore/kapplication.cpp:550
#28 0xb6f0656e in QEventLoop::activateTimers (this=0x85b13e0)
    at kernel/qapplication.h:523
#29 0xb6ec0348 in QEventLoop::processEvents (this=0x85b13e0, flags=4)
    at kernel/qeventloop_x11.cpp:392
#30 0xb6f27b80 in QEventLoop::enterLoop (this=0x85b13e0)
    at kernel/qeventloop.cpp:201
#31 0xb6f27a16 in QEventLoop::exec (this=0x85b13e0)
    at kernel/qeventloop.cpp:148
#32 0xb6f10cff in QApplication::exec (this=0xbf8520f8)
    at kernel/qapplication.cpp:2761
#33 0x0805b89a in main (argc=0, argv=0x509)
    at /tmp/buildd/kdepim-3.5.9/./kontact/src/main.cpp:163

Comment 6 Andras Georgy Bekes 2008-08-28 14:10:15 UTC

Since I sent the backtrace, every time kmail crashes again I check whether it's the same as what I sent. I checked like 4 or 5 such backtraces and it is always exactly the same (file names and line numbers match).

The crash always happens after the folder gets mis-sorted and I switch to another folder and back. If I quit kmail after the folder gets screwed up and delete ~/.kde/share/apps/kmail/imap/.$WHEIRD_NUMBER.directory/.$FOLDERNAME.index.* files, everything works again.

Comment 7 Andras Georgy Bekes 2009-01-26 10:46:23 UTC

I still have this problem with KMail 1.9.9, both with an m$ exchange IMAP server and a Sun IMAP server (a "Sun Java System Messaging Server" I think).

Comment 8 Michael Leupold 2009-04-04 17:08:09 UTC

Is this bug still reproducible using KMail 1.9.10 or even one of the KDE4 versions? Unfortunately I don't get it here (trunk r948809).

Comment 9 Andras Georgy Bekes 2009-04-06 11:42:18 UTC

I am still using KMail 1.9.9. and the problem still exists (I'm quitting KMail and deleting  ~/.kde/share/apps/kmail/imap/.$WHEIRD_NUMBER.directory/.$FOLDERNAME.index.* several times a day).

I will switch to KMail 1.9.10 or KDE 4.2 whenever they enter Debian testing.

Comment 10 Christophe Marin 2009-05-23 14:01:00 UTC

(In reply to comment #9)
> I am still using KMail 1.9.9. and the problem still exists (I'm quitting KMail
> and deleting 
> ~/.kde/share/apps/kmail/imap/.$WHEIRD_NUMBER.directory/.$FOLDERNAME.index.*
> several times a day).
> 
> I will switch to KMail 1.9.10 or KDE 4.2 whenever they enter Debian testing.

Changing the bug status until we get some feedback with KMail from KDE > 4.2

Comment 11 Andras Georgy Bekes 2009-10-13 10:41:08 UTC

It seems the bug does not exist on KDE 4.3 (KMail 1.12.1).