1. 11 Oct, 2019 1 commit
  2. 14 Sep, 2019 1 commit
  3. 26 Aug, 2019 1 commit
  4. 12 Aug, 2019 4 commits
  5. 17 Jul, 2019 2 commits
  6. 16 Jul, 2019 3 commits
  7. 28 Jun, 2019 8 commits
    • Guido Gunther's avatar
      Merge branch 'x11-frame' into 'librem5-0.6.x' · 4e1177b1
      Guido Gunther authored
      x11: Send a frame event on the pointer after button events
      
      See merge request !47
      4e1177b1
    • Dorota Czaplejewicz's avatar
      x11: Send a frame event on the pointer after button events · 9a4508a6
      Dorota Czaplejewicz authored
      Without the immediate frame event, the button event would not be processed in time: https://source.puri.sm/Librem5/phoc/issues/
      9a4508a6
    • Guido Gunther's avatar
      Merge branch 'touchup' into 'librem5-0.6.x' · 1ae7f7b0
      Guido Gunther authored
      wlr_seat_touch: Don't destroy touch point with surface
      
      See merge request !45
      1ae7f7b0
    • Guido Gunther's avatar
      Merge branch 'ssh-logout' into 'librem5-0.6.x' · 01243521
      Guido Gunther authored
      Don't freeze session on ssh logout
      
      See merge request !46
      01243521
    • Jan Chren's avatar
      session/logind: check for XDG_SESSION_ID first · 1f5145a8
      Jan Chren authored
      In order to support compositors running as systemd user units without display manager,
      a mechanism for specifying session ID exactly must exist.
      
      Checking for `XDG_SESSION_ID` mimics loginctl behaviour https://github.com/systemd/systemd/blob/e95be7def26c6c5feaf08a4135aa4f50c53263a8/src/login/loginctl.c#L856.
      1f5145a8
    • Jan Chren's avatar
      session/logind: specify seat exactly · fff57b71
      Jan Chren authored
      "/org/freedesktop/login1/seat/self" path triggers seat-finding code path in logind,
      which currently relies on getting the session based on caller's PID.
      This behaviour is deprecated in logind as it doesn't work eg. with systemd user units,
      which run outside of user session.
      
      We check for "seat0" in logind_change_vt() already as introduced in 47985d2d,
      so hard-coding it here is not a problem, otherwise sd_session_get_seat() could be used.
      fff57b71
    • Brian Ashworth's avatar
      session/logind: keep active for pause_device gone · 61978952
      Brian Ashworth authored
      This appears to be a quick fix for compositors freezing when a dock is
      disconnected. Disconnection of the dock is causing `pause_device` for
      the DRM devices associated with the dock. Since these devices major
      number is `DRM_MAJOR`, the session was being set to inactive. This just
      makes it so the session is not set to inactive when the device's state
      is `gone`.
      61978952
    • Guido Gunther's avatar
      wlr_seat_toch: Don't destroy touch point with surface · e26217c5
      Guido Gunther authored
      When the surface is destroyed clear it's reference but wait for the up
      event to destroy the touch point via wlr_seat_touch_notify_up().
      
      If the surface is destroyed before the up event we end up with
      incomplete sequences sent to the client like
      
      [915821.276] wl_touch@3.down(146, 2475027, wl_surface@38, 0, 236.000000, 515.000000)
      [915821.608] wl_touch@3.frame()
      [915821.637] wl_touch@3.motion(2475027, 0, 236.000000, 515.000000)
      [915821.779] wl_touch@3.frame()
      
      so there's never an up event. While it should be something like
      
      [2461229.051] wl_touch@3.down(81, 3236959, wl_surface@34, 0, 218.000000, 478.000000)
      [2461229.435] wl_touch@3.frame()
      [2461229.484] wl_touch@3.motion(3236959, 0, 218.000000, 478.000000)
      [2461229.636] wl_touch@3.frame()
      [2461277.520] wl_touch@3.up(82, 3237007, 0)
      [2461277.681] wl_touch@3.frame()
      
      this confuses tookits intepreting the next down event incorrectly. So
      don't destroy the touch point too early.
      e26217c5
  8. 03 May, 2019 1 commit
  9. 29 Apr, 2019 3 commits
  10. 28 Apr, 2019 3 commits
  11. 27 Apr, 2019 4 commits
  12. 26 Apr, 2019 5 commits
  13. 25 Apr, 2019 1 commit
  14. 23 Apr, 2019 3 commits