[SOLVED] on last reboot, two wicd-clients running + two tray icons?

Question

Hi,
I've been using wicd forever and for the first time, I had two tray icons showing this morning. I used to use xfce but switched to openbox about a month ago and have been using an autostart.sh like so:
$ cat .config/openbox/autostart.sh |tail
#bg
eval `cat ~/.fehbg` &
#post-start operations
(tint2) &
(conky -c /etc/conky/conky.conf) &
(conky -c /etc/conky/conky-top.conf) &
(wicd-client) &
This has been working fine, at least as far as I knew. Suddenly this morning when I started up X, I had two wireless icons in my tray. I found that two wicd-clients were running:
$ ps ax |grep wicd
3492 ? S 0:00 /usr/bin/python2 -O /usr/share/wicd/daemon/wicd-daemon.py
3500 ? S 0:00 /usr/bin/python2 -O /usr/share/wicd/daemon/monitor.py
3573 tty1 S 0:00 /usr/bin/python2 -O /usr/share/wicd/gtk/wicd-client.py
3578 tty1 S 0:00 /usr/bin/python2 -O /usr/share/wicd/gtk/wicd-client.py
3641 ? Ss 0:00 wpa_supplicant -B -i wlan0 -c /var/lib/wicd/configurations/001b5311e850 -D wext
This has never happened and I'm not sure why it would start all of the sudden like this. If I remove it from ~/.config/openbox/autostart.sh, I only get one wicd-client. If I put it back, I get two. But I never used to get two even when it was in autostart.sh before (like as of any time before this morning), which is why this is so puzzling.
I thought it might have been an upgrade, but I just reinstalled Arch completely on Saturday to do encryption and pacman.log shows that this is the only version of wicd that's been installed.
I wondered if having wicd in /etc/rc.conf daemons was enough to start the client upon startx, but the Arch wiki on wicd implies that you should have wicd-client in autostart.sh or equivalent.
Can anyone assist in diagnosing the problem? I guess I'd be looking for:
1) validation that wicd in DAEMONS of /etc/rc.conf is sufficient to start the client
2) some way to find out where both wicd-clients are being started from (if that's even possible); for example, autostart.sh-started apps might potentially be tied to my username, whereas if something's being started from the system side, perhaps the process is owned by root and we could reveal that somehow
3) any other suggestions or comments
Thanks.
Last edited by jwhendy (2011-03-10 03:00:56)

Answer 1

@skunktrader: Whoops... but won't that be redundant? I already know where one instance was coming from: autostart.sh. I want to know why the other one is starting, since no one seemed to think that wicd automatically launched wicd-client. Anyway, several reboots later, here's the full scoop:
| wicd in /etc/rc.conf deamons: no
| wicd-client in ~/.config/openbox/autostart.sh: no
`---
Note: In previous reboots, I get asked by gksu to allow wicd to access my network cards. This past time, I got a message from gksu saying that wicd had been granted access to my network cards.
| before starting openbox (nothing):
`---
$ ps ax -o user,pid,ppid,command |grep wicd
| after starting openbox:
`---
$ ps ax -o user,pid,ppid,command |grep wicd
jwhendy 3569 1 /usr/bin/python2 -O /usr/share/wicd/gtk/wicd-client.py
root 3617 1 /usr/bin/python2 -O /usr/share/wicd/daemon/wicd-daemon.py
root 3619 3617 /usr/bin/python2 -O /usr/share/wicd/daemon/monitor.py
root 3669 1 wpa_supplicant -B -i wlan0 -c /var/lib/wicd/configurations/001b5311e850 -D wext
=====================
| wicd in /etc/rc.conf deamons: yes
| wicd-client in ~/.config/openbox/autostart.sh: no
`---
| before starting openbox:
`---
$ ps ax -o user,pid,ppid,command|grep wicd
root 3445 1 /usr/bin/python2 -O /usr/share/wicd/daemon/wicd-daemon.py
root 3447 3445 /usr/bin/python2 -O /usr/share/wicd/daemon/monitor.py
root 3566 1 wpa_supplicant -B -i wlan0 -c /var/lib/wicd/configurations/001b5311e850 -D wext
| after starting openbox:
`---
$ ps ax -o user,pid,ppid,command|grep wicd
root 3445 1 /usr/bin/python2 -O /usr/share/wicd/daemon/wicd-daemon.py
root 3447 3445 /usr/bin/python2 -O /usr/share/wicd/daemon/monitor.py
root 3566 1 wpa_supplicant -B -i wlan0 -c /var/lib/wicd/configurations/001b5311e850 -D wext
jwhendy 3666 1 /usr/bin/python2 -O /usr/share/wicd/gtk/wicd-client.py
=====================
| wicd in /etc/rc.conf deamons: yes
| wicd-client in ~/.config/openbox/autostart.sh: yes
`---
| before starting openbox:
`---
$ ps ax -o user,pid,ppid,command|grep wicd
root 3420 1 /usr/bin/python2 -O /usr/share/wicd/daemon/wicd-daemon.py
root 3422 3420 /usr/bin/python2 -O /usr/share/wicd/daemon/monitor.py
root 3543 1 wpa_supplicant -B -i wlan0 -c /var/lib/wicd/configurations/001b5311e850 -D wext
| after starting openbox:
`---
$ ps ax -o user,pid,ppid,command|grep wicd
root 3420 1 /usr/bin/python2 -O /usr/share/wicd/daemon/wicd-daemon.py
root 3422 3420 /usr/bin/python2 -O /usr/share/wicd/daemon/monitor.py
root 3543 1 wpa_supplicant -B -i wlan0 -c /var/lib/wicd/configurations/001b5311e850 -D wext
jwhendy 3657 1 /usr/bin/python2 -O /usr/share/wicd/gtk/wicd-client.py
jwhendy 3662 3641 /usr/bin/python2 -O /usr/share/wicd/gtk/wicd-client.py
=====================
So, this is why I said that the test is a bit redundant. The real question still remains: why with no wicd in rc.conf and it commented in autostart.sh is wicd related stuff starting at all? I already know one instance is definitely occurring from autostart.sh, because when I commented it out, I only had one left. But if autostart.sh is supposed to be mandatory, where is the other one coming from? More so... without it in the daemons line, the behavior with gksu indicates that something, somewhere is trying to get wicd up and running. That is what I really don't get at all.