Enabling an auth method shouldn't prevent you from using others, but if you enable fingerprint auth via #fprintd, privilege escalation commands like #sudo don't let you use a password anymore to authorize actions; you must use a fingerprint (until the fingerprint request times out)

#PolicyKit dialogs show a useless "Authenticate" button that never actually gets clicked, but not a password entry textbox (until after fingerprint auth fails)

The UI is already there, just show it!

@eliasp @rust_discussions #PolicyKit used to be quite the obtusely documented mess. Has that improved?

All the JS-based rules stuff seems to still have no documentation in Debian (even with policykit-1-doc installed) beyond the default rules (if you count that as docs).

@rust_discussions none of my systems has #sudo - and never had.
"Back in the days", I just used "su", nowadays most applications use #PolicyKit to get elevated privileges for a specific operation and in case I need a full shell, "machinectl shell .host" (aliased to "msh" here) provides a proper (not just subprocess-spawned) session incl. a DBus and systemd user-session.

#systemd #dbus #linux