By default, ubuntu-emulator creates an /etc/network/interfaces file with
the following contents:
auto lo
iface lo inet loopback
auto eth0
iface eth0 inet static
address 10.0.2.15
netmask 255.255.255.0
gateway 10.0.2.2
dns-nameservers 10.0.2.3
iface eth1 inet manual
iface eth2 inet manual
iface eth3 inet manual
iface eth4 inet manual
iface eth5 inet manual
These interfaces are processed individually by the init script network-
interface, and as eth0 is the only 'auto' interface, ifupdown will
attempt to configure it.
My guess is that some system-level change in r20 introduces a race
condition which prevents ifupdown from properly configuring the default
route for eth0.
If the network-interface jobs is restarted, the default route is
properly configured, and the browser is able to access the network.
That said, this doesn't resolve the problem with scopes not starting...
Here's the syntax for re-starting the interface:
# restart network-interface INTERFACE=eth0
Note, I've also tested the latest emulator rc ( #27 ) and confirmed that
the restart works there as well. I also verified that I get the same
system-settings failure ( eg. white screen after launching system-
settings ) that @Dave described in comment #13.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1587808
Title:
Ubuntu-emulator no network on latest image
To manage notifications about this bug go to:
https://bugs.launchpad.net/canonical-devices-system-image/+bug/1587808/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
