1. 14 Feb, 2019 2 commits
  2. 13 Feb, 2019 6 commits
  3. 12 Feb, 2019 3 commits
    • Marek Cernocky's avatar
      Updated Czech translation · fdd531f3
      Marek Cernocky authored
    • Matej Urbančič's avatar
      Updated Slovenian translation · 70c45f89
      Matej Urbančič authored
    • Niels De Graef's avatar
      meta-launcher: g_propagate_*_error takes ownership · b82fa2c6
      Niels De Graef authored
      This means we need to make sure we don't accidentally free the provided
      source GError (which automatically happens with `g_autoptr`), so use
      This fixes an issue where, when launched in a bubblewrap environment
      (such as the one provided by Buildstream), mutter would give the
      following warning message:
      mutter-WARNING **: 8:31:35:069: Can't initialize KMS backend: (null)
      ... which isn't that useful when trying to debug the actual issue.
  4. 11 Feb, 2019 3 commits
  5. 09 Feb, 2019 7 commits
  6. 07 Feb, 2019 1 commit
  7. 06 Feb, 2019 8 commits
  8. 05 Feb, 2019 2 commits
  9. 04 Feb, 2019 5 commits
  10. 03 Feb, 2019 1 commit
    • Josh Triplett's avatar
      Don't include potentially sensitive window titles in logs · b4ae6cdd
      Josh Triplett authored
      For various error and warning messages, mutter includes a description of
      the window, and that description includes a snippet of the title of the
      window. Those snippets find their way into system logs, which then means
      they can potentially find their way into bug reports and similar. Remove
      the window title information to eliminate this potential privacy issue.
  11. 01 Feb, 2019 2 commits
    • Georges Basile Stavracas Neto's avatar
      clutter/paint-nodes: Push/pop framebuffer · 317414ab
      Georges Basile Stavracas Neto authored
      Unfortunately, many parts of GNOME Shell and Mutter and Clutter
      still use the implicit Cogl1 API. As such, it as a transition
      between the old and new APIs, it is important to keep the
      implicit draw framebuffer updated.
      ClutterRootNode does not keep it updated though, and it might
      lead to problems when rendering offscreen textures.
      Fix that by pushing and popping the root node framebuffer on
      pre- and post-draw, respectively.
    • Georges Basile Stavracas Neto's avatar
      clutter/paint-nodes: Expose ClutterRootNode · b63e1045
      Georges Basile Stavracas Neto authored
      The ClutterRootNode paint node is theoretically the
      top-most node of a paint nodes tree, except that we
      are not in the point of having full rendering trees
      in Clutter (all rendering performed by paint nodes
      is still local and immediate).
      When controlling the rendering tree, MetaShapedTexture
      may need to paint into an offscreen framebuffer under
      some circumstations.
      Expose ClutterRootNode so that MetaShapedTexture can
      use it to render to offscreen framebuffers.