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

  • TuEstUnePommeDeTerre@midwest.social
    ·
    1 year ago

    ID_INPUT_SWITCH (Line 88 here) appears to be an option that is excluded from the list on the libinput page.
    I went through some similar issues with PostmarketOS on a Chromebook. The libinput quirks and udev rules are highly undocumented and unstable right now. You have to piece together information from existing configurations and poking around in the libinput repo.

    • beh_93825561489@lemmy.ml
      hexagon
      ·
      edit-2
      1 year ago

      update so after realising I have ACPI: button: The lid device is not compliant to SW_LID. in my logs I found a couple of bug reports in the kernel https://bugzilla.kernel.org/show_bug.cgi?id=192231 https://bugzilla.kernel.org/show_bug.cgi?id=202421

      so I guess this can be as well a kernel issue

      so I made a bug report in the arch linux bug reporter: https://bbs.archlinux.org/viewtopic.php?pid=2119116

      so yeah I guess and I hope someone understand the problem fix it with udev or the linux kernel directly or at least give me the steps to do so anyway yeah that's all

      and I guess if this plan didn't work I have to learn C to fix the issue