1. 18 Dec, 2020 1 commit
  2. 10 Dec, 2020 1 commit
  3. 09 Oct, 2020 1 commit
  4. 26 Sep, 2020 1 commit
  5. 17 Jun, 2020 1 commit
  6. 16 Jun, 2020 1 commit
  7. 15 Oct, 2019 2 commits
  8. 14 Oct, 2019 1 commit
  9. 11 Oct, 2019 1 commit
  10. 12 Oct, 2017 2 commits
  11. 11 Oct, 2017 2 commits
  12. 02 Oct, 2017 1 commit
  13. 27 Sep, 2017 1 commit
  14. 05 May, 2017 2 commits
  15. 08 Oct, 2016 3 commits
  16. 15 Mar, 2016 3 commits
    • Andrew den Exter's avatar
      [wayland] Clear the retained clipboard data when a client clipboard is... · 66be489a
      Andrew den Exter authored
      [wayland] Clear the retained clipboard data when a client clipboard is cleared. Contributes to JB#33931
      
      Clear should mean clear.  When a client drops its data source drop the
      retained data and notify other clients in the same way as if the client
      simply set different data.
      
      Change-Id: Iaff5d0905d788fb990de6f78f06d1d0654285e19
      66be489a
    • Andrew den Exter's avatar
      Merge branch 'jb32781' into 'mer-5.4' · 516a78bb
      Andrew den Exter authored
      [qtwayland] Fix copying to the clipboard failing.  Fixes JB#32781
      
      A ulong timestamp with millisecond resolution overflows after a little
      under 9 hours meaning a direct comparison between timestamps is only
      valid in the first 9 hours the compositor has been running.
      
      Given the timestamps originate in the compositor when the data source
      object is created it is difficult to see what information they provide
      which isn't implicit in the order of execution of calls to the function
      the check is in, making removing the check the safest course of action.
      
      Change-Id: I1b1d4458b913d54028e5e58d7eb3f217cc5b8186
      
      See merge request !5
      516a78bb
    • Andrew den Exter's avatar
      [qtwayland] Fix copying to the clipboard failing. Fixes JB#32781 · de92b081
      Andrew den Exter authored
      A ulong timestamp with millisecond resolution overflows after about
      49 hours meaning a direct comparison between timestamps is only
      valid until that wrap point is reached.
      
      Given the timestamps originate in the compositor when the data source
      object is created it is difficult to see what information they provide
      which isn't implicit in the order of execution of calls to the function
      the check is in, making removing the check the safest course of action.
      
      Change-Id: I1b1d4458b913d54028e5e58d7eb3f217cc5b8186
      de92b081
  17. 25 Feb, 2016 1 commit
    • Raine Makelainen's avatar
      Merge branch 'jb34185' into 'mer-5.4' · 9dad99fb
      Raine Makelainen authored
      [wayland] Fix crash when pinging a surface with an invalid resource. Fixes JB#34185
      
      Check the surface hasn't been deleted before initiating the ping so
      that an invalid resource isn't dereferenced when printing a warning
      after the operation inevitably fails.
      
      Change-Id: I205def680971e50e59d761f16128cd4019234037
      
      See merge request !3
      9dad99fb
  18. 24 Feb, 2016 1 commit
  19. 11 Jan, 2016 2 commits
  20. 10 Jan, 2016 2 commits
  21. 12 Nov, 2015 1 commit
  22. 10 Nov, 2015 1 commit
    • Giulio Camuffo's avatar
      client: Remove the event thread · eabca263
      Giulio Camuffo authored
      If the compositor sends events to us while the main thread is blocked
      the socket notifier in the events thread would keep sending out the
      activated() signal, but no events would actually be read until the
      main thread starts to run again. That causes the event thread to keep
      queueing new events, and so allocating memory, potentially forever.
      This patch fixes the issue in maybe a bit radical way, that is by removing
      the event thread. The socket notifier now runs in the main thread so it
      will block if the events are not being read.
      Nowadays there is no real reason to keep the event thread around, as every
      thread that needs to receive wayland events can dispatch them on its own,
      we don't need a central dispatcher thread anymore.
      
      Change-Id: Ib7885e4b038b82719d78d193f465618a72cbe6af
      Reviewed-by: plfiorini's avatarPier Luigi Fiorini <pierluigi.fiorini@gmail.com>
      eabca263
  23. 23 Oct, 2015 2 commits
  24. 09 Oct, 2015 1 commit
  25. 21 Sep, 2015 1 commit
  26. 09 Sep, 2015 1 commit
  27. 07 Sep, 2015 2 commits
  28. 04 Sep, 2015 1 commit