[Helping: cc_INC] WICD and #! Statler - OpenBox

Sector11 · 2010-05-31 23:44:14

Ok, I have wicd installed and it works, I am here which is proof.

However I can not get it to automatically show on tint2 like it did with v9.04

I added the following to ~/.config/openbox/autostart.sh:

# Start WICD
wicd-client &

and my desktop went funny and I had to boot into #! v9.04 and edit autostart.sh to comment out wicd-client &.

It does work with "gmrun" but doesn't stay for a and doesn't autostart.

Hints?

Last edited by Sector11 (2010-11-25 13:13:34)

oupsemma · 2010-06-01 02:32:30

 wicd-client -n &

works for desktops environments that don't have notifications area.

Sector11 · 2010-06-01 02:56:16

oupsemma wrote:

 wicd-client -n & 
works for desktops environments that don't have notifications area.

Right, it starts the GUI app but does not leave the icon in tint2, which is a notification area capable panel. In terminal I get:

$ wicd-client -n &
[1] 24318
$ Has notifications support True
Loading...
Connecting to daemon...
Connected.
/usr/share/wicd/gtk/gui.py:152: GtkWarning: gtk_toolbar_set_icon_size: assertion `icon_size != GTK_ICON_SIZE_INVALID' failed
  self.wTree = gtk.glade.XML(gladefile)
refreshing...
$

So it sees a notification area (tint2) but doesn't put it there.

$ wicd-client &
[1] 28731
$ Has notifications support True
Loading...
Connecting to daemon...
Connected.
displaytray True
Done loading.

Sees the notification area (tint2) and the icon appears but, maybe an hour or less later, it disappears.

With #! v9.04 run "wicd-client &" once in a terminal and the icon was "always" there in tint2 every boot up.

wicd is running every time I boot up, I just can't get it to keep it's icon on tint2 panel even though it is running.

Edit:
NOTE: I have an entry in OpenBox menu to run WICD and leave the icon in tint2 in case I need it, but it should stay permanently the same way Network Manager icon stays.

Last edited by Sector11 (2010-06-01 02:59:18)

oupsemma · 2010-06-01 03:45:30

You may need the WICD Tray:
Command: /opt/wicd/tray.py
Perhaps with that: sudo ln /opt/wicd/tray.py ~/.config/openbox/autostart.sh/tray.py

Edit: Found that: http://ubuntuforums.org/archive/index.p … 85453.html
Seems that adding

(sleep 3s && wicd-client) &

in your autostart.sh should work

it's a delay issue, most *box's have it.
you need to put a sleep on the ones that are missing, whats happening is the background is covering them.
you can play with the time, wicd needs the panel fully loaded & conky has to come after the background is done.

Last edited by oupsemma (2010-06-01 04:17:51)

Sector11 · 2010-06-01 04:33:47

oupsemma wrote:

You may need the WICD Tray:
Command: /opt/wicd/tray.py
Perhaps with that: sudo ln /opt/wicd/tray.py ~/.config/openbox/autostart.sh/tray.py
Edit: Found that: http://ubuntuforums.org/archive/index.p … 85453.html
Seems that adding
(sleep 3s && wicd-client) &
in your autostart.sh should work
it's a delay issue, most *box's have it.
you need to put a sleep on the ones that are missing, whats happening is the background is covering them.
you can play with the time, wicd needs the panel fully loaded & conky has to come after the background is done.

SOLVED

MERCI! Thank you, that sleep command did it ... it is running, I hope it sticks throughout the day. I'll know soon enough, but at least it is starting after a 10 second delay. I will play with that.

cc_INC · 2010-11-23 22:32:45

I've put this in my autostart.sh:

(sleep 3s && wicd-client) &

I've used command wicd-client in a terminal and that works, but for some reason wicd won't start automatically. What am I overlooking? I've removed network-manager-gnome to be sure it's not conflicting or anything like that. Any help on this would be much appreciated!
Thanks..

Sector11 · 2010-11-23 23:06:50

cc_INC wrote:

I've put this in my autostart.sh:
(sleep 3s && wicd-client) &
I've used command wicd-client in a terminal and that works, but for some reason wicd won't start automatically. What am I overlooking? I've removed network-manager-gnome to be sure it's not conflicting or anything like that. Any help on this would be much appreciated!
Thanks..

If Wicd fails to connect after you install it, make sure that the only entry in your /etc/network/interfaces file is

    auto lo
    iface lo inet loopback

Are you running OpenBox or Xfce?

If you are using a desktop environment without a notification area, you can run the Wicd GUI by running
wicd-client -n
If you are using a desktop environment with a notification area, you can start the tray icon by running
wicd-client

johnraff · 2010-11-24 17:00:24

cc_INC wrote:

I've put this in my autostart.sh:
(sleep 3s && wicd-client) &
I've used command wicd-client in a terminal and that works, but for some reason wicd won't start automatically. What am I overlooking? I've removed network-manager-gnome to be sure it's not conflicting or anything like that. Any help on this would be much appreciated!
Thanks..

Could it be you just need to increase the 'sleep' a second or two?

cc_INC · 2010-11-24 23:11:18

This is very weird. I have nothing but

    auto lo
    iface lo inet loopback

In my /etc/network/interfaces file and I just set the sleep time to 6s in my autostart,sh
Still not working as it should. I'm running OpenBox. I need to start the wicd-client in a terminal every time I want to use it. Also just noticed that it doesn't scan for wifi yikes
What the hell am I doing wrong :'(

Sector11 · 2010-11-24 23:50:55

cc_INC wrote:

This is very weird. I have nothing but
    auto lo
    iface lo inet loopback
In my /etc/network/interfaces file and I just set the sleep time to 6s in my autostart,sh
Still not working as it should. I'm running OpenBox. I need to start the wicd-client in a terminal every time I want to use it. Also just noticed that it doesn't scan for wifi
What the hell am I doing wrong :'(

  20:49 ~
         $ wicd-client &
[1] 21005

  20:50 ~
         $ Has notifications support True
Loading...
Connecting to daemon...
Connected.
displaytray True
Done loading.

cc_INC · 2010-11-25 08:31:41

That's the exact same thing I get:

ccinc@ccinc:~$ wicd-client &
[1] 2566
ccinc@ccinc:~$ Has notifications support True
Loading...
Connecting to daemon...
Connected.
displaytray True
Done loading.

A mystery? I give up for now smile
Someday it might hit me..

Sector11 · 2010-11-25 13:19:26

cc_INC wrote:

That's the exact same thing I get:
ccinc@ccinc:~$ wicd-client &
[1] 2566
ccinc@ccinc:~$ Has notifications support True
Loading...
Connecting to daemon...
Connected.
displaytray True
Done loading.
A mystery? I give up for now
Someday it might hit me..

For the life of me I can't see where you are doing anything wrong.
Why not add it to you OB menu until you get a permanent fix:

        <item label="WICD">
            <action name="Execute">
                <execute>
                    wicd-client $
                </execute>
            </action>
        </item>

almax00 · 2010-11-26 20:55:23

launch wicd-client from a terminal. did you tick the little check box "automatically connect to this network" under the essid for your preferred network?

cc_INC · 2010-11-29 21:22:39

Thanks for all the help you guys!!!!! Very much appreciated.
Sorry for my late reply, I was MIA. Been a bit busy sad

Sector11 · 2010-11-29 21:50:35

cc_INC wrote:

Thanks for all the help you guys!!!!! Very much appreciated.
Sorry for my late reply, I was MIA. Been a bit busy

MIA because you are busy is OK - and one heck of a lot better than some of the other options. roll

CrunchBang Linux

SEARCH

#1 2010-05-31 23:44:14

[Helping: cc_INC] WICD and #! Statler - OpenBox

#2 2010-06-01 02:32:30

Re: [Helping: cc_INC] WICD and #! Statler - OpenBox

#3 2010-06-01 02:56:16

Re: [Helping: cc_INC] WICD and #! Statler - OpenBox

#4 2010-06-01 03:45:30

Re: [Helping: cc_INC] WICD and #! Statler - OpenBox

#5 2010-06-01 04:33:47

Re: [Helping: cc_INC] WICD and #! Statler - OpenBox

#6 2010-11-23 22:32:45

Re: [Helping: cc_INC] WICD and #! Statler - OpenBox

#7 2010-11-23 23:06:50

Re: [Helping: cc_INC] WICD and #! Statler - OpenBox

#8 2010-11-24 17:00:24

Re: [Helping: cc_INC] WICD and #! Statler - OpenBox

#9 2010-11-24 23:11:18

Re: [Helping: cc_INC] WICD and #! Statler - OpenBox

#10 2010-11-24 23:50:55

Re: [Helping: cc_INC] WICD and #! Statler - OpenBox

#11 2010-11-25 08:31:41

Re: [Helping: cc_INC] WICD and #! Statler - OpenBox

#12 2010-11-25 13:19:26

Re: [Helping: cc_INC] WICD and #! Statler - OpenBox

#13 2010-11-26 20:55:23

Re: [Helping: cc_INC] WICD and #! Statler - OpenBox

#14 2010-11-29 21:22:39

Re: [Helping: cc_INC] WICD and #! Statler - OpenBox

#15 2010-11-29 21:50:35

Re: [Helping: cc_INC] WICD and #! Statler - OpenBox

Board footer