Status Update
Comments
ap...@google.com <ap...@google.com> #2
2022-01-19 11:01:47,579 [ 43614] INFO - manager.EmulatorProcessHandler - Emulator: /home/ghost/Android/Sdk/emulator/emulator -netdelay none -netspeed full -avd Pixel_API_31
2022-01-19 11:01:47,600 [ 43635] INFO - manager.EmulatorProcessHandler - Emulator: WARNING | unexpected system image feature string, emulator might not function correctly, please try updating the emulator.
2022-01-19 11:01:47,698 [ 43733] INFO - manager.EmulatorProcessHandler - Emulator: WARNING | cannot add library /home/ghost/Android/Sdk/emulator/qemu/linux-x86_64/lib64/vulkan/libvulkan.so: failed
2022-01-19 11:01:47,760 [ 43795] INFO - manager.EmulatorProcessHandler - Emulator: qemu-system-x86_64: -chardev socket,port=45697,host=::1,nowait,nodelay,ipv6,id=modem: address resolution failed for ::1:45697: Name or service not known
2022-01-19 11:02:27,813 [ 83848] INFO - rationStore.ComponentStoreImpl - Saving Project(name=armino_rents, containerState=COMPONENT_CREATED, componentStore=/home/ghost/StudioProjects/armino_rents)KotlinCommonCompilerArguments
ap...@google.com <ap...@google.com> #3
/path/to/emulator -verbose -show-kernel -avd <avename> -feature -ModemSimulator
the above command line will not use modem, just to see if it is related.
ap...@google.com <ap...@google.com> #4
Attaching the log below.
ap...@google.com <ap...@google.com> #5
"qemu-system-x86_64: -chardev socket,port=38379,host=::1,nowait,nodelay,ipv6,id=modem: address resolution failed for ::1:38379: Name or service not known"
Adding the "-feature -ModemSimulator" flags worked around the issue for me.
ap...@google.com <ap...@google.com> #6
Hi truefalsetrue101@, could you try look at your /etc/hosts file on your machine? On my machine, it looks like
##
# Host Database
#
# localhost is used to configure the loopback interface
# when the system is booting. Do not change this entry.
##
127.0.0.1 localhost
255.255.255.255 broadcasthost
::1 localhost
If ::1 localhost
is missing, that probably explains why "Name or service was not known".
ap...@google.com <ap...@google.com> #7
I have that entry. Here's my entire /etc/hosts (my IP and hostname have been replaced with "xxx"):
#
# hosts This file describes a number of hostname-to-address
# mappings for the TCP/IP subsystem. It is mostly
# used at boot time, when no name servers are running.
# On small systems, this file can be used instead of a
# "named" name server.
# Syntax:
#
# IP-Address Full-Qualified-Hostname Short-Hostname
#
127.0.0.1 localhost
# special IPv6 addresses
::1 localhost ipv6-localhost ipv6-loopback
fe00::0 ipv6-localnet
ff00::0 ipv6-mcastprefix
ff02::1 ipv6-allnodes
ff02::2 ipv6-allrouters
ff02::3 ipv6-allhosts
192.168.xxx.xxx xxx
ap...@google.com <ap...@google.com> #8
RE#7
bohu@, any idea why this call would fail on host? I am also guessing maybe it has to do with the /etc/resolv.conf
on host.
if ((rc = getaddrinfo(addr, port, &ai, &local)) != 0) {
error_setg(errp, "address resolution failed for %s:%s: %s", addr, port,
gai_strerror(rc));
goto err;
}
ap...@google.com <ap...@google.com> #9
could be related to the linux flavor regarding address resolution.
my machine has almost the same config, and the getaddrinfo just works.
I wonder if there is some sys log you can put up here regarding that error.
ap...@google.com <ap...@google.com> #10
il...@google.com <il...@google.com> #11
OpenSUSE Tumbleweed has a toggle in it's network settings for "Enable IPv6". I don't have IPv6 on my internet connection and none of my local devices need it, so I usually leave it disabled.
I tried enabling it and viola, the emulator is starting for me again (without needing the ModemSimulator flag).
It looks like that toggle adds net.ipv6.conf.all.disable_ipv6 = 1
to /etc/sysctl.conf.
Description
Navigation Compose has APIs that would be a better fit as part of the base Navigation library. Instead of allowing Navigation Compose to go to 1.0.0 stable with the libraries and attempting to deprecate them later when they are added to base Navigation, we should instead add those APIs to the next version of Navigation and move Navigation Compose in sync with that.
This means that Navigation Compose will be part of Navigation 2.4.0 instead of an 1.0.0.