Commits on Source (11)
-
Don't forget to transfer the fullscreen setting from the config to the backend. Without this, weston tries to resize the window with the windowed output API but that is not registered with new_config.fullscreen == true. This code was accidentally lost in 0a5bb7ac ("backend-wayland: Use renderer enum type for config selection"). So just restore it. Signed-off-by: Michael Olbrich <m.olbrich@pengutronix.de> (cherry picked from commit 4ce6b1e4)
b9b56edc -
One .TP was lost, causing --wait-for-debugger section to be merged in the previous section. Fix it. Fixes 5ffda17e Signed-off-by: Pekka Paalanen <pekka.paalanen@collabora.com> (cherry picked from commit 406e3d2a)
314bb810 -
The override-redirect window will not be assigned a shell_surface object. If it is used as a parent window, it will cause a crash when calling the set_parent function. The EWMH specification does not describe the behavior of an override-redirect window as a parent window, so we should ignore this case. Signed-off-by: Liu, Kai1 <kai1.liu@intel.com> (cherry picked from commit b468687d)
6bfe0da0 -
In 2d70bdfd "drm-backend: add support to output capture writeback source" we've ensured that disable_planes should be false in order to support writeback capture tasks. But this was wrong; disable_planes is transient (it is true when there's some sort of content recording happening), and we enable/disable that during compositor's lifetime. This is dangerous and may result in a crash. Imagine the following sequence: 1. screen recording starts, disable_planes is set to true. 2. for whatever reason the output size changes, and we end up not updating capture info because we think that writeback is not supported by the device. 3. screen recording stops, disable_planes is set to false. 4. user tries to take a writeback screenshot, and the DRM-backend will pull a writeback capture task with weston_output_pull_capture_task(). 5. this function has an assert to ensure that the DRM-backend did not forget to update the capture info, and we hit that assert. With this patch we drop disable_planes being false as a condition to support writeback. So now we keep the capture info up-to-date even when screen recording is happening, and we gracefully fail writeback tasks. Signed-off-by: Leandro Ribeiro <leandro.ribeiro@collabora.com> (cherry picked from commit 6d8e3c56)
46c94eb3 -
Since 2d70bdfd "drm-backend: add support to output capture writeback source", the DRM-backend was broken for KMS devices that do not support the atomic API. This fixes that. We don't support writeback screenshots without atomic modeset support. So for such devices, we never update the output capture info (weston_output_update_capture_info()) for the writeback source. The function that we use to pull writeback tasks (weston_output_pull_capture_task()) asserts that the capture providers (renderers, DRM-backend) did not forget to update the capture info (size/format) if something changed. But as we've never updated the capture info for such devices, it is zeroed, leading to an assert hit. With this patch we only pull the capture task for KMS devices that support the atomic API. Signed-off-by: Leandro Ribeiro <leandro.ribeiro@collabora.com> (cherry picked from commit 32264175)
8b0c2e31 -
If the source is not supported, we won't receive the capture information. So the capture info (size/format) will be zeroed, and we fail while trying to create a buffer for the screenshot with size/format zeroed. With this patch we fail if we don't receive the capture info, what makes the failure reason more explicit. Signed-off-by: Leandro Ribeiro <leandro.ribeiro@collabora.com> (cherry picked from commit cf64fbe7)
ea821df7 -
We already only conditionally use base.offset when an icon exists. We should also avoid trying to create a coordinate with a NULL icon, as it will fire an assert(). Signed-off-by: Derek Foreman <derek.foreman@collabora.com> (cherry picked from commit 815a560d)
c88001e5 -
The ensure_single_mode() helper replaces an output's single mode. Extract it into libweston so it can be reused by the VNC backend, and rename it to weston_output_set_single_mode(). At the same time, set the the previously missing WL_OUTPUT_MODE_CURRENT flag on the new mode. Fixes #758 Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de> (cherry picked from commit e58452d6)
0806922c -
Use the shared helper extracted from the RDP backend to avoid leaking modes into the output mode list on every resize. Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de> (cherry picked from commit 04c29e6a)
2fb14091 -
Marius Vlad authored
Until kernel mainline does merge the aysnc page flip ioctl, make the whole bit look like it's unsupported. We can further switch it back when it lands into the kernel. Fixes: 9203d98f Signed-off-by: Marius Vlad <marius.vlad@collabora.com> Reported-by: Simon Ser <contact@emersion.fr> (cherry picked from commit 3e4aff6a)
bfc7ce3b -
Marius Vlad authored
We seem to be using at least mesa 21.1.1 since Weston 10, but we never explicitly asked for it. Fixes: #790 Signed-off-by: Marius Vlad <marius.vlad@collabora.com> (cherry picked from commit 0713ea7e)
babb4761