Mutter

mutter:work-with-old-libdrm

  1. Git
  2. lp:mutter
  3. work-with-old-libdrm
Last commit made on 2024-03-19
Get this branch:
git clone -b work-with-old-libdrm https://git.launchpad.net/mutter

Branch merges

Branch information

Name:
work-with-old-libdrm
Repository:
lp:mutter

Recent commits

3c22b2e... by Ray Strode <email address hidden>

backends/native: Work with old libdrm

commit a775241efd8b840e7789077fb2224f0df2361d54 recently introduced
usage of a sort of new API, drmModeCloseFb. Unfortunately, this API
has not yet made it into freedesktop-sdk.

As an interim answer, this commit adds a drmIoctl based reimplementation
of drmModeCloseFb that only gets used if the real implementation isn't
available in libdrm.

Later we can just drop this function without changing any other code.

e4dd50e... by A S Alam <email address hidden>

Update Punjabi translation

c475368... by =?utf-8?q?Florian_M=C3=BCllner?= <email address hidden>

Bump version to 46.0

Update NEWS.

64a1da9... by =?utf-8?q?Jonas_Dre=C3=9Fler?= <email address hidden>

clutter/input-method: Check for equality before notifying properties

ClutterInputMethods content hint or purpose will be set again (even to the
same values) whenever a wayland client sends us a new content type/purpose.
Gtk appears to always set a content purpose on wl_text_input changes, so we
currently set and notify the "content-purpose" property on every change in a
gtk text field.

Since the OSK is gnome-shell listens to this property and re-generates its
entire layout when the content-purpose prop gets notified, this is currently
causing lag/freezes on every keypress in the OSK in gnome-shell.

So ensure to not notify these properties in case they're equal and set the
properties in the same way as we usually set them instead of going via
GObject.

Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3645>

a775241... by Jocelyn Falempe <email address hidden>

backend/native: Use drmModeCloseFB for flicker-free login

When logging in from gdm to gnome, the main plane is deactivated, and
leads to the screen going blank before gnome is able to enable it
again.
Using the new CloseFB ioctl, allows to keep the gdm login screen
displayed until gnome-shell replace it.

Signed-off-by: Jocelyn Falempe <email address hidden>
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3659>

a50bc0f... by Sebastian Wick <email address hidden>

onscreen/native: Only set a VRR update if the CRTC supports the property

This also gets rid of the MetaFrameSyncMode enum and instead issues a
VRR update when the requested state differs from the CRTC state.

Fixes: fee33299 ("onscreen/native: Allow requesting frame synchronization")
Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3646>

51811ec... by Sebastian Wick <email address hidden>

output: Add a function to check if VRR is enabled for the output

An output with enabled VRR requires that the mode is a VRR mode which
also means that VRR is supported.

Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3646>

91e3180... by Sebastian Wick <email address hidden>

output/kms: Track in OutputInfo if the output is VRR capable

This includes checking the vrr_capable property on the connector as well
as the VRR_ENABLE property on any CRTC the connector might get assigned
to. Also takes into account when a GPU is tagged for broken VRR support.

Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3646>

514a18f... by Sebastian Wick <email address hidden>

kms/crtc: Track if the VRR_ENABLED property is supported

Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3646>

f480de4... by Bilal Elmoussaoui <email address hidden>

plugin-manager: Guard MetaPluginClass.xevent_filter

As we are getting close to have a Wayland-only build, guard those usages
so we don't 'regress'.
Once Kiosk figures it use case, we can revert both this commit and the
previous one.

Part-of: <https://gitlab.gnome.org/GNOME/mutter/-/merge_requests/3652>