this post was submitted on 22 Sep 2024
7 points (81.8% liked)

Linux

8110 readers
40 users here now

Welcome to c/linux!

Welcome to our thriving Linux community! Whether you're a seasoned Linux enthusiast or just starting your journey, we're excited to have you here. Explore, learn, and collaborate with like-minded individuals who share a passion for open-source software and the endless possibilities it offers. Together, let's dive into the world of Linux and embrace the power of freedom, customization, and innovation. Enjoy your stay and feel free to join the vibrant discussions that await you!

Rules:

  1. Stay on topic: Posts and discussions should be related to Linux, open source software, and related technologies.

  2. Be respectful: Treat fellow community members with respect and courtesy.

  3. Quality over quantity: Share informative and thought-provoking content.

  4. No spam or self-promotion: Avoid excessive self-promotion or spamming.

  5. No NSFW adult content

  6. Follow general lemmy guidelines.

founded 1 year ago
MODERATORS
 

I have an issue on my Lenovo Laptop where the Lenovo Active Pen 2 under Arch / CachyOS with GNOME on Wayland always recognises the eraser as pressed. While this is probably a libinput issue, I can’t wait for possibly months to get a fix on that side. While I will report this issue to them, I would like to fix the problem intermediately.

This was never a problem under Fedora with GNOME on Wayland. I think the problem might be that libinput on Arch loads the Wacom driver, while Fedora probably just fell back to the generic libinput driver. I got that idea because in GNOME settings my screen now is configurable in the Wacom settings, that never was the case on Fedora.

I stumbled across this thread, however, that is not viable in Wayland any more since there is no config file available for libinput. Is there any way I can force the libinput driver for the “Wacom HID 52C2 Pen” device under Wayland, while GNOME is not specifically exposing this setting?

Any pointers would be greatly appreciated :)

Edit: Scratch all that, I just tried the live ISO for Fedora 41 and found out it's not related to Arch. After some trial, it seems like this might actually be an issue with the 6.11 Kernel. After downgrading to 6.10.10 everything works fine again. I guess my new question is now where would I report this? Is this still a libinput or a Kernel upstream issue?

you are viewing a single comment's thread
view the rest of the comments
[–] Max_P@lemmy.max-p.me 3 points 1 month ago (1 children)

If downgrading the kernel fixes it then it sounds a lot like a kernel bug. Still worth reporting to libinput I guess, they'll probably be of better help to report it to the kernel properly with details of what broke, if it ends up that way.

If you really want to get involved you can also bisect the exact commit that caused it in the kernel, but that's a lot of kernel compiling and rebooting ahead of you.

[–] RayJW@sh.itjust.works 1 points 1 month ago

I looked at some info for reporting this to the kernel developers but the process is too complicated at the time. I'm currently a bit short on time but I did report it to libinput, maybe they can give pointers where exactly to report this.