Comment 5 for bug 82463

Revision history for this message
Bogdan Butnaru (bogdanb) wrote :

'lshal -m' doesn't output anything, even with sudo. I tried "lshal --monitor" and it works:

First, I started the monitor, I closed the lid, counted to ten, then I opened it. (Incidentally, gnome-screensaver refuses to unlock the screen, but this is unrelated, I think, because they often happen separately.)

$ sudo lshal --monitor
Start monitoring devicelist:
-------------------------------------------------
acpi_LID property button.state.value = true
acpi_LID condition ButtonPressed = lid
acpi_BAT0 property battery.voltage.current = 12421 (0x3085)
acpi_LID property button.state.value = false
acpi_LID condition ButtonPressed = lid
acpi_BAT0 property battery.voltage.current = 12420 (0x3084)

*******************
Then I restarted 'ls-hal --monitor', I closed the lid and re-opened it immediately; it remained blank. I counted to ten and then again closed and opened it immediately. The second time it turned on.

$ sudo lshal --monitor

Start monitoring devicelist:
-------------------------------------------------
acpi_LID condition ButtonPressed = lid
acpi_LID condition ButtonPressed = lid
acpi_LID property button.state.value = true
acpi_LID condition ButtonPressed = lid
acpi_BAT0 property battery.voltage.current = 12419 (0x3083)
acpi_LID property button.state.value = false
acpi_LID condition ButtonPressed = lid
acpi_BAT0 property battery.voltage.current = 12420 (0x3084)