[Wayland-bugs] [Bug 98839] Somehow conditionalize hysteresis (hardware black/whitelist, device property introspection, user-exposed setting, etc)

2018-01-10 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=98839 --- Comment #89 from Daniel van Vugt --- I mostly agree, and was already aware of the 3 layers of stack issue. This is certainly worth the effort before resorting to that. If a config option was to ever be created

[Wayland-bugs] [Bug 783901] Restoring maximized window state in Wayland results in tiny window

2018-01-10 Thread mutter
https://bugzilla.gnome.org/show_bug.cgi?id=783901 Jonas Ådahl changed: What|Removed |Added Attachment #366610|none|reviewed

[Wayland-bugs] [Bug 98839] Somehow conditionalize hysteresis (hardware black/whitelist, device property introspection, user-exposed setting, etc)

2018-01-10 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=98839 --- Comment #88 from Peter Hutterer --- (In reply to Daniel van Vugt from comment #87) > I am happy to wait and see how the patch in comment #77 goes in the wild but > I'm slightly less optimistic about it only taking

[Wayland-bugs] [Bug 98839] Somehow conditionalize hysteresis (hardware black/whitelist, device property introspection, user-exposed setting, etc)

2018-01-10 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=98839 --- Comment #87 from Daniel van Vugt --- I am happy to wait and see how the patch in comment #77 goes in the wild but I'm slightly less optimistic about it only taking 80ms. Starting on a login screen I find

[Wayland-bugs] [Bug 783901] Restoring maximized window state in Wayland results in tiny window

2018-01-10 Thread mutter
https://bugzilla.gnome.org/show_bug.cgi?id=783901 Jonas Ådahl changed: What|Removed |Added Attachment #366609|none|accepted-commit_now

[Wayland-bugs] [Bug 780820] [Wayland] Focused window under application first window

2018-01-10 Thread mutter
https://bugzilla.gnome.org/show_bug.cgi?id=780820 Jonas Ådahl changed: What|Removed |Added Attachment #366607|none|accepted-commit_now

[Wayland-bugs] [Bug 783901] Restoring maximized window state in Wayland results in tiny window

2018-01-10 Thread mutter
https://bugzilla.gnome.org/show_bug.cgi?id=783901 Olivier Fourdan changed: What|Removed |Added Attachment #354146|reviewed|none

[Wayland-bugs] [Bug 783901] Restoring maximized window state in Wayland results in tiny window

2018-01-10 Thread mutter
https://bugzilla.gnome.org/show_bug.cgi?id=783901 Olivier Fourdan changed: What|Removed |Added Attachment #354148|reviewed|none

[Wayland-bugs] [Bug 780820] [Wayland] Focused window under application first window

2018-01-10 Thread mutter
https://bugzilla.gnome.org/show_bug.cgi?id=780820 --- Comment #26 from Olivier Fourdan --- Humm, looks like this patch is breaking stacking of g-s dialogs... -- You are receiving this mail because: You are on the CC list for the

[Wayland-bugs] [Bug 98839] Somehow conditionalize hysteresis (hardware black/whitelist, device property introspection, user-exposed setting, etc)

2018-01-10 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=98839 --- Comment #86 from Peter Hutterer --- thanks for testing, basically matches my expectations. Note that you are fine-tuned to notice this bug at the moment. The timeout is 80ms and it only needs to be triggered once

[Wayland-bugs] [Bug 791656] GTK misbehaves at scale factors >2

2018-01-10 Thread gtk+
https://bugzilla.gnome.org/show_bug.cgi?id=791656 --- Comment #7 from Drew DeVault --- Additional rationale for a more broadly applicable patch: more accessibility reasons. Consider the use-case of setting scale to 4 on a 4K display, then downscaling it 2x normally, but

[Wayland-bugs] [Bug 780820] [Wayland] Focused window under application first window

2018-01-10 Thread mutter
https://bugzilla.gnome.org/show_bug.cgi?id=780820 Olivier Fourdan changed: What|Removed |Added Attachment #366553|reviewed|none

[Wayland-bugs] [Bug 94986] ETPS/2 Elantech Touchpad imprecise pointer movement using libinput

2018-01-10 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=94986 --- Comment #7 from Daniel van Vugt --- Maybe see how the fix for bug 101139 goes too. -- You are receiving this mail because: You are the assignee for the bug.___

[Wayland-bugs] [Bug 94986] ETPS/2 Elantech Touchpad imprecise pointer movement using libinput

2018-01-10 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=94986 --- Comment #6 from Daniel van Vugt --- Sounds like a duplicate of bug 98839. The fix for that bug resolves imprecise pointer movement on every touchpad I had tested. It is due for release in libinput 1.10.0 --

[Wayland-bugs] [Bug 98839] Somehow conditionalize hysteresis (hardware black/whitelist, device property introspection, user-exposed setting, etc)

2018-01-10 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=98839 --- Comment #85 from Daniel van Vugt --- I have done more hardware testing today with four different laptops and three different versions of libinput. The laptops are X1 Carbon gen 4, X1 Carbon gen 5, Dell XPS 13

[Wayland-bugs] [Bug 104470] Dell xps 13 8th gen: synaptics touchpad too slow and palm detection basically not working

2018-01-10 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=104470 --- Comment #3 from Daniel van Vugt --- I have been testing a Dell XPS 13 (5th gen) today and find the fix for bug 98839 is all it needs to address the responsiveness problems. That's due for release in libinput

[Wayland-bugs] [Bug 100752] Cursor lag on synaptics touchpad

2018-01-10 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=100752 --- Comment #17 from Daniel van Vugt --- Duplicate of bug 98839. Not having enough precision to "reach stuff like buttons, links, window borders etc" is fixed with bug 98839, due for release in libinput 1.10. --

[Wayland-bugs] [Bug 103619] libinput has problems with precise mouse pointer movement on Lenovo X1v5

2018-01-10 Thread bugzilla-daemon
https://bugs.freedesktop.org/show_bug.cgi?id=103619 --- Comment #8 from Daniel van Vugt --- I have been testing an X1 Carbon gen 5 today and have confirmed that all it needs is the fix for bug 98839. That's due for release in libinput 1.10. So this is probably a