After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 743959 - Automatically collapsing threads after folder update
Automatically collapsing threads after folder update
Status: RESOLVED FIXED
Product: evolution
Classification: Applications
Component: Mailer
3.12.x (obsolete)
Other Linux
: Normal normal
: ---
Assigned To: evolution-mail-maintainers
Evolution QA team
Depends on:
Blocks:
 
 
Reported: 2015-02-04 07:00 UTC by Milan Crha
Modified: 2015-02-04 07:06 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Milan Crha 2015-02-04 07:00:06 UTC
Moving this from a downstream bug report:
https://bugzilla.redhat.com/show_bug.cgi?id=1148978

Description of problem:
Much of the time, when I expand a thread with unread messages in it, then click on one of the unread message titles, Evolution will collapse the thread and show me only the first message in it instead.

Version-Release number of selected component (if applicable):
evolution-3.12.6-1.fc21.x86_64

How reproducible:
Often, but not 100%

Steps to Reproduce:
1. Collapse all the threads in a mailing list (I use ctrl-alt-b for this)
2. Browse down to a thread with unread messages.
3. Expand the thread.
4. Click on an unread message.

Actual results:
The thread collapses and shows me the contents of the first email in the thread. The thread has to be expanded again. Clicking on the unread message works after expanding the thread for the second time.

Expected results:
Evolution should just display the requested email and not collapse the thread.
Comment 1 Milan Crha 2015-02-04 07:06:51 UTC
After some investigation, the problem was that the message list's 'searching' check didn't agree in message_list_regen_done_cb() and message_list_regen_idle_cb(). The later caused that the current expand state was not saved to the disk, neither the current state was remembered to be used at the former function, thus an old expand state had been loaded from the disk, which was the one with all threads collapsed.

Created commit 4c1da5e in evo master (3.13.90+) [1]
Created commit 69d6222 in evo evolution-3-12 (3.12.11+)

https://git.gnome.org/browse/evolution/commit/?id=4c1da5e