https://bugs.kde.org/show_bug.cgi?id=499807

            Bug ID: 499807
           Summary: kwin does not correctly close the touchpad event node
                    when the touchpad is disabled
    Classification: Plasma
           Product: kwin
           Version: 6.2.5
          Platform: Other
                OS: Linux
            Status: REPORTED
          Severity: normal
          Priority: NOR
         Component: libinput
          Assignee: kwin-bugs-n...@kde.org
          Reporter: w...@tuxedocomputers.com
  Target Milestone: ---

SUMMARY
Comming from here:
https://gitlab.freedesktop.org/libinput/libinput/-/issues/558#note_2773967
Unlike Gnome (Wayland), Plasma (Wayland) seems to not close the respective file
descriptor of the /sys/class/input/event* node when the touchpad is disabled.
This is relevant for the kernel to know when the touchpad is actually in use
and when it can be deactivated, safeing some battery life and triggering
touchpad enabled/disabled leds.

STEPS TO REPRODUCE
1. Deactivate touchpad e.g. by using a shortcut

OBSERVED RESULT
The kernel does not see a change in the file descriptor open count.

EXPECTED RESULT
The file descriptor is closed and kernel can react to it.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 6.2.5
KDE Plasma Version: 6.2.5 (Wayland)
KDE Frameworks Version: 6.10.0
Qt Version: 6.8.1

ADDITIONAL INFORMATION
All my knowledge about libinput comes from the libinput issue I linked above,
so please excuse some errors and vagueness and this is my guess based in this
xD:
Gnome and Plasma seem to use libinput, which handles the file descriptors,
differently. Especially: While switching from Plasma to a TTY
libinput_suspend() and libinput_resume() seem to be called accordingly, they
seem not to be called when enabling or disabling the touchpad in Plasma. From
the perspective on libinput the touchpad seems to always be active.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to