[Wayland-bugs] [Bug 104985] Intuos paper generating button click on palm off

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=104985

Peter Hutterer  changed:

   What|Removed |Added

 Status|NEW |ASSIGNED
 CC||peter.hutte...@who-t.net

--- Comment #1 from Peter Hutterer  ---
https://lists.freedesktop.org/archives/wayland-devel/2018-February/037151.html

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 105108] Lenovo Yoga 11S touchpad is jittery

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=105108

Peter Hutterer  changed:

   What|Removed |Added

 Depends on||105202


Referenced Bugs:

https://bugs.freedesktop.org/show_bug.cgi?id=105202
[Bug 105202] Add libinput measure touchpad-fuzz
-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 105202] Add libinput measure touchpad-fuzz

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=105202

Bug ID: 105202
   Summary: Add libinput measure touchpad-fuzz
   Product: Wayland
   Version: unspecified
  Hardware: Other
OS: All
Status: NEW
  Severity: normal
  Priority: medium
 Component: libinput
  Assignee: wayland-bugs@lists.freedesktop.org
  Reporter: peter.hutte...@who-t.net
Blocks: 105108

To measure a device's fuzz value, see bug 105108. Note that the tool must reset
the kernel fuzz value to 0 before commencing any measurement to avoid
interference with the kernel fuzz.


Referenced Bugs:

https://bugs.freedesktop.org/show_bug.cgi?id=105108
[Bug 105108] Lenovo Yoga 11S touchpad is jittery
-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 105050] DualShock 4 Touchpad not working with libinput.

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=105050

Peter Hutterer  changed:

   What|Removed |Added

 Status|REOPENED|NEEDINFO

--- Comment #5 from Peter Hutterer  ---
> 2. When specifying the driver manually in xorg.conf, it shouldn't matter
> if ID_INPUT is set.

it does matter, a device without ID_INPUT set never gets to the point where we
even check the assigned drivers in the server.

Based on the bits of the log you posted in comment 2, it does get rejected
because of the missing ID_INPUT tag. But you're right, that would apply for the
evdev driver too. So I'll need a full xorg.log please (most likely the
interesting bit was outside the snippet pasted here) and an evemu-record with a
touchs sequence to move the pointer so I can check what else is going on.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 105108] Lenovo Yoga 11S touchpad is jittery

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=105108

--- Comment #11 from Peter Hutterer  ---
Created attachment 137524
  --> https://bugs.freedesktop.org/attachment.cgi?id=137524=edit
0001-evdev-change-hysteresis-to-work-across-both-axes.patch

> Reassess the feasibility of making hysteresis omnidirectional so that circles 
> with the finger don't equate to squares with the cursor.

I had a patch for this a year or so ago, but it didn't get any testing or
positive test results, can't remember. Attaching here so it's public at least.
should apply on 1.9.0 but probably not on master

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 105108] Lenovo Yoga 11S touchpad is jittery

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=105108

--- Comment #10 from Daniel van Vugt  ---
Sounds like a plan:

1. Start using fuzz if available.
2. Never disable hysteresis; and
3. Submit proper measurements and fuzz tweaks per-model.

And maybe in parallel:

Reassess the feasibility of making hysteresis omnidirectional so that circles
with the finger don't equate to squares with the cursor.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 105108] Lenovo Yoga 11S touchpad is jittery

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=105108

--- Comment #9 from Peter Hutterer  ---
it's already doable, the EV_ABS lines in 60-evdev.hwdb support fuzz and flat as
well (order is x:y:resolution:fuzz:flat).

But before we do that we need a tool to measure what the fuzz would be. Having
users just submit entries they think are correct to the system-wide hwdb is
bound to be painful in the long run. Oh, and that tool needs to reset fuzz to 0
to make sure the kernel doesn't get in the way of the measurements.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 105050] DualShock 4 Touchpad not working with libinput.

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=105050

Simon  changed:

   What|Removed |Added

 Status|RESOLVED|REOPENED
 Resolution|NOTOURBUG   |---

--- Comment #4 from Simon  ---
I still think it is a libinput problem, because..

1. Why does it work with the evemu driver then? If it's not a libinput driver
problem it shouldn't work with other drivers too.

2. When specifying the driver manually in xorg.conf, it shouldn't matter if
ID_INPUT is set.

3. I checked and ID_INPUT is in fact set:

udevadm info from ds4 touchpad:
P:
/devices/pci:00/:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.3/0003:054C:09CC.0006/input/input43/event17
N: input/event17
S:
input/by-id/usb-Sony_Interactive_Entertainment_Wireless_Controller-event-if03
S: input/by-path/pci-:00:1d.0-usb-0:1.2:1.3-event
E:
DEVLINKS=/dev/input/by-id/usb-Sony_Interactive_Entertainment_Wireless_Controller-event-if03
/dev/input/by-path/pci-:00:1d.0-usb-0:1.2:1.3-event
E: DEVNAME=/dev/input/event17
E:
DEVPATH=/devices/pci:00/:00:1d.0/usb2/2-1/2-1.2/2-1.2:1.3/0003:054C:09CC.0006/input/input43/event17
E: ID_BUS=usb
E: ID_INPUT=1
E: ID_MODEL=Wireless_Controller
E: ID_MODEL_ENC=Wireless\x20Controller
E: ID_MODEL_ID=09cc
E: ID_PATH=pci-:00:1d.0-usb-0:1.2:1.3
E: ID_PATH_TAG=pci-_00_1d_0-usb-0_1_2_1_3
E: ID_REVISION=0100
E: ID_SERIAL=Sony_Interactive_Entertainment_Wireless_Controller
E: ID_TYPE=hid
E: ID_USB_DRIVER=usbhid
E: ID_USB_INTERFACES=:010100:010200:03:
E: ID_USB_INTERFACE_NUM=03
E: ID_VENDOR=Sony_Interactive_Entertainment
E: ID_VENDOR_ENC=Sony\x20Interactive\x20Entertainment
E: ID_VENDOR_ID=054c
E: LIBINPUT_DEVICE_GROUP=3/54c/9cc:usb-:00:1d.0-1
E: MAJOR=13
E: MINOR=81
E: SUBSYSTEM=input
E: USEC_INITIALIZED=134424850721

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 105108] Lenovo Yoga 11S touchpad is jittery

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=105108

--- Comment #8 from Daniel van Vugt  ---
The wobble is gone because hysteresis is always enabled (I hardcoded it to
enabled). That's not a change introduced by the patch though.

Moving in squares (when the finger moves in circles) is the same old problem
with the hysteresis algorithm, not a problem with the hysteresis magnitude.

That all said, I support the idea of committing attachment 137490. Just
remember to not close this bug.

Once we're using fuzz, perhaps it will be possible to tweak the fuzz (hence
tweak the hysteresis) for each touchpad externally, like libinput-model-quirks?

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 105160] libinput crashes GNOME shell with gnome-shell: ../libinput-1.10.0/src/evdev-mt-touchpad-tap.c:1073: tp_tap_handle_state: Assertiontp->tap.nfingers_down <= tp->nfingers_down

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=105160

Daniel van Vugt  changed:

   What|Removed |Added

   See Also||https://launchpad.net/bugs/
   ||1750664

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 786694] wayland: fix fontconfig monitoring

[gnome-settings-daemon]

https://bugzilla.gnome.org/show_bug.cgi?id=786694

--- Comment #11 from Bastien Nocera  ---
(In reply to Martin Blanchard from comment #10)
> (In reply to Bastien Nocera from comment #8)
> > It's too late to land this for GNOME 3.28. The gnome-shell patch will need
> > reviewing before this can land, assuming the code is correct.
> 
> May have missed something here, sorry: what is this gnome-shell patch you
> are talking about?

Never mind, the gtk+ patch rather. I'll review it later.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 105108] Lenovo Yoga 11S touchpad is jittery

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=105108

--- Comment #7 from Peter Hutterer  ---
'moves in squares' when you actually move the cursor, right? Does it wobble?

1) fwiw, a bug link is not always a signal that the bug is fixed, but rather a
reference to some other documentation so in a year's time we know where we got
a patch idea from.

2) fuzz of 0 as "no hysteresis" is used by the synaptics driver, but tbh I'm
doubtful that's a correct approach. Devices have a tendency to be outright
wrong and 0 is the only default value here. Which means 0 is shared by devices
that don't have fuzz and by devices that simply don't fill it in.

Having said that, might be worth just seeing how long it takes for someone to
complain :)

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 786694] wayland: fix fontconfig monitoring

[gnome-settings-daemon]

https://bugzilla.gnome.org/show_bug.cgi?id=786694

--- Comment #10 from Martin Blanchard  ---
(In reply to Bastien Nocera from comment #8)
> It's too late to land this for GNOME 3.28. The gnome-shell patch will need
> reviewing before this can land, assuming the code is correct.

May have missed something here, sorry: what is this gnome-shell patch you are
talking about?

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 786694] wayland: fix fontconfig monitoring

[gnome-settings-daemon]

https://bugzilla.gnome.org/show_bug.cgi?id=786694

Martin Blanchard  changed:

   What|Removed |Added

 Attachment #368196|0   |1
is obsolete||

--- Comment #9 from Martin Blanchard  ---
Created attachment 368734
  --> https://bugzilla.gnome.org/attachment.cgi?id=368734=edit
Introduce org.gnome.SettingsDaemon.FontConfig (timestamp as int64)

Fourth version: removed a couple of extra whitespaces.

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 105153] Raspberry official Touchscreen absolute axes issue libinput 1.10

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=105153

Peter Hutterer  changed:

   What|Removed |Added

 Status|NEEDINFO|RESOLVED
 Resolution|--- |MOVED

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 105160] libinput crashes GNOME shell with gnome-shell: ../libinput-1.10.0/src/evdev-mt-touchpad-tap.c:1073: tp_tap_handle_state: Assertiontp->tap.nfingers_down <= tp->nfingers_down

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=105160

Peter Hutterer  changed:

   What|Removed |Added

 Resolution|--- |FIXED
 Status|ASSIGNED|RESOLVED

--- Comment #7 from Peter Hutterer  ---
commit 01a633b6ebea514cc26bb00f2bf85789fe5409e3
Author: Peter Hutterer 
Date:   Tue Feb 20 13:27:57 2018 +1000

touchpad: only begin fake touches when we have at least one finger down

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 105153] Raspberry official Touchscreen absolute axes issue libinput 1.10

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=105153

--- Comment #6 from Peter Hutterer  ---
https://github.com/systemd/systemd/pull/8226 is one example for such a PR. Make
sure you cc @whot on it so I see it

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 105153] Raspberry official Touchscreen absolute axes issue libinput 1.10

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=105153

--- Comment #5 from MadPapo  ---
Can you provide me a Bugzilla link where to post the issue?

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 793062] [Wayland] Crash under gdk_wayland_window_attach_image()

[gtk+]

https://bugzilla.gnome.org/show_bug.cgi?id=793062

--- Comment #30 from Olivier Fourdan  ---
I've filed two MR (gtk3 and gtk4) for this here:

gtk3: https://gitlab.gnome.org/GNOME/gtk/merge_requests/31
gtk4: https://gitlab.gnome.org/GNOME/gtk/merge_requests/32

-- 
You are receiving this mail because:
You are on the CC list for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 98894] Add an API for taking screenshots and recording screencasts

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=98894

--- Comment #3 from James Henstridge  ---
> Afaik, applications can't lie about /proc/[pid]/exe and the compositor could
> use .desktop files from /usr/share/applications for identification (with both
> name and icon).

It is pretty easy to spoof the result of readlink() on /proc/[pid]/exe though. 
With user and mount namespaces, a regular user could bind mount a different
executable over a trusted one before executing it.

This could be detected by comparing stat() information, but that would also
give false positives when upgrading a running application.

There's not an obvious generic solution.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs

[Wayland-bugs] [Bug 105108] Lenovo Yoga 11S touchpad is jittery

[bugzilla-daemon]

https://bugs.freedesktop.org/show_bug.cgi?id=105108

--- Comment #6 from Daniel van Vugt  ---
Confirmed on two machines (Yoga 11S and X1 Carbon gen 5) that using fuzz is a
better idea than resolution/2. Just still not as good as completely disabling
hysteresis (the cursor still visibly moves in squares, just smaller squares
now).

Caveats:
  1. That patch mentions this bug when it shouldn't. It's not a fix for this
bug.
  2. That patch assumes fuzz==0 means unknown fuzz. But I suspect for some
devices, fuzz=0 is the correct fuzz to use (equivalent to never enabling
hysteresis at all). I can't find documentation confirming this theory though.

-- 
You are receiving this mail because:
You are the assignee for the bug.___
wayland-bugs mailing list
wayland-bugs@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/wayland-bugs