1. 17 Mar, 2019 1 commit
  2. 14 Mar, 2019 1 commit
    • Erik Kurzinger's avatar
      wayland/buffer: Try realizing EGLStream before EGLImage buffer · 056c45fe
      Erik Kurzinger authored
      Currently, it is assumed that if querying the EGL_TEXTURE_FORMAT of a
      Wayland buffer succeeds it is an EGLImage. However, this assumption will no
      longer hold on upcoming versions of the NVIDIA EGL Wayland driver which
      will include support for querying this attribute for EGLStream buffers as
      well. Hence, we need to check if buffers are EGLStreams first.
      
      Fixes #488
      !477
      056c45fe
  3. 12 Mar, 2019 7 commits
  4. 11 Mar, 2019 3 commits
  5. 05 Mar, 2019 1 commit
    • Andrea Azzarone's avatar
      sound-player: Don't deadlock in finish_cb · 8856a396
      Andrea Azzarone authored
      The function finish_cb can be called as a result of a call to ca_context_cancel
      in cancelled_cb. This will result in a deadlock because, as per documentation,
      g_cancellable_disconnect cannot be called inside the cancellable handler.
      
      It is possible to detect if the call to finish_cb is caused by ca_context_cancel
      checking if error_code == CA_ERROR_CANCELED. To avoid the deadlock we should
      call g_signal_handler_disconnect instead g_cancellable_disconnect if this is the
      case.
      
      !474
      8856a396
  6. 04 Mar, 2019 4 commits
    • Florian Müllner's avatar
      x11-display: Split out restoring of active workspace · 7abceb43
      Florian Müllner authored
      Splitting out the X11 display initialization from display_open() broke
      restoring the previously active workspace in two ways:
      
       - when dynamic workspaces are used, the old workspaces haven't
         been restored yet, so we stay on the first workspace
      
       - when static workspaces are used, the code tries to access
         the compositor that hasn't been initialized yet, resulting
         in a segfault
      
      Fix both those issues by splitting out restoring of the active workspace.
      
      #479
      7abceb43
    • Carlos Garnacho's avatar
      wayland: Minor refactor · 3e472faf
      Carlos Garnacho authored
      We use the input_method on both branches, but only check for its existence
      when enabling the text_input. The case of focusing out shouldn't happen in
      practice as we couldn't have focused in ever before, but still make the
      check one level above so it's clearer that the text_input's IM focus cannot
      be enabled without an IM implementation.
      
      !432
      3e472faf
    • Carlos Garnacho's avatar
      wayland: Only enable OSK if receiving .enable when already active · eabb7893
      Carlos Garnacho authored
      Enable the OSK if receiving .enable consecutively (i.e. the
      ClutterInputFocus was already focused). We specifically want to avoid
      enabling the panel just because of focus changes within a surface (where
      the .disable request across focus change would previously unfocus the
      ClutterInputFocus). Prior state should be preserved if possible in that
      situation.
      
      !432
      eabb7893
    • Carlos Garnacho's avatar
      clutter: Make ClutterInputFocus API to set panel state explicit · 3fd0e23e
      Carlos Garnacho authored
      Before we just had API to toggle the OSK panel state. Make this API
      generic so the upper layers may set the state as they see fit.
      All callers have been updated.
      
      !432
      3fd0e23e
  7. 01 Mar, 2019 10 commits
  8. 28 Feb, 2019 2 commits
    • verdre's avatar
      wayland/touch: Remove undelivered touches earlier · 8d9a5e3c
      verdre authored
      When the touch_down event was not delivered to Wayland clients, there's
      no point in keeping the touchpoint in our list, so remove it early
      inside update() instead of removing it after the touch ended.
      
      This fixes a crash inside touch_handle_surface_destroy() where the
      assertion to make sure the surface is removed fails because the
      touch_count of the surface never reached 0. This in turn happened
      because a new sequence was added, while a (already ended one) wasn't
      removed from the touch->touches list before. This caused the touch
      counter to get incremented by 1 while no new sequence was added to the
      list (because Clutter reuses sequence IDs, the old sequence is equal to
      the new one, i.e. the new sequence already is present in the list).
      
      Fixes #200
      
      !426
      8d9a5e3c
    • Niels De Graef's avatar
      Use a consistent style for enum braces · 1c6ea5d1
      Niels De Graef authored
      !361
      1c6ea5d1
  9. 27 Feb, 2019 1 commit
  10. 26 Feb, 2019 10 commits