No password prompt after v3 upgrade

[luispabon]

After upgrading from v2.1.0 to current master (f5b624d), on occassion after resuming from sleep gtklock shows no login box. The only way around it is to switch to a tty to manually kill gtklock.

gtklock is started via:

gtklock -d -b /path/to/wallpaper.png

Versions:

• sway version 1.10-dev-28fd7358 (Jul 7 2024, branch 'master')
• gtklock master f5b624d

~/.config/gtklock/style.css:

window {
    background-size: cover;
    background-repeat: no-repeat;
    background-position: center;
    background-color: #31455b;
 }

 #clock-label, #input-label {
     color: #ffffff;
 }

[luispabon]

I can reproduce this pretty much every time I suspend, with caveats. If I suspend and resume soon after, there's no problem. If I suspend and resume for a longer period, let's say overnight, the problem happens 100% of the time.

When doing so, gtklock will display, the prompt displays for a couple of seconds (but can't be interacted with and does not respond to enter + fingerprint) then disappears. It doesn't seem to matter if I'm connected to my dock which has 2 extra displays. I do usually suspend with the dock connected however.

[jovanlanik]

Could you check if you get the same issue on sway 1.9?
I suspect this is only a problem on the dev version...

[luispabon]

I'll check 👍🏽

[luispabon]

Unfortunately it also happens with sway v1.9 and wlroots 0.17.1 (ubuntu 24.04 packages).

I have a hunch it might be related to locking, suspending and resuming with a different amount of displays active in sway. Right now just happened suspending on my thunderbolt dock with 3 displays total and resuming to just the laptop's display. The other scenario is suspending on the dock with 3 displays active and resuming with the dock also connected - it takes a few seconds to initialize after resuming.

gtklock is at 76ec411

[jovanlanik]

Can you also try the --follow-focus option and moving the mouse around all the monitors?

[luispabon]

Sure thing. Do you want me to continue testing against sway 1.9 or 1.10-rc1?

[jovanlanik]

I guess either will work.

[luispabon]

I'll try both

…

On Mon, 30 Sept 2024, 23:01 Jovan Lanik, ***@***.***> wrote: I guess either will work. — Reply to this email directly, view it on GitHub <#98 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ABQXYV35MUYNCZNOVZ6UQCDZZHC43AVCNFSM6AAAAABKSRVCK6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGOBUGI2TQOBUHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[luispabon]

I left it suspended overnight - went to sleep off the dock (eg just the laptop display) and it resumed correctly. On sway 1.9. I'll update to 1.10-rc1 and check what happens on different scenarios

[luispabon]

An interesting thing happened with the above. The login box does appear with the --follow-focus option (sway 1.10-rc1 and 1.9) HOWEVER I can't type on it - clicking on the password box does not put it in focus. The "unlock" button is clickable however and I can log in by clicking it then using the fingerprint reader.

[bartlibert]

I have the exact same issue with sway 1.10 and gtklock 4.0.0
I also think it is related to different amount of displays when locking/unlocking and suspending. If there is anymore logging/debugging I can do, I'd be glad to help.

Addendum: I see the error gtk_widget_event: assertion 'WIDGET_REALIZED_FOR_EVENT (widget, event)' failed a lot for gtklock when the issue occurs.

Addendum2: I just had the issue without any suspend happening