GitLab

emersion authored Oct 08, 2019 and Guido Gunther committed Oct 11, 2019

(cherry picked from commit 9796abcc)

Since e26217c5, touchpoints can outlive
surfaces. This works fine as long as the client stays around, but fails
horribly otherwise; therefore we have to make sure that touchpoints don't
outlive their clients.

Fixes #35

(cherry picked from commit 15dc71d603ad4b0393c5d8d045499dda78b1e42b)

Drew DeVault authored Aug 09, 2019 and Guido Gunther committed Aug 26, 2019

This libinput version adds a new tablet tool type.

(cherry picked from commit 94f65e35)

Sebastian Krzyszkowiak authored Aug 07, 2019 and Guido Gunther committed Aug 12, 2019

It's added to manager->input_methods list in manager_get_input_method, but
wasn't removed anywhere, leading to possible use-after-free in
wlr_input_method_manager_v2_destroy.

(cherry picked from commit 913cac18)

Sebastian Krzyszkowiak authored Aug 08, 2019 and Sebastian Krzyszkowiak committed Aug 12, 2019

Fixes #897

(cherry picked from commit 52037d13)

Sebastian Krzyszkowiak authored Aug 08, 2019 and Sebastian Krzyszkowiak committed Aug 12, 2019

Fixes #933

(cherry picked from commit 78d96009)

Sebastian Krzyszkowiak authored Aug 08, 2019 and Sebastian Krzyszkowiak committed Aug 12, 2019

(cherry picked from commit 40d17c13)

Sebastian Krzyszkowiak authored Jul 15, 2019 and Sebastian Krzyszkowiak committed Jul 17, 2019

(cherry picked from commit 415267ac)

Sebastian Krzyszkowiak authored Jul 15, 2019 and Sebastian Krzyszkowiak committed Jul 17, 2019

This brings it in line with wlr_keyboard and wlr_pointer

(cherry picked from commit 2d4bc66f)

emersion authored May 06, 2019 and Sebastian Krzyszkowiak committed Jul 16, 2019

This allows the toplevel to have proper decorations on compositors that support
xdg-decoration-unstable-v1.

(cherry picked from commit 292d20e4)

When the surface was destroyed but the resource is still around
we might dereference a null pointer otherwise.

(cherry picked from commit 692a16ce)

(cherry picked from commit 91752e82)

x11: Send a frame event on the pointer after button events

See merge request !47

Dorota Czaplejewicz authored Jun 17, 2019 and Guido Gunther committed Jun 28, 2019

Without the immediate frame event, the button event would not be processed in time: https://source.puri.sm/Librem5/phoc/issues/

wlr_seat_touch: Don't destroy touch point with surface

See merge request !45

Don't freeze session on ssh logout

See merge request !46

Jan Chren authored May 22, 2019 and Guido Gunther committed Jun 28, 2019

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.

Jan Chren authored May 22, 2019 and Guido Gunther committed Jun 28, 2019

"/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.

Brian Ashworth authored May 13, 2019 and Guido Gunther committed Jun 28, 2019

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`.

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.

This makes it so we don't miss build failures because the CI misses a
dependency.

Closes: https://github.com/swaywm/wlroots/issues/1662

See https://github.com/swaywm/wlroots/pull/1675#issuecomment-487300445

Xwayland expects an xdg_output.done event to always be sent with a
wl_output.done event.

This commit introduces wlr_output_schedule_done and refactors the mechanism
used to send wl_output events to clients.

wlr_output_schedule_done schedules a wl_output.done event. This allows clients
to see wlr_output property changes as atomic.

This function is also useful for add-on interfaces like xdg_output which need
to trigger a wl_output.done event to apply their new state.

We want to damage the whole output in this mode. However if we overwrite the
damaged region after it's useless.

Fixes: 57d32d03

See https://github.com/swaywm/wlroots/issues/1665

We only need to damage the parts of the screen that changed since last frame,
we don't need to accumulate damage from previous buffers.

We still need to re-render the accumulated damage.

Fixes https://github.com/swaywm/wlroots/issues/1665

According to the spec:

> If <n_rects> is 0 then <rects> is ignored and the entire
> surface is implicitly damaged and the behaviour is equivalent
> to calling eglSwapBuffers.

When we want to swap with an empty damage region, set the damage to a single
empty rectangle.

This does not require any code changes, as we already copy the keymap
data separately for each client.

For details, see https://gitlab.freedesktop.org/wayland/wayland/commit/905c0a341ddf0a885811d19e2b79c65a3f1d210c

Fixes: 5e6766a1

This new name makes more sense, since it is a request from the backend to get
a new frame. In the future a commit may not convey a new frame.