On 05/31/10 12:20, Massimo Maiurana wrote: > in the acpi-bindings configuration I have 5 available bindings and 2 possible > actions, bounded together as it follows (default): > > ac adapter unplugged -> dim screen > ac adapter plugged -> undim screen > lid closed -> no action > power button -> no action > sleep button -> no action > > so pressing the power button nothing should happen, shouldn't it? How do you possibly have no action there ?? That makes no sense at all. The defaults are setup so that lid closed will call suspend (as will sleep button)...power button calls halt.
> well, actually pressing the power button asks the system to halt, and at the > same time my /etc/acpi/acpi_handler.sh script calls /usr/sbin/hibernate, so at > the end I have an hibernated system which will halt at next reboot. > Yes, raster made mention the other day about *buntu acpi_handler scripts needing to be modified when using E's acpi handling. > of course I unloaded the acpi module so for me it is not a problem anymore, > but I was just curious why it takes an action which is undefined in > acpi-bindings. > Well, that just unloads the Config Acpi Bindings module, not the acpi code itself, so any presses (or lid closes, etc, etc) will still fire those events in E....so really your solution of "unloading the module" doesn't fix it... dh ------------------------------------------------------------------------------ _______________________________________________ enlightenment-devel mailing list enlightenment-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/enlightenment-devel
