[Wayland-bugs] [Bug 105409] Touchpad deadzone on Razer Blade Stealth

[bugzilla-daemon]

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

--- Comment #24 from Dave  ---
So far so good, will keep you posted

-- 
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 105409] Touchpad deadzone on Razer Blade Stealth

[bugzilla-daemon]

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

--- Comment #23 from Dave  ---
Created attachment 138118
  --> https://bugs.freedesktop.org/attachment.cgi?id=138118=edit
output of evemu-describe when no deadzone was observed

I haven't had a chance to try the patch yet, but I've noticed that the issue
isn't present 100% of the time anymore. After resuming from suspend, there was
no apparent deadzone for a couple minutes, but it eventually returned.
I ran evenmu-describe when it was working, to highlight what changes have been
made, hoping it might point to something.

Since the issues has returned, I'll try the patch now.

-- 
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 105512] Invalid tap event TAP_EVENT_RELEASE in state TAP_STATE_{TAPPED, MULTITAP}

[bugzilla-daemon]

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

--- Comment #2 from Vincent Blut  ---
(In reply to Peter Hutterer from comment #1)
> I'll need an evemu-record that triggers that bug please, thanks.
Ok, will do as soon as possible.

> You're on 1.10.3?
Indeed.

-- 
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 105512] Invalid tap event TAP_EVENT_RELEASE in state TAP_STATE_{TAPPED, MULTITAP}

[bugzilla-daemon]

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

Peter Hutterer  changed:

   What|Removed |Added

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

--- Comment #1 from Peter Hutterer  ---
I'll need an evemu-record that triggers that bug please, thanks. You're on
1.10.3?

-- 
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 105512] Invalid tap event TAP_EVENT_RELEASE in state TAP_STATE_{TAPPED, MULTITAP}

[bugzilla-daemon]

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

Bug ID: 105512
   Summary: Invalid tap event TAP_EVENT_RELEASE in state
TAP_STATE_{TAPPED,MULTITAP}
   Product: Wayland
   Version: unspecified
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
  Severity: normal
  Priority: medium
 Component: libinput
  Assignee: wayland-bugs@lists.freedesktop.org
  Reporter: vincent.deb...@free.fr

Hello,

Libinput 1.10.x branch introduced a regression regarding three-finger click on
my Elantech touchpad.
Sporadically, any middle click attempt is ineffective. When that happens, the
following errors get logged:

(EE) event1  - ETPS/2 Elantech Touchpad: libinput bug: invalid tap event
TAP_EVENT_RELEASE in state TAP_STATE_TAPPED
(EE) event1  - ETPS/2 Elantech Touchpad: libinput bug: invalid tap event
TAP_EVENT_RELEASE in state TAP_STATE_MULTITAP

Do you have an idea about what goes wrong?

-- 
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 105409] Touchpad deadzone on Razer Blade Stealth

[bugzilla-daemon]

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

--- Comment #22 from Benjamin Tissoires  ---
Created attachment 138113
  --> https://bugs.freedesktop.org/attachment.cgi?id=138113=edit
kernel patch to remove the deadzone and palm detection

Would it be possible for you to try the attached patch on a recent kernel?
I locally tested it with your recording, and I now see all of the events.

However, the things I am not so sure are for the reporting of the buttons, and
if disabling the device palm detection is worse than having it (like if you get
ghosts events).

-- 
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 105507] Crash when destroying a newly resized EGLsurface with wayland egl (dri2)

[bugzilla-daemon]

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

--- Comment #2 from Daniel Stone  ---
You could place any orphaned wl_buffers on an per-surface list instead, and
spin at destruction until that emptied. I won't have the time to look into it
myself for a while though.

Johan - which test hits this?

-- 
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 105507] Crash when destroying a newly resized EGLsurface with wayland egl (dri2)

[bugzilla-daemon]

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

Emil Velikov  changed:

   What|Removed |Added

 CC||dan...@fooishbar.org

--- Comment #1 from Emil Velikov  ---
Daniel, any suggestions?

-- 
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 103749] SW_TABLET_MODE disables monitor bezel button in tablet mode

[bugzilla-daemon]

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

Michał Kopeć  changed:

   What|Removed |Added

 CC||mkope...@gmail.com

--- Comment #20 from Michał Kopeć  ---
I've managed to adapt the patch (comment #15) to my specific machine and latest
libinput version, but there's no change in behaviour. Let me know if you want
me to run any tests or provide information about my configuration.

-- 
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 103749] SW_TABLET_MODE disables monitor bezel button in tablet mode

[bugzilla-daemon]

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

--- Comment #19 from Michał Kopeć  ---
I have the same problem with my ThinkPad X60 hardware tablet buttons. Switching
the machine to laptop mode (rotating the screen) disables the buttons located
on the screen bezel. 

Components:
- libinput 1.10.2
- Arch Linux (kernel 4.15.8)
- GNOME Shell 3.26.2

-- 
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 105507] Crash when destroying a newly resized EGLsurface with wayland egl (dri2)

[bugzilla-daemon]

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

Bug ID: 105507
   Summary: Crash when destroying a newly resized EGLsurface with
wayland egl (dri2)
   Product: Mesa
   Version: 17.3
  Hardware: x86-64 (AMD64)
OS: Linux (All)
Status: NEW
  Severity: normal
  Priority: medium
 Component: EGL/Wayland
  Assignee: wayland-bugs@lists.freedesktop.org
  Reporter: johan.hels...@qt.io
QA Contact: mesa-...@lists.freedesktop.org

In dri2_wl_surface_release_buffers, a wl_buffer is not destroyed if it's
locked. Afterwards it's set to null regardless
(dri2_surf->color_buffers[i].wl_buffer = NULL;)

Normally, this is fine, since the buffer will be released by the
wl_buffer_release event when the compositor is done with it. But if the
EGLSurface is destroyed first, then the event queue for the surface (and for
the wl_buffer) is destroyed, and the wl_release event then causes a crash
because we try to use a destroyed event queue.

One solution would be to maintain a separate list of buffers we tried to
destroy, but couldn't because they were locked. And make sure they are
destroyed in dri2_wl_destroy_surface.

This might not be a problem users frequently run into, but it's causing many
unit tests in Qt to be flaky, and we probably have to blacklist them until this
is fixed (https://bugreports.qt.io/browse/QTBUG-66848)

-- 
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 105485] Add hwdb entry for X280 trackpoint (too fast)

[bugzilla-daemon]

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

--- Comment #2 from Benjamin Berg  ---
Got confused a bit at first, but the measurement was without the sensitivity
scaling in the end.

-- 
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 105258] libinput crashes Xorg with SIGABRT in tp_tap_handle_state() [evdev-mt-touchpad-tap.c:1030|1028]

[bugzilla-daemon]

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

--- Comment #27 from mrbloo...@hotmail.com ---
Thank you. I have tested it with 1.10.3 and it's fixed.
I got confused for a bit, because the bug tracker on the distribution said it
was fixed in 1.10.2, but they meant the first bug in this report.

-- 
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