Skip to content
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

Closed
trbjo opened this issue May 20, 2022 · 8 comments
Closed

Crash when disabling display #6

trbjo opened this issue May 20, 2022 · 8 comments

Comments

@trbjo
Copy link

trbjo commented May 20, 2022

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

@jovanlanik
Copy link
Owner

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.

@trbjo
Copy link
Author

trbjo commented May 20, 2022

Arch linux, just built it using make and make install. Will debug later and post the output here.

  • local/gtk3 1:3.24.34-1
  • sway version 1.8-dev-b20585b2 (Apr 23 2022, branch 'HEAD')
  • local/gtk-layer-shell 0.7.0-2
  • local/wlroots-git 0.16.0.r5457.640f3b9f-1

@jovanlanik
Copy link
Owner

Okay, I'll try replicating in my arch vm.

@jovanlanik
Copy link
Owner

Also check out the AUR package, if you don't want to compile gtklock manually.
https://aur.archlinux.org/packages/gtklock-git

@jovanlanik
Copy link
Owner

@trbjo Any info on this? I can't reproduce...

@jovanlanik
Copy link
Owner

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.
It can also happen while an output is initializing (you connect an external display, internal gets disabled, gtklock exits and only after the external is initialized) or after a device resumes from sleep.

@jovanlanik
Copy link
Owner

I think 20a5b4d fixed this, can you confirm?

@jovanlanik
Copy link
Owner

I'm confident this issue was fixed, so I'm closing it.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants