1. 10 Feb, 2016 9 commits
  2. 09 Feb, 2016 2 commits
  3. 08 Feb, 2016 7 commits
  4. 07 Feb, 2016 16 commits
  5. 06 Feb, 2016 6 commits
    • Piotr Drąg's avatar
      Updated Polish translation · 1a524f37
      Piotr Drąg authored
      1a524f37
    • Matthias Clasen's avatar
      level bar: Fix offset behavior · ccd8c76f
      Matthias Clasen authored
      We had some odd special-casing for the lowest and highest offset
      that did not quite work. The new rule is simple: If the value
      is between offset n-1 and n, it gets the style for offset n.
      
      https://bugzilla.gnome.org/show_bug.cgi?id=761416
      ccd8c76f
    • Matthias Clasen's avatar
      level bar: Improve documentation · 1a71579b
      Matthias Clasen authored
      The docs were not explaining at all what happens to existing
      level offsets when the min- or max-value of a level bar are
      changed.
      1a71579b
    • Matthias Clasen's avatar
      level bar: Make the full offset official · 8776bb53
      Matthias Clasen authored
      We are adding 3 offsets, not just two. Add a define for the
      third one, and mention it in the docs.
      8776bb53
    • Dušan Kazik's avatar
      Updated Slovak translation · 7b668660
      Dušan Kazik authored
      7b668660
    • Ray Strode's avatar
      wayland: rework buffer management code (3 changes) · 2ebae407
      Ray Strode authored
      There are a couple of issues with the way that buffers are handled in
      wayland in right.  These issues mean that:
      
       - buffers can get leaked at a fairly fast clip under the right
         conditions. This leads to the OOM killer kicking in and
         gnome-shell and gnome-terminal (for instance) showing memory
         usage in the high gigabytes range.
      
       - drawing can happen to a shared memory buffer at the same time
         the compositor is reading out the pixels.  This can lead to
         glitching in drawing and other undefined behavior by the compositor.
      
      This changeset reworks how buffer management is done in the code to try
      to address both problems.
      
      The first change (commit 2c300081) addresses the leak by dropping code
      that has an unchecked cairo_surface_reference call.  The code is dropped
      rather than fixed, because it has a more serious issue: it's overarching
      purpose is to deal with shared memory buffer contention with the
      compositor, but it does it in a racy way and so fails at that mission.
      
      The second change (commit 40e91195) moves what layer of the code buffer
      release events are handled. This is an organizational change in the
      code, with no functional changes, but it's important for the last change
      in the changeset.
      
      The last change (commit c80dd549) adds back code for dealing with shared
      member buffer contention in a race free way. The new code is careful to
      never reuse a buffer that hasn't been explicitly released by the
      compositor.
      2ebae407