[Bug 14941] New: acpid: ignores events if input event numbering is not contiguous

[bugzilla at busybox.net]

https://bugs.busybox.net/show_bug.cgi?id=14941

            Bug ID: 14941
           Summary: acpid: ignores events if input event numbering is not
                    contiguous
           Product: Busybox
           Version: 1.35.x
          Hardware: All
                OS: Linux
            Status: NEW
          Severity: normal
          Priority: P5
         Component: Other
          Assignee: unassigned at busybox.net
          Reporter: spam at ipik.org
                CC: busybox-cvs at busybox.net
  Target Milestone: ---

Have noticed a problem with busybox acpid input scan in /dev/input/event*
All is fine as long as event numbering is contiguous, but if there is a "hole"
in-between, acpid does not take inputs after the hole.

Exemple below on Alpine 3.16 where fuser shows event0 and event1 are handled,
but event3 is ignored (event2 missing), despite restarting acpid.

$ service acpid status
 * status: started

$ ls /dev/input/
event0  event1  event3  mice    mouse0

$ pidof acpid
4530

$ fuser /dev/input/event3

$ fuser /dev/input/event0
4530 

$ fuser /dev/input/event1
4530 

$ service acpid restart
 * Stopping busybox acpid ...                                                  
                         [ ok ]
 * Starting busybox acpid ...                                                  
                         [ ok ]
$ fuser /dev/input/event3
$ fuser /dev/input/event0
4613

This is quite annoying in situations where devices may come & go (like
bluetooth keyboards, AVRCP,...), and therefore create such holes in event
numbering.

-- 
You are receiving this mail because:
You are on the CC list for the bug.