yes I talked to the developers and well I guess I am supposed to figure it out myself but I don’t know how so I am basically seeking help here this is the bug report: https://github.com/systemd/systemd/issues/28942

I guess I should post my own pr but I have no idea how to say to udev that the key specified as d8 is actually the lid being closed and the key specified as d7 is actually the lid being open

basically yes I am a noob and a helpful response will be just a documentation page to show me where can I begin to fix this problem

  • beh_93825561489OP
    4·
    1 year ago

    there is one problem with those links they are forcing a whole device to be another device and I just want the key with scan code d7 to be state 0 of SW_LID and d8 to be state 1

    and fixing this issue in the udev level will automatically fix everything like I will finally be able to use logind.conf

    yeah read that bug report and to be honest I don’t understand the developer standpoint like sorry at least give where can I find the documentation for udev rules

    • even if I use libinput these are the id_input available: ID_INPUT_KEYBOARD, ID_INPUT_KEY, ID_INPUT_MOUSE, ID_INPUT_TOUCHPAD, ID_INPUT_TOUCHSCREEN, ID_INPUT_TABLET, ID_INPUT_JOYSTICK, ID_INPUT_ACCELEROMETER

    and there is no lid one so yeah I don’t know is this problem unfixable with udev rules alone + I made this whole thread just to not make that bug report one of the other 1.9k other open ones except the fact that I wanna improve my experience with linux

    +_+