Arch Linux

martinnj

Member

Registered: 2011-05-28

Posts: 28

dbus error between wicd and awesome

Hey!

I use wicd as network manager but i dislike the GTK interface så i use wicd-curses as client.
Now this has the drawback that i don't have a widget/notify icon that tells me connection status.
Since i use Awesome as DE/WM i thought: "HEY! I can just make it in lua! And use wicd's postconnect/disconnect script folders!"

So i went about creating the scripts:

#!/bin/bash
# Should be placed in the /etc/wicd/scripts subfolder for disconnect.
STRING="myESSIDwidget.text=\"  <span color=\'red\'>Not Connected</span>  | \""
echo -e $STRING | su martin awesome-client

STRING2="naughty.notify({ title = \"Disconnected!\", text = \"Wicd just disconnected\", timeout = 5 })"
echo -e $STRING2 | su martin awesome-client

And:

#!/bin/bash
# Should be placed in the /etc/wicd/scripts subfolder for connect.

ESSID=`iwconfig wlan0 |grep "ESSID"|sed -e 's/.*ESSID:"\(.*\)"/\1/'`

STRING='myESSIDwidget.text="  Connected to:<span color=\"green\"> '$ESSID'</span>  | "'

echo -e $STRING | su martin awesome-client

Which when executed works just fine...
However when wicd runs them, i nothing happens, so i addded this line in each:

echo NOMNOM >> /home/martin/ItRuns

And the files get generated, so i know it runs the files...

Apparently the bug is in the awesome-client...

So i try to run the client but when i enter the commands i get this error:

Failed to open connection to "session" message bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

So my question is this, how do i get wicd to talk to awesome-client?

With the hope of some assistance, many regards
Martin NJ