Commits on Source (19)
-
Jonas Ådahl authored
This makes sure we don't accidentally try to paste from past Xwayland connection instances. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2364>
81da4a15 -
Jonas Ådahl authored
To be used for clipboard testing. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2364>
5aaad20a -
Jonas Ådahl authored
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2364>
20c4843f -
Jonas Ådahl authored
This avoids warnings when we're just slightly unlucky when Xwayland went away due to inactivity. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2364>
df8d0631 -
Jonas Ådahl authored
Will be used for test cases to fake-crash the Xwayland process. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2364>
573eae6e -
Jonas Ådahl authored
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2364>
c3f6f9b0 -
Jonas Ådahl authored
Xwayland can disappear at any time, for example during a new_async() or read_async() call. When we eventually finalize the stream, the X11 display it was created for is gone, thus can't clean up the X11 resources. Handle this by making the MetaX11Display pointer a weak pointer, and ignore cleaning up if it disappeared. This is fine since the X11 server it created those resources one is gone already. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2364>
48f39bee -
Jonas Ådahl authored
The Xwayland server can go away at any time; when this happen we might have a test client running, and for it to tear down more nicely, make sure to avoid trying to clean up X11 resources on the old X11 display. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2364>
5f5042d8 -
Jonas Ådahl authored
It works by using an X11 client to set the clipboard content, using a mimetype that on purpose is not handled by the clipboard manager. The test then makes sure we don't crash when trying to transfer data from the old X11 selection source. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2364>
4fc3c27a -
Jonas Ådahl authored
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2364>
df4f91f0 -
Robert Mader authored
Our internal interpretation of output transforms is not in line with the Wayland spec. Wayland describes them as the transform that a compositor will apply to a surface to compensate for the rotation or mirroring of an output device - counter-clockwise. Mutter in turn interprets it the other way around. One could argue it does the same but clock-wise - or it interprets the transform from the viewpoint of the content, not the device. In either way, the difference is that 90 and 270 degree values are switched. Thus swap these accordingly when we translate from `WL_OUTPUT_TRANSFORM` to `META_MONITOR_TRANSFORM`. See: https://gitlab.freedesktop.org/wayland/weston/issues/99 Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1055> (cherry picked from commit 8d9bbe10)
cd52c57b -
Michel Dänzer authored
Fixes leak: ==14889== 2,168 (16 direct, 2,152 indirect) bytes in 1 blocks are definitely lost in loss record 15,308 of 15,584 ==14889== at 0x48445EF: calloc (vg_replace_malloc.c:1328) ==14889== by 0x4BAC1D0: g_malloc0 (gmem.c:155) ==14889== by 0x4AAFF60: meta_wayland_dma_buf_feedback_new (meta-wayland-dma-buf.c:298) ==14889== by 0x4AAFFE0: meta_wayland_dma_buf_feedback_copy (meta-wayland-dma-buf.c:317) ==14889== by 0x4AB16B6: ensure_surface_feedback (meta-wayland-dma-buf.c:1121) ==14889== by 0x4AB1848: dma_buf_handle_get_surface_feedback (meta-wayland-dma-buf.c:1169) ==14889== by 0x66F77E9: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==14889== by 0x66F6922: ??? (in /usr/lib/x86_64-linux-gnu/libffi.so.8.1.0) ==14889== by 0x5318750: ??? (in /usr/lib/x86_64-linux-gnu/libwayland-server.so.0.20.0) ==14889== by 0x5313B99: ??? (in /usr/lib/x86_64-linux-gnu/libwayland-server.so.0.20.0) ==14889== by 0x5316649: wl_event_loop_dispatch (in /usr/lib/x86_64-linux-gnu/libwayland-server.so.0.20.0) ==14889== by 0x4AA7C19: wayland_event_source_dispatch (meta-wayland.c:110) Fixes: 64e6bedb ("wayland/dma-buf: Add support for scanout surface feedback") Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2469> (cherry picked from commit 4af54225)
57cf77b4 -
Jonas Ådahl authored
'screen-cast/monitor-src: Use clutter_stage_paint_to_buffer' (6c818cd8) made the non-dma-buf path use clutter_stage_paint_to_buffer() to avoid running into direct scanout issues. At a glance, the dma-buf paths didn't have the same issue since it explicitly handled dma-bufs by blitting them. What it also did was move the recording to an idle callback, to avoid paint reentry issues. A side effect of this, however, is that it also broke the dma-buf paths, as they rely on the back buffer existing, and the stage view direct scanout already being setup, which it isn't in an idle callback. Fix this by using the dma-buf variant of clutter_stage_paint_to_buffer(): clutter_stage_paint_to_framebuffer(). This has some negative performance impact, but we can't use cogl_blit_framebuffer() when using an idle callback for recording. Potential performance improvements to make things work more as they did before is to enhance 'cogl_blit_framebuffer()' a bit, making it a vfunc that could be implemented by MetaOnscreenNative. A flag to say whether to look at the back or front buffer would let MetaOnscreenNative know whether to use the already committed-to-KMS buffer, or the current back buffer. Fixes: 6c818cd8 Closes: https://gitlab.gnome.org/GNOME/mutter/-/issues/2282 Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2462>
9fba0fbb -
Jonas Ådahl authored
The pixel clock determines how fast pixels can be processed. When adding non-native common modes, avoid adding modes that exceed the max pixel clock frequency of the native modes. Avoiding these avoids potential mode setting failures where the GPU can't handle the modeline since the configured pixel clock is too fast. This replaces the "bandwidth" check which used the number of pixels and refresh rate, which wasn't enough to avoid incompatible modes. Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/2492> (cherry picked from commit 43860110)
8e522111 -
Florian Müllner authored
Update NEWS.
1903356b -
Jeremy Bicha authored90b6847f
-
Jeremy Bicha authored
Upstream version 42.3
26f219cb -
Jeremy Bicha authored840680a4
-
Jeremy Bicha authored9d7860e6