I created an emulator instance using revision 19. I verified indeed
that it's running NM , per comment #8. The indicator shows that
airplane mode is active, although urfill isn't running (
/usr/share/urfkill/scripts/flight-mode throws an error ). When I run
'nmcli d', I see that ril_0 ( the modem ) is unavailable, and then I see
a number of ethernet devices listed, all which are reported as
"unmanaged". This means NM isn't managing the devices. In the case of
the emulator, 'eth0' is configured in /etc/network/interfaces like this:
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
To confirm that NM really doesn't effect the default networking in the
emulator, I dropped an upstart override containing "manual" into
/etc/init, and re-started the emulator. I re-started, confirmed NM was
longer running, and then used wget to pull down a webpage ( slashdot.org
).
Next I created an emulator using the latest rc image ( #23 ), and after
swiping down in the OOB/How-To-Swipe app, I get a white screen, and the
apps scope is never displayed, nor does the launcher appear when
dragging from the left.
I re-created an emulator using revision 20, with the same effect. If I
kill the instance, and restart, after entering the device PIN, I again
just get a white screen. phablet-screenshot isn't able to grab an image
either...
The last thing I see on the console is:
[ 4.994175] systemd-logind[606]: Failed to start user service: Unknown unit:
[email protected]
* Setting up X socket directories... [ OK ]
/lib/init/init-d-script: 12: /etc/rc2.d/S02whoopsie: -c: not found
basename: missing operand
Try 'basename --help' for more information.
* Starting virtual private network daemon(s)...
[ 10.583711] systemd-logind[606]: Failed to start user service: Unknown unit:
[email protected]
sdk/emulator/opengl/host/libs/Translator/GLES_V2/GLESv2Imp.cpp:glTexParameterf:1786
error 0x500
sdk/emulator/opengl/host/libs/Translator/GLES_V2/GLESv2Imp.cpp:glTexParameterf:1786
error 0x500
I see these same errors with revision 19, so they don't seem to be the
cause of the networking and/or unity errors.
@Dave
Could you try to disable NM startup per my instructions above and see if
you get the same results?
--
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
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
