Your message dated Sat, 15 Apr 2006 23:45:15 +0100
with message-id <[EMAIL PROTECTED]>
and subject line Bug#362815: Conflict between x11-common and xlockmore
has caused the attached Bug report 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 I am
talking about this indicates a serious mail system misconfiguration
somewhere. Please contact me immediately.)
Debian bug tracking system administrator
(administrator, Debian Bugs database)
--- Begin Message ---
Package: x11-common
Version: 1:7.0.11
x11-common conflicts with xlockmore, but it seems that xlockmore runs
happily together with the new X build. Without xlockmore I can't lock
my computer in an open lab...
--- End Message ---
--- Begin Message ---
On Sat, Apr 15, 2006 at 11:42:48AM -0700, Xin Liu wrote:
> x11-common conflicts with xlockmore, but it seems that xlockmore runs
> happily together with the new X build. Without xlockmore I can't lock
> my computer in an open lab...
This is because xlockmore ships a file in /usr/X11R6/bin. xscreensaver
and other such screensavers provide lock functionality, in the meantime.
--- End Message ---
