I have the same issue as previous poster. Cannot lock screen with super + L or by clicking Lock in the panel. Running budgie-screensaver manually with debug information enabled, i can see the following in the output
[error_watch] ../src/gs-window-x11.c:821 (18:48:10): command error output:
[error_watch] ../src/gs-window-x11.c:821 (18:48:10): command error output: ** (process:21107): WARNING **: 18:48:10.678: /etc/pam.d/budgie-screensaver does not exist.
[error_watch] ../src/gs-window-x11.c:821 (18:48:10): command error output: Authentication via PAM is unlikely to work.
[error_watch] ../src/gs-window-x11.c:821 (18:48:10): command error output: [gs_debug_init] ../src/gs-debug.c:106 (18:48:10): Debugging enabled
[error_watch] ../src/gs-window-x11.c:821 (18:48:10): command error output:
[lock_command_watch] ../src/gs-window-x11.c:1346 (18:48:10): command output: NOTICE=AUTH FAILED
[error_watch] ../src/gs-window-x11.c:821 (18:48:10): command error output: (budgie-screensaver-dialog:21107): GLib-CRITICAL **: 18:48:10.736: Source ID 17 was not found when attempting to remove it
[error_watch] ../src/gs-window-x11.c:821 (18:48:10): command error output: [do_auth_check] ../src/gnome-screensaver-dialog.c:303 (18:48:10): Verify user returned: FALSE
[error_watch] ../src/gs-window-x11.c:821 (18:48:10): command error output: [do_auth_check] ../src/gnome-screensaver-dialog.c:306 (18:48:10): Verify user returned error: Authentication failed.
[error_watch] ../src/gs-window-x11.c:821 (18:48:10): command error output: [auth_check_idle] ../src/gnome-screensaver-dialog.c:365 (18:48:10): Authentication failed, retrying (1)
[error_watch] ../src/gs-window-x11.c:821 (18:48:10): command error output:
On the screen, I cannot enter the password (no option appears) and mouse movement is very erratic, appearing and disappearing when moved. I have to manually kill the process in a virtual terminal to proceed. Hopefully this issue can be resolved, as so far aside from this I’m really enjoying using Budgie.