Status Update
Comments
il...@google.com <il...@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
[Deleted User] <[Deleted User]> #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.
il...@google.com <il...@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.
[Deleted User] <[Deleted User]> #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".
lo...@gmail.com <lo...@gmail.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
mu...@gmail.com <mu...@gmail.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;
}
[Deleted User] <[Deleted User]> #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.
[Deleted User] <[Deleted User]> #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.
[Deleted User] <[Deleted User]> #12
that is very helpful information.
I was surprised that emulator does not even try ipv4 when ipv6 failed;
error_setg should be just a warning instead of quitting.
h....@gmail.com <h....@gmail.com> #13
Yes,turning IPv6 on worked for me too.
Description
DETAILS:-
The destination home is an activity with a NavHostFragment (FirstFragment.kt) which initially navigates to the second destination (SecondActivity.kt), then immediately comes back to the FirstFragment, and then navigates to third destination (FirstPopupFragment.kt). (Navigation can be observed in the attached screen-record).
LOG:-
2018-05-27 20:39:52.794 3289-3289/? E/AndroidRuntime: FATAL EXCEPTION: main
Process: com.example.cyrilnoah.navigationegapp, PID: 3289
java.lang.IllegalArgumentException: navigation destination com.example.cyrilnoah.navigationegapp:id/action_first_to_first_popup is unknown to this NavController
at androidx.navigation.NavController.navigate(NavController.java:605)
at androidx.navigation.NavController.navigate(NavController.java:565)
at androidx.navigation.NavController.navigate(NavController.java:553)
at com.example.cyrilnoah.navigationegapp.FirstFragment$onViewCreated$1.onClick(FirstFragment.kt:40)
at android.view.View.performClick(View.java:6579)
at android.view.View.performClickInternal(View.java:6556)
at android.view.View.access$3100(View.java:777)
at android.view.View$PerformClick.run(View.java:25660)
at android.os.Handler.handleCallback(Handler.java:819)
at android.os.Handler.dispatchMessage(Handler.java:99)
at android.os.Looper.loop(Looper.java:164)
at android.app.ActivityThread.main(ActivityThread.java:6656)
at java.lang.reflect.Method.invoke(Native Method)
at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:438)
at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:823)
Component used:
"android.arch.navigation:navigation-fragment-ktx:$nav_version"
"android.arch.navigation:navigation-ui-ktx:$nav_version"
Version used:
nav_version = '1.0.0-alpha01'
Devices/Android versions reproduced on:
Tested on Pixel 2 XL (emulator), and Xiaomi Mi Max 2 (real device). Probably crashes on all, not so sure.
- Sample project to trigger the issue.
(Project attached below)
- A screenrecord or screenshots showing the issue (if UI related).
(Screen-record attached below)