Bug 106734 - Fullscreen GL applications aren't visible with Xwayland, or there's Weston panel on top of it
Summary: Fullscreen GL applications aren't visible with Xwayland, or there's Weston pa...
Status: RESOLVED MOVED
Alias: None
Product: Wayland
Classification: Unclassified
Component: weston (show other bugs)
Version: unspecified
Hardware: Other All
: high major
Assignee: Wayland bug list
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-05-30 15:00 UTC by Eero Tamminen
Modified: 2019-03-05 16:39 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Eero Tamminen 2018-05-30 15:00:09 UTC
Setup:
- Skylake i5 (BXT had same issue too)
- Git versions of:
  - kernel (support atomic modesetting)
  - X server / Xwayland
  - Mesa
  - Weston
  (latest releases may be enough, but hasn't been tested)
- New enough dependencies for above, so that modifiers are supported
- GL application supporting fullscreen in both X and Wayland:
  # apt install glmark2 glmar2-wayland

Test-case:
- Start Weston with --xwayland
- Start fullscreen Wayland GL application:
  glmark2-wayland --fullscreen
- Start fullscreen X GL application:
  glmark2 --fullscreen
- Start windowed X GL application:
  glmark2

Expected outcome:
- Fullscreen X GL application works as well through XWayland, as native Wayland GL applications

Actual outcome:
- Wayland GL application fullscreen window works fine
- X GL application fullscreen window never becomes visible
  - Or with some applications, it appears on random runs, after random delay, but with Weston panel on top of it instead of as fullscreen
- Windowed X GL application windows work fine

Notes:
- Same thing regardless of whether application uses GLES or GL, glX or EGL
- With some fullscreen GL benchmarks, the window appears after a while, but in that case it's below the Weston panel i.e. not really fullscreen
  - Whether and when the (non-fullscreen) window appears seems *completely random*
  - I've seen this most reliably with Ungine Heaven and Valley benchmarks

I haven't tried XWayland before, but I assume it must be a regression.

Xprop and Xwininfo report following for the running invisible glmark2 window:
---------------------
_NET_WM_DESKTOP(CARDINAL) = 0
WM_STATE(WM_STATE):
		window state: Normal
		icon window: 0x0
WM_PROTOCOLS(ATOM): protocols  WM_DELETE_WINDOW
WM_NAME(STRING) = "glmark2 2014.03+git20150611.fa71af2d"
_NET_WM_STATE(ATOM) = _NET_WM_STATE_FULLSCREEN
---------------------
  Absolute upper-left X:  0
  Absolute upper-left Y:  0
  Relative upper-left X:  0
  Relative upper-left Y:  0
  Width: 1920
  Height: 1080
  Depth: 24
  Visual: 0x24
  Visual Class: TrueColor
  Border width: 0
  Class: InputOutput
  Colormap: 0x400001 (not installed)
  Bit Gravity State: ForgetGravity
  Window Gravity State: NorthWestGravity
  Backing Store State: NotUseful
  Save Under State: no
  Map State: IsViewable
  Override Redirect State: no
  Corners:  +0+0  -0+0  -0-0  +0-0
  -geometry 1920x1080+0+0
---------------------
(This was on FullHD monitor.)
Comment 1 Olivier Fourdan 2018-05-30 15:15:10 UTC
This looks more of a weston/xwm issue than Xwayland actually.
Comment 2 Olivier Fourdan 2018-05-30 15:19:05 UTC
Reproduced under weston, yet the same works fine GNOME on Wayland → moving to weston.
Comment 3 Eero Tamminen 2018-06-04 13:34:18 UTC
(In reply to Olivier Fourdan from comment #2)
> Reproduced under weston, yet the same works fine GNOME on Wayland → moving
> to weston.

Increasing importance.  Fullscreen (XWayland) windows not being visible is at least high major issue.
Comment 4 GitLab Migration User 2018-06-08 23:56:32 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/wayland/weston/issues/114.
Comment 5 Eero Tamminen 2019-03-05 16:39:04 UTC
(In reply to GitLab Migration User from comment #4)
> You can subscribe and participate further through the new bug through this
> link to our GitLab instance:
> https://gitlab.freedesktop.org/wayland/weston/issues/114.

Ping.  I haven't seen any activity either here, or in gitlab bug tracker for this issue.  Any idea what's causing it / who might be looking into it?

(Commenting here as I haven't registered to gitlab tracker.)


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.