There have been multiple accounts created with the sole purpose of posting advertisement posts or replies containing unsolicited advertising.

Accounts which solely post advertisements, or persistently post them may be terminated.

my lid is being detected as a keyboard button

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: 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 ,

If you are using Wayland, it might be time to play with libinput quirks.
I’ve found the best way to set them is by first reading ones that may already cover your situation, the finding the right string to match on.

beh_93825561489 OP ,

well as far as I understand adding “AttrLidSwitchReliability=unreliable” will not actually fix the issue and I hope this issue is fixable to be honest

TuEstUnePommeDeTerre ,

Then you’ll likely have to mess with the udev rules and force the device to recognized as a lid switch.
Per the example under “Querying the hwdb,” you need the ID_INPUT_SWITCH property to be set correctly.
There’s an example of how to group devices in the Arch wiki for graphics tablets that may be of use if libinput will accept two different switches as one.

beh_93825561489 OP ,

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

+_+

TuEstUnePommeDeTerre ,

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 OP ,

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 bugzilla.kernel.org/show_bug.cgi?id=192231 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: 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

  • All
  • Subscribed
  • Moderated
  • Favorites
  • •
  • [email protected]
  • random
  • lifeLocal
  • goranko
  • All magazines
    •