nevaforget
e51a847d48
The real cause of the unlock SIGSEGV: gtk4-session-lock destroys the lock windows itself when the lock ends (per its header), so unlock_callback's `unlock(); app.quit();` destroyed them a second time — surface already gone → gdk_surface_get_display NULL → crash in gtk_window_destroy. Reproduces on a plain single-monitor lock/unlock, no suspend needed. unlock_callback now calls only unlock(); a new connect_unlocked handler quits the app after the library finishes teardown. Mirrors the upstream examples/simple.rs exactly. Reverts the v0.6.15/v0.6.16 monitor-pruning + LockscreenHandles.monitor: it was a misdiagnosis (the crash is monitor-independent) and manually manipulated library-managed lock windows, which the upstream example explicitly warns against. Monitor removal is left to the library.
35 lines
795 B
TOML
35 lines
795 B
TOML
[package]
|
|
name = "moonlock"
|
|
version = "0.6.17"
|
|
edition = "2024"
|
|
description = "A secure Wayland lockscreen with GTK4, PAM and fingerprint support"
|
|
license = "MIT"
|
|
|
|
[dependencies]
|
|
gtk4 = { version = "0.11", features = ["v4_10"] }
|
|
gtk4-session-lock = { version = "0.4", features = ["v1_2"] }
|
|
glib = "0.22"
|
|
gdk4 = "0.11"
|
|
gdk-pixbuf = "0.22"
|
|
gio = "0.22"
|
|
toml = "0.8"
|
|
serde = { version = "1", features = ["derive"] }
|
|
graphene-rs = { version = "0.22", package = "graphene-rs" }
|
|
nix = { version = "0.29", features = ["user"] }
|
|
zeroize = { version = "1", features = ["derive", "std"] }
|
|
libc = "0.2"
|
|
log = "0.4"
|
|
systemd-journal-logger = "2.2"
|
|
|
|
[dev-dependencies]
|
|
tempfile = "3"
|
|
|
|
[build-dependencies]
|
|
glib-build-tools = "0.22"
|
|
|
|
[profile.release]
|
|
lto = "thin"
|
|
codegen-units = 1
|
|
strip = false
|
|
debug = true
|