#20 acpid doesn't survive input device removal

Mikhail Krivtsov

I have second set of keyboard and mouse attached via "PS2 to USB Converter". Sometimes it is temporarily disconnected. In such case corresponding /dev/input/event* items disappear and acpid starts complaining "acpid: input layer read error: No such device (19)" and finally exits with message "acpid: too many errors reading input layer - aborting".
It would be nice to make acpid survive input device removal and notice addition of new input devices.


  • patch for acpid-1.0.10-netlink4 to survive input device removal

  • Ted Felix
    Ted Felix

    Sorry, still trying to figure out how to monitor things in sourceforge, so I'm just finding out about this now. This patch is great. I was thinking about rewriting connection_list using queue(3) as I didn't want to try and implement a delete_connection() of my own, but this one is perfect. I'll get it in ASAP and release an initial fix for this issue.

    This covers the case where a device is removed from the system. Now we need to cover the case where a device is added. I'm not sure how I can get notification that new devices have appeared as /dev/input/event* files. Anyone have any advice?


  • Ted Felix
    Ted Felix

    I just uploaded a 1.0.10-netlink5 version of acpid which includes this patch. It's in the patches section for this project. This item can now be closed.