[PATCH libinput] udev: copy the trackpoint sensitivity directly from sysfs

2018-05-02 Thread Peter Hutterer
Rather than going the roundabout way of having systemd set the sensitivity followed by us reading that udev property and hoping, just take the sensitivity directly from sysfs. This makes us basically independent of what systemd does (or the lack of systemd, where that is a problem). It does remove

libweston program segfaults on weston_compositor_load_backend

2018-05-02 Thread adlo
I am trying to write a simple test compositor using libweston, but it segfaults on weston_compositor_load_backend. Here is my code: main.c: #include #include #include #include #include #include #include #include int main (intargc, char **argv) { struct wl_display *

Re: [PATCH libinput 2/4] touchpad: reset the wobble detection for non-pointer events

2018-05-02 Thread Peter Hutterer
On Wed, May 02, 2018 at 12:08:58PM +0300, Konstantin Kharlamov wrote: > On 30.04.2018 08:33, Peter Hutterer wrote: > > If we get an event other than a motion event we're not wobbling so we need > > to > > reset and restart. > > > > Signed-off-by: Peter Hutterer > > IMO this shouldn't matter, be

Re: unique id for wayland objects

2018-05-02 Thread zou lan
Hi pekka Thank you for your clearly analysis. I understand the presentation protocol is enough for the requirement now. I used to not study the protocol deeply because the code is a little more than just record the flip timestamp. The test want to do this as simple as possible. I will try the pr

Re: [PATCH weston v9 0/9] Head-based output configuration API a.k.a clone mode infrastructure

2018-05-02 Thread Pekka Paalanen
On Mon, 30 Apr 2018 16:23:14 +0100 Daniel Stone wrote: > Hi Pekka, > > On 19 April 2018 at 13:09, Pekka Paalanen wrote: > > this is actually clone mode series v9 part 3. > > > > Yes, part 2 was never posted separately, it was landed directly from v6 > > as it didn't need any changes. This here

Re: [PATCH libinput 2/4] touchpad: reset the wobble detection for non-pointer events

2018-05-02 Thread Konstantin Kharlamov
On 30.04.2018 08:33, Peter Hutterer wrote: If we get an event other than a motion event we're not wobbling so we need to reset and restart. Signed-off-by: Peter Hutterer IMO this shouldn't matter, because if a user managed to consciously trigger an event other than movement, it would definit

[PATCH weston 1/1] desktop-shell: detect stale shell surface outputs

2018-05-02 Thread Fabien Lahoudere
From: Semi Malinen When displays are hot (un)plugged, it may happen that a shell surface is left with a stale pointer to an output that has already been freed. Add an output destroy listener to catch such situations and set the output pointer to NULL. Signed-off-by: Semi Malinen Signed-off-by:

Re: unique id for wayland objects

2018-05-02 Thread Pekka Paalanen
On Wed, 2 May 2018 16:33:43 +0800 zou lan wrote: > Add to wayland mail list. > > Hi pekka > > I used to consider the time line and presentation protocol. But they are > all focus on surface, not buffer. The test want to know the buffer latency, > although they are the same as surface's on > mos

Fwd: unique id for wayland objects

2018-05-02 Thread zou lan
Add to wayland mail list. Hi pekka I used to consider the time line and presentation protocol. But they are all focus on surface, not buffer. The test want to know the buffer latency, although they are the same as surface's on most cases. Applications think maybe some buffers doesn't display and

[PATCH weston 1/4] desktop-shell: handle NULL output in get_output_work_area()

2018-05-02 Thread Fabien Lahoudere
From: Pekka Paalanen This is a tentative crash fix for a case where there are no enabled weston_outputs at all. Let get_output_work_area() return a zero area if the given output is NULL. If there is no output, there is no area. Unfortunately we cannot return "no position" but have to use 0,0 ins

[PATCH weston 0/4] Handle several NULL output pointer

2018-05-02 Thread Fabien Lahoudere
This is a series of fixes, for the case when Weston is running without any connected outputs (weston_outputs). Pekka Paalanen (4): desktop-shell: handle NULL output in get_output_work_area() desktop-shell: handle NULL output in center_on_output() desktop-shell: do not lower_fullscreen_layer(

[PATCH weston 3/4] desktop-shell: do not lower_fullscreen_layer(s, NULL)

2018-05-02 Thread Fabien Lahoudere
From: Pekka Paalanen In activate, do not call lower_fullscreen_layer() at all if the output is NULL. It should not do anything in that case, per the existing comment. This is a tentative crash fix for a case where there are no enabled weston_outputs at all. Signed-off-by: Pekka Paalanen Signed

[PATCH weston 4/4] desktop-shell: survive NULL output in shell_configure_fullscreen()

2018-05-02 Thread Fabien Lahoudere
From: Pekka Paalanen Running 'weston-simple-egl -f -b' (fullscreen, unthrottled) caused a crash in shell_ensure_fullscreen_black_view() due to shsurf->fullscreen_output being NULL. Also shell_configure_fullscreen() could crash on that condition. Fix shell_configure_fullscreen() to bail out with

[PATCH weston 2/4] desktop-shell: handle NULL output in center_on_output()

2018-05-02 Thread Fabien Lahoudere
From: Pekka Paalanen This is a tentative crash fix for a case where there are no enabled weston_outputs at all. If no output is given, just put the surface at 0,0. At least it should become mostly visible if an output is plugged in, if not centered. Signed-off-by: Pekka Paalanen Signed-off-by:

Re: Referencing enums in other protocols

2018-05-02 Thread Pekka Paalanen
On Tue, 1 May 2018 10:18:08 + Auke Booij wrote: > On Mon, Apr 23, 2018 at 9:08 AM, Pekka Paalanen wrote: > > I think that's an oversight. It should indeed be possible to reference > > enums just like interfaces from other protocol files. > > From my point of view, we did not add this whe