Many thanks to David Wolfskill and David A. Bagley.
Fix: Patch attached with submission follows:
Please note that the reason xlockmore 5.29.1 was released is that 5.29
will fail if invoked from within certain "virtual" window managers.
The failure is accompanied by a message:
| X Error of failed request: BadWindow (invalid Window parameter)
| Major opcode of failed request: 3 (X_GetWindowAttributes)
| Resource id in failed request: 0x45
| Serial number of failed request: 82
| Current serial number in output stream: 83
and xlockmore fails to actually lock the screen.
(I specifically observed it with the piewm and tvtwm window managers,
and noted that the failure does not occur using the twm window
manager. I believe that in general, window managers based on tvtwm are
susceptible. It is possible that any "virtual" window manager is
As a common way to invoke xlock(more) is via xautolock (in which case,
the message is not generally displayed in a place where anyone would see
it), the overall effect is that one would leave the computer, expecting
that xlock(more) would offer at least some protection, while in fact,
nothing of the sort happens: the machine is merely left logged in and
This is probably a bit more of a security exposure than folks using
xautolock would be likely to expect. Getting this committed prior to
the release of 8.0 would thus be welcome.
(I have also verified that the fix is effective for both piewm and
David H. Wolfskill firstname.lastname@example.org
Depriving a girl or boy of an opportunity for education is evil.
See http://www.catwhisker.org/~david/publickey.gpg for my public key.
miwi 2009-10-18 11:10:58 UTC
FreeBSD ports repository
x11/xlockmore Makefile distinfo
- Update to 5.29.1
Submitted by: Marius Nuennerich <email@example.com> (maintainer)
Revision Changes Path
1.121 +1 -1 ports/x11/xlockmore/Makefile
1.64 +3 -3 ports/x11/xlockmore/distinfo
firstname.lastname@example.org mailing list
To unsubscribe, send any mail to "email@example.com"