[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Bug#718267: marked as done (ITP: xidle -- run a program on X inactivity)

Your message dated Tue, 11 Feb 2014 11:39:04 -0800
with message-id <20140211193904.GX24404@rzlab.ucr.edu>
and subject line [CTTE #727708] Default init system for Debian
has caused the Debian Bug report #718267,
regarding ITP: xidle -- run a program on X inactivity
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 owner@bugs.debian.org
immediately.)


-- 
718267: http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=718267
Debian Bug Tracking System
Contact owner@bugs.debian.org with problems
--- Begin Message --- 
Package: wnpp
Severity: wishlist
Owner: Thorsten Glaser <tg@mirbsd.de>

* Package name    : xidle
  Version         : CVS HEAD
  Upstream Author : Federico G. Schwindt <fgsch@cvs.openbsd.org>
* URL             : https://www.mirbsd.org/man1/xidle
* License         : 2-clause UCB
  Programming Lang: C
  Description     : run a program on X inactivity

xidle uses the XScreenSaver(3) extension to receive inactivity events
when a timeout is specified, running a specific program after the
elapsed time. xidle also monitors the very corner of the given position
for pointer activity and runs a program if the pointer sits there for
more than the specified number of seconds. This behavior is always
present, whether -timeout is specified or not.

For example, I’ve got this in my ~/.xinitrc for use with evilwm:

# run xlock on moving to the upper-right corner
xidle -ne -program '/usr/bin/xlock -mode life' &

--- End Message ---
--- Begin Message --- 
The technical committee was asked in #727708 to decide which init
system would be the default init system for Debian. The decision is
below:

==== RESOLUTION ====

We exercise our power to decide in cases of overlapping jurisdiction
(6.1.2) by asserting that the default init system for Linux
architectures in jessie should be systemd.

Should the project pass a General Resolution before the release of
"jessie" asserting a "position statement about issues of the day" on
init systems, that position replaces the outcome of this vote and is
adopted by the Technical Committee as its own decision.

==== END OF RESOLUTION ====

Additional discussions regarding the technical policy necessary for
implementing this decision are anticipated and will be carried out via
the normal technical policy procedure.

Please see http://bugs.debian.org/727708 for discussion of
this bug.

-- 
Don Armstrong                      http://www.donarmstrong.com

If I had a letter, sealed it in a locked vault and hid the vault
somewhere in New York. Then told you to read the letter, thats not
security, thats obscurity. If I made a letter, sealed it in a vault,
gave you the blueprints of the vault, the combinations of 1000 other
vaults, access to the best lock smiths in the world, then told you to
read the letter, and you still can't, thats security.
 -- Bruce Schneier

Attachment: signature.asc
Description: Digital signature


--- End Message ---
Reply to: