[HOWTO] Run scripts for laptop lid open/close and dock/undock events

**airtonix** · February 27th, 2010

More improvements (working version)

1. Create the following three files at these locations (next version i'll include ability to specify your open/close script locations as parameters

~/bin/laptop-lid/open

Code:

 #!/bin/bash
notify-send "lid opened"
#play a open sound
aplay /usr/lib/openoffice/basis3.1/share/gallery/sounds/sparcle.wav
#change Pidgin status
purple-remote 'setstatus?status=available&message=I am here...'

~/bin/laptop-lid/close

Code:

#!/bin/bash
aplay /usr/lib/openoffice/basis3.1/share/gallery/sounds/falling.wav
#change Pidgin status
purple-remote 'setstatus?status=away&message=My laptop lid is closed...'

~/bin/laptop-lid/event

Code:

#!/usr/bin/env python
import os
import dbus, gobject
from dbus.mainloop.glib import DBusGMainLoop

class LaptopLid:

    def __init__(self):
        self.dbusSystemObject = "org.gnome.PowerManager.Backlight"
        self.dbusSystemObjectPath = "/org/gnome/PowerManager/Backlight"
        self.acpiLIDstatePath = "/proc/acpi/button/lid/LID0/state"                            #this may vary dending on your system
        self.scriptPath="~/bin/laptop-lid"
        self.state="closed"

        dbus.mainloop.glib.DBusGMainLoop(set_as_default=True)
        self.bus = dbus.SessionBus()
        self.bus.add_signal_receiver(self.cb_func, dbus_interface=self.dbusSystemObject, path=self.dbusSystemObjectPath)

        self.loop = gobject.MainLoop()
        self.loop.run()

    def cb_func(self,message,sender=None):
        #    if(laptopLidState==)
        f = open(self.acpiLIDstatePath, 'r').read()
        if f.count("open") > 0 : #and self.state=="closed" :
            print "opened"
            os.system('sh '+self.scriptPath+'/open')
            self.state = "open"
        elif f.count("closed") > 0 : # and self.state=="open":
            print "closed"
            os.system('sh '+self.scriptPath+'/close')
            self.state = "closed"

l = LaptopLid()

Make it run after login..
1 open : system > preferences > startup applications
2. click add
3. name : DBUS Laptop Lid Event Detector
4. command : python ~/bin/laptop-lid/event

Testing...
Test it by opening terminal and typing :

Code:

python ~/bin/laptop-lid/event

**lunatico** · February 27th, 2010

Excellent contribution airtonix!

When I wrote this I never thought about a multi-user scenario, this was done on my personal work laptop, no one else will ever use it other than me.

I'll edit the main post to guide users wanting multi-user support for the lid event to come to your post.

**SlickRick** · February 27th, 2010

when running dbus-monitor I do get some output but nothing when I open and close the lid.
This is the output I get

Code:

signal sender=org.freedesktop.DBus -> dest=:1.97 serial=2 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=NameAcquired
   string ":1.97"
method call sender=:1.97 -> dest=org.freedesktop.DBus serial=3 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
   string "type='method_call'"
method call sender=:1.97 -> dest=org.freedesktop.DBus serial=4 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
   string "type='method_return'"
method call sender=:1.97 -> dest=org.freedesktop.DBus serial=5 path=/org/freedesktop/DBus; interface=org.freedesktop.DBus; member=AddMatch
   string "type='error'"

**airtonix** · February 28th, 2010

Originally Posted by SlickRick

when running dbus-monitor I do get some output but nothing when I open and close the lid.

But i assume you do have a lid entry in :

Code:

/proc/acpi/button/lid

This is what mine looks like :

Code:

$ tree /proc/acpi/button
/proc/acpi/button
|-- lid
|   `-- LID0
|       |-- info
|       `-- state
|-- power
|   |-- PWRB
|   |   `-- info
|   `-- PWRF
|       `-- info
`-- sleep
    `-- SLPB

Not sure that it matters, but i have my lid event in gnome-power-manager set to blank the screen.

I assume you are running gnome ?

**airtonix** · February 28th, 2010

I just discovered something else that might cause problems :

In the above python dbus event listener, I am sniffing for an event signal sent by "org.gnome.PowerManager.Backlight", but this only fires when i close/open the lid if my power cable is plugged in.

Only org.gnome.Screensaver fires regardless of whether or not the power cable is plugged in.

problem is that I need a service :

Code:

        self.dbusSystemObject = "org.gnome.PowerManager.Backlight"

And a path :

Code:

        self.dbusSystemObjectPath = "/org/gnome/PowerManager/Backlight"

however if you look at the output from dbus-monitor when i close/open the laptop lid :

Code:

method call sender=:1.19 -> dest=:1.20 serial=571 path=/; interface=org.gnome.ScreenSaver; member=Throttle
   string "Power screensaver"
   string "Laptop lid is closed"
method return sender=:1.20 -> dest=:1.19 reply_serial=571
   uint32 526562257
signal sender=:1.19 -> dest=(null destination) serial=572 path=/org/gnome/PowerManager/Backlight; interface=org.gnome.PowerManager.Backlight; member=BrightnessChanged
   uint32 50
method call sender=:1.19 -> dest=:1.20 serial=573 path=/; interface=org.gnome.ScreenSaver; member=UnThrottle
   uint32 526562257
method return sender=:1.20 -> dest=:1.19 reply_serial=573
signal sender=:1.19 -> dest=(null destination) serial=574 path=/org/gnome/PowerManager/Backlight; interface=org.gnome.PowerManager.Backlight; member=BrightnessChanged
   uint32 50

org.gnome.ScreenSaver, does not have a valid path that i cant use in the above python dbus event listener.

**SlickRick** · February 28th, 2010

Originally Posted by airtonix

But i assume you do have a lid entry in :

Code:

/proc/acpi/button/lid

This is what mine looks like :

Code:

$ tree /proc/acpi/button
/proc/acpi/button
|-- lid
|   `-- LID0
|       |-- info
|       `-- state
|-- power
|   |-- PWRB
|   |   `-- info
|   `-- PWRF
|       `-- info
`-- sleep
    `-- SLPB

Not sure that it matters, but i have my lid event in gnome-power-manager set to blank the screen.

I assume you are running gnome ?

Mine looks like this:

Code:

$ tree /proc/acpi/button
/proc/acpi/button
|-- lid
|   `-- LID
|       |-- info
|       `-- state
`-- power
    |-- PWRB
    |   `-- info
    `-- PWRF
        `-- info

And yes, I am using gnome and I have the power manager set to blank screen

I tried running this a thousand times and closing the lid quickly and it seems the lid state changes to closed when I close it

Code:

cat /proc/acpi/button/lid/LID/state

So the event is detected but I have no idea where to go from here

**airtonix** · March 1st, 2010

SlickRick, after trying to work out a better way to sniff the actual laptop lid dbus event, i found that by default dbus-monitor only listens to the session bus.

you should try running :

Code:

dbus-monitor --system

Also, i've since changed aspects of the python event listener to look at the actual dbus lid objects signals ... you can check your dbus hal exposes such an object with :

Code:

hal-find-by-property --key info.product --string "Lid Switch"

My output from this looks like :

Code:

/org/freedesktop/Hal/devices/computer_logicaldev_input_4

If you don't get any output, then try browsing through the output of :

Code:

lshal > ~/lshal.txt && gedit ~/lshal.txt

See if you can find anything to do with a laptop lid switch/button.

still cleaning up the code i'm making then i'll post it here.

**airtonix** · March 1st, 2010

Download

v0.03 dbus-laptop-lid-listener.py
v0.02 dbus-laptop-lid-listener.py

Install/Setup

download it somwhere to your homefolder (ie : ~/bin )

make it exectuable :

Code:

chmod +x ~/bin/dbus-laptop-lid-listener.py

add it to your session startup applications :
1. system > preferences > startup applications
2. click "add"
3. Name : DBUS Laptop Lid Event Listener
4. command :
  Code:
```
~/bin/dbus-laptop-lid-listener.py listen
```
5. click close.
Create a script to run when laptop lid OPENS :
1. Code:
```
gedit ~/bin/laptop-lid-opened.sh
```
2. paste in the following :
  Code:
```
#!/bin/sh
notify-osd "lid open"
```
3. make it executable :
  Code:
```
chmod +x ~/bin/laptop-lid-opened.sh
```

Create a script to run when laptop lid CLOSES :

Code:
```
gedit ~/bin/laptop-lid-closed.sh
```

paste in the following :

Code:

 
#!/bin/sh
# do stuff.
# like change awway status on empathy or pidgin,
# or pause rhythmbox, etc, etc.

make it executable :
Code:
```
 chmod +x ~/bin/laptop-lid-closed.sh
```

Script won't take effect till you either :

run it manually, or
restart your current session by logging out and back in again.

Syntax

Code:

dbus-laptop-lid-listener.py mode openScript closeScript

mode

listen
what you'd be interested in... sits in memory listening for dbus signals and runs your openScript when the acpi laptop lid state changes to "open" and your close script when it changes to "closed"
test
prints out the hal address of your laptop lid switch.

openScript, closeScript
Any script, terminal commands, etc that can be executed under your users account.

**SlickRick** · March 1st, 2010

running this

Code:

dbus-monitor --system

doesn't detect the lid event

I went through your tutorial and it doesn't work for me. When running the script manually I get this.
With the listen option

Code:

DBUS Laptop Lid Event Listener : Open Script Found
DBUS Laptop Lid Event Listener : Close Script Found
DBUS Laptop Lid Event Listener : Laptop Lid Hal Address << found laptop switch : /org/freedesktop/Hal/devices/computer_logicaldev_input_3 >>
DBUS Laptop Lid Event Listener : Listening << waiting for laptop lid events... >>

and the test option

Code:

DBUS Laptop Lid Event Listener : Laptop Lid Hal Address << found laptop switch : /org/freedesktop/Hal/devices/computer_logicaldev_input_3 >>
/org/freedesktop/Hal/devices/computer_logicaldev_input_3