Confirm here, upgrading from dapper to hardy (and the computer is on another continent, behind a firewall so a user there needs now to take action to reconnect to me..).
Setting up network-manager (0.6.6-0ubuntu5) ... Installing new version of config file /etc/dbus-1/event.d/25NetworkManager ... Installing new version of config file /etc/dbus-1/event.d/26NetworkManagerDispatcher ... Installing new version of config file /etc/dbus-1/system.d/NetworkManager.conf ... Auto interfaces found: lo eth0 eth1 eth2 ath0 wlan0 iface to disable = eth0 iface to disable = eth1 iface to disable = eth2 iface to disable = ath0 iface to disable = wlan0 Disabling interface: eth0 ... done. Disabling interface: eth1 ... done. Disabling interface: eth2 ... done. Disabling interface: ath0 ... done. Disabling interface: wlan0 ... done. * Reloading system message bus config... Failed to open connection to system message bus: Failed to connect to socket /var/run/dbus/system_bus_socket: Connection refused invoke-rc.d: initscript dbus, action "force-reload" failed. It definitely should not restart network interfaces unless user agrees.. -- do-release-upgrade to gutsy disables eth0 https://bugs.launchpad.net/bugs/151169 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
