[Bug 14868] acpi lid close script is no good for kde

bugzilla-daemon at bugzilla.ubuntu.com bugzilla-daemon at bugzilla.ubuntu.com
Thu Sep 8 13:24:01 UTC 2005


Please do not reply to this email.  You can add comments at
http://bugzilla.ubuntu.com/show_bug.cgi?id=14868
Ubuntu | acpi-support





------- Additional Comments From jools at oxfordinspire.co.uk  2005-09-08 14:24 UTC -------
I've just realise the crash issu ewas not due to xscreensaver-command directly, but due to the lid event being run over and over again while  
the lid is closed, causing xscreensaver-common to eat up resources or something. here is a snippet from the acpid log (which is about 25  
meg!!!!!).  
  
[Mon Sep  5 17:31:29 2005] END HANDLER MESSAGES  
[Mon Sep  5 17:31:29 2005] action exited with status 1  
[Mon Sep  5 17:31:29 2005] completed event "button/lid LID 00000080 00000028"  
[Mon Sep  5 17:31:29 2005] received event "button/lid LID 00000080 00000029"  
[Mon Sep  5 17:31:29 2005] executing action "/etc/acpi/lid.sh"  
[Mon Sep  5 17:31:29 2005] BEGIN HANDLER MESSAGES  
xscreensaver-command: no screensaver is running on display :0.0  
[Mon Sep  5 17:31:29 2005] END HANDLER MESSAGES  
[Mon Sep  5 17:31:29 2005] action exited with status 1  
[Mon Sep  5 17:31:29 2005] completed event "button/lid LID 00000080 00000029"  
[Mon Sep  5 17:31:29 2005] received event "button/lid LID 00000080 0000002a"  
[Mon Sep  5 17:31:29 2005] executing action "/etc/acpi/lid.sh"  
[Mon Sep  5 17:31:29 2005] BEGIN HANDLER MESSAGES  
xscreensaver-command: no screensaver is running on display :0.0  
[Mon Sep  5 17:31:29 2005] END HANDLER MESSAGES  
[Mon Sep  5 17:31:29 2005] action exited with status 1  
[Mon Sep  5 17:31:29 2005] completed event "button/lid LID 00000080 0000002a"  
[Mon Sep  5 17:31:29 2005] received event "button/lid LID 00000080 0000002b"  
[Mon Sep  5 17:31:29 2005] executing action "/etc/acpi/lid.sh"  
[Mon Sep  5 17:31:29 2005] BEGIN HANDLER MESSAGES  
xscreensaver-command: no screensaver is running on display :0.0  
[Mon Sep  5 17:31:29 2005] END HANDLER MESSAGES  
[Mon Sep  5 17:31:29 2005] action exited with status 1  
[Mon Sep  5 17:31:29 2005] completed event "button/lid LID 00000080 0000002b"  
[Mon Sep  5 17:31:29 2005] received event "button/lid LID 00000080 0000002c"  
[Mon Sep  5 17:31:29 2005] executing action "/etc/acpi/lid.sh"  
[Mon Sep  5 17:31:29 2005] BEGIN HANDLER MESSAGES  
xscreensaver-command: no screensaver is running on display :0.0  
[Mon Sep  5 17:31:30 2005] END HANDLER MESSAGES  
[Mon Sep  5 17:31:30 2005] action exited with status 1  
[Mon Sep  5 17:31:30 2005] completed event "button/lid LID 00000080 0000002c"  
[Mon Sep  5 17:31:33 2005] received event "button/lid LID 00000080 0000002d"  
[Mon Sep  5 17:31:33 2005] executing action "/etc/acpi/lid.sh"  
[Mon Sep  5 17:31:33 2005] BEGIN HANDLER MESSAGES  
xscreensaver-command: no screensaver is running on display :0.0  
[Mon Sep  5 17:31:34 2005] END HANDLER MESSAGES  
[Mon Sep  5 17:31:34 2005] action exited with status 1  
[Mon Sep  5 17:31:34 2005] completed event "button/lid LID 00000080 0000002d"  
[Mon Sep  5 17:31:34 2005] received event "button/lid LID 00000080 0000002e"  
[Mon Sep  5 17:31:34 2005] executing action "/etc/acpi/lid.sh"  
[Mon Sep  5 17:31:34 2005] BEGIN HANDLER MESSAGES  
xscreensaver-command: no screensaver is running on display :0.0  
[Mon Sep  5 17:31:34 2005] END HANDLER MESSAGES  
  
and so on and so on..  
  
is this a problem with my DSDT, or the way acpid detects lid events? 

-- 
Configure bugmail: http://bugzilla.ubuntu.com/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug, or are watching the QA contact.




More information about the kubuntu-bugs mailing list