Bug 1724984

Summary:	[ECompEditor] Ensure attendee changes stored before save
Product:	Red Hat Enterprise Linux 8	Reporter:	Michal Odehnal <modehnal>
Component:	evolution	Assignee:	Milan Crha <mcrha>
Status:	CLOSED ERRATA	QA Contact:	Desktop QE <desktop-qa-list>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.1
Target Milestone:	rc
Target Release:	8.0
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:	evolution-3.28.5-9.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-11-05 22:39:23 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 Michal Odehnal 2019-06-28 08:04:22 UTC

Description of problem:
In Meeting editor when attendee text field is still being focused and not confirmed, I am allowed Save & Close the editor, but the attendee is required and after clicking on the created meeting, evolution will segfault

Version-Release number of selected component (if applicable):
evolution-data-server-3.28.5-11.el8.x86_64
evolution-3.28.5-8.el8.x86_64
evolution-ews-3.28.5-5.el8.x86_64

How reproducible:
Always

Steps to Reproduce:
1. Open evolution.
2. Calendar -> File -> New -> Meeting.
3. In Editor write random Summary.
4. Click Add button.
5. Write an email. Do not confirm by Enter, have it focused.
6. Click Save & Close -> click Do Not Send.


Actual results:
Save is allowed, but upon clicking on the meeting, evolution will segfault.

Expected results:
Save is not allowed.

Additional info:

Comment 1 Milan Crha 2019-06-28 09:23:13 UTC

Thanks for a bug report. Related Fedora bug is bug #1721543. I've an upstream fix for it [1], thus acking.

[1] https://gitlab.gnome.org/GNOME/evolution/commit/dab5df03ed

Comment 3 Michal Odehnal 2019-07-03 13:15:38 UTC

Cannot reproduce with evolution-3.28.5-9.el8

Comment 5 errata-xmlrpc 2019-11-05 22:39:23 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2019:3699