1186624 – X11-based applications unusable in GNOME wayland session

Bug 1186624 - X11-based applications unusable in GNOME wayland session

Summary: X11-based applications unusable in GNOME wayland session

Status:	RESOLVED DUPLICATE of bug 1186092

Alias:	None

Product:	openSUSE Distribution
Classification:	openSUSE
Component:	GNOME (show other bugs)
Version:	Leap 15.3
Hardware:	Other Other

Priority:	P5 - None Severity: Normal (vote)
Target Milestone:	---
Assignee:	E-mail List
QA Contact:	E-mail List

URL:
Whiteboard:
Keywords:

Depends on:
Blocks:

Clone This Bug

Reported:	2021-05-28 16:42 UTC by Vincent Untz
Modified:	2021-05-31 00:49 UTC (History)
CC List:	1 user (show)

See Also:
Found By:	---
Services Priority:
Business Priority:
Blocker:	---
Marketing QA Status:	---
IT Deployment:	---

Attachments
Example of a blank window (this is xeyes) (22.79 KB, image/png) 2021-05-28 16:42 UTC, Vincent Untz	Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.

Description Vincent Untz 2021-05-28 16:42:25 UTC

Created attachment 849788 [details]
Example of a blank window (this is xeyes)

(filing in GNOME, but this is probably lower in the stack)

I upgraded to Leap 15.3 yesterday, and am using the wayland session.

Every time I start a X11-based application, I only get some transparent window (that I see because of the drop shadow but that I can't interact with). I don't really have much to debug except lines like this one from journalctl:

gnome-shell[2271]: Modifiers specified, but DRI is too old

Comment 1 Yifan Jiang 2021-05-31 00:49:56 UTC

Hi Vincent,

This seems the same issue as bsc#1186092, this fix is on the way to maintenance update with the following change:

Tue May 18 11:23:30 UTC 2021 - Daike Yu <yu.daike@suse.com>

- U_xwayland-glamor-gbm-Handle-DRM_FORMAT_MOD_INVALID-gracefully.patch
  * xwayland: Fix invisible window produced by Xwayland
    (boo#1186092, boo#1184906)

Please feel free to reopen if we have more information to sync.

*** This bug has been marked as a duplicate of bug 1186092 ***