http://bugzilla.novell.com/show_bug.cgi?id=602547 http://bugzilla.novell.com/show_bug.cgi?id=602547#c0 Summary: powerdevil does not catch lid close / lid open events on Dell Inspiron mini 1010 (Atom platform) Classification: openSUSE Product: openSUSE 11.2 Version: Final Platform: Other OS/Version: Other Status: NEW Severity: Normal Priority: P5 - None Component: KDE4 Workspace AssignedTo: kde-maintainers@suse.de ReportedBy: dieter.jurzitza@t-online.de QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; de; rv:1.9.2.3) Gecko/20100401 SUSE/3.6.3-1.1 Firefox/3.6.3 When configuring PowerDevil to perform a s2ram or s2disk on the Dell Inspiron mini 1010, there is almost never a reaction on the open / close events of the Netbook lid switch. However, acpi events to show correctly so this is not an issue of acpid. To further debug this, some support would be helpful. Reproducible: Always Steps to Reproduce: 1. Activate powerdevil 2. activate s2ram or s2disk on lid close 3. close lid / open lid: nothing happens Actual Results: Well, no s2ram / s2disk Expected Results: s2ram / s2disk I modified acpid to generate logging information (by the way, folks, why am I forced to edit /etc/init.d/acpid to achieve this?): line 76 in /etc/init.d/acpid was modified to startproc $ACPID_BIN -d -f -l > /var/log/acpidlog 2>&1 This results in the following output (/var/log/acpidlog): Number of valid entries: 1 Token >><< could not be identified! Switching from vt7 to vt1 fbcon fb0 state 1 fbcon fb0 state 0 switching back to vt7 acpid: action exited with status 0 acpid: 3 total rules matched acpid: completed event "button/lid LID0 00000080 0000000a" acpid: client 1281[0:0] has disconnected acpid: received event "button/lid LID0 00000080 0000000b" acpid: rule from 1560[101:102] matched acpid: notifying client 1560[101:102] acpid: rule from /etc/acpi/events/lid_button matched acpid: executing action "/usr/lib/acpid/lid_button" pm-profiler: Lid opened, do nothing acpid: action exited with status 0 acpid: 2 total rules matched acpid: completed event "button/lid LID0 00000080 0000000b" acpid: client connected from 1281[0:0] acpid: 1 client rule loaded acpid: received event "button/lid LID0 00000080 0000000c" acpid: rule from 1560[101:102] matched acpid: notifying client 1560[101:102] acpid: rule from 1281[0:0] matched acpid: notifying client 1281[0:0] acpid: rule from /etc/acpi/events/lid_button matched acpid: executing action "/usr/lib/acpid/lid_button" pm-profiler: Lid closed, executing /usr/sbin/s2ram So, I see lid events, and /proc/acpi/button/lid/LID0/state depicts bravely what should be expected. I helped myself this way, one script in /etc/acpid/events: **************************************************************************** # care about the lid open / close event=button/lid.* action=/usr/lib/acpid/lid_button **************************************************************************** one script in /usr/lib/acpid: **************************************************************************** #!/bin/bash # # Copyright (C) 2010 Dr. Ing. Dieter Jurzitza # # This file is released under the GPLv2. # SED="/bin/sed" EXEC="/usr/sbin/s2ram" STATEFILE="/proc/acpi/button/lid/LID0/state" STATE=`${SED} 's/state:\ *//g' ${STATEFILE}` # check if we have pm-profiler and an active profile. If so, $EXEC can be # overwritten by the active profile's configuration /etc/pm-profiler.conf > /dev/null 2>&1 if [ "$?" = "0" ]; then . /etc/pm-profiler/${PM_PROFILER_PROFILE}/config >/dev/null 2>&1 fi [ -z "${LID_BUTTON_HOOK}" ] || EXEC="${LID_BUTTON_HOOK}" if [ "open" == "${STATE}" ]; then logger -s -t pm-profiler "Lid opened, do nothing" else logger -s -t pm-profiler "Lid closed, executing $EXEC" ${EXEC} fi **************************************************************************** But IMHO this is not the way things ought to be. Therefore I would need some help how to debug this further, specifically whether this is a powerdevil issue (I don't think so). I guess this is buried somewhere in the IPC - and this is where my know how ends now. Thank you for looking into this, take care Dieter Jurzitza -- Configure bugmail: http://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.