pam_unix(system-auth:account): setuid failed: Operation not permitted and other xsecurelock messages in journalctl after resuming from suspend

[xfzv]

I'm using the following systemd service unit to lock my session before suspending/hibernating:

# /etc/systemd/system/[email protected]

[Unit]
Description=Lock screen before suspend/hibernate
Before=suspend.target
Before=suspend-then-hibernate.target
Before=hibernate.target
Before=hybrid-sleep.target
Before=sleep.target

[Service]
User=%I
Type=simple
Environment=DISPLAY=:0
Environment=XSECURELOCK_AUTH_CURSOR_BLINK=0
Environment=XSECURELOCK_COMPOSITE_OBSCURER=0
Environment=XSECURELOCK_DATETIME_FORMAT="%%Y-%%m-%%d - %%H:%%M"
Environment=XSECURELOCK_DISCARD_FIRST_KEYPRESS=0
Environment=XSECURELOCK_PASSWORD_PROMPT=time_hex
Environment=XSECURELOCK_SHOW_DATETIME=1
Environment=XSECURELOCK_SHOW_HOSTNAME=0
Environment=XSECURELOCK_SHOW_KEYBOARD_LAYOUT=0
Environment=XSECURELOCK_SHOW_USERNAME=0

ExecStart=/usr/bin/xsecurelock
ExecStartPost=/usr/bin/sleep 1
TimeoutSec=infinity

[Install]
WantedBy=suspend.target
WantedBy=suspend-then-hibernate.target
WantedBy=hibernate.target
WantedBy=hybrid-sleep.target
WantedBy=sleep.target

I have no issue whatsoever for now, it works as expected. After resuming from suspend, I can unlock my session with my user password just fine.

However, journalctl -u [email protected] always contains the following (in this case after suspending):

% journalctl -u [email protected]
systemd[1]: Starting Lock screen before suspend/hibernate...
systemd[1]: Started Lock screen before suspend/hibernate.
xsecurelock[52239]: YYYY-MM-DDTHH:MM:SSZ 52239 xsecurelock: Someone overlapped the composite overlay window window. Undoing that.
xsecurelock[52239]: YYYY-MM-DDTHH:MM:SSZ 52239 xsecurelock: Someone overlapped the background window. Undoing that.
xsecurelock[52239]: YYYY-MM-DDTHH:MM:SSZ 52239 xsecurelock: MaybeRaiseWindow miss: something obscured my window 27262985 but I can't find it.
authproto_pam[52559]: pam_unix(system-auth:account): setuid failed: Operation not permitted
systemd[1]: [email protected]: Deactivated successfully.

Just curious as to what could trigger these messages. Tried without Environment=XSECURELOCK_COMPOSITE_OBSCURER=0 (Picom user, I'm using it to avoid the "INCOMPATIBLE COMPOSITOR, PLEASE FIX!" text as suggested in Known Compatibility Issues but it doesn't make any difference.

Should I just ignore these considering everything works fine?

Thanks!