Bug 2126523

Summary:	Prepare for webkit2gtk3 2.40.x
Product:	Red Hat Enterprise Linux 8	Reporter:	Milan Crha <mcrha>
Component:	evolution	Assignee:	Milan Crha <mcrha>
Status:	CLOSED ERRATA	QA Contact:	Michal Odehnal <modehnal>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.7	Keywords:	Triaged
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:	evolution-3.28.5-22.el8	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-05-16 08:15:45 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 Milan Crha 2022-09-13 17:50:56 UTC

Evolution depends on frame-flattening setting on the WebKitGTK side to show the mail preview properly. The WebKitGTK 2.37.90 dropped the functionality, while keeping the relevant option existing, even it did nothing. That had been reported upstream [1]. The 2.38.0 will have the functionality returned, but the next major release of the WebKitGTK 2.40.x will have the frame-flattening gone again.

The change at [1] uses the frame-flattening conditionally, only for 2.38.x and below and simulates the option when a newer WebKitGTK is used (the version is checked in runtime, not in compile time).

I want to apply the upstream patch now, to have the code ready for the users. Even if there will be found any problems with the patch, it can be updated later. The main point is that the users will be able to use Evolution once the related WebKitGTK reaches RHEL, without a need to rebuild Evolution.

[1] https://gitlab.gnome.org/GNOME/evolution/-/issues/2001

Comment 5 errata-xmlrpc 2023-05-16 08:15:45 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 (evolution bug fix and enhancement update), 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/RHBA-2023:2749