Bug 2232583

Summary:	WebKitGTK core dumps on s390x
Product:	Red Hat Enterprise Linux 8	Reporter:	Michal Odehnal <modehnal>
Component:	webkit2gtk3	Assignee:	Michael Catanzaro <mcatanza>
Status:	CLOSED MIGRATED	QA Contact:	Michal Odehnal <modehnal>
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	8.9	CC:	desktop-qa-list, dhorak, tpelka, tpopela
Target Milestone:	rc	Keywords:	MigratedToJIRA
Target Release:	---	Flags:	pm-rhel: mirror+
Hardware:	s390x
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2023-09-15 17:50:13 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 2023-08-17 13:24:14 UTC

This bug was initially created as a copy of Bug #2227691

I am copying this bug because: 



Description of problem:
Starting webkit MiniBrowser on s390x core dumps.

Version-Release number of selected component (if applicable):
webkit2gtk3-2.40.4-1.el9.s390x

How reproducible:
100%

Steps to Reproduce:
1. Have the devel packages installed so you have the Minibroswer present.
2. Open the browser $/usr/libexec/webkit2gtk-4.0/MiniBrowser https://html5test.com/
3.

Actual results:
Page does not open and core dump is generated.

Expected results:
Page opens with no issue and no core dump is present.

Additional info:

Comment 3 RHEL Program Management 2023-09-15 17:49:51 UTC

Issue migration from Bugzilla to Jira is in process at this time. This will be the last message in Jira copied from the Bugzilla bug.

Comment 4 RHEL Program Management 2023-09-15 17:50:13 UTC

This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "RHEL-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.