[Wayland-bugs] [Bug 97288] Handle wacom tablet touch on/off switch

[bugzilla-daemon]

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

Peter Hutterer  changed:

   What|Removed |Added

 Status|ASSIGNED|RESOLVED
 Resolution|--- |WONTFIX

--- Comment #3 from Peter Hutterer  ---
Closing as wontfix, no immediate for it for 1.5 years so let's implement it
when someone needs 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 104788] Touchpad hysteresis doesn't work

[bugzilla-daemon]

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

--- Comment #4 from Peter Hutterer  ---
No, there's no toggle short of adding code and recompiling, sorry. But it
disables after 80ms of no movement with the finger on the touchpad, so the
easiest way to get around the initial disabling is to just use the keyboard + a
mouse to log in. Or start evemu from a vt, it doesn't care about the session
anyway since it sits below everything.

-- 
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 104788] Touchpad hysteresis doesn't work

[bugzilla-daemon]

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

--- Comment #3 from Hi-Angel  ---
(In reply to Peter Hutterer from comment #2)
> libinput looks at the touchpad motion and if the finger is down for some
> time without motion events (i.e. without wobbles) the motion hysteresis is
> disabled. See bug 98839.
> 
> This would explain why it works after login and then starts wobbling later -
> likely after the hysteresis was disabled. Once disabled, it stays disabled
> until you log out/restart.
> 
> You can easily verify this with sudo libinput debug-events --verbose, pipe
> it into a file and check for a hysteresis disabled message once it starts
> wobbling.
> 
> To debug this further though I'll need an evemu record that triggers this
> because the one you attached doesn't seem to disable the hysteresis.

Thanks for your response. Any way to enable motion hysteresis in running
system? I'm asking because it's a bit problematic to catch the moment it's is
still working. For example when I installed latest git version for testing, I
restarted sddm, and upon logging into system hysteresis have already been
disabled. That's the reason I was surprised when the next day after reboot it
was working for some time.

But if there's no way, of course I'll try to catch the moment manually.

-- 
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 104828] Jumpy AlpsPS/2 ALPS DualPoint TouchPad

[bugzilla-daemon]

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

--- Comment #2 from Daniel van Vugt  ---
Note that version 1.9.4-2ubuntu1 is just 1.9.4-2 with the fix for bug 98839
added.

-- 
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 104828] Jumpy AlpsPS/2 ALPS DualPoint TouchPad

[bugzilla-daemon]

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

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 recording of the issue please, thanks.

-- 
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 104812] kernel: touchpad jump (libinput 1.9.3) Lenovo R61

[bugzilla-daemon]

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

Peter Hutterer  changed:

   What|Removed |Added

 CC||benjamin.tissoi...@gmail.co
   ||m, peter.hutte...@who-t.net
 Status|NEW |NEEDINFO

--- Comment #1 from Peter Hutterer  ---
Attach a dmesg please and the output of hid-record for the device, thanks.

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

Peter Hutterer  changed:

   What|Removed |Added

 Resolution|--- |WONTFIX
 Status|NEEDINFO|RESOLVED

--- Comment #18 from Peter Hutterer  ---
sorry, closing after another 2+ weeks in needinfo. I can't merge these things
without testing the hwdb is not something I can test locally unless I have the
exact same device.

-- 
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 104569] Touchpad two-finger scrolling is 2x the velocity of cursor movement

[bugzilla-daemon]

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

Peter Hutterer  changed:

   What|Removed |Added

 Status|NEW |NEEDINFO

-- 
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 104734] Unreliable two-finger scrolling

[bugzilla-daemon]

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

--- Comment #8 from Peter Hutterer  ---
Yeah, I agree, we can be a bit more detailed here and check for motion
distance/motion speed/something? Not sure what exactly though and I'm
bottlenecking everywhere already, so I'll definitely will need help with that,
sorry.

-- 
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 104788] Touchpad hysteresis doesn't work

[bugzilla-daemon]

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

Peter Hutterer  changed:

   What|Removed |Added

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

--- Comment #2 from Peter Hutterer  ---
libinput looks at the touchpad motion and if the finger is down for some time
without motion events (i.e. without wobbles) the motion hysteresis is disabled.
See bug 98839.

This would explain why it works after login and then starts wobbling later -
likely after the hysteresis was disabled. Once disabled, it stays disabled
until you log out/restart.

You can easily verify this with sudo libinput debug-events --verbose, pipe it
into a file and check for a hysteresis disabled message once it starts
wobbling.

To debug this further though I'll need an evemu record that triggers this
because the one you attached doesn't seem to disable the hysteresis.


Referenced Bugs:

https://bugs.freedesktop.org/show_bug.cgi?id=98839
[Bug 98839] Somehow conditionalize hysteresis (hardware black/whitelist, device
property introspection, user-exposed setting, etc)
-- 
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 98839] Somehow conditionalize hysteresis (hardware black/whitelist, device property introspection, user-exposed setting, etc)

[bugzilla-daemon]

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

Peter Hutterer  changed:

   What|Removed |Added

 Blocks||104788


Referenced Bugs:

https://bugs.freedesktop.org/show_bug.cgi?id=104788
[Bug 104788] Touchpad hysteresis doesn't work
-- 
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 104867] Export the number of touches

[bugzilla-daemon]

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

Peter Hutterer  changed:

   What|Removed |Added

 CC||carl...@gnome.org,
   ||peter.hutte...@who-t.net

--- Comment #1 from Peter Hutterer  ---
Just a few notes: the TOUCH capability is assigned to any touch device, even
single-touch touchscreens. Whether it's single touch or multi-touch is not
exposed, but we have device->mt.slots_len with the number of slots internally.

There is no capability API outside of that, the closest we have for querying
specific devices is the libinput_device__has* set of functions to check
for buttons or keys. So libinput_device_touch_get_num_touches() would fit, and
so would libinput_device_touch_has_multitouch() for a basic boolean check.

CC-ing carlos in case he has any thoughts on using it in mutter.

-- 
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 104415] My wireless all-in-one (keyboard/mouse) requires a triple-tap to highlight a word

[bugzilla-daemon]

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

Peter Hutterer  changed:

   What|Removed |Added

   Assignee|wayland-bugs@lists.freedesk |peter.hutte...@who-t.net
   |top.org |

--- Comment #9 from Peter Hutterer  ---
Created attachment 137101
  --> https://bugs.freedesktop.org/attachment.cgi?id=137101=edit
0001-evdev-add-a-quirk-to-disable-debouncing-on-the-MS-Na.patch

Give this one a test please. You'll need to update the hwdb accordingly, see:
https://wayland.freedesktop.org/libinput/doc/latest/udev_config.html#hwdb

Unless I typoed something, it should work after the above commands and a
restart. Make sure the udev property appears in the udevadm info output before
you restart 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

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

[gtk+]

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

--- Comment #3 from Olivier Fourdan  ---
I wonder how we can end up in end_paint() with a wl_surface being NULL.

_gdk_frame_clock_emit_paint() ends up calling gtk_widget_render() which calls
gdk_window_end_draw_frame (window, context) which calls
gdk_window_impl_wayland_end_paint(), but there the window's wl_surface is NULL.

As Martin pointed out, this is from:

1833 case GDK_EXPOSE:
1834   if (event->any.window)
1835 gtk_widget_render (event_widget, event->any.window,
event->expose.region);
1836   break;

So the window here from event->any.window has its wl_surface NULL.

That event here comes from _gdk_window_process_updates_recurse_helper():

 3835   /* While gtk+ no longer handles exposes on anything but native
 3836  window we still have to send them to all windows that have the
 3837  event mask set for backwards compat. We also need to send
 3838  it to all native windows, even if they don't specify the
 3839  expose mask, because they may have non-native children that do. */
 3840   if (gdk_window_has_impl (window) ||
 3841   window->event_mask & GDK_EXPOSURE_MASK)
 3842 {
 3843   GdkEvent event;
 3844 
 3845   event.expose.type = GDK_EXPOSE;
 3846   event.expose.window = window; /* we already hold a ref */
 3847   event.expose.send_event = FALSE;
 3848   event.expose.count = 0;
 3849   event.expose.region = clipped_expose_region;
 3850   cairo_region_get_extents (clipped_expose_region,
);
 3851 
 3852   _gdk_event_emit ();
 3853 }
 3854 

And this is from gdk_window_process_updates_internal(window) called from:

 4163 static void
 4164 gdk_window_process_updates_with_mode (GdkWindow *window,
 4165   intrecurse_mode)
 4166 {
 ...
 4174 
 4175   find_impl_windows_to_update (list, window, recurse_mode);
 4176 
 4177   if (window->impl_window != window)
 4178 g_ptr_array_add (list, g_object_ref (window->impl_window));
 4179 
 4180   for (i = (int)list->len - 1; i >= 0; i --)
 4181 {
 4182   GdkWindow *impl_window = g_ptr_array_index (list, i);
 4183 
 4184   if (impl_window->update_area &&
 4185   !impl_window->update_freeze_count &&
 4186   !gdk_window_is_toplevel_frozen (impl_window) &&
 4187 
 4188   /* Don't recurse into process_updates_internal, we'll
 4189* do the update later when idle instead. */
 4190   !impl_window->in_update)
 4191 {
 4192   gdk_window_process_updates_internal (impl_window);
 4193   gdk_window_remove_update_window (impl_window);
 4194 }
 4195 }

-- 
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 98770] kernel: Elantech 3320KD-3100 Touchpad behind [ASUS T300CHI DOCKING] Bluetooth not recognised

[bugzilla-daemon]

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

--- Comment #27 from er453r  ---
I did some more digging, and confirmed that the Asus driver sends additional
commands to the device on Windows to enable the multitouch capabilities.

I've also did a packet dump on windows of the device communications with the OS
(without ASUS driver, with ASUS driver, and then testing gesture and mouse
commands).

I can confirm that the driver indeed sends additional commands. I've tried
sending them by hand to the device descriptor but it did not trigger the
mutlitouch events :/

Attaching the bluetooth dump, maybe this will help someone.

-- 
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 98770] kernel: Elantech 3320KD-3100 Touchpad behind [ASUS T300CHI DOCKING] Bluetooth not recognised

[bugzilla-daemon]

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

--- Comment #26 from er453r  ---
Created attachment 137089
  --> https://bugs.freedesktop.org/attachment.cgi?id=137089=edit
wireshark logs of bluetooth communication with and without the ASUS driver

-- 
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 773274] [Wayland] Crash under gdk_wayland_window_attach_image()

[gtk+]

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

Olivier Fourdan  changed:

   What|Removed |Added

 Attachment #367641|none|needs-work
 status||

--- Comment #34 from Olivier Fourdan  ---
Review of attachment 367641:

Seems it can still crash for the same reason in
gdk_window_impl_wayland_end_paint()

-- 
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 793062] [Wayland] Crash under gdk_wayland_window_attach_image()

[gtk+]

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

--- Comment #2 from Martin Stransky  ---
This crash happens at gdk_window_impl_wayland_end_paint() and at
wl_surface_damage() where impl->display_server.wl_surface is null.

-- 
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 793062] [Wayland] Crash under gdk_wayland_window_attach_image()

[gtk+]

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

--- Comment #1 from Martin Stransky  ---
I see another crash with this patch applied:

(gdb) pimpl->display_server.wl_surface
$2 = (struct wl_surface *) 0x0

It also comes from the expose event handler, bt:

#8  0x7f9f66b3a52f in wl_surface_damage (height=,
width=, y=, x=,
wl_surface=) at /usr/include/wayland-client-protocol.h:3478
#9  0x7f9f66b3a52f in gdk_window_impl_wayland_end_paint
(window=0x7f9f2b3c4830 [GdkWaylandWindow])
at gdkwindow-wayland.c:952
#10 0x7f9f66aee8bb in gdk_window_end_paint_internal
(window=window@entry=0x7f9f2b3c4830 [GdkWaylandWindow])
at gdkwindow.c:3021
#11 0x7f9f66aeec88 in gdk_window_end_draw_frame
(window=window@entry=0x7f9f2b3c4830 [GdkWaylandWindow],
context=context@entry=0x7f9f408735b0 [GdkDrawingContext]) at gdkwindow.c:3289
#12 0x7f9f671276e3 in gtk_widget_render (widget=widget@entry=0x7f9f344d0e60
[GtkWindow], window=0x7f9f2b3c4830 [GdkWaylandWindow], region=)
at gtkwidget.c:17522
#13 0x7f9f66fc7a49 in gtk_main_do_event (event=) at
gtkmain.c:1834
#14 0x7f9f66ad5305 in _gdk_event_emit (event=event@entry=0x7fffc1dfbf80) at
gdkevents.c:73
#15 0x7f9f66ae5655 in _gdk_window_process_updates_recurse_helper
(window=0x7f9f2b3c4830 [GdkWaylandWindow], expose_region=) at
gdkwindow.c:3852
#16 0x7f9f66ae6856 in gdk_window_process_updates_internal
(window=0x7f9f2b3c4830 [GdkWaylandWindow]) at gdkwindow.c:3998
#17 0x7f9f66ae6a50 in gdk_window_process_updates_with_mode
(window=, recurse_mode=)
at gdkwindow.c:4192
#21 0x7f9f6444266f in  (instance=instance@entry=0x7f9f3fff2430,
signal_id=, detail=detail@entry=0) at gsignal.c:3447
#18 0x7f9f6442673d in g_closure_invoke (closure=0x7f9f344cde40,
return_value=0x0, n_param_values=1, param_values=0x7fffc1dfc260,
invocation_hint=0x7fffc1dfc1e0) at gclosure.c:804
#19 0x7f9f644394de in signal_emit_unlocked_R
(node=node@entry=0x7f9f49804220, detail=detail@entry=0,
instance=instance@entry=0x7f9f3fff2430,
emission_return=emission_return@entry=0x0,
instance_and_params=instance_and_params@entry=0x7fffc1dfc260) at gsignal.c:3635
#20 0x7f9f64441d05 in g_signal_emit_valist (instance=0x7f9f3fff2430,
signal_id=, detail=0, var_args=var_args@entry=0x7fffc1dfc430) at
gsignal.c:3391
#22 0x7f9f66ade13f in _gdk_frame_clock_emit_paint
(frame_clock=frame_clock@entry=0x7f9f3fff2430 [GdkFrameClockIdle])
at gdkframeclock.c:640
#23 0x7f9f66ade871 in gdk_frame_clock_paint_idle (data=0x7f9f3fff2430) at
gdkframeclockidle.c:430
#24 0x7f9f66ac99d0 in gdk_threads_dispatch (data=data@entry=0x7f9f36415460)
at gdk.c:743
#25 0x7f9f6414e5dd in g_timeout_dispatch (source=0x7f9f3fe13cf0,
callback=0x7f9f66ac99b0 , user_data=0x7f9f36415460) at
gmain.c:4615
#26 0x7f9f6414db77 in g_main_dispatch (context=0x7f9f693a5f50) at
gmain.c:3142

-- 
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 773274] [Wayland] Crash under gdk_wayland_window_attach_image()

[gtk+]

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

--- Comment #33 from Martin Stransky  ---
(In reply to Olivier Fourdan from comment #32)
> If that helps (and even if it doesn't), I reckon best would be to continue
> in a separate (new) bug, unlikely people will monitor an old (closed) bug...
> Also because I think it's a different issue/backtrace.

It seems to be fixed - filed a new Bug 793062. Please backport to F27 at least
to enable Wayland browser run there.

-- 
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 793062] New: [Wayland] Crash under gdk_wayland_window_attach_image()

[gtk+]

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

Bug ID: 793062
   Summary: [Wayland] Crash under
gdk_wayland_window_attach_image()
Classification: Platform
   Product: gtk+
   Version: 3.22.x
OS: Linux
Status: NEW
  Severity: major
  Priority: Normal
 Component: Backend: Wayland
  Assignee: gtk-b...@gtk.org
  Reporter: stran...@redhat.com
QA Contact: gtk-b...@gtk.org
CC: j...@eischmann.cz, kubr...@fgv6.net,
maximilien.ric...@gmail.com, mc...@redhat.com,
ofour...@redhat.com, peter.we...@mailbox.org,
r...@robster.org.uk, rstr...@redhat.com,
stran...@redhat.com,
wayland-bugs@lists.freedesktop.org
 GNOME version: ---

Follow up from Bug 773274 comment 27.

The provided patch from
https://bugzilla.gnome.org/attachment.cgi?id=367641=diff works as
expected - the issue is fixed.

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