Comment 20 for bug 438402

I've had the same problems, but more so, and the patch doesn't fix it for me.

The other problems are a "Bad marshal data" error when importing the python gobject package. I worked around this by removing the python -O flag from /usr/sbin/wicd, /usr/bin/wicd-gtk and /usr/bin/wicd-curses scripts. Once I'd done this, then wicd fails to connect automatically to ticked entries, and stalls as described when asked to connect. They tray icon also fails to indicate connection status.

Fortunately, wicd-curses works fine. I've resorted to automatically opening it in an xterm (actually urxvtc, but that's by the by) when logging into my netbook.

All this started happening when I upgraded to Ubuntu 10.04, which included upgrading wicd to version 1.7.0. I use xmonad as my window manager, xfce as my session manager, and nodm as my display manager.

After all that, it is still more reliable and less annoying than network-manager, but I'd be really grateful if anyone could shed any light on what might be causing all this.