This bug was fixed in the package network-manager -
0.8.3+git.20101219t181118.e919218-0ubuntu1
---------------
network-manager (0.8.3+git.20101219t181118.e919218-0ubuntu1) natty; urgency=low
* upstream snapshot 2010-12-19 18:11:18 (GMT)
+ e91921814569bf9033fa0779837a77b22eb98e4a
- libnm-util: fix a memory leak in nm_setting_to_string()
- various ipv6 fixes
- libnm-util: fix nm_utils_security_valid() checks for Ad-Hoc APs
- dns: direct IPv4 reverse DNS queries to split DNS servers
- policy: stop touching /etc/hosts
- dhclient: split out dhclient config merging and add testcases
- dhclient: explicitly request WPAD option (bgo #368423)
* Drop the patch to not write localhost.localdomain in /etc/hosts, it's no
longer needed now that NM doesn't change the hosts file.
- delete debian/patches/never-localhostlocaldomain.patch
- update debian/patches/series
* debian/libnm-glib2.symbols: Add new symbols for libnm-glib2:
+ nm_dhcp6_config_get_one_option
+ nm_dhcp6_config_get_options
+ nm_dhcp6_config_get_type
+ nm_dhcp6_config_new
* Add vpn-up/vpn-down options for the NM dispatcher script. This should really
fix bug 661951. (LP: #661951)
- update debian/network-manager-dispatcher.script
-- Mathieu Trudel-Lapierre <[email protected]> Mon, 20 Dec 2010 13:55:42
-0500
** Changed in: network-manager (Ubuntu)
Status: In Progress => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/661951
Title:
Incorrect /etc/NetworkManager/dispatcher.d/01ifupdown
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
