I ran into the same bug on Xubuntu 13.10. However I did not post because of that (apparently it'll probably be fixed in the next release). I post because I believe you should also make wicd give more information if and when it runs into critical problems (for example with this backup). Critical problems as in preventing the program from starting. There was no message on the screen, no entry in the syslog, no files in wicd's own log directory and even the above error on the terminal would not have been of any use to an average user who has no knowledge of Python.
IMHO, the correct way would be to provide at least a clear and understandable error message, preferably with instructions to fix it. Like: "Failed to backup /etc/resolv.conf. Make your own backup and then re-run wicd with parameter --no-backup" or something like that. Sooner or later, someone will have similar problems again and then they should be able to help themselves. Because having to google for problems with your network manager provides a fine example of a chicken-egg-problem. Just my 0.02$ -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1132529 Title: Can't start wicd daemon To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/wicd/+bug/1132529/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
