delta/mutter.git, branch wip/tintou/clutter-frame-clock-delegates gitlab.gnome.org: GNOME/mutter.git clutter/frame-clock: Define ClutterFrameListenerIface elements as delegates 2020-08-29T15:22:43+00:00 Corentin Noël corentin.noel@collabora.com 2020-08-25T15:08:04+00:00 342f78c9ebf9cfa9224c1b8bc621e6b7e7fc523c This allows the introspection to properly understand that the fields of the ClutterFrameListenerIface structure are delegates. https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1413 
This allows the introspection to properly understand that the fields of the
ClutterFrameListenerIface structure are delegates.

https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1413
Update Chinese (China) translation 2020-08-29T13:30:16+00:00 Boyuan Yang 073plan@gmail.com 2020-08-29T13:30:16+00:00 c8e073b0e62a29a68a58fb938f4c23c488f89dfb 






wayland/surface: Don't update outputs recursively on mapped changes
2020-08-29T12:40:11+00:00

Jonas Dreßler
verdre@v0yd.nl

2020-07-07T14:49:31+00:00

0b9a71ea3cb9c752e5748d002b45fd4cdfbf37dc

There's no need to update the outputs recursively in case the actor gets
mapped or unmapped. That's because mapping happens recursively itself,
so if a window with multiple subsurfaces is shown, all subsurfaces will
receive a "notify::mapped" signal.

Since this was the only remaining user of
meta_wayland_surface_update_outputs_recursively(), we can now remove
that function.

https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1358





There's no need to update the outputs recursively in case the actor gets
mapped or unmapped. That's because mapping happens recursively itself,
so if a window with multiple subsurfaces is shown, all subsurfaces will
receive a "notify::mapped" signal.

Since this was the only remaining user of
meta_wayland_surface_update_outputs_recursively(), we can now remove
that function.

https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1358







wayland/surface: Don't update outputs on all geometry changes
2020-08-29T12:40:11+00:00

Jonas Dreßler
verdre@v0yd.nl

2020-05-03T15:55:28+00:00

35f847ac6dc237c23344038294fc0395ce40f718

Since we now listen to the "stage-views-on-changed" signal (which
"catches" all the changes we want) on MetaWaylandActorSurfaces for
updating the wl_outputs the surface is on, we no longer need to call
meta_wayland_surface_update_outputs_recursively() on all geometry
changes, so remove that signal handler.

https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1358





Since we now listen to the "stage-views-on-changed" signal (which
"catches" all the changes we want) on MetaWaylandActorSurfaces for
updating the wl_outputs the surface is on, we no longer need to call
meta_wayland_surface_update_outputs_recursively() on all geometry
changes, so remove that signal handler.

https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1358







wayland/actor-surface: Update outputs on stage-views changes
2020-08-29T12:40:11+00:00

Jonas Dreßler
verdre@v0yd.nl

2020-03-12T22:35:28+00:00

abdbc14ca8a6dffd452d738c10f3984787cc1d45

ClutterActors new "stage-views-changed" signal fits pretty well for the
updating of wl_outputs a MetaWaylandActorSurface is on: With that signal
we get notified if the surface moved to a different CRTC, of which every
output has at least one.

So start listening to that signal, which fixes a bug where the wl_output
of a surface changes, but its allocation remains the same (which means
no signals triggering an update of the outputs will be emitted) and no
enter/leave events for the new wl_outputs are sent to the client. This
can happen when a monitor is hotplugged but the new allocation is
exactly the same as the old one even though it's on a different monitor.

Since the "stage-views-on-changed" signal will also get emitted when a
parent actor of the surface is moved, this means we can now remove the
call to meta_wayland_surface_update_outputs_recursively() on window
position changes or the completion of window-effects.

https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1358





ClutterActors new "stage-views-changed" signal fits pretty well for the
updating of wl_outputs a MetaWaylandActorSurface is on: With that signal
we get notified if the surface moved to a different CRTC, of which every
output has at least one.

So start listening to that signal, which fixes a bug where the wl_output
of a surface changes, but its allocation remains the same (which means
no signals triggering an update of the outputs will be emitted) and no
enter/leave events for the new wl_outputs are sent to the client. This
can happen when a monitor is hotplugged but the new allocation is
exactly the same as the old one even though it's on a different monitor.

Since the "stage-views-on-changed" signal will also get emitted when a
parent actor of the surface is moved, this means we can now remove the
call to meta_wayland_surface_update_outputs_recursively() on window
position changes or the completion of window-effects.

https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1358







Update Ukrainian translation
2020-08-29T11:03:08+00:00

Yuri Chornoivan
yurchor@ukr.net

2020-08-29T11:03:08+00:00

f552ed13038ab814bdfd01ac437493192ec7f7cd












Update Ukrainian translation
2020-08-29T10:57:46+00:00

Yuri Chornoivan
yurchor@ukr.net

2020-08-29T10:57:46+00:00

55c3c084de9c9c4c2e07968d0761298cbd607231












screen-cast: Add vmwgfx to the DMA buffer deny list
2020-08-29T10:32:20+00:00

Grey Christoforo
grey@christoforo.net

2020-07-29T20:02:27+00:00

aaf70b28d198811e4fa838f0eeb4e41c8aacc889

VMWare has the same issues with mmap():ing DMA buffers cross process
boundaries so fall back to regular shared memory for 'vmwgfx' as well.

https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1318





VMWare has the same issues with mmap():ing DMA buffers cross process
boundaries so fall back to regular shared memory for 'vmwgfx' as well.

https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1318







screen-cast: Disable DMA buffer based screen casting for QXL
2020-08-29T10:32:20+00:00

Jonas Ådahl
jadahl@gmail.com

2020-06-17T15:50:17+00:00

986066ed407213f3c2ad79d8ddad3cd5bc1548e4

QXL doesn't support mmap():ing a DMA buffer allocated in mutter inside
the PipeWire stream consumer process. To make screen casting work again
on QXL, disable DMA buffer based screen casting for QXL.

Eventually, it should be the client that renegotiates the supported
buffer types, but until then we need this list.

https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1318





QXL doesn't support mmap():ing a DMA buffer allocated in mutter inside
the PipeWire stream consumer process. To make screen casting work again
on QXL, disable DMA buffer based screen casting for QXL.

Eventually, it should be the client that renegotiates the supported
buffer types, but until then we need this list.

https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1318







kms/device: Provide driver name and description
2020-08-29T10:32:20+00:00

Jonas Ådahl
jadahl@gmail.com

2020-06-17T15:49:12+00:00

d73a858dc2878a69ea69a863a6d668037c5fc7c1

Retrieved from drmGetVersion(), to be used to identify what driver a DRM
device is driven by.

https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1318





Retrieved from drmGetVersion(), to be used to identify what driver a DRM
device is driven by.

https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/1318