Brian J. Tarricone
c3166f0b9c
If the user presses enter or escape in order to get the unlock dialog to show in the first place, forwarding that event to the dialog will only cause it to close immediately. Also took the opportunity to clean up the dependencies where I have my own patches. I'm now using the cargo 'patch' section so that the dependencies specified in the individual Cargo.toml files are clean.
29 lines
797 B
Plaintext
29 lines
797 B
Plaintext
Source: bscreensaver
|
|
Maintainer: Brian Tarricone <brian@tarricone.org>
|
|
Section: x11
|
|
Priority: optional
|
|
Standards-Version: 3.9.2
|
|
Build-Depends:
|
|
debhelper (>= 13),
|
|
pkg-config,
|
|
libxcb-randr0-dev,
|
|
libxcb-xfixes0-dev,
|
|
libxcb1-dev,
|
|
libxkbcommon-x11-dev,
|
|
libgtk-3-dev,
|
|
libpam0g-dev,
|
|
cargo (>= 0.57),
|
|
rustc (>= 1.58),
|
|
help2man
|
|
|
|
Package: bscreensaver
|
|
Architecture: any
|
|
Depends: ${shlibs:Depends}, ${misc:Depends}
|
|
Description: secure X11 screen locker
|
|
BScreensaver is a privilege-separated screen locker that attempts to
|
|
be as secure as possible, meaning that a crash one one of its
|
|
non-critical components will not cause the screen to unlock.
|
|
.
|
|
It is fairly barebones so far, and only supports blanking the screen.
|
|
There is a single unlock dialog implementation that uses GTK3.
|