-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Crash when disabling display #6
Comments
Can't seem to reproduce... Maybe you could give me more info? What distro are on? Are you using a package or building gtklock yourself? Versions of sway and all libraries (gtk3, gtk-layer-shell, wayland, pam)? Maybe try logging the crash in gdb and send me the output. |
Arch linux, just built it using make and make install. Will debug later and post the output here.
|
Okay, I'll try replicating in my arch vm. |
Also check out the AUR package, if you don't want to compile gtklock manually. |
@trbjo Any info on this? I can't reproduce... |
My bad, I misunderstood the steps. Managed to replicate the issue. The bug seems to happen when the last window get closed by a wayland event (specifically zwlr_layer_surface_v1::closed). After that the application exits because there aren't any open windows. |
I think 20a5b4d fixed this, can you confirm? |
I'm confident this issue was fixed, so I'm closing it. |
If you disable a display, for example when you connect your laptop to an external display, gtklock will crash, leaving the session unlocked.
How to reproduce:
Run
gtklock &!; sleep 2; swaymsg output eDP-1 disable; sleep 2; swaymsg output eDP-1 enable
The text was updated successfully, but these errors were encountered: