https://bugs.kde.org/show_bug.cgi?id=498925
--- Comment #5 from Jakob Petsovits <jpe...@petsovits.com> --- See this comment in the KWin MR for which devices libinput will react on: https://invent.kde.org/plasma/kwin/-/merge_requests/6928#note_1097227 As far as I can tell, your "projecteur" virtual mouse should not cause the touchpad to be disabled because it has neither a "USB" nor "Bluetooth" tag. And the touchscreen *probably* doesn't have a "mouse" or "pointingstick" tag assigned, so I figure that will also not result in the touchpad getting disabled. I can't test this here though, please confirm once you have access to a Plasma 6.3 setup. If the current heuristics aren't sufficient, the best course of action might be to tighten the heuristics within libinput. Alternatively, KWin could implement the same logic as libinput (it's fairly straightforward) but allow additional configuration. Ideally though, I think we'd like to just make it work for as many people as possible by default. -- You are receiving this mail because: You are watching all bug changes.
