Public bug reported:
Binary package hint: upstart
After upgrade to karmic beta quite a number of apps (standard: cups, and
third-party: openvpn, tpfand, daemontools) stop working because their starting
scripts are not migrated into new infrastructure and seem to be just ignored.
They work fine when manually started with "/etc/init.d/script start". I also
cannot find a good docs for dealing with this. I can deal with it myself but I
think that this means *lots* of broken/half working systems there. I think
there should be a fall-back for starting daemons not supported by the install -
probably with the clear message indicating that something should be done with
it and how to do it.
Good quick-and-dirty (or better quick and clean) tutorial in easily visible
place would not hurt at all.
I do feel this is fairly important stuff (esp. for cups and openvpn). I
fear there will be *lots* of phone calls with "I upgraded and now my
system is broken" theme to them. I feel this could be a real support
nightmare if unfixed before release.
** Affects: upstart (Ubuntu)
Importance: Undecided
Status: New
--
Karmic upgrade breaks many apps startup scripts.
https://bugs.launchpad.net/bugs/445312
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
