This bug was fixed in the package network-manager -
0.7~~svn20081015t024626-0ubuntu1
---------------
network-manager (0.7~~svn20081015t024626-0ubuntu1) intrepid; urgency=low
new upstream snapshot Wed 2008-10-15 02:46:26 +0000 (bzrrev 3637); topic:
- more vpn and routing fixes
[ Alexander Sack <[EMAIL PROTECTED]> ]
* drop upstreamed IFUPDOWN patches
- delete debian/patches/003-IFUPDOWN-remove-unused-callbacks.loom.patch
- delete debian/patches/004-IFUPDOWN-devtracking.loom.patch
- delete debian/patches/005-IFUPDOWN-unmanaged-mode.loom.patch
- delete debian/patches/006-IFUPDOWN-parse-system-settings.loom.patch
- delete debian/patches/007-IFUPDOWN-managed-mode.loom.patch
* adjust patches that didnt apply cleanly anymore
- update
debian/patches/008-BACKEND-debian-fallback-to-generic-loopback.loom.patch
* fix eventual restart races by --retry'ing at least 5 seconds for NM to stop
in init script
[ Mario Limonciello <[EMAIL PROTECTED]> ]
* debian/network-manager.postinst:
- Set startup priority to be lower than Ubiquity to allow only-ubiquity
installs to have network access. (LP: #277302)
-- Alexander Sack <[EMAIL PROTECTED]> Thu, 16 Oct 2008 00:08:41 +0200
** Changed in: network-manager (Ubuntu)
Status: Triaged => Fix Released
--
NetworkManager is starting up "after" ubiquity in only-ubiquity mode
https://bugs.launchpad.net/bugs/277302
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
