[Bug 324918] Re: Laptop mode not enabled on lid closed

2011-03-17 Thread ceg
Of course, you want to be able to close the lid and save power but not suspending completely. For example when your laptop is supposed to monitor or control a service or device. The fix for this is to ship l-m-t with an an appropriate hook for pm- utils that replaces the old acpid hook

[Bug 324918] Re: Laptop mode not enabled on lid closed

2010-11-25 Thread Gurmeet
+ me-too on the bug When the lid on the laptop is closed, only the display gets turned off, not the machine. Everything internally is working. Expected behavior : On lid close, laptop should suspend with all peripherals, disk, CPU, wireless etc off. On lid open, laptop should Resume normal

[Bug 324918] Re: Laptop mode not enabled on lid closed

2009-12-03 Thread ceg
If the /etc/acpi/events/lm_lid script has been removed from the ubuntu package of laptop-mode-tools (as the laptop-mode-tools are adapted to the invocation by pm-utils used in ubuntu), do pm-tools not provide a replacement hook for the lid closed event? I wonder because as aunt carry would have

[Bug 324918] Re: Laptop mode not enabled on lid closed

2009-12-03 Thread ceg
Why would you not simply set a policy of suspending the laptop on lid close, instead of turning on laptop-mode? Because laptop-mode (with all the additional disk idleing features of the laptop-mode-tools) is different from suspending into a unresponsive state. And doesn't gnome-power provide

[Bug 324918] Re: Laptop mode not enabled on lid closed

2009-12-01 Thread Steve Langasek
This doesn't work because the /etc/acpi/events/lm_lid script has been intentionally removed from the Ubuntu package of laptop-mode-tools. I'm not sure this is something we want to support. Why would you not simply set a policy of suspending the laptop on lid close, instead of turning on

[Bug 324918] Re: Laptop mode not enabled on lid closed

2009-12-01 Thread Steve Langasek
(Note that acpid itself is considered deprecated in Ubuntu, and will cease to be installed by default once acpi-support is no longer needed.) -- Laptop mode not enabled on lid closed https://bugs.launchpad.net/bugs/324918 You received this bug notification because you are a member of Ubuntu

[Bug 324918] Re: Laptop mode not enabled on lid closed

2009-06-15 Thread Ritesh Raj Sarraf
Looks like you too are affected with the same bug as in: #387057 Can you try the same steps as mentioned there in the comments ? -- Laptop mode not enabled on lid closed https://bugs.launchpad.net/bugs/324918 You received this bug notification because you are a member of Ubuntu Bugs, which is

[Bug 324918] Re: Laptop mode not enabled on lid closed

2009-02-03 Thread Hanno Stock (hefe_bia)
** Attachment added: laptop-mode.conf http://launchpadlibrarian.net/21948625/laptop-mode.conf -- Laptop mode not enabled on lid closed https://bugs.launchpad.net/bugs/324918 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. --

[Bug 324918] Re: Laptop mode not enabled on lid closed

2009-02-03 Thread Tormod Volden
Thanks for your report. You say the display is properly turned off, you mean it goes black? That could be a hardware switch turning of the backlight. Or do you get the locked screen (password dialog) when you open it? Can you try: sleep 10 cat /proc/acpi/button/lid/LID/state -- Laptop mode

Re: [Bug 324918] Re: Laptop mode not enabled on lid closed

2009-02-03 Thread Hanno Stock (hefe_bia)
Tormod Volden schrieb: Thanks for your report. You say the display is properly turned off, you mean it goes black? That could be a hardware switch turning of the backlight. Or do you get the locked screen (password dialog) when you open it? Can you try: sleep 10 cat

[Bug 324918] Re: Laptop mode not enabled on lid closed

2009-02-03 Thread Tormod Volden
In the old times, the acpid should react on the event defined in /etc/acpi/events/lidbtn and run /etc/acpi/lid.sh. You can verify this by restarting acpid in debug mode: sudo pkill ^acpid sudo acpid -d ... now close the lid and open it again Afterwards stop the debug one and restart it