Back to bug 105258

Who When What Removed Added
nicolas-freedesktop 2018-02-26 18:33:26 UTC CC nicolas-freedesktop
peter.hutterer 2018-02-27 01:42:43 UTC CC peter.hutterer
Status NEW NEEDINFO
peter.hutterer 2018-02-28 00:44:49 UTC Status NEEDINFO ASSIGNED
peter.hutterer 2018-02-28 07:25:56 UTC Attachment #137615 Attachment mime type text/x-log text/plain
peter.hutterer 2018-03-01 02:28:14 UTC CC aplattner
peter.hutterer 2018-03-05 00:24:32 UTC CC me
peter.hutterer 2018-03-05 00:37:55 UTC Status ASSIGNED RESOLVED
Resolution --- FIXED
andyrtr 2018-03-06 15:57:56 UTC CC andyrtr
peter.hutterer 2018-03-07 00:38:52 UTC CC quantumphoton007
stas-t 2018-03-11 13:41:59 UTC Status RESOLVED REOPENED
Resolution FIXED ---
peter.hutterer 2018-03-12 01:05:06 UTC CC krejzi
peter.hutterer 2018-03-12 01:06:04 UTC CC daniel.van.vugt
peter.hutterer 2018-03-12 01:40:07 UTC CC dudeand2000
peter.hutterer 2018-03-12 01:49:24 UTC CC gentoosiastic
peter.hutterer 2018-03-12 02:01:17 UTC Resolution --- FIXED
Status REOPENED RESOLVED
daniel.van.vugt 2018-03-12 09:18:22 UTC Summary libinput crashes Xorg with SIGABRT in libinput_event_get_pointer_event libinput crashes Xorg with SIGABRT in tp_tap_handle_state() [evdev-mt-touchpad-tap.c:1030 (master), 1028 (1.10-branch)]
daniel.van.vugt 2018-03-12 09:19:57 UTC See Also http://bugs.debian.org/892714
daniel.van.vugt 2018-03-12 09:20:25 UTC See Also https://launchpad.net/bugs/1751086
peter.hutterer 2018-03-13 00:05:54 UTC CC silencly07
daniel.van.vugt 2018-03-13 03:24:37 UTC Summary libinput crashes Xorg with SIGABRT in tp_tap_handle_state() [evdev-mt-touchpad-tap.c:1030 (master), 1028 (1.10-branch)] libinput crashes Xorg with SIGABRT in tp_tap_handle_state() [evdev-mt-touchpad-tap.c:1030|1028]
mrblooter 2018-03-13 18:05:22 UTC CC mrblooter
peter.hutterer 2018-03-20 05:44:15 UTC Blocks 105535
peter.hutterer 2018-04-02 22:39:43 UTC CC postadelmaga
viraj.deshmukh.13 2019-02-21 00:50:35 UTC CC viraj.deshmukh.13

Back to bug 105258

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.