IssueTracker

Can you share android studio version

Android Studio 2.3.3

It's been happening for the last couple of years, probably longer.

Getting this error as well. Preloading the stdc++ seems to work as mentioned in #3

Consider updating Linux compiler/libstdc++ to gcc 4.9?

Seems to be solved here on my machine, now using Android emulator version 25.0.3.0.

Bug suddenly appears for me as well. OS X 10.11.2 here, Android Studio 2.0 preview 5 + 7, SDK Tools 25.0.2 rc3

Hax is enabled
Hax ram_size 0x60000000
HAX is working and emulator runs in fast virt mode.
adb_server_notify: Failed to establish connection to ADB server
console on port 5554, ADB on port 5555
Failed to sync vcpu reg
Failed to sync vcpu reg
Failed to sync vcpu reg
Failed to sync vcpu reg
Failed to sync vcpu reg
Failed to sync HAX vcpu context

I checked back with updated version of the emulator and SDK tools:

Emulator Version: Android 6.0 - Google APIs Intel x86 Atom System Image (revision 12)
Android SDK Tools: 25.0.3 rc4

Same error, though.

A tentative fix is here: https://android-review.googlesource.com/#/c/202063/

Thanks to showloaber.felxhomann for providing information. The root cause of the problem is likely that the Radeon GL driver library requires a more recent libstdc++.so than the one bundled with the emulator.

The propose -use-system-libs flag (and ANDROID_EMULATOR_USE_SYSTEM_LIBS env. variable) should work-around this problem, by forcing the use of the system library.

Note that #11 is a completely different issue and should have its own entry.

Great. I am looking forward for the patched emulator being shipped. I will test it.

Just for completeness: Meanwhile Android SDK Tools: 25.0.5 are out. I can still reproduce the error with that version.

Yes, the fix will be part of the next release of the preview emulator (or the first official 2.0 release, whichever comes first).

#3 worked for me. You need to install lib64stdc from synaptic.

Confirmed. I now installed libstdc++6 via apt-get. Then the following starts the emulator:

$ LD_PRELOAD='/usr/lib64/libstdc++.so.6' emulator -no-boot-anim -netdelay none -netspeed full -avd Nexus_5_API_22_Google -qemu -m 2047
ERROR: ld.so: object '/usr/lib64/libstdc++.so.6' from LD_PRELOAD cannot be preloaded (wrong ELF class: ELFCLASS64): ignored.
console on port 5554, ADB on port 5555

There are other issues when using it but I will first try it for a while before I report these.

I still have the issue... with Android Studio 2.0 beta 5, SDK tools 25.0.7
Really I don't understand... seems very easy to me to solve this issue... I can't work with my Debian distro...

Installing libstdc++6 and starting the emulator with LD_PRELOAD='/usr/lib64/libstdc++.so.6' fixed the issue for me too.

I'm on Ubuntu 16.04 with open source radeon drivers (AMD 7790).

I got my emulator working again by just copying my system's libstdc++.so.6 and libstdc++.so.6.0.21 (current version on my system) into ~/Android/SDK/tools/lib64 - after moving the original files out of that location to a temporary location.

After that I can launch emulators from Android Studio with no adjustments to command lines.

Confirmed. I create a symlink and then I can start the emulator without prepending LD_PRELOAD as stated before.

$ cd $ANDROID_HOME/android-sdk-linux_x86/tools/lib64/libstdc++
$ mv libstdc++.so.6 libstdc++.so.6.bak
$ ln -s /usr/lib64/libstdc++.so.6 $ANDROID_HOME/android-sdk-linux_x86/tools/lib64/libstdc++

Thank you for the hint!

Hey, could someone tell me where should I put the parameter -use-system-libs when starting the emulator from the Studio?

I get the following Error on Ubuntu 16.04 (amd open source drivers on AMD R9 380)
after applying any workaround from above.

X Error of failed request:  BadAlloc (insufficient resources for operation)
  Major opcode of failed request:  149 ()
  Minor opcode of failed request:  2
  Serial number of failed request:  36
  Current serial number in output stream:  37
 
   

Works fine now with latest Ubuntu update.

FirePro M8900 Ubuntu 16.04 LTS
...
libGL error: unable to load driver: r600_dri.so
...

#23 tobias.preuss method works perfectly just create symlink. THX man!

Ubuntu 16.04 LTS, Android Studio 2.1.

unable to load driver r600_dri.so

#23 tobias.preuss method works perfectly for me too! thanks you! :D

better locate your system default libstdc++.so.6 using the command
locate libstdc++.so.6

And Then Take a back up of the android sdk version of the file in ~/Android/Sdk/tools/lib64/libstdc++/

And create a soft link for libstdc++.so.6 with the same name in the above path replacing the existing one pointing to the default file in the system

This way we do not need restart the emulator every time from command line.

I have the same issue, wrote in terminal "export ANDROID_EMULATOR_USE_SYSTEM_LIBS=1" to force using own system libs but failed, so I had to delete(renamed lib64 to lib64.renamed) the folder: "/home/MY_USER_NAME/Android/Sdk/tools/lib64" in order to work, now every thing works fine, but I feel there is a better way to do this, any ideas?

#30 EDIT
fixed "ANDROID_EMULATOR_USE_SYSTEM_LIBS" error, turns out I improbably assigned ANDROID_HOME, reassigned the value "export ANDROID_HOME=/[installation location]/SDK", then "export PATH=${PATH}:$ANDROID_HOME/tools:$ANDROID_HOME/platform-tools".
My bad :(, now time to start my first android application ever :D, thanks all.

Since I upgraded to Ubuntu Gnome 16.04 and Android Studio 2.1 the problem returned for me. Also I got an error installing the new 25.1.3 SDK due to the installer not being happy about having to deal with my link to libstdc++
So, I deleted my link and the SDK installed and then I noticed my link was broken anyway so WTF - I decided not to replace it but just delete the libstdc++.so that was installed in /tools/lib64/
This leaves just libstdc++.so.6.0.18 in that folder. I then tried launching an emulator from Android Studio 2.1 and it worked. So this seems to me like the easiest workaround as it should allow new SDKs to install successfully.

#23 tobias.preuss method works via Ubuntu 16.04.  Big Thanks to all!

#23 confirmed on Ubuntu Mate 16.04 inside a vmware player as well! Only thing I had to change is "lib64" to "lib32".

#23 worked for me. Thank you!

#23 tobias.preuss method works on XUBUNTU 16.04 Linux 4.6
Thank you!

#23 props and thanks!

Cannot launch AVD in emulator.
Output:
libGL error: unable to load driver: radeonsi_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: radeonsi
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
X Error of failed request:  GLXBadContext
  Major opcode of failed request:  155 (GLX)
  Minor opcode of failed request:  6 (X_GLXIsDirect)
  Serial number of failed request:  47
  Current serial number in output stream:  46
libGL error: unable to load driver: radeonsi_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: radeonsi
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
X Error of failed request:  GLXBadContext
  Major opcode of failed request:  155 (GLX)
  Minor opcode of failed request:  6 (X_GLXIsDirect)
  Serial number of failed request:  47
  Current serial number in output stream:  46

#23 tobias.preuss method works on Ubuntu Xenial GNOME (i3WM) 16.04 LTS
Linux 4.4.0.-22 Generic

Thank you!

cd $ANDROID_HOME/android-sdk-linux_x86/tools/lib64/libstdc++
should i have to enter along with_x86 or with only
cd $ANDROID_HOME/android-sdk-linux/tools/lib64/libstdc++

If I create a soft link as mentioned above, no error is reported, but the emulator will hang on the loading screen (prior to showing the actual android device).

Now with SDK Tools 25.2 even manually replacing the files with version 20 doesn't work:

Cannot launch AVD in emulator.
Output:
libGL error: unable to load driver: r600_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: r600
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
X Error of failed request:  GLXBadContext
  Major opcode of failed request:  155 (GLX)
  Minor opcode of failed request:  6 (X_GLXIsDirect)
  Serial number of failed request:  49
  Current serial number in output stream:  48
libGL error: unable to load driver: r600_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: r600
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
X Error of failed request:  GLXBadContext
  Major opcode of failed request:  155 (GLX)
  Minor opcode of failed request:  6 (X_GLXIsDirect)
  Serial number of failed request:  49
  Current serial number in output stream:  48
libGL error: unable to load driver: r600_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: r600
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  155 (GLX)
  Minor opcode of failed request:  24 (X_GLXCreateNewContext)
  Value in failed request:  0x0
  Serial number of failed request:  33
  Current serial number in output stream:  34
QObject::~QObject: Timers cannot be stopped from another thread

$ cd $ANDROID_HOME/android-sdk-linux_x86/tools/lib64/libstdc++
$ mv libstdc++.so.6 libstdc++.so.6.bak
$ ln -s /usr/lib64/libstdc++.so.6 $ANDROID_HOME/android-sdk-linux_x86/tools/lib64/libstdc++

This is working nicely.. Thanks....

32(F1SHE4RS) worked for me. Thank you! doru.marinau@gmail.com

Just upgraded to Ubuntu 16.10 and encountered this issue. For me the fix was to move libstdc++.so.6 out of the way. i.e. renamed it to libstdc++.so.6.bak.

This is the same as #32. Now I can start an AVD again!

i have sdk version 24.0.3, ubuntu version - 16.04.1 LTS

I don't have android studio installed. I built the android source code which went fine.
now trying to launch emulator is giving me this error.

----------------------------------------------------------------------
$ libGL error: unable to load driver: r600_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: r600
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
X Error of failed request:  GLXBadContext
  Major opcode of failed request:  155 (GLX)
  Minor opcode of failed request:  6 (X_GLXIsDirect)
  Serial number of failed request:  49
  Current serial number in output stream:  48
emulator: WARNING: system partition size adjusted to match image file (1792 MB > 200 MB)

emulator: WARNING: data partition size adjusted to match image file (550 MB > 200 MB)

libGL error: unable to load driver: r600_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: r600
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
X Error of failed request:  GLXBadContext
  Major opcode of failed request:  155 (GLX)
  Minor opcode of failed request:  6 (X_GLXIsDirect)
  Serial number of failed request:  49
  Current serial number in output stream:  48
emulator: WARNING: encryption is off
libGL error: unable to load driver: r600_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: r600
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  155 (GLX)
  Minor opcode of failed request:  24 (X_GLXCreateNewContext)
  Value in failed request:  0x0
  Serial number of failed request:  33
  Current serial number in output stream:  34
QObject::~QObject: Timers cannot be stopped from another thread
----------------------------------------------------------------------

There are a couple of workarounds to this kind of problem at http://stackoverflow.com/questions/40066007/

This issue reappeared when I updated to Ubuntu 16.10, I'm using AS 2.2.2 with only NDK not updated to the latest version, renaming libstdc++.so.6.0.18 and libstdc++.so.6 fixed the issue for me.

#48 rename those two files (adding ".bak") works for me.

sh: 1: glxinfo: not found
sh: 1: glxinfo: not found
emulator: WARNING: Host CPU is missing the following feature(s) required for x86_64 emulation: SSSE3 SSE4.1 SSE4.2
Hardware-accelerated emulation may not work properly!
libGL error: unable to load driver: r600_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: r600
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  155 (GLX)
  Minor opcode of failed request:  24 (X_GLXCreateNewContext)
  Value in failed request:  0x0
  Serial number of failed request:  33
  Current serial number in output stream:  34
QObject::~QObject: Timers cannot be stopped from another thread

i just rename the file Android/Sdk/lib64/libstdc++/libstdc++.so.6 to libstdc++.so.6 and works

Just updated Android tools and got this again :(

#23 process worked for me.

If you are a linux noob, keep in mind that #23's file paths will most likely be different

Getting this on 16.10 current. Renamed the libstdc++ as per #43, emulator does come up, but crashes when apk is deployed. This is with intel hd 3000 graphics. Same setup on a different machine with nvidia all seems fine.
I wish google would have the honesty to just say that their principal supported platform is apple macs rather than make everybody go through a regular waste of time
dance.

I used the method described above where you create a Symlink to a user library, and it worked for a while. But it broke for me within the past few weeks. I think it may have been caused by updating something in the Android SDK. I'm back to getting error messages when I try to launch an emulator with "automatic" or "hardware". "software" still works.

The messages are now:

/home/mwelke/Android/Sdk/tools/emulator -netdelay none -netspeed full -avd Nexus_5_API_16
libGL error: unable to load driver: radeonsi_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: radeonsi
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
X Error of failed request:  GLXBadContext
  Major opcode of failed request:  155 (GLX)
  Minor opcode of failed request:  6 (X_GLXIsDirect)
  Serial number of failed request:  49
  Current serial number in output stream:  48
libGL error: unable to load driver: radeonsi_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: radeonsi
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
X Error of failed request:  GLXBadContext
  Major opcode of failed request:  155 (GLX)
  Minor opcode of failed request:  6 (X_GLXIsDirect)
  Serial number of failed request:  49
  Current serial number in output stream:  48
libGL error: unable to load driver: radeonsi_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: radeonsi
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
X Error of failed request:  BadValue (integer parameter out of range for operation)
  Major opcode of failed request:  155 (GLX)
  Minor opcode of failed request:  24 (X_GLXCreateNewContext)
  Value in failed request:  0x0
  Serial number of failed request:  33
  Current serial number in output stream:  34
QObject::~QObject: Timers cannot be stopped from another thread

I performed some troubleshooting and wanted to comment with what I did too to see if that helps anyone working on this.

I opened up the SDK Manager through Tools > Android. On the SDK Tools tab, I noticed I had the following things installed:

- Android SDK Built-Tools
- Android SDK Platofrm-Tools
- Android DK Tools 25.2.5

I figured since I had modified the contents of my Android/Sdk directory, by creating the symlink as per the above troubleshooting recommendation, it might be a good idea to reinstall those parts. So I uninstalled the three things listed above, checked that the contents of the folder where that "stdc++..." file was was now empty, and then reinstalled the things. I now have the following files in my ~/Android/Sdk/tools/lib64/libstdc++ directory:

-rwxrwxr-x 1 mwelke mwelke 4821336 Feb  1 22:40 libstdc++.so.6*
-rwxrwxr-x 1 mwelke mwelke 4821336 Feb  1 22:40 libstdc++.so.6.0.18*

The problem still continues.

My system is Ubuntu 16.04 LTS by the way.

Don't symlink, delete or rename the files. It works with Ubuntu 16.04 and 16.10 both.

It does not work with Ubuntu 16.04.  Renaming the file is sufficient.  No need to symlink the system version.

The issue still exists with 2.4 Preview 2.

I found my libstdc++ folder underneath $ANDROID_SDK_LOCATION/emulator/lib64/libstdc++ in case anyone is having troubles trying to locate it.

Seems as though I have to perform the workaround in #43 every time the tools update.

idea log at ~/.AndroidStudio2.3/system/log
android-sdk-linux/emulator/emulator-check": error=13, Permissão negada
WARN - vdmanager.AvdManagerConnection - Failed to create the SD card.
WARN - vdmanager.AvdManagerConnection - Failed to create sdcard in the AVD folder.

In my case happens because some executable files in ~/android-sdk-linux/emulator cannot be executed.Go to this folder and make all files executable by this command :

chmod +x -R *

worked for me ;.)

Re-opening to see if we can get a better fix here.

One idea would be to just stop shipping our own libstdc++.so (we historically haven't done with for things like adb). Building against prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8 will guarantee that we support anything with a libstdc++ equal or newer than what shipped with Ubuntu 14.04.

digit: Do you know why we ship our own libstdc++? I'm guessing it was to support even older systems?

Alternatively, if we could detect the version of libstdc++ on the user's system, we could just default to loading that if it's newer than ours.

Emulator has to support not just Ubuntu before 14.04, but also other Linux distributions; another source of (loud) feedback is custom environment configurations on user machines. The only way to handle all these is to always ship the core dependencies and make sure we use those first :(

> ship the core dependencies and make sure we use those first

But this is just ridiculous. We have to delete these bundled libstdc++ on every emulator pkg update to get emulator working...

It is right and proper that the tools support more than just Ubuntu on the Linux platform, as #62 states. However I agree with #63 that this leads to a ridiculous situation where an upgrade consciously breaks systems. How hard / feasible would the last suggestion of #61 be whereby you detect effected systems and load the appropriate libstdc++ at runtime or even _move_ the bundled ones out of the way at install / upgrade time?

To answer #61, the history is the following:

* Initially, link libstdc++ statically to all binaries, everything was peachy, but we had to stop once we used third-party shared libraries (namely Qt).
* Switched to using the system libstdc++, and found it broke on many systems (at the time), including our *own* *build* *servers* who used a version that didn't have the C++11 features we needed.
* Started to bundle our own libstdc++.so with the emulator, problems were fixed for a significant time.
* Later, we experimented issues on users' machine like the ones described here.

The root issue is that only one of our custom libstdc++ or the system one can be loaded at the same time. When a library like libGL.so is loaded with a libstdc++ that is too old, things get weird.

We should first try to update to the new toolchain as suggested by Dan (we're currently using prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.8, so switching to glibc2.15, released on 2012-03-21, seems reasonable today). And also rebuild all prebuilt libraries with it as well.

In practical terms, this means:

1) update the repo manifest in the emu-master-dev branch to use  prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.15-4.8 instead of  prebuilts/gcc/linux-x86/host/x86_64-linux-glibc2.11-4.8
2) updating one line in aosp_prebuilt_toolchain_subdir_for() in external/qemu/android/scripts/utils/aosp_dir.shi, to select the new toolchain.
3) calling the build-XXXX.sh scripts for every one of our dependencies with the new toolchain (and hope this doesn't break stuff).
4) submit the prebuilt binaries under prebuilts/android-emulator-build/...
5) rebuild the emulator and check that everything works correctly.

If this doesn't work, I can only see two solutions to fix this:

A) Keep using a custom libstdc++.so, but rename it (e.g. libstdc++_emulator.so) and ensure our C++ third-party libraries (and _all_ their C++ dependencies) are linked against them.
This requires rebuilding the library from sources, which is tricky, though :-/

B) Switch back to using the system libstdc++.so, However, that's what -use-system-libs is supposed to do, so I'm surprised this doesn't work ??

I'm no longer on the emu-dev team, so hope someone can work on this.

Still exists with Ubuntu 17.04 and Android everything updated to the latest of today:

Cannot launch AVD in emulator.
Output:
libGL error: driver pointer missing
libGL error: failed to load driver: i965
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
X Error of failed request:  GLXBadContext
  Major opcode of failed request:  155 (GLX)

I am on openSUSE Tumbleweed and I have a similar issue.

Emulator: libGL error: unable to load driver: i965_dri.so
Emulator: libGL error: driver pointer missing
Emulator: libGL error: failed to load driver: i965
Emulator: libGL error: unable to load driver: i965_dri.so
Emulator: libGL error: driver pointer missing
Emulator: libGL error: failed to load driver: i965
Emulator: libGL error: unable to load driver: swrast_dri.so
Emulator: libGL error: failed to load driver: swrast
Emulator: X Error of failed request:  BadValue (integer parameter out of range for operation)
Emulator: Major opcode of failed request:  155 (GLX)
Emulator: Minor opcode of failed request:  24 (X_GLXCreateNewContext)
Emulator: Value in failed request:  0x0
Emulator: Serial number of failed request:  42
Emulator: Current serial number in output stream:  43
Emulator: Process finished with exit code 1

Change to P1 as more users are impacted by this bug. https://stackoverflow.com/questions/42831999/android-studio-2-3-ubuntu-16-10-emulator-do-not-start

We've upgraded glibc to 2.15. Hopefully this will ease the pain. https://android-review.googlesource.com/#/c/423120/

I am currently experiencing this problem with Android Studio 2.3 and 3.0 when trying to start Android emulator version 26.1.4.0 (build_id 4266726) (CL:add3139bafe4f34502c851716afcee834068103a)

Hiding the libraries in emulator/lib64/libstdc++ makes the problem go away and everything works fine.

12:56 PM        Emulator: libGL error: unable to load driver: i965_dri.so
12:56 PM        Emulator: libGL error: driver pointer missing
12:56 PM        Emulator: libGL error: failed to load driver: i965
12:56 PM        Emulator: libGL error: unable to load driver: i965_dri.so
12:56 PM        Emulator: libGL error: driver pointer missing
12:56 PM        Emulator: libGL error: failed to load driver: i965
12:56 PM        Emulator: libGL error: unable to load driver: swrast_dri.so
12:56 PM        Emulator: libGL error: failed to load driver: swrast
12:56 PM        Emulator: X Error of failed request:  BadValue (integer parameter out of range for operation)
12:56 PM        Emulator: Major opcode of failed request:  155 (GLX)
12:56 PM        Emulator: Minor opcode of failed request:  24 (X_GLXCreateNewContext)
12:56 PM        Emulator: Value in failed request:  0x0
12:56 PM        Emulator: Serial number of failed request:  39
12:56 PM        Emulator: Current serial number in output stream:  40
12:56 PM        Emulator: Process finished with exit code 1
1:00 PM Emulator: libGL error: unable to load driver: i965_dri.so
1:00 PM Emulator: libGL error: driver pointer missing
1:00 PM Emulator: libGL error: failed to load driver: i965
1:00 PM Emulator: libGL error: unable to load driver: i965_dri.so
1:00 PM Emulator: libGL error: driver pointer missing
1:00 PM Emulator: libGL error: failed to load driver: i965
1:00 PM Emulator: libGL error: unable to load driver: swrast_dri.so
1:00 PM Emulator: libGL error: failed to load driver: swrast
1:00 PM Emulator: X Error of failed request:  BadValue (integer parameter out of range for operation)
1:00 PM Emulator: Major opcode of failed request:  155 (GLX)
1:00 PM Emulator: Minor opcode of failed request:  24 (X_GLXCreateNewContext)
1:00 PM Emulator: Value in failed request:  0x0
1:00 PM Emulator: Serial number of failed request:  39
1:00 PM Emulator: Current serial number in output stream:  40
1:00 PM Emulator: Process finished with exit code 1

Which exact Linux distribution are you using? The GLibc 2.15 should have fixed that already.

I am using Arch Linux with GLibc 2.16. So still need to remove prebundled libstdc

I didn't notice that this has been fixed. But actually on my ubuntu 17.04 is still broken. This evening I'll try to make a fresh install an report the details

I had a similar issue on ubuntu 17.04 with an ATI Radeon HD5670 installed, trying to start the emulator from the command line gave me this error like some of the others here ...

libGL error: unable to load driver: r600_dri.so

... based on the comments here the following resolved the issue ...

cd $ANDROID_HOME/emulator/lib/libstdc++/
mv libstdc++.so.6 libstdc++.so.6.bak
mv libstdc++.so.6.0.18 libstdc++.so.6.0.18.bak
ln -s /usr/lib/i386-linux-gnu/libstdc++.so.6 libstdc++.so.6
ln -s /usr/lib/i386-linux-gnu/libstdc++.so.6.0.22 libstdc++.so.6.0.22

cd $ANDROID_HOME/emulator/lib64/libstdc++/
mv libstdc++.so.6 libstdc++.so.6.bak
mv libstdc++.so.6.0.18 libstdc++.so.6.0.18.bak
ln -s /usr/lib/x86_64-linux-gnu/libstdc++.so.6 libstdc++.so.6
ln -s /usr/lib/x86_64-linux-gnu/libstdc++.so.6.0.22 libstdc++.so.6.0.22

I got also the errors on 17.10 of missing libraries, tried the soft links and now I get an exit code 0
12:08   Emulator: Process finished with exit code 0
but in the run log I get an info:
10/30 12:08:48: Launching app
Error while waiting for device: The emulator process for AVD Nexus_5X_API_23 was killed.

... without any other info

xubuntu 17.10 has the issue as well.

I am running Ubuntu 17.04 and I got following error:


8:33 Emulator: libGL error: unable to load driver: r600_dri.so

8:33 PM Emulator: libGL error: driver pointer missing

8:33 PM Emulator: libGL error: failed to load driver: r600

8:33 PM Emulator: libGL error: unable to load driver: r600_dri.so

8:33 PM Emulator: libGL error: driver pointer missing

8:33 PM Emulator: libGL error: failed to load driver: r600

8:33 PM Emulator: libGL error: unable to load driver: swrast_dri.so

8:33 PM Emulator: libGL error: failed to load driver: swrast

8:33 PM Emulator: X Error of failed request:  BadValue (integer parameter out of range for operation)

8:33 PM Emulator: Major opcode of failed request:  156 (GLX)

8:33 PM Emulator: Minor opcode of failed request:  24 (X_GLXCreateNewContext)

8:33 PM Emulator: Value in failed request:  0x0

8:33 PM Emulator: Serial number of failed request:  37

8:33 PM Emulator: Current serial number in output stream:  38

8:33 PM Emulator: Process finished with exit code 1


I symlinked libstdc++.so.6 to ~/android/sdk/tools/lib/

and changed Graphics to "Software - GLES 2.0 " instead of automatic in Virtual Device Configuration.

Now it works fine except when I click on virtual sensors option on running AVD.

Reproduced on ubuntu 17.10.

It looks like video drivers are compiled against newer versions of libstdc++, and they require specific functionality not found in ours.

libstdc++ should be backwards compatible, so a possible workaround would be to figure out which version is available on the local machine, vs the one we provide.
Attached files show which CXXABI we provide (us) vs the one on the machine (them). In this case the video drivers require a newer CXXABI than we have.

Launching with -use-system-libs should resolve most problems.

Launching with  

LD_DEBUG=versions ./emulator @[YOUR_AVD] 2>&1 > /dev/null |  grep -Po \`.*\' | sort -u

Will tell us which library versions you depend on, which can help us identify potential problems with versioning.

We should figure out which version of libstdc++ is available on the local system, and set the ld path such that we pick the one with the max version.

"Some features in the C++ language make versioning especially difficult. In particular, compiler generated constructs such as implicit instantiations for templates, typeinfo information, and virtual tables all may cause ABI leakage across shared library boundaries. Because of this, mixing C++ ABIs is not recommended at this time." (https://gcc.gnu.org/onlinedocs/libstdc++/manual/abi.html), the max version will not guarantee success.

Same here on Gentoo:
- mesa 17.2.6
- llvm 5.0.0 (required by mesa)
- gcc 5.4.0-r3

I think on gcc-4.9.4 and mesa 17.1.10 emulator works ok

Looks like gcc-5 introduces some changes that could cause issues: See https://gcc.gnu.org/onlinedocs/libstdc++/manual/using_dual_abi.html. (Most notably std::string, std::list). This might explain why 4.9.4 still works, newer libraries might link against the newer std::string which we don't have.

Same on Ubuntu Budgie 17.10 with Android Studio 3.0.1...

11:56   Gradle sync started
11:56   Project setup started
11:56   Gradle sync finished in 1s 873ms (from cached state)
11:57   * daemon not running; starting now at tcp:5037
11:57   * daemon started successfully
11:57   Emulator: libGL error: unable to load driver: i965_dri.so
11:57   Emulator: libGL error: driver pointer missing
11:57   Emulator: libGL error: failed to load driver: i965
11:57   Emulator: libGL error: unable to load driver: i965_dri.so
11:57   Emulator: libGL error: driver pointer missing
11:57   Emulator: libGL error: failed to load driver: i965
11:57   Emulator: libGL error: unable to load driver: swrast_dri.so
11:57   Emulator: libGL error: failed to load driver: swrast
11:57   Emulator: X Error of failed request:  BadValue (integer parameter out of range for operation)
11:57   Emulator: Major opcode of failed request:  155 (GLX)
11:57   Emulator: Minor opcode of failed request:  24 (X_GLXCreateNewContext)
11:57   Emulator: Value in failed request:  0x0
11:57   Emulator: Serial number of failed request:  64
11:57   Emulator: Current serial number in output stream:  65
11:57   Emulator: Process finished with exit code 1
11:57   Executing tasks: [:app:assembleDebug]
11:58   Gradle build finished in 21s 579ms

it'd be great if i could get a hack or quick fix for this

On 4 Jan 2018 12:04, <buganizer-system@google.com> wrote:

See my post: https://myachinqa.blogspot.com/2017/12/android-buntu.html
U can add "export ANDROID_EMULATOR_USE_SYSTEM_LIBS=1" in ${HOME}/.profile

I agree that problem is fixed by adding "export ANDROID_EMULATOR_USE_SYSTEM_LIBS=1" to the environment.

Please refer to work-around rather than ruining emulator.

Project: platform/external/qemu
Branch: emu-master-dev

commit 437c640b57c7693f4fcbf6934ab9c578438e228b
Author: Erwin Jansen <jansene@google.com>
Date:   Wed Feb 07 19:38:50 2018

    Use libc++ instead of libstdc++ on linux.
   
    - We now use libc++ with clang vs. libstdc++ with gcc4.8
    - Fixes compiler issues
    - Fixes build scripts to use libc.so, set rpath in executables
    - Removes libstdc++.so copying
    - Deprecrates -use-system-libs
    - Fix reporting bug in rebuild.sh
    - Run tests on newer versions of wine.
    - Remove 32 bit support on windows, cross compilers currently expect
      same bitness on host as as target. Clang only produces 64 bit,
      breaking the 32 bit build.
   
    Test: Unit tests green, can launch
    Test: Runs on Xenial
    Bug: b/37075150
    Change-Id: Id37a98c36d7e9c0d26d737286e3a2f9e46269cf6

M       android/android-emu/android/base/memory/ScopedPtr.h
M       android/android-emu/android/base/system/System.h
M       android/android-emu/android/emulation/qemud/android_qemud_common.h
M       android/android-emu/android/help.c
M       android/android-emu/android/utils/timezone.cpp
M       android/android-emugl/common.mk
M       android/android-emugl/host/tools/emugen/Android.mk
M       android/build/Makefile.top.mk
M       android/build/emulator/binary.make
M       android/build/emulator/definitions.make
M       android/configure.sh
M       android/qemu1/Makefile.qemu1-common.mk
M       android/qemu1/qobject/json-lexer.c
M       android/rebuild.sh
M       android/scripts/build-curl.sh
M       android/scripts/build-protobuf.sh
M       android/scripts/build-qt.sh
M       android/scripts/gen-android-sdk-toolchain.sh
M       android/scripts/utils/aosp_dir.shi
M       android/third_party/libkeymaster3/include/keymaster/android_keymaster_messages.h
M       build.gradle

https://android-review.googlesource.com/611517
https://goto.google.com/android-sha1/437c640b57c7693f4fcbf6934ab9c578438e228b

Estoy en ubuntu 16.04 corriendo android-studio 3

https://ubuverse.com/android-emulator-does-not-launch-in-ubuntu-16-10

Esto me funciono.

I recently upgraded to Fedora 28 from Fedora 27 and I encountered this bug.

libGL error: unable to load driver: i965_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: i965
libGL error: unable to load driver: i965_dri.so
libGL error: driver pointer missing
libGL error: failed to load driver: i965
libGL error: unable to load driver: swrast_dri.so
libGL error: failed to load driver: swrast
Segmentation fault (core dumped)

export ANDROID_EMULATOR_USE_SYSTEM_LIBS=1 or using flag -use-system-libs are the workarounds.

This fix has recently been merged into the 2.7 release branch (a03b1637bf) and should be in canary by now.

Emulator: Process finished with exit code 1

15:09   Executing tasks: [:app:assembleDebug]

15:09   Emulator: init: Could not find wglGetExtensionsString!

15:09   Emulator: getGLES2ExtensionString: Could not find GLES 2.x config!

15:09   Emulator: Failed to obtain GLES 2.x extensions string!

15:09   Emulator: Could not initialize emulated framebuffer

15:09   Emulator: emulator: ERROR: OpenGLES emulation failed to initialize. Please consider the following troubleshooting steps:

15:09   Emulator: Process finished with exit code -1073741819 (0xC0000005)

Windows 10, Nvidia GeForce 1050TI. After disabling GPU driver and re-enabling it - all starts working again.