From d5ff9d75a80fdc4fcba5d1fcead50c9002e2cb67 Mon Sep 17 00:00:00 2001 From: Peter Hutterer Date: Wed, 3 Jan 2024 08:39:45 +1000 Subject: [PATCH] triage-policies: emphasize that recordings must be attached --- .triage-policies.yml | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/.triage-policies.yml b/.triage-policies.yml index 9a93cea5..df901a46 100644 --- a/.triage-policies.yml +++ b/.triage-policies.yml @@ -31,7 +31,7 @@ resource_rules: - "bugbot::hid-recorder" comment: | Looks like we may need some extra information that isn't yet available in this issue. - Please attach the output of `hid-recorder` from [hid-tools](https://gitlab.freedesktop.org/libevdev/hid-tools/) + Please **attach** (do not paste) the output of `hid-recorder` from [hid-tools](https://gitlab.freedesktop.org/libevdev/hid-tools/) for this device (run `sudo hid-recorder` without argument and it will let you pick the device). This should show the data the kernel receives from the device and may provide a hint on what's going on here. - name: "Request libinput record output" @@ -42,7 +42,7 @@ resource_rules: remove_labels: - "bugbot::libinput-record" comment: | - Looks like we may need some extra information. Please attach the full output + Looks like we may need some extra information. Please **attach** (do not paste) the full output of `libinput record` and `libinput debug-events --verbose` (if you haven't yet). The [documentation](https://wayland.freedesktop.org/libinput/doc/latest/tools.html#libinput-record-and-libinput-replay) has some information on what we're looking for to be able to triage bugs.