Fix error when opening settings, on some wayland compositors

Luna Lovecraftrequested to merge
ciubix/krita:wayland-extension-checking into master

Before this, the wayland color management system always assumed that the compositor had the wp_color_manager_v1 extension. However currently some compositors don't support the extensions.

https://wayland.app/protocols/color-management-v1#compositor-support

Now it checks if the extension is present in the wayland registry, and only enables wayland color management if it is.

Test Plan

  1. Launch krita on a compositor that does not support the wp_color_manager_v1 extension
  2. Krita correctly detects that surface color management is not supported
  3. Launch krita on a compositor that does support the wp_color_manager_v1 extension
  4. Surface color management is enabled

Formalities Checklist

  • I confirmed this builds.
  • I confirmed Krita ran and the relevant functions work.
  • I tested the relevant unit tests and can confirm they are not broken. (If not possible, don't hesitate to ask for help!)
  • I made sure my commits build individually and have good descriptions as per KDE guidelines.
  • I made sure my code conforms to the standards set in the HACKING file.
  • I can confirm the code is licensed and attributed appropriately, and that unattributed code is mine, as per KDE Licensing Policy.
  • Does the patch add a user-visible feature? If yes, is there a documentation MR ready for it at Krita Documentation Repository?

Reminder: the reviewer is responsible for merging the patch, this is to ensure at the least two people can build the patch. In case a patch breaks the build, both the author and the reviewer should be contacted to fix the build. If this is not possible, the commits shall be reverted, and a notification with the reasoning and any relevant logs shall be sent to the mailing list, kimageshop@kde.org.

Merge request reports