882e3c2680
udev gives no guarantee that before each "changed" event for a device there's an "add" event, or that before each "remove" is an "add", or that before each "add" there was no "add" already and so on. Users can trigger these events at any time with "udevadm trigger", and netlink is a lossy transport, hence the events can come in unexpected ordering. With other words: regardless which event is generated, the X server must not choke on it and make the best of it, hence make sure that if we get an "add" event for an existing device we don't add the device a second time. Signed-off-by: Lennart Poettering <lennart@poettering.net> Reviewed-by: Peter Hutterer <peter.hutterer@who-t.net> Signed-off-by: Peter Hutterer <peter.hutterer@who-t.net> |
||
|---|---|---|
| .. | ||
| 10-evdev.conf | ||
| config-backends.h | ||
| config.c | ||
| dbus-api | ||
| dbus-core.c | ||
| dbus.c | ||
| fdi2iclass.py | ||
| hal.c | ||
| Makefile.am | ||
| udev.c | ||
| x11-input.fdi | ||
| xorg-server.conf | ||