Don't laptops do this in hardware? turning off the screen when the lid is closed? (Mine does so). Whyd would you need acpid to control this?

I don't think my laptop does this. If someone has a Dell Inspiron e1505/6400 and knows how to make it turn off the backlight in hardware, please tell me. -- Leonid

On Sun, Feb 8, 2009 at 1:08 PM, Leonid Grinberg wrote:

...

Don't laptops do this in hardware? turning off the screen when the lid is closed? (Mine does so). Whyd would you need acpid to control this?

I don't think my laptop does this. If someone has a Dell Inspiron e1505/6400 and knows how to make it turn off the backlight in hardware, please tell me.

You're in luck! I maintain the acpid package *and* my notebook is a Dell Inspiron 6400. I use the default handler.sh file for my stuff, found in /etc/acpi. I have the lid closure trigger a suspend-to-ram: button/lid) #echo "LID switched!">/dev/tty5 grep -q closed /proc/acpi/button/lid/*/state if [ $? = 0 ]; then echo -n mem >/sys/power/state fi ;; You can easily replace "echo -n mem >/sys/power/state" with any of the following, depending on your desired result: xset dpms force off xscreensaver-command -lock etc.

I use the default handler.sh file for my stuff, found in /etc/acpi. I have the lid closure trigger a suspend-to-ram:

button/lid) #echo "LID switched!">/dev/tty5 grep -q closed /proc/acpi/button/lid/*/state if [ $? = 0 ]; then echo -n mem >/sys/power/state fi ;;

You can easily replace "echo -n mem >/sys/power/state" with any of the following, depending on your desired result:

xset dpms force off xscreensaver-command -lock etc.

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. -- damjan

On Mon, Feb 9, 2009 at 11:03 AM, Leonid Grinberg 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.

After many hours of searching, I still cannot figure it out. The problem is definitely not in the xset dpms force off command -- it's in the fact that ACPI simply stops realising that the lid is closed. Is there anything that can be done?

The backlight stays on. I am going to try a different command (a much more visible one); if it gets run correctly each time, then it's xset's fault; else, acpid's. 2009/2/18 Thayer Williams :

On Wed, Feb 18, 2009 at 11:02 AM, Leonid Grinberg wrote:

...

After many hours of searching, I still cannot figure it out. The problem is definitely not in the xset dpms force off command -- it's in the fact that ACPI simply stops realising that the lid is closed. Is there anything that can be done?

Is it that the backlight stays on after close, or does it stay off and being opened?

Have you tried any commands other than xset, such as xscreensaver, etc.?

I have the exact same laptop and experience no such behaviour.