We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Is your feature request related to a problem? Please describe.
Maybe not
Describe the solution you'd like
I would like to request support for the automatic recognition of Touch Pad devices and to enable the related options.
My facter.json reported the Touch Pad device.
{ ... "pointing_device": [ { "handle": 44, "mouse_type": { "name": "Track Point", "value": 5 }, "interface": { "name": "PS/2", "value": 4 }, "buttons": 3 }, { "handle": 45, "mouse_type": { "name": "Touch Pad", "value": 7 }, "interface": { "name": "Other", "value": 1 }, "buttons": 2 } ], ... }
I tried to write a new module to enable services.libinput through mouse_type, but I couldn't find any mouse devices in config.facter.report.hardware.
services.libinput
mouse_type
config.facter.report.hardware
Then I didn't know how to continue.
Describe alternatives you've considered
None
Additional context
The text was updated successfully, but these errors were encountered:
We have an open issue on nixos-facter related to correctly capturing touchpad information.
I should have some time before NixCon to look at this.
Sorry, something went wrong.
brianmcgee
No branches or pull requests
Is your feature request related to a problem? Please describe.
Maybe not
Describe the solution you'd like
I would like to request support for the automatic recognition of Touch Pad devices and to enable the related options.
My facter.json reported the Touch Pad device.
I tried to write a new module to enable
services.libinput
throughmouse_type
, but I couldn't find any mouse devices inconfig.facter.report.hardware
.Then I didn't know how to continue.
Describe alternatives you've considered
None
Additional context
None
The text was updated successfully, but these errors were encountered: