Skip to content

Detachable keyboard computer fails to log #219

Open

Description

@J0nnyMak0

I have a 2-in-1 computer which fails to log keys. Following the documentation of this project, I found -d event24 fixes the problem. I'm reporting this issue per documentation. /proc/bus/input/devices attached.
devices.txt

Activity

  1. J0nnyMak0 commented on Jun 27, 2020

    @J0nnyMak0
    Author

    Also is there a way to pass the device # to llk script?

  2. J0nnyMak0 commented on Jun 27, 2020

    @J0nnyMak0
    Author

    And unfortunately, the event # changes with every reboot. It would be nice if there was some way to figure this out. Happy to provide debug info.

  3. J0nnyMak0 commented on Jun 27, 2020

    @J0nnyMak0
    Author

    After thinking about this, the solution here would be to have an option for logkeys to identify devices by-id which are persistent and don't change across boots.

    So, perhaps something like

    logkeys -s -d-by-id  some-device-name
    

    Alternatively if -d can take a relative path as input that should also work. In which case it would look like:

    logkeys -s -d by-id/some-device-name
    

    where the default location is /dev/input and then it would look in by-id directory for the device by id.

    I prefer the second option since it gives us the flexibility to navigate to other device locations relative to /dev/input

  4. kernc commented on Jun 28, 2020

    @kernc
    Owner

    Some related effort expended in #161.

    Alternatively if -d can take a relative path as input that should also work.

    Seems only a slight adjustment needed there. PR welcome.

    logkeys/src/logkeys.cc

    Lines 675 to 677 in 0427dec

    else { // event device supplied as -d argument
    std::string::size_type i = args.device.find_last_of('/');
    args.device = (std::string(INPUT_EVENT_PATH) + args.device.substr(i == std::string::npos ? 0 : i + 1));

  5. J0nnyMak0 commented on Jun 28, 2020

    @J0nnyMak0
    Author

    Some related effort expended in #161.

    Alternatively if -d can take a relative path as input that should also work.

    Seems only a slight adjustment needed there. PR welcome.

    logkeys/src/logkeys.cc

    Lines 675 to 677 in 0427dec

    else { // event device supplied as -d argument
    std::string::size_type i = args.device.find_last_of('/');
    args.device = (std::string(INPUT_EVENT_PATH) + args.device.substr(i == std::string::npos ? 0 : i + 1));

    Absolutely, I got this working locally just last night. I'm looking at another issue where logkeys quits logging. I'm not sure what is causing it. It just issues a message that it has stopped logging. Either way, I'll open a PR soon-ish.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions