https://bugs.freedesktop.org/show_bug.cgi?id=97288
Peter Hutterer changed:
What|Removed |Added
Status|ASSIGNED|RESOLVED
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
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
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
https://bugs.freedesktop.org/show_bug.cgi?id=104828
Peter Hutterer changed:
What|Removed |Added
Status|NEW |NEEDINFO
https://bugs.freedesktop.org/show_bug.cgi?id=104812
Peter Hutterer changed:
What|Removed |Added
CC|
https://bugs.freedesktop.org/show_bug.cgi?id=103749
Peter Hutterer changed:
What|Removed |Added
Resolution|--- |WONTFIX
https://bugs.freedesktop.org/show_bug.cgi?id=104569
Peter Hutterer changed:
What|Removed |Added
Status|NEW |NEEDINFO
--
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
https://bugs.freedesktop.org/show_bug.cgi?id=104788
Peter Hutterer changed:
What|Removed |Added
CC|
https://bugs.freedesktop.org/show_bug.cgi?id=98839
Peter Hutterer changed:
What|Removed |Added
Blocks||104788
https://bugs.freedesktop.org/show_bug.cgi?id=104867
Peter Hutterer changed:
What|Removed |Added
CC|
https://bugs.freedesktop.org/show_bug.cgi?id=104415
Peter Hutterer changed:
What|Removed |Added
Assignee|wayland-bugs@lists.freedesk
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,
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
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
https://bugzilla.gnome.org/show_bug.cgi?id=773274
Olivier Fourdan changed:
What|Removed |Added
Attachment #367641|none|needs-work
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
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
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
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
21 matches
Mail list logo