https://bugzilla.gnome.org/show_bug.cgi?id=793062
--- Comment #17 from Martin Stransky ---
I can 100% reproducible with the firefox-59 build I provide. Navigate to url
bar and type "about:addons" there. When awesomebar disappears FF crashes.
--
You are receiving this mail
https://bugs.freedesktop.org/show_bug.cgi?id=105094
Bug ID: 105094
Summary: Two finger scroll stuck/not happening
Product: Wayland
Version: unspecified
Hardware: Other
OS: All
Status: NEW
Severity: normal
https://bugzilla.gnome.org/show_bug.cgi?id=793062
--- Comment #18 from Olivier Fourdan ---
(In reply to Martin Stransky from comment #16)
> With the latest patch applied I still see a crash:
Weird. Can you double-check the version you use is the one with the patch?
Reason
https://bugzilla.gnome.org/show_bug.cgi?id=793062
--- Comment #20 from Olivier Fourdan ---
(In reply to Martin Stransky from comment #19)
> Yes, I checked it again. I use my own custom build with the patch, I checked
> package build log and the patch is applied. It also
https://bugzilla.gnome.org/show_bug.cgi?id=793062
--- Comment #16 from Martin Stransky ---
With the latest patch applied I still see a crash:
#6 0x7fcd1de3aaf0 in () at /lib64/libpthread.so.0
#7 0x7fcd1671ee79 in wl_proxy_marshal (proxy=0x0, opcode=2) at
https://bugzilla.gnome.org/show_bug.cgi?id=793062
--- Comment #19 from Martin Stransky ---
(In reply to Olivier Fourdan from comment #18)
> (In reply to Martin Stransky from comment #16)
> > With the latest patch applied I still see a crash:
>
> Weird. Can you double-check
https://bugzilla.gnome.org/show_bug.cgi?id=793062
--- Comment #21 from Olivier Fourdan ---
FWIW, the code in gdk/gdkwindow.c with the patch applied should read as:
3802 static void
3803 _gdk_window_process_updates_recurse_helper (GdkWindow *window,
3804
https://bugs.freedesktop.org/show_bug.cgi?id=105103
Bug ID: 105103
Summary: Wayland master causes Mesa to fail to compile
Product: Wayland
Version: unspecified
Hardware: Other
OS: All
Status: NEW
https://bugs.freedesktop.org/show_bug.cgi?id=105104
Bug ID: 105104
Summary: Cannot set tap button map with wayland
Product: Wayland
Version: unspecified
Hardware: Other
OS: Linux (All)
Status: NEW
https://bugs.freedesktop.org/show_bug.cgi?id=105104
--- Comment #1 from ron.koerner+f...@gmail.com ---
Addition: I'm using libinput 1.8.2-1ubuntu2 on Ubuntu 17.10.
--
You are receiving this mail because:
You are the assignee for the bug.___
https://bugs.freedesktop.org/show_bug.cgi?id=105043
--- Comment #12 from Peter Hutterer ---
oops, sorry, I forgot: you need to --enable-tap, it's disabled by default on
your device. Could be the fw, could be the HW, could be the protocol. You're on
PS2 as well, try
https://bugs.freedesktop.org/show_bug.cgi?id=105043
--- Comment #11 from Hi-Angel ---
I shall say I noticed that 2-finger tap often sends the same tuple from
1-finger tap and 2-finger tap. It doesn't make any sense except that those who
wrote the firmware are asses.
Oh,
https://bugs.freedesktop.org/show_bug.cgi?id=105043
--- Comment #10 from Hi-Angel ---
(In reply to Peter Hutterer from comment #9)
> run libinput debug-events --verbose at the same time, that give you more
> debugging output and you can tell what tap state a touch is in and
https://bugs.freedesktop.org/show_bug.cgi?id=105043
--- Comment #14 from Peter Hutterer ---
(In reply to Hi-Angel from comment #13)
> Np, I did the record with the option; will try the kernel boot option, but a
> bit later — I'm travelling, don't have ATM a live-usb/cd
https://bugs.freedesktop.org/show_bug.cgi?id=105043
--- Comment #13 from Hi-Angel ---
(In reply to Peter Hutterer from comment #12)
> oops, sorry, I forgot: you need to --enable-tap, it's disabled by default on
> your device. Could be the fw, could be the HW, could be the
15 matches
Mail list logo