Cursor not hidden when i3lock is run from a different TTY

[nikarh]

This issue is a....

[x] Bug
[ ] Other kind of issue (Please describe in detail)

Current Behavior

I'm running i3lock on a DBUS org.freedesktop.login1.Session Lock signal. In my particular case, this signal is sent by lightdm when I switch from my session to greeter, after the switch to greeter TTY happened. If I switch back to a TTY with my session (ctrl+alt+f1 in my case), I see i3lock, but the cursor is visible (but it's a wait cursor for some reason) and stuck to some coordinate and not moveable. If I run it with i3lock -p default I see a moveable (also a wait one) cursor, and with -p win I see moveable windows cursor as expected.

Expected Behavior

Without -p flag I would expect not to see cursor at all.

Reproduction Instructions

An easy way to reproduce would be switching to a console TTY, running i3lock from there and switching back to X session TTY.

Environment

Output of i3lock --version:

i3lock version: aur-e8b9943 (2023-03-31)

Where'd you get i3lock-color from?

i3lock-color-git from AUR