Your message dated Sat, 21 May 2016 19:22:22 +0000
with message-id <[email protected]>
and subject line Bug#823685: fixed in xtrlock 2.8
has caused the Debian Bug report #823685,
regarding 'xtrlock -f' option to fork after locking
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact [email protected]
immediately.)
--
823685: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=823685
Debian Bug Tracking System
Contact [email protected] with problems
--- Begin Message ---
Package: xtrlock
Version: 2.6
Tags: patch
My laptop's most convenient CLI suspend command does not come with a
screen-lock, so I find it useful to run xtrlock before I suspend.
However, it's currently inconvenient to arrange to do those two things
in the right order: 'xtrlock & my-suspend-command' risks xtrlock losing
the race, and putting a sleep in between is bodgy and takes longer than
necessary.
It would be more useful if xtrlock had an option to notify me itself
when the locking process has been successfully completed. The attached
patch adds this feature, in the form of an '-f' option which causes
xtrlock to fork and return success once it has taken out its lock. So
now I can run 'xtrlock -f && my-suspend-command', which does just what I
wanted.
Cheers,
Simon
--
for k in [pow(x,37,0x1a1298d262b49c895d47f) for x in [0x50deb914257022de7fff,
0x213558f2215127d5a2d1, 0x90c99e86d08b91218630, 0x109f3d0cfbf640c0beee7,
0xc83e01379a5fbec5fdd1, 0x19d3d70a8d567e388600e, 0x534e2f6e8a4a33155123]]:
print "".join([chr(32+3*((k>>x)&1))for x in range(79)]) # <[email protected]>
0001-Add-f-option-to-fork-after-a-successful-locking.patch
Description: application/msdos-program
--- End Message ---
--- Begin Message ---
Source: xtrlock
Source-Version: 2.8
We believe that the bug you reported is fixed in the latest version of
xtrlock, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to [email protected],
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Matthew Vernon <[email protected]> (supplier of updated xtrlock package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing [email protected])
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Sat, 21 May 2016 19:08:12 +0100
Source: xtrlock
Binary: xtrlock
Architecture: i386 source
Version: 2.8
Distribution: unstable
Urgency: low
Maintainer: Matthew Vernon <[email protected]>
Changed-By: Matthew Vernon <[email protected]>
Closes: 823685
Description:
xtrlock - Minimal X display lock program
Changes:
xtrlock (2.8) unstable; urgency=low
.
* patch from Simon Tatham to add a -f option [fork, and return success
from parent once lock acquired] (Closes: #823685)
Checksums-Sha1:
4704fc00d2cdb070300f31b12b8192f793cdfcd1 1463 xtrlock_2.8.dsc
622cf35748cee30c54e6a30b4e51801d321ddb7e 21125 xtrlock_2.8.tar.gz
fe7c3ea60e2a601b44f5a6adfaf849277a6248cb 8960 xtrlock_2.8_i386.deb
Checksums-Sha256:
66cb74d8cf512a3dc51160f09a7c3bf23e941813f1670b00085b65bb72336834 1463
xtrlock_2.8.dsc
3848b0c9f2597247e82932f43c42cc9fd7171b808dc08ae84b40a13f7f969604 21125
xtrlock_2.8.tar.gz
95a94b26372e9e3c02e019c5a82c086d8ae98f8d6be03f13147e60c2aa8ca651 8960
xtrlock_2.8_i386.deb
Files:
59e6e9dade297e91d2eb7b480db64be0 1463 x11 optional xtrlock_2.8.dsc
18560ad5bae3daac84012bfc0f1c1728 21125 x11 optional xtrlock_2.8.tar.gz
8981024796d56364619dc01a9996c5a5 8960 x11 optional xtrlock_2.8_i386.deb
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.12 (GNU/Linux)
iQIcBAEBCgAGBQJXQKxzAAoJEBL00hyPamPIQnEP/2CJ3OWQleoMRAiLT1Bv0hqc
R0iNpV2jN5fUHzEe3CqmYUEKtZiNFZi57yYBR5ZcXtXGY/RHtGEES+rrsWHUQ3lX
27yMZrTRMjxTr+yMAstfMjZ/1WpbHrI5c1QrIrBpRX6CT/UB5uAsQ7Rf77iPtQlP
E8O7rKfUiq2xAAzD8EKDYCrBoLefYngTq1QzGcVqO0MQGZEkZujFK7m614e15NE5
CQhl7XwuGQiUpYkWMXzVyf3sAe+2KJXNupAyIEY3y4RhoUmhzMxCy3m6k7KL4qdx
74o+/p6iW5yKaZqowG7+IjWHZNYKz1JM3xSJiEgAZzCRDa9R1BgXwA9OZxArYP++
HREspcsHpWGURzPhDVR65YecTAg9htXapPT7UzP5gODJnUbuVmHomfQNFpnFEh99
FkLXFgv3RB5sGk3hJNXs8UzpuOCEEtjPYU5Rik5lQdsEZ24mAC5nkjj5y/Aqrn7j
2o3gezeT8MiWTfV2eEBPZ+iBu0SQocci1XjIpb91LEipve6vYCNQUzm0BM2wyluM
S+NxBY7Nc2t4LTjKM3fmEUxEettylwkiDC/oXCNhWT6pneoNG49oDHJFe8PDzmXS
dJksMzD4NiRafk0D1jaLjOcvEdV/k0tUvpnKhtvQuuDz/jOn51O0wVo6DwT+jDjp
DePTHb+Rvpp3nk+MW7Ym
=RmEz
-----END PGP SIGNATURE-----
--- End Message ---
