[Wayland-bugs] [Bug 103757] eglGetDisplay() is broken for Wayland

https://bugs.freedesktop.org/show_bug.cgi?id=103757 --- Comment #10 from Pekka Paalanen --- (In reply to Michael Olbrich from comment #9) > (In reply to Pekka Paalanen from comment #1) > > Any reason you cannot use EGL_KHR_platform_wayland? > > It's not my code. It's

[Wayland-bugs] [Bug 103594] Touchpad works horrible

https://bugs.freedesktop.org/show_bug.cgi?id=103594 --- Comment #9 from Max S --- (In reply to Pavel from comment #7) I have 2 Xiaomi 12.5 here. They already have kernel 4.14 running. I am typing this now after switching to kernel 4.10.17-2-MANJARO The problem does definitely

[Wayland-bugs] [Bug 103210] One-finger tap registered as two-finger tap when touch-size-based palm rejection is triggered

https://bugs.freedesktop.org/show_bug.cgi?id=103210 --- Comment #19 from Peter Hutterer --- yep, it's a thumb detection bug. Should be fixed now on that branch with 58bee17f, thanks -- You are receiving this mail because: You are the assignee for the

[Wayland-bugs] [Bug 101140] Expose an acceleration setting

https://bugs.freedesktop.org/show_bug.cgi?id=101140 Nate Graham changed: What|Removed |Added Resolution|--- |WONTFIX

[Wayland-bugs] [Bug 98535] libinput touchpad acceleration tracker bug

https://bugs.freedesktop.org/show_bug.cgi?id=98535 Bug 98535 depends on bug 101140, which changed state. Bug 101140 Summary: Expose an acceleration setting https://bugs.freedesktop.org/show_bug.cgi?id=101140 What|Removed |Added

[Wayland-bugs] [Bug 99268] With Clickfinger behavior, pointer movement briefly turns into a scroll when a thumb is dropped onto the pad

https://bugs.freedesktop.org/show_bug.cgi?id=99268 --- Comment #7 from Nate Graham --- Created attachment 135511 --> https://bugs.freedesktop.org/attachment.cgi?id=135511=edit evemu record with git master and kernel 4.13.0 Correction: I was mistakenly using areas mode

[Wayland-bugs] [Bug 99268] With Clickfinger behavior, pointer movement briefly turns into a scroll when a thumb is dropped onto the pad

https://bugs.freedesktop.org/show_bug.cgi?id=99268 Nate Graham changed: What|Removed |Added Status|RESOLVED|REOPENED

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

https://bugs.freedesktop.org/show_bug.cgi?id=101139 --- Comment #4 from Greg Reichow --- Created attachment 135510 --> https://bugs.freedesktop.org/attachment.cgi?id=135510=edit Patch for Macbook Pro 8,2 testing Patch from libinput 1.9.1 attached Changes: 1. Added thumb

[Wayland-bugs] [Bug 99267] Cursor resolution/refresh rate decreases when a thumb is resting on the pad, especially with clickfinger behavior

https://bugs.freedesktop.org/show_bug.cgi?id=99267 --- Comment #16 from Nate Graham --- OK, so I am now running libinput from git master and I have the 4.13.0 kernel, but there is still no improvement here. xinput still shows "SynPS/2 Synaptics TouchPad" How do I turn on

[Wayland-bugs] [Bug 101147] Elantech touchpad double Tap Time too short on ASUS Zenbook UX410UQ

https://bugs.freedesktop.org/show_bug.cgi?id=101147 --- Comment #15 from Peter Hutterer --- sorry, completely swamped. I just sent the patch for replacing the tool with a python version to the list. It doesn't do double-tap yet though.

[Wayland-bugs] [Bug 103594] Touchpad works horrible

https://bugs.freedesktop.org/show_bug.cgi?id=103594 Peter Hutterer changed: What|Removed |Added Depends on||98839 ---

[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 Peter Hutterer changed: What|Removed |Added Blocks||103594

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

https://bugs.freedesktop.org/show_bug.cgi?id=101139 --- Comment #3 from Nate Graham --- Greg, if you put that in patch form, I'd love to test it out. -- You are receiving this mail because: You are the assignee for the bug.___

[Wayland-bugs] [Bug 103594] Touchpad works horrible

https://bugs.freedesktop.org/show_bug.cgi?id=103594 --- Comment #7 from Pavel --- (In reply to Max S from comment #5) Are you sure it is not libinput, but kernel? My kernel version is 4.13.0-16-generic I have described problems on Ubuntu 17.10 Wayland session. BUT on X.org

[Wayland-bugs] [Bug 103594] Touchpad works horrible

https://bugs.freedesktop.org/show_bug.cgi?id=103594 --- Comment #5 from log...@mx-s.me --- Hello, I stumbled upon this bug; I noticed the same behaviour earlier this year. You can find a short thread here: https://bbs.archlinux.org/viewtopic.php?pid=1731889#p1731889 I'm pretty sure it is no

[Wayland-bugs] [Bug 103757] eglGetDisplay() is broken for Wayland

https://bugs.freedesktop.org/show_bug.cgi?id=103757 --- Comment #9 from Michael Olbrich --- (In reply to Pekka Paalanen from comment #1) > Any reason you cannot use EGL_KHR_platform_wayland? It's not my code. It's somewhere in gstreamer-vaapi. I was just debugging why

[Wayland-bugs] [Bug 103757] eglGetDisplay() is broken for Wayland

https://bugs.freedesktop.org/show_bug.cgi?id=103757 --- Comment #8 from Michael Olbrich --- (In reply to Daniel Stone from comment #7) > Good point - I guess it'd have to be if > (_eglPointerIsDereferencable(child_pointer) && > _eglPointerIsDereferencable(((char *)

[Wayland-bugs] [Bug 103757] eglGetDisplay() is broken for Wayland

https://bugs.freedesktop.org/show_bug.cgi?id=103757 --- Comment #7 from Daniel Stone --- (In reply to Michael Olbrich from comment #6) > (In reply to Daniel Stone from comment #2) > > > Michael, I'll attach a compiled but untested patch; can you please let me > > know if

[Wayland-bugs] [Bug 103757] eglGetDisplay() is broken for Wayland

https://bugs.freedesktop.org/show_bug.cgi?id=103757 --- Comment #6 from Michael Olbrich --- (In reply to Daniel Stone from comment #2) > Michael, I'll attach a compiled but untested patch; can you please let me > know if it helps? Looks good. It does the right thing

[Wayland-bugs] [Bug 103561] libinput 1.8.3 -> 1.9.1: laptop keyboard not working

https://bugs.freedesktop.org/show_bug.cgi?id=103561 --- Comment #27 from dpaessler --- (In reply to Benjamin Berg from comment #26) but it looks like it might be fixing the issue that dpaessler is seeing. Thanks for pointing this out, that indeed fixed it for me (kernel

[Wayland-bugs] [Bug 103757] eglGetDisplay() is broken for Wayland

https://bugs.freedesktop.org/show_bug.cgi?id=103757 --- Comment #5 from Daniel Stone --- (In reply to Emil Velikov from comment #4) > > I do recall mentioning that exposing the same symbol(s) will lead to bad > experiences. Followed by some ideas... > Yep, as per the

[Wayland-bugs] [Bug 103757] eglGetDisplay() is broken for Wayland

https://bugs.freedesktop.org/show_bug.cgi?id=103757 --- Comment #4 from Emil Velikov --- I do recall mentioning that exposing the same symbol(s) will lead to bad experiences. Followed by some ideas... WRT eglGetDisplay - I'd recommend moving towards the

[Wayland-bugs] [Bug 103673] Missing mouse button release event when multiple buttons are released

https://bugs.freedesktop.org/show_bug.cgi?id=103673 --- Comment #3 from Antti Korpi --- Just confirming that I agree this is a duplicate. Thanks! -- You are receiving this mail because: You are the assignee for the bug.___ wayland-bugs

[Wayland-bugs] [Bug 103757] eglGetDisplay() is broken for Wayland

https://bugs.freedesktop.org/show_bug.cgi?id=103757 --- Comment #3 from Daniel Stone --- Created attachment 135490 --> https://bugs.freedesktop.org/attachment.cgi?id=135490=edit egldisplay-try-interface-name-for-wl-display.patch -- You are receiving this mail because:

[Wayland-bugs] [Bug 103757] eglGetDisplay() is broken for Wayland

https://bugs.freedesktop.org/show_bug.cgi?id=103757 --- Comment #2 from Daniel Stone --- (In reply to Pekka Paalanen from comment #1) > eglGetDisplay() is by definition broken on multi-platform implementations, > yes. Ugh. It is broken by definition, but Mesa does go to

[Wayland-bugs] [Bug 790201] Settings in ~/.config/gtk-3.0/settings.ini ignored with GDK_BACKEND=wayland

https://bugzilla.gnome.org/show_bug.cgi?id=790201 --- Comment #4 from Alex Ivanov --- Created attachment 363679 --> https://bugzilla.gnome.org/attachment.cgi?id=363679=edit don't provide gsetting if dconf is not available Fix for Emmanuele Bassi case > Alternatively, remove

[Wayland-bugs] [Bug 103757] eglGetDisplay() is broken for Wayland

https://bugs.freedesktop.org/show_bug.cgi?id=103757 --- Comment #1 from Pekka Paalanen --- eglGetDisplay() is by definition broken on multi-platform implementations, yes. Any reason you cannot use EGL_KHR_platform_wayland? -- You are receiving this mail because: You are

[Wayland-bugs] [Bug 103757] eglGetDisplay() is broken for Wayland

https://bugs.freedesktop.org/show_bug.cgi?id=103757 Bug ID: 103757 Summary: eglGetDisplay() is broken for Wayland Product: Mesa Version: git Hardware: Other OS: All Status: NEW Severity: normal

[Wayland-bugs] [Bug 790201] Settings in ~/.config/gtk-3.0/settings.ini ignored with GDK_BACKEND=wayland

https://bugzilla.gnome.org/show_bug.cgi?id=790201 --- Comment #3 from Alex Ivanov --- > My strong suggestion is for you to change the GSettings, if you're running > under Wayland, instead of trying to use a key/value file for everything That's hard to achieve outside of Gnome,

[Wayland-bugs] [Bug 790201] Settings in ~/.config/gtk-3.0/settings.ini ignored with GDK_BACKEND=wayland

https://bugzilla.gnome.org/show_bug.cgi?id=790201 Emmanuele Bassi (:ebassi) changed: What|Removed |Added CC|

[Wayland-bugs] [Bug 790201] Settings in ~/.config/gtk-3.0/settings.ini ignored with GDK_BACKEND=wayland

https://bugzilla.gnome.org/show_bug.cgi?id=790201 --- Comment #1 from Alex Ivanov --- Created attachment 363663 --> https://bugzilla.gnome.org/attachment.cgi?id=363663=edit ability to use GtkSettings under Wayland This patch adds GDK_WAYLAND_USE_GTKSETTINGS environment

[Wayland-bugs] [Bug 103476] RFE: libinput: Add support for Trust TB-4200 Wireless Scroll Tablet (Aiptek based)

https://bugs.freedesktop.org/show_bug.cgi?id=103476 --- Comment #5 from Martin Kolman --- (In reply to Peter Hutterer from comment #4) > ping? Sorry, I was quite busy so far, but I should be able to take a look at it on Friday. :) -- You are receiving this mail