Ah, great to hear that this is fixed for you; sounds like your problem was bug #447654 then (network-manager wouldn't start because it was waiting for remote filesystems to be mounted first). There's still another outstanding bug as described in the title of this bug report, which we will hopefully also have resolved for karmic.
-- arbitrary remote mount points under FHS directories (incl. /home) block the 'filesystem' signal https://bugs.launchpad.net/bugs/447649 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
