I don't use wicd -- I just use netcfg, so I probably won't voice my opinion on the bug report just as a +1 post, so as to keep the kruft to a minimum
]]>It seems that the consensus was that some wanted it and others didn't, but that the lesser experienced majority would expect it to be autostarted and so they were going to leave it.
I wouldn't mind this and would just say, trash /etc/xdg/autostart/* for whatever you don't want. Unfortunately, it seems that every time wicd is upgraded, you'll get it back again. Since I don't have pyxdg installed for anything, I'm no longer affected. No one without the pyxdg package will be affected by this.
]]>But then again, I am the only user on the computer of mine...so it's pretty much moot.
]]>If you have pyxdg installed, you'll get an things in /etc/xdg/autostart/*.desktop that start up on log in. If you don't... you won't.
So... since I decided I didn't need dexter as of Monday, suddenly wicd-client wasn't showing up anymore and I was mystified. No longer! Pretty cool, huh?
]]>Great. I added a note in the Wiki, both in the running wicd section where it advises adding wicd-client to DE/WM startup files, a note at end of the troubleshooting section, and two new external links to this post and the bug report you provided. That should cover it
I am always pleased when users take the time to solve their problem and accordingly update the wiki so as to help others.
Kudos to you jwhendy and Thank you.
]]>Thanks.
]]>By placing an application's .desktop file in one of the Autostart directories the application will be automatically launched during startup of the user's desktop environment after the user has logged in.
So (based on reading more of that article), it seems that anything in /etc/xdg/autostart and ~/.config/autostart gets... autostarted.
I don't know why others aren't getting this issue as well, since I found this:
$ sudo pacman -Ql wicd
...
wicd /etc/xdg/autostart/wicd-tray.desktop
...
If this file is part of the wicd package and they have it in autostart... shouldn't it be double appearing for everyone?
]]>I'd also be curious as to:
1) if other wicd/openbox users have the file
2) if other wicd/openbox users removed wicd-client from autostart if it would still start up
The existence of that file explains, perhaps, why even with wicd removed from /etc/rc.conf gksu was still trying to access it.
]]>jwhendy 3666 1 /usr/bin/python2 -O /usr/share/wicd/gtk/wicd-client.py
Now look at the last iteration with the pid 3641 you're interested in. Note that it contains:
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
That last iteration featured wicd-client in autostart.sh and so unsurprisingly:
$ ps ax |grep 3641
3641 tty1 S 0:00 /usr/bin/openbox
We want to know why there's wicd-client processes with a parent pid of 1 (init). That process is the oddity, not the one being started by autostart.
]]>