mailarchive of the ptxdist mailing list
 help / color / mirror / Atom feed
From: Philipp Zabel <p.zabel@pengutronix.de>
To: ptxdist@pengutronix.de
Cc: Philipp Zabel <p.zabel@pengutronix.de>
Subject: [ptxdist] [PATCH] systemd: add missing input-id rule
Date: Thu, 30 Nov 2017 10:46:31 +0100	[thread overview]
Message-ID: <20171130094631.14632-1-p.zabel@pengutronix.de> (raw)

Without this, udev does not tag input devices with ID_INPUT variables,
which causes libinput to ignore them.

For example, when starting weston:

  event0  - Logitech USB-PS/2 Optical Mouse: not tagged as supported input device
  event0  - not using input device '/dev/input/event0'
  event1  - gpio-keys: not tagged as supported input device
  event1  - not using input device '/dev/input/event1'
  event2  - HID 046a:0023: not tagged as supported input device
  event2  - not using input device '/dev/input/event2'
  warning: no input devices on entering Weston. Possible causes:
 	- no permissions to read /dev/input/event*
 	- seats misconfigured (Weston backend option 'seat', udev device property ID_SEAT)
  failed to create input devices

Signed-off-by: Philipp Zabel <p.zabel@pengutronix.de>
---
 rules/systemd.make | 1 +
 1 file changed, 1 insertion(+)

diff --git a/rules/systemd.make b/rules/systemd.make
index 468e547b7..d2b55606e 100644
--- a/rules/systemd.make
+++ b/rules/systemd.make
@@ -226,6 +226,7 @@ SYSTEMD_UDEV_HELPER-$(PTXCONF_SYSTEMD_UDEV_MTD_PROBE)		+= mtd_probe
 
 SYSTEMD_UDEV_RULES-y := \
 	50-udev-default.rules \
+	60-input-id.rules \
 	60-persistent-alsa.rules \
 	60-persistent-input.rules \
 	60-persistent-storage-tape.rules \
-- 
2.11.0


_______________________________________________
ptxdist mailing list
ptxdist@pengutronix.de

                 reply	other threads:[~2017-11-30  9:46 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20171130094631.14632-1-p.zabel@pengutronix.de \
    --to=p.zabel@pengutronix.de \
    --cc=ptxdist@pengutronix.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox