Bug 94735 - Weston renders sub-surface even if parent is not mapped
Summary: Weston renders sub-surface even if parent is not mapped
Status: RESOLVED MOVED
Alias: None
Product: Wayland
Classification: Unclassified
Component: weston (show other bugs)
Version: unspecified
Hardware: Other All
: medium normal
Assignee: Wayland bug list
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2016-03-29 07:38 UTC by Martin Flöser
Modified: 2018-06-08 23:54 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
WAYLAND_DEBUG output (274.27 KB, text/plain)
2016-03-29 07:38 UTC, Martin Flöser
Details

Description Martin Flöser 2016-03-29 07:38:41 UTC
Created attachment 122602 [details]
WAYLAND_DEBUG output

Weston renders sub-surfaces with a not mapped parent. According to the Wayland spec a sub-surface should only be mapped if the parent is mapped: "A sub-surface becomes mapped, when a non-NULL wl_buffer is applied and the parent surface is mapped."

To reproduce:
* run systemsettings5
* go to Desktop Behavior -> Desktop Effects
* this creates a sub-surface tree with not mapped parents, but the child is visible

Please see the attached log with WAYLAND_DEBUG of systemsettings. The last child which is incorrectly rendered is wl_surface@97 which is a sub-surface to wl_surface@65, but wl_surface@65 never gets a buffer attached.

This is of course also a client bug which is reported at https://bugreports.qt.io/browse/QTBUG-52192, but of course the compositor should behave according to the spec ;-)
Comment 2 GitLab Migration User 2018-06-08 23:54:27 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/74.


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.