fix: prune per-monitor windows on monitor removal (v0.6.15)
Resume-unlock SIGSEGV: connect_monitor only adds windows to all_handles, never removes them when a monitor powers off on suspend. gtk4-session-lock unmaps and drops its own ref, but the GtkApplication and all_handles keep theirs, so the orphaned window survives until unlock — where destroying it dereferences its now-NULL monitor association and crashes. Watch display.monitors() and prune handles whose monitor is no longer valid, releasing the app ref via remove_window (the lib already unmapped and dereffed the window — we must not destroy it ourselves). Revert the earlier idle_add_local_once deferral: the logs proved it ineffective (crash happens inside the idle trampoline). Diagnostic unlock logging kept until a suspend/resume cycle confirms the fix.
This commit is contained in:
+1
-1
@@ -1,6 +1,6 @@
|
||||
[package]
|
||||
name = "moonlock"
|
||||
version = "0.6.14"
|
||||
version = "0.6.15"
|
||||
edition = "2024"
|
||||
description = "A secure Wayland lockscreen with GTK4, PAM and fingerprint support"
|
||||
license = "MIT"
|
||||
|
||||
Reference in New Issue
Block a user