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

You are viewing a single thread.
View all comments
12 points

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.

permalink
report
reply
5 points

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

permalink
report
parent
reply
4 points

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.

permalink
report
parent
reply
4 points

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

+_+

permalink
report
parent
reply

Linux

!linux@lemmy.ml

Create post

From Wikipedia, the free encyclopedia

Linux is a family of open source Unix-like operating systems based on the Linux kernel, an operating system kernel first released on September 17, 1991 by Linus Torvalds. Linux is typically packaged in a Linux distribution (or distro for short).

Distributions include the Linux kernel and supporting system software and libraries, many of which are provided by the GNU Project. Many Linux distributions use the word “Linux” in their name, but the Free Software Foundation uses the name GNU/Linux to emphasize the importance of GNU software, causing some controversy.

Rules

  • Posts must be relevant to operating systems running the Linux kernel. GNU/Linux or otherwise.
  • No misinformation
  • No NSFW content
  • No hate speech, bigotry, etc

Related Communities

Community icon by Alpár-Etele Méder, licensed under CC BY 3.0

Community stats

  • 7.4K

    Monthly active users

  • 6.6K

    Posts

  • 179K

    Comments