[arch-general] Weird acpid issue

Leonid Grinberg lgrinberg at gmail.com
Fri Feb 13 16:31:37 EST 2009

So, after a few days of problem-free acpid functionality, it, again,
failed to work last night and required a /etc/rc.d/acpid restart,
which fixed it. Does anyone know what might cause this?

2009/2/9 Thayer Williams <thayerw at gmail.com>:
> On Mon, Feb 9, 2009 at 11:03 AM, Leonid Grinberg <lgrinberg at gmail.com> wrote:
>>> xset needs to connect to the X server, so it needs both for the
>>> DISPLAY to be specified and also to have access to the XAuthority
>>> cookie for the X server. Otherwise it will not work - can't connect to
>>> the X server.
>>> Since acpid runs as a sytem service it ussually doesn't have access to
>>> that information.
>> Hmm, so, so far, everything seems to be working fine... One can play
>> "DISPLAY=:0" before "xset dpms force off", but how does one grant it
>> access to the XAuthority cookie?
> Can't help you guys much there.  I never blank my screen without
> enabling some sort of screenlock/screensaver.  For instance, I use
> slock which locks the X session and, as a side effect, shuts off the
> monitor.

More information about the arch-general mailing list