I'm running Hardy on a Dell Inspiron 8100 and still experiencing this issue. Judging by many the many similar reports from others, it also seems to affect many other Dell laptops, but I can't say for certain as I personally have never owned any other Dells.
The solution for me was to follow the advice given here: http://ubuntuforums.org/showthread.php?t=358432 Please note that there he mentions a different place to place the command "vbetool dpms off" because even if gnome-power-manager is set to "Do Nothing" on lid events, /etc/acpi/lid.sh never gets past the following policy check: if [ `CheckPolicy` == 0 ]; then exit; fi Therefore the original suggestion of placing it in the else clause outside the for loop no longer works. However, the whole making-another- file funny business can be avoided by simply placing grep -q open /proc/acpi/button/lid/*/state if [ $? = 0 ] then vbetool dpms on fi before the policy check. Also, it seems that it is not necessary to place "vbetool dpms off" anywhere, as for some reason, Dell laptops turn off their screens unconditionally whenever the lid is closed. I have no idea why; the poster in the forum thread I linked to thinks it is a hardware or BIOS soft of deal. Finally, these bugs seem related: https://bugs.launchpad.net/ubuntu/+source/gnome-power-manager/+bug/67231 https://bugs.launchpad.net/ubuntu/+source/acpi/+bug/49521 https://bugs.launchpad.net/ubuntu/+source/acpi-support/+bug/44393 -- lid.sh should use vbetool instead of xset https://bugs.launchpad.net/bugs/22987 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
