Bug 1254852

Summary:	Deleting multiple messages leaves cursor outside of view
Product:	[Fedora] Fedora	Reporter:	David Dillow <dave>
Component:	evolution	Assignee:	Milan Crha <mcrha>
Status:	CLOSED UPSTREAM	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	23	CC:	lucilanga, mbarnes, mcrha, tpopela
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-19 10:27:43 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description David Dillow 2015-08-19 05:16:30 UTC

Description of problem:
Selecting multiple messages and deleting them leaves the cursor outside of the viewport; moving the cursor using the keyboard snaps the viewport to the cursor.

Version-Release number of selected component (if applicable):
evolution-3.17.4-2.fc23.x86_64
evolution-3.16.5-1.fc22.x86_64 (and every version I've tried in 22)

How reproducible:
100% if CPU is not loaded.


Steps to Reproduce:
1. Select multiple messages (more than fit in the list view window). I use threaded-mode, but it is not clear that is a requirement for the bug.
2. Delete the messages.

Actual results:
Messages deleted, cursor is on next message after deleted ones, but is not visible in message list (nor is the message subject). Moving the cursor with the arrow keys scrolls the list such that it is visible.

Expected results:
Messages delete, cursor is on next message after deleted ones, with message list scrolled such that the cursor (highlighted message) is visible.

Additional info:
This appears to be a race condition, either in sending or processing events relating to the message list. If the CPU is unloaded, this is 100% reproducible. If I have a background compile going that makes heavy use of all cores, this is much less reproducible -- I suspect it can still happen, but I've not been able to do so.

Comment 1 Milan Crha 2015-08-19 10:27:43 UTC

Thanks for a bug report. A very similar bug is filled upstream [1], thus I'm closing this in a favour of the upstream bug report. Please see [1] for any further updates.

https://bugzilla.gnome.org/show_bug.cgi?id=677862