[Wayland-bugs] [Bug 84817] Allow another local user to run programs on a WAYLAND_DISPLAY

https://bugs.freedesktop.org/show_bug.cgi?id=84817 --- Comment #7 from Paranoik --- This! They pretend that they care about our security and limit sudo graphical programs but in reality they simply didn't thought about multiuser desktop as a kind. Actually if one really care

[Wayland-bugs] [Bug 84817] Allow another local user to run programs on a WAYLAND_DISPLAY

https://bugs.freedesktop.org/show_bug.cgi?id=84817 --- Comment #9 from Daniel Stone --- (In reply to Daniel Stone from comment #8) > You can grant access to the socket to whichever uid you like, or you can > specifically bind-mount the uid into a particular container. So it

[Wayland-bugs] [Bug 84817] Allow another local user to run programs on a WAYLAND_DISPLAY

https://bugs.freedesktop.org/show_bug.cgi?id=84817 Daniel Stone changed: What|Removed |Added Status|NEW |RESOLVED

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

https://bugs.freedesktop.org/show_bug.cgi?id=98839 --- Comment #77 from Peter Hutterer --- https://lists.freedesktop.org/archives/wayland-devel/2018-January/036475.html fixes the issue with the current code, but it doesn't fully address James' issue. That however

[Wayland-bugs] [Bug 104533] Hysteresis detection fails on the single-touch axes after a while

https://bugs.freedesktop.org/show_bug.cgi?id=104533 Bug ID: 104533 Summary: Hysteresis detection fails on the single-touch axes after a while Product: Wayland Version: unspecified Hardware: Other OS: All

[Wayland-bugs] [Bug 84817] Allow another local user to run programs on a WAYLAND_DISPLAY

https://bugs.freedesktop.org/show_bug.cgi?id=84817 --- Comment #10 from Paranoik --- (In reply to Daniel Stone from comment #8) > > It's much more flexible than that. Wayland doesn't do a user lookup at all, > or rely on particular authentication files: it relies on

[Wayland-bugs] [Bug 103749] SW_TABLET_MODE disables monitor bezel button in tablet mode

https://bugs.freedesktop.org/show_bug.cgi?id=103749 --- Comment #16 from Peter Hutterer --- ping? -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs mailing list

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

https://bugs.freedesktop.org/show_bug.cgi?id=98839 --- Comment #78 from Daniel van Vugt --- Back on the topic of this bug in particular, I have recently seen that both Dell XPS 13 and Apple Macbook airs also require this fix. Although they have really nice touchpad

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

https://bugs.freedesktop.org/show_bug.cgi?id=98839 --- Comment #79 from Peter Hutterer --- which fix? the one in comment #68? then, well, yeah, that's the whole reason for this bug report to begin with. -- You are receiving this mail because: You are the assignee for

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

https://bugs.freedesktop.org/show_bug.cgi?id=98839 --- Comment #83 from Peter Hutterer --- huh? what fix, the one from comment #77? did the XPS have pointer wobbles before? -- You are receiving this mail because: You are the assignee for the

[Wayland-bugs] [Bug 104469] kernel: Touchpad cursor jumps (libinput 1.9.4) ASUS F3S

https://bugs.freedesktop.org/show_bug.cgi?id=104469 Peter Hutterer changed: What|Removed |Added Resolution|--- |MOVED

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

https://bugs.freedesktop.org/show_bug.cgi?id=98839 --- Comment #81 from Daniel van Vugt --- More good news: This fix works like magic on the Dell XPS 13. It's wonderful now. -- You are receiving this mail because: You are the assignee for the

[Wayland-bugs] [Bug 101139] Acceleration still too slow with medium finger movements

https://bugs.freedesktop.org/show_bug.cgi?id=101139 --- Comment #14 from Peter Hutterer --- That 'dead' zone is intentional, see https://who-t.blogspot.com.au/2016/12/libinput-touchpad-pointer-acceleration.html for a few graphs. And the main motivation there was that

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

https://bugs.freedesktop.org/show_bug.cgi?id=104470 Peter Hutterer changed: What|Removed |Added CC|

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

https://bugs.freedesktop.org/show_bug.cgi?id=98839 --- Comment #80 from Daniel van Vugt --- Put another way, I haven't yet seen any touchpad that didn't need hysteresis turned off (or reduced, or redesigned). I just made that comment because I was surprised to see

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

https://bugs.freedesktop.org/show_bug.cgi?id=98839 --- Comment #82 from Peter Hutterer --- we had turned the hysteresis off once and re-enabled it because of a whack-a-mole game with touchpads that needed it. look up the history between

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

https://bugs.freedesktop.org/show_bug.cgi?id=98839 --- Comment #84 from Daniel van Vugt --- No, the original fix from comment #68, I think. Or more precisely - libinput version 1.9.4-1 from Debian/Ubuntu does the trick (reverted in 1.9.4-2 due to James' issue

[Wayland-bugs] [Bug 103809] Inconsistent behaviour in relation to thumb rejection

https://bugs.freedesktop.org/show_bug.cgi?id=103809 --- Comment #15 from Peter Hutterer --- correct, a tap (when detected) should provide a left button press + release a bit later. there are a few timeouts involved, but it should still be obvious. The first issue