Suggestion: Use system PAM directory for lockscreen authentication

[erhaver]

I have a small suggestion regarding the lockscreen PAM configuration.
Currently, the lockscreen uses a hardcoded config file at:

modules/lockscreen/LockScreen.qml:670
configDirectory: Qt.resolvedUrl("../../config/pam").toString().replace("file://", "")
config: "password.conf"

This makes the PAM config file live inside the source directory (~/.local/src/ambxst/config/pam/password.conf), which gets overwritten on updates.

It would be great if Ambxst could look for password.conf in the standard system PAM directory (/etc/pam.d/) instead. This would:

1. Persist across updates — user customizations won't be lost when pulling new changes
2. Follow Linux conventions — /etc/pam.d/ is the standard location for PAM service configurations
3. Make it easier to manage — users can backup, version control, or modify system PAM configs without worrying about their shell being overwritten

If you'd prefer to keep the custom path for portability reasons, maybe a fallback mechanism could work: first check /etc/pam.d/, then fall back to the bundled config.

[Axenide]

This is a limitation of how Quickshell's PAM work. At least from all the examples and documentation I found during development.

I'll check if that changed.