Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Bug 1957807

Summary: Gdk-Message: 13:44:53.888: Error 22 (Invalid argument) dispatching to Wayland display.
Product: Red Hat Enterprise Linux 9 Reporter: Michal Odehnal <modehnal>
Component: mutterAssignee: Jonas Ã…dahl <jadahl>
Status: CLOSED CURRENTRELEASE QA Contact: Michal Odehnal <modehnal>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 9.0CC: fmuellner, jadahl, jkoten, mkrajnak, pvlasin, tpelka
Target Milestone: betaKeywords: TestBlocker, Triaged
Target Release: 9.0 BetaFlags: pm-rhel: mirror+
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: mutter-40.4-3.el9_b Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
: 2003032 (view as bug list) Environment:
Last Closed: 2021-12-07 21:33:05 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:
Bug Depends On:    
Bug Blocks: 2003032    
Attachments:
Description Flags
wayland_debug_log none

Description Michal Odehnal 2021-05-06 14:02:59 UTC
Created attachment 1780314 [details]
wayland_debug_log

Description of problem:
When running our desktop automation tests under Wayland - via python3 - the wl_display will sometime attempt to delete the same display twice and the communication between client(python3) and compositor will end with message: Gdk-Message: 13:44:53.888: Error 22 (Invalid argument) dispatching to Wayland display.

Version-Release number of selected component (if applicable):
mutter-40.0-5.el9.x86_64

How reproducible:
Not 100% but eventually will appear.

Steps to Reproduce:
Do not have step by step reproducer. See attachment.

Actual results:
Gdk-Message: 13:44:53.888: Error 22 (Invalid argument) dispatching to Wayland display.

In attached log you can see the attempted delete being done twice and error being thrown:
[2290116.343] wl_display(30)
[2304123.380] wl_display(30)
[2305128.434] wl_display(wl_display@1, 0, "invalid object 30")


Expected results:
No error in journal and the communication between the client and compositor not being ended.

Additional info:
Issue filed upstream as it can be reproduced on Fedora 35 also https://gitlab.gnome.org/GNOME/mutter/-/issues/1797

Comment 3 Michal Odehnal 2021-09-08 09:12:28 UTC
I am no longer able to reproduce the issue with the fix provided by Olivier in https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/77 , he made a scratch build for rhel-9 which I run on multiple machines and multiple test suites and not a single occurrence of this issue was found.