Open MrQubo opened 1 month ago
tudor-host-launcher.service
takes some time to start. I think it would be better to start it automatically on system startup instead of on the first use via dbus.
Just starting tudor-host-launcher
won't do much - you want to auto-launch fprintd
instead, which will cause the host launcher to start as well. To do so, you can simply use a systemd overlay file to add it to a boot target of your choosing; I do this as well on my own laptop.
Maybe we should install this overlay by default to add fprintd
to multi-user.target
?
Maybe we should install this overlay by default to add
fprintd
tomulti-user.target
?
I prefer not interfering with the configuration files of other services, so I wouldn't be in favor of that. Instead, I think documenting this somewhere so that interested users can make the modification themselves is the better way forward here.
tudor-host-launcher.service
takes some time to start. I think it would be better to start it automatically on system startup instead of on the first use via dbus.