Bug 450353

Summary:	[evolution] hide deleted messages intermittently stop working
Product:	[Fedora] Fedora	Reporter:	Dave Maley <dmaley>
Component:	evolution	Assignee:	Matthew Barnes <mbarnes>
Status:	CLOSED UPSTREAM	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	low	Docs Contact:
Priority:	low
Version:	9	CC:	bojan, christoph.wickert, mcrha, mike, mitr
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2008-06-09 12:10:24 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dave Maley 2008-06-06 21:48:53 UTC

Description of problem:
After upgrading to evolution-2.22.2-2 today I'm seeing problems w/ the "Hide
Deleted Messages" view option.  When deleting (or moving an email to a folder)
the msg will sometimes remain as a striked msg.


Version-Release number of selected component (if applicable):
evolution-2.22.2-2.fc9.x86_64

How reproducible:
intermittent

Steps to Reproduce:
1. delete an email, or move email to folder
2.
3.
  
Actual results:
striked msg remains

Expected results:
deleted message no londer displayed

Additional info:
* I never encountered this problem before upgrading to 2.22.2-2 (was previously
running 2.22.1-2).
* I tried moving my .evolution out of the way but the problem persisted

Comment 1 Milan Crha 2008-06-09 12:08:28 UTC

*** Bug 450391 has been marked as a duplicate of this bug. ***

Comment 2 Milan Crha 2008-06-09 12:10:24 UTC

Thanks for reporting this. We are solving this as a part of the upstream bug
[1], patches there comes to 2.22.x too.

[1] http://bugzilla.gnome.org/show_bug.cgi?id=535749

Comment 3 Matthew Barnes 2008-06-13 05:07:47 UTC

*** Bug 451161 has been marked as a duplicate of this bug. ***

Comment 4 Milan Crha 2008-06-17 16:14:35 UTC

*** Bug 451811 has been marked as a duplicate of this bug. ***