OK. So I will write what's happening. Everybody, look inside yours "/etc/rcS.d" directory - which priority have "networking" and which "firestarter"? At my system it is respectively 40 and 65. It means that first "/etc/init.d/networking" is running and with that "/etc/network/if-up.d/50firestarter" which contains "/etc/init.d/firetarter restart". So, "networking" scripts trying to restart "firestarter daemon" but it is not loaded yet - so it exits with "return code 2". After that feew tings is loaded and then "firestarter" is loading from system wide "rc.d".
Dirty hack for this is either to change loading priority of "networking" to above 65 (which is not wise since it is "device" and these should be loaded at least to 40 priority position) or to change loading priority of "firestarter" below|to 40 (I don't know if it is wise since not every devices and filesystems are set and running at the time). Dirty hack 1: sudo update-rc.d -f networking remove sudo update-rc.d networking S 70 . or Dirty hack 2: sudo update-rc.d -f firestarter remove sudo update-rc.d firestarter S 40 . -- [gutsy] /etc/network/if-up.d/50firestarter exited with return code 2 https://bugs.launchpad.net/bugs/132039 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
