When I delete or move an email to another folder the currently selected email correctly moves to highlighting the next email in the list but will randomly move the position of the list to somewhere else so you can't actually see the currently selected email so it requires a lot of manual scrolling. This is in "Vertical View" with Preview and Groups/Treads enabled. evolution-ews-3.2.3-1.fc16.x86_64 evolution-NetworkManager-3.2.3-1.fc16.x86_64 evolution-3.2.3-1.fc16.x86_64 evolution-data-server-3.2.3-2.fc16.x86_64 evolution-help-3.2.3-1.fc16.noarch evolution-mapi-3.2.3-1.fc16.x86_64
Thanks for a bug report. What do you sort by? Right click above the table header (for example above the Messages) and pick "Customize Current View...", then there is shown what you are sorting by. It should be related. I have there "Not sorted" and it does not jump here and there when I'm deleting messages in threads. The current algorithm, for message delete, is that the evolution selects the next message in the view, before it removes the message user currently marked for deletion. If you sort by date and you have threads sorted by latest date in it, then the thread itself can change its position, but you should be on the next message already, which is, for me, the next latest message/thread in my view (I usually sort by date with newest at bottom).
Sorted by "Date (decending)". The next message is selected correctly as expected but the view scrolls down to some random location. If I hold the mouse over the scroll bar and use the wheel to scroll back to the selected message it's what I would expect (and want) to be selected, it's just that the selected message isn't viewable in the list of messages.
Can it be related to this thread [1]? It doesn't have a solution, it just sounds like a similar symptoms. I'm asking, because with your "Date (descending)" (newest at top) sort-by I can reproduce the move of the whole thread to its new position, but I have the view scrolled to the right position, selected message is kept visible. I'm trying in one of my On This Computer subfolders. This is with evolution-3.2.3-1.fc16.x86_64 gtk3-3.2.3-1.fc16.x86_64 [1] http://mail.gnome.org/archives/evolution-list/2012-January/msg00176.html
This message is a reminder that Fedora 16 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 16. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '16'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 16's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 16 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged to click on "Clone This Bug" and open it against that version of Fedora. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Still seeing it on F-18 with IMAP using the following verisons: evolution-ews-3.6.3-1.fc18.x86_64 evolution-data-server-3.6.3-2.fc18.x86_64 evolution-3.6.3-2.fc18.x86_64
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '18'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.