I cannot confirm this bug, but I don't have any wireless interfaces, so this buy may only be triggered when you have both wired and wireless interfaces. You could try building version 1.4.2 yourself, it should just be a number bump :-).

This is an upstream bug, please report it at their bugtracker: https://launchpad.net/wicd

The package has already been flagged out of date.

This bug should never have been closed
- We don't know that the bug isn't caused by Arch's packaging of Wicd, even though it's unlikely
- It should not be closed until the bug is known to be reported upstream
- It should not be closed just because there's a newer version - the new version may not fix it.

It turns out the bug results from WiCD writing to its own scripts. The reason it persists after reinstall is that the scripts stick around; if you experience this bug, you must delete everything in /usr/lib/wicd before reinstalling it.

I'm going to try out version 1.5.1, the current version, and see if it still has this problem.

BTW - the version in Extra-x86 doesn't have a maintainer. Is anyone able to take up maintenance of the package?

I installed WiCD 1.5.1 using a PKGBUILD I cobbled up, based on the AUR one for wicd-svn (see attached file). Unfortunately I can't figure out whether this bug is still around, because the client crashes on start with this error:

Traceback (most recent call last):
File "/usr/lib/wicd/wicd-client.py", line 557, in <module>
main(sys.argv)
File "/usr/lib/wicd/wicd-client.py", line 538, in main
tray_icon = TrayIcon(use_tray, animate)
File "/usr/lib/wicd/wicd-client.py", line 102, in __init__
self.icon_info = self.TrayConnectionInfo(self.tr, use_tray, animate)
File "/usr/lib/wicd/wicd-client.py", line 121, in __init__
self.update_tray_icon()
File "/usr/lib/wicd/wicd-client.py", line 178, in update_tray_icon
[state, info] = daemon.GetConnectionStatus()
File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 68, in __call__
return self._proxy_method(*args, **keywords)
File "/usr/lib/python2.5/site-packages/dbus/proxies.py", line 140, in __call__
**keywords)
File "/usr/lib/python2.5/site-packages/dbus/connection.py", line 607, in call_blocking
message, timeout)
dbus.exceptions.DBusException: org.freedesktop.DBus.Error.UnknownMethod: Traceback (most recent call last):
File "/usr/lib/python2.5/site-packages/dbus/service.py", line 643, in _message_cb
(candidate_method, parent_method) = _method_lookup(self, method_name, interface_name)
File "/usr/lib/python2.5/site-packages/dbus/service.py", line 244, in _method_lookup
raise UnknownMethodException('%s is not a valid method of interface %s' % (method_name, dbus_interface))
UnknownMethodException: org.freedesktop.DBus.Error.UnknownMethod: Unknown method: GetConnectionStatus is not a valid method of interface org.wicd.daemon

Not sure what is wrong here, maybe it needs another dependency?

Okay, restarting dbus before wicd fixes it. When the new version hits the repos, the install script ought to warn users to restart dbus first.

I cannot reproduce this bug on my computer, with the following packages installed:
dbus-python 0.83.0-1
pygtk 2.12.1-1
dhclient 3.0.6-2
wpa_supplicant 0.5.10-1
ethtool 6-1
wicd 1.4.1-4

D'oh... It seems to appear when eth0 is listed in NETWORKS=(), so it was a mistake on my part that caused this.

On the other hand, wicd should not be writing to itself in that fashion...