1. 09 Dec, 2018 9 commits
  2. 04 Dec, 2018 1 commit
  3. 20 Nov, 2018 5 commits
  4. 15 Nov, 2018 1 commit
    • Dima Ryazanov's avatar
      Don't look for weston.ini in the current working directory · ad0d83bd
      Dima Ryazanov authored
      
      
      It's a bit surprising that Weston looks different when launched from the root
      of the git repo vs from elsewhere.
      
      But it's also technically a security vulnerability: if I launch it from
      a directory like /tmp, it might pick up a weston.ini created by another user,
      which could then load modules with arbitrary code. Basically, it's the same
      problem as including "." in $PATH.
      Signed-off-by: Dima Ryazanov's avatarDima Ryazanov <dima@gmail.com>
      ad0d83bd
  5. 05 Nov, 2018 4 commits
  6. 03 Nov, 2018 1 commit
  7. 02 Nov, 2018 8 commits
  8. 30 Oct, 2018 6 commits
  9. 18 Oct, 2018 2 commits
  10. 12 Oct, 2018 1 commit
  11. 23 Sep, 2018 2 commits
    • Daniel Stone's avatar
      compositor-drm: Don't warn about missing backlight control · bff27cb8
      Daniel Stone authored
      
      
      Not every output will have a backlight control, and even if it does we
      may just not be able to find it. Not having backlight control isn't an
      error, so don't spam the log with it, as doing so can confuse users into
      thinking this is an actual error which is responsible for their real
      problems.
      Signed-off-by: Daniel Stone's avatarDaniel Stone <daniels@collabora.com>
      bff27cb8
    • Daniel Stone's avatar
      gl-renderer: Remove warning on missing extensions · a65d55e1
      Daniel Stone authored
      
      
      Not having swap_buffers_with_damage could cause a performance impact on
      some backends, but at least on GBM it causes no issues. It also seems to
      confuse users into thinking it's a legitimate error which could explain
      session slowness.
      
      Similarly with buffer_age, whilst we do lose a little bit of performance
      by not being able to do partial renders, it is not a great deal, and the
      user is unlikely to be able to do anything about it in any event.
      
      Remove the warning; we print the full extension list at startup, so we
      already have enough information from the logs to easily diagnose any
      real errors.
      Signed-off-by: Daniel Stone's avatarDaniel Stone <daniels@collabora.com>
      a65d55e1