I am new to Manjaro and tried to install the driver for my fingerprinter.
When using lsusb i see that my fingerprinter is
Bus 003 Device 002: ID 10a5:9800 FPC FPC Sensor Controller L:0001 FW:16.26.23.14
Lenovo published an offical driver for it for Ubuntu which could be found here: FPC FingerPrint Driver for Ubuntu 20.04, Ubuntu 22.04 - ThinkPad E14 Gen 4, E15 Gen 4 - Lenovo Support AT.
I found this (AUR (en) - libfprint-fpcmoh-git) AUR package where i thinked it should be the published driver from Lenovo for Arch. However after installing i still get the error: Impossible to enroll: GDBus.Error:net.reactivated.Fprint.Error.NoSuchDevice: No devices available. when i use the fprintd-enroll command. Does some one know if i miss a step or did something wrong?
To provide terminal output, copy the text you wish to share, and paste it here, surrounded by three (3) backticks, a.k.a grave accents. Like this:
```
pasted text
```
Or three (3) tilde signs, like this:
~~~
pasted text
~~~
This will just cause it to be rendered like this:
Portaest sed
elementum
cursus nisl nisi
hendrerit ac quis
sit
adipiscing
tortor sit leo commodo.
Instead of like this:
Portaest sed elementum cursus nisl nisi hendrerit ac quis sit adipiscing tortor sit leo commodo.
Alternatively, paste the text you wish to format as terminal output, select all pasted text, and click the </> button on the taskbar. This will indent the whole pasted section with one TAB, causing it to render the same way as described above.
Thereby improving legibility and making it much easier for those trying to be of assistance.
Additionally
If your language isn’t English, please prepend any and all terminal commands with LC_ALL=C. For example:
LC_ALL=C bluetoothctl
This will just cause the terminal output to be in English, making it easier to understand and debug.
And while this is for Ubuntu, Ubuntu is also a Linux Distribution, so it applies to Manjaro as well in this case.
Which is actually what I said earlier:
Edit #2:
That driver you tried to install, what was the output during the process? Maybe, since the AUR package is there, and available to be installed, you’re simply missing the kernel headers or something…
Without more information, it is impossible to be sure…
The unit files have no installation config (WantedBy=, RequiredBy=, UpheldBy=,
Also=, or Alias= settings in the [Install] section, and DefaultInstance= for
template units). This means they are not meant to be enabled or disabled using systemctl.
Possible reasons for having this kind of units are:
• A unit may be statically enabled by being symlinked from another unit's
.wants/ or .requires/ directory.
• A unit's purpose may be to act as a helper for some other unit which has
a requirement dependency on it.
• A unit may be started when needed via activation (socket, path, timer,
D-Bus, udev, scripted systemctl call, ...).
• In case of template units, the unit is meant to be enabled with some
instance name specified.
Tip: 
sure…
