GNOME Bugzilla – Bug 598984
Evolution reorders threaded messages incorrectly after deletion
Last modified: 2009-10-22 14:58:17 UTC
When showing the message list with threading and by date, Evolution correctly shows the oldest message in the thread first. When deleting the first message, Evolution sometimes messes up the order and shows the second oldest message first. When this happens, Evolution still moves the message selector to the next oldest message - but it is now the second message listed in the thread with the second oldest listed first. See attached screenshots.
Created attachment 145804 [details] screenshot showing evolution listing a thread correctly The first message is the oldest message and is selected and about to be deleted.
Created attachment 145805 [details] screenshot showing evolution listing a thread incorrectly After deleting the oldest message in a thread, the next oldest message is selected automatically, but it is now listed second with the second oldest message listed first. This happens to me quite a lot - with one type of messages that I receive (cron reports as can be seen in the shortcut) its rather rare and only happens once every 10 times or so. With another type of threaded messages where the time difference between messages is very short (sometimes only a few seconds), it happens almost all the time - so it might be some problem in the date sort algorithm.
After looking a bit closer into it, I believe that this problem always occurs if the two threaded message's time stamps are less then 5 minutes apart.
Could you uncheck View->Hide deleted messages and give here say 3-5 messages of the offending thread? Feel free to sanitize the content with anything but Date header, which would be the best to have it as is. What is the account type it is doing this on? I know there was a bug report about unsorted messages not sorted by appearance in the store (very close to UID), but I thought it was fixed already.
I'm using a MAPI account, and it is sorted by by Date ascending - i.e. older messages are shown above newer messages - according to the date header, not delivery order which I assume is what you mean by "sorted by appearance". How do you want me to show the messages here?
Created attachment 145983 [details] another incorrectly ordered thread - deleted messages shown Here is a screen shot showing a thread (that experienced the incorrect ordering issue) with deleted messages shown. The first two undeleted messages are problematic - they're dates are only 1 second apart and in this view they are ordered correctly, as they were if the deleted messages were not deleted.
Created attachment 145984 [details] another incorrectly ordered thread - deleted messages hidden Here is the second screenshot showing the same thread with the deleted messages hidden. Note that the selected message in this screenshot (that is a bit hard to notice due to the color scheme) is the same one from the previous screenshot, though here it is shown second even though its date header has a time earlier by 1 second. Here are the headers for the selected message: ---8<--- Received: from server520.appriver.com ([72.32.252.97]) by office.taboola.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 21 Oct 2009 03:59:59 +0200 Received: from [10.242.228.180] (HELO inbound.appriver.com) by server520.appriver.com (CommuniGate Pro SMTP 5.2.11) with ESMTP id 212913060 for alerts@taboola.com; Tue, 20 Oct 2009 20:59:59 -0500 ... Received: from [82.80.226.115] (HELO prod2-f5.taboolasyndication.com) by inbound.appriver.com (CommuniGate Pro SMTP 5.1.9) with ESMTP id 142268005 for alerts@taboola.com; Tue, 20 Oct 2009 20:59:57 -0500 Received: from prod2-f5.taboolasyndication.com (localhost.localdomain [127.0.0.1]) by prod2-f5.taboolasyndication.com (Postfix) with ESMTP id B320B119858A for <alerts@taboola.com>; Wed, 21 Oct 2009 03:59:51 +0200 (IST) Date: Wed, 21 Oct 2009 03:59:51 +0200 (IST) From: alerts@taboola.com To: alerts@taboola.com Message-ID: <1494004073.11011256090391705.JavaMail.taboola@prod2-f5.taboolasyndication.com> Subject: [TRC] Taboola Service Error (prod2-f5.taboolasyndication.com) ... X-OriginalArrivalTime: 21 Oct 2009 01:59:59.0523 (UTC) FILETIME=[31F00730:01CA51F2] ... ---8<--- and here are the headers for the second message: ---8<--- Received: from server520.appriver.com ([72.32.252.97]) by office.taboola.com with Microsoft SMTPSVC(6.0.3790.3959); Wed, 21 Oct 2009 03:59:54 +0200 Received: from [10.242.228.181] (HELO inbound.appriver.com) by server520.appriver.com (CommuniGate Pro SMTP 5.2.11) with ESMTP id 212913031 for alerts@taboola.com; Tue, 20 Oct 2009 20:59:54 -0500 ... Received: from [82.80.226.115] (HELO prod2-f5.taboolasyndication.com) by inbound.appriver.com (CommuniGate Pro SMTP 5.1.9) with ESMTP id 142458950 for alerts@taboola.com; Tue, 20 Oct 2009 20:59:51 -0500 Received: from prod2-f5.taboolasyndication.com (localhost.localdomain [127.0.0.1]) by prod2-f5.taboolasyndication.com (Postfix) with ESMTP id 266A2119858B for <alerts@taboola.com>; Wed, 21 Oct 2009 03:59:52 +0200 (IST) Date: Wed, 21 Oct 2009 03:59:52 +0200 (IST) From: alerts@taboola.com To: alerts@taboola.com Message-ID: <1086111751.11021256090392155.JavaMail.taboola@prod2-f5.taboolasyndication.com> Subject: [TRC] Taboola Service Error (prod2-f5.taboolasyndication.com) ... X-OriginalArrivalTime: 21 Oct 2009 01:59:54.0789 (UTC) FILETIME=[2F1DAD50:01CA51F2] ... ---8<--- I hope that helps. Please let me know if you want me to provide a sample in another way.
Thanks for the data, I found the issue and also that this one is a duplicate of some older, thus I'm marking it as such and let's move there. *** This bug has been marked as a duplicate of bug 484839 ***