7

After upgrading my android studio - I tried creating an emulator but get this error when trying to start the AVD :

Emulator: statvfs('/home/nompumelelo/.android/avd/Pixel_2_API_24.avd/snapshots/default_boot/ram.img') failed:
No such file or directory

I have restarted the android studio, recreated the AVD - but still no success.

The error below is what shows on my terminal.

jww
  • 97,681
  • 90
  • 411
  • 885
Nompumelelo
  • 929
  • 3
  • 17
  • 28
  • is the emulator successfully created? – afhamu Aug 08 '19 at 23:34
  • 1
    Try changing the emulator configuration to 'Cold Boot' (assuming it was quick boot which uses the snapshot) then start the emulator - once started you can change option back to quick-boot - it should save a new snapshot. –  Aug 09 '19 at 00:44
  • 1
    @Afhamu - the emulator gets created but it-s not functional. – Nompumelelo Aug 09 '19 at 12:21
  • @Andy: I tried the cold boot option, now the problem is with the space. I get this error not `Emulator: emulator: ERROR: Not enough space to create userdata partition. Available: 5528.578125 MB ` – Nompumelelo Aug 09 '19 at 12:22
  • Ok what's the available memory space of your Local Drive C? – afhamu Aug 09 '19 at 12:32
  • Its 5.8 GB - I am working on setting a smaller sized memory and storage, will tell you if it worked. – Nompumelelo Aug 09 '19 at 12:37
  • 1
    I am having the same issue, must be because of the latest update... oh google :( – HennyKo Aug 11 '19 at 10:28
  • I just downgraded my Emulator by putting the "emulator" folder (found in the zip) to the sdk folder (e.g. `/home/sufian/Android/Sdk` for me, or see your folder by going to settings and search for "SDK"). [This answer](https://stackoverflow.com/a/49284378/1276636) provides the download link. – Sufian Sep 19 '19 at 12:00
  • Someone has reported this on the [issue tracker](https://issuetracker.google.com/issues/141143926). – Sufian Sep 20 '19 at 06:35

2 Answers2

1

I can confirm that the Emulator 29.2.1 Stable fixes this bug.

An excerpt from the link above:

Fixed crash on startup on Linux Wayland systems. This was because XkbGetKeyboard was used to query the host system's keyboard state. It seems usage of XkbGetKeyboard is not advisable on Linux and perhaps in general: https://github.com/glfw/glfw/issues/389

Sufian
  • 6,405
  • 16
  • 66
  • 120
0

I was having the same problem using XWayland, after switching to X11 it worked again.

williampaulo
  • 11
  • 1