Ubuntu

Andoid AVD Can't start WARNING: Application calling GLX 1.3 function "glXCreatePbuffer"

Asked by Bahh on 2012-07-20

just installed of kubuntu 12.04

Remoted in using nomachine NX from winXp and trying to start an android AVD, it fails to start and I get the following message:

Starting emulator for AVD 'HTC-HERO-API-7-r2.1'
WARNING: Application calling GLX 1.3 function "glXCreatePbuffer" when GLX 1.3 is not supported! This is an application bug!
X Error of failed request: GLXUnsupportedPrivateRequest
  Major opcode of failed request: 147 (GLX)
  Minor opcode of failed request: 16 (X_GLXVendorPrivate)
  Serial number of failed request: 20
  Current serial number in output stream: 22

When I try from the local console on the kubuntu machine, AVD starts with no issues.

When remoted using nomachine NX from winXp into a kubuntu 10.x on a different machine AVD started with no issues.

Any ideas?

Question information

Language:
English Edit question
Status:
Expired
For:
Ubuntu xorg Edit question
Assignee:
No assignee Edit question
Last query:
2012-11-09
Last reply:
2012-11-27

Can you give the output of:

sudo lshw -C display; lsb_release -a; uname -a

Thanks

Hannes (hannes-software) said : #2

I run into same issue. my output of sudo lshw -C display; lsb_release -a; uname -a

  *-display
       Beschreibung: VGA compatible controller
       Produkt: RS880 [Radeon HD 4290]
       Hersteller: Hynix Semiconductor (Hyundai Electronics)
       Physische ID: 5
       Bus-Informationen: pci@0000:01:05.0
       Version: 00
       Breite: 32 bits
       Uhr: 33MHz
       Fähigkeiten: pm msi vga_controller bus_master cap_list rom
       Konfiguration: driver=radeon latency=0
       Ressourcen: irq:18 memory:d0000000-dfffffff ioport:e000(Größe=256) memory:fe700000-fe70ffff memory:fe600000-fe6fffff
LSB Version: core-2.0-amd64:core-2.0-noarch:core-3.0-amd64:core-3.0-noarch:core-3.1-amd64:core-3.1-noarch:core-3.2-amd64:core-3.2-noarch:core-4.0-amd64:core-4.0-noarch:cxx-3.0-amd64:cxx-3.0-noarch:cxx-3.1-amd64:cxx-3.1-noarch:cxx-3.2-amd64:cxx-3.2-noarch:cxx-4.0-amd64:cxx-4.0-noarch
Distributor ID: Ubuntu
Description: Ubuntu 12.04 LTS
Release: 12.04
Codename: precise
Linux abcserver 3.2.0-26-generic #41-Ubuntu SMP Thu Jun 14 17:49:24 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

R. Palubjak (r7-hwmdbg) said : #3

quite annoying, since now I can't remote access (tried X-fwd, VNC, NoMachine) development machine.

  *-display
       description: VGA compatible controller
       product: Caicos [Radeon HD 6450]
       vendor: Hynix Semiconductor (Hyundai Electronics)
       physical id: 0
       bus info: pci@0000:01:00.0
       version: 00
       width: 64 bits
       clock: 33MHz
       capabilities: pm pciexpress msi vga_controller bus_master cap_list rom
       configuration: driver=radeon latency=0
       resources: irq:44 memory:d0000000-dfffffff memory:e1420000-e143ffff ioport:3000(size=256) memory:e1400000-e141ffff
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04 LTS
Release: 12.04
Codename: precise
Linux r7-PC 3.2.0-27-generic #43-Ubuntu SMP Fri Jul 6 14:25:57 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux

Bahh (kmeaghermd) said : #4

Sorry for the delay, I've been out of town.

  *-display
       description: VGA compatible controller
       product: 82G33/G31 Express Integrated Graphics Controller
       vendor: Intel Corporation
       physical id: 2
       bus info: pci@0000:00:02.0
       version: 10
       width: 32 bits
       clock: 33MHz
       capabilities: msi pm vga_controller bus_master cap_list rom
       configuration: driver=i915 latency=0
       resources: irq:42 memory:fdf00000-fdf7ffff ioport:ff00(size=8) memory:d0000000-dfffffff memory:fdc00000-fdcfffff
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 12.04 LTS
Release: 12.04
Codename: precise
Linux vista 3.2.0-26-generic-pae #41-Ubuntu SMP Thu Jun 14 16:45:14 UTC 2012 i686 i686 i386 GNU/Linux

Thanks!

Bahh (kmeaghermd) said : #5

Is this likely an issue with my graphics controller? My older computer with kubuntu 10.x has an nvidia video card. Should I try swapping the older video card into the new computer?

R. Palubjak (r7-hwmdbg) said : #6

Some more observation on starting avd:
X-fwd with Cygwin from WinXP works.
X-Fwd from RedHat does not work.
VNC from WinXP does not work.
I saw someone with NVidia card having same problem.
I guess it may be related to version of Android tools as they were recently updated few times, shadowed by Ubuntu update.

R. Palubjak (r7-hwmdbg) said : #7

WinXP -> NX -> Kubuntu
although
$emulator @name fails,
$emulator-arm @name does not!

R. Palubjak (r7-hwmdbg) said : #8

as for my comment #7: the error message is called by emulator GPU acceleration. if invoked by "emulator", emulator support libraries libOpenglRender.so (libEGL_translator.so, libGLES_CM_translator.so, libGLES_V2_translator.so, libOpenglRender.so) from Android/sdk/r18/tools/lib/ are found and later we get error message.
However "emulator-arm" cannot find libOpenglRender.so etc (looking in /usr/lib*/_many_possible_dirs_/), and after giving a short warning:

emulator: Initializing hardware OpenGLES emulation support
emulator: ERROR: Could not load OpenGLES emulation library: libOpenglRender.so: cannot open shared object file: No such file or directory
emulator: WARNING: Could not initialize OpenglES emulation, using software renderer.

starts using software renderer.

It seems to me this issue is not related to K/Ubuntu at all, but recent android tools/emulator.

Adem Caliskan (adem.caliskan) said : #9

Possible reason is that the emulator couldn't find the file libOpenglRender.so in some path variables where android-sdk is looking for.

I tried this in Ubuntu 11.10:
- Navigate to android-sdk/tools/lib
- start emulator with [code] ../emulator -avd <your_avd> -gpu on [/code]

Notice: GPU Acceleration work only on AVD's API Level 15 (Android 4.0.3) or higher.
See http://developer.android.com/tools/devices/emulator.html#accel-graphics

Adem

Bahh (kmeaghermd) said : #10

As with #7 above emulator-arm works with the following error message (same as #8 above).

~/android-sdks/tools/lib$ ../emulator-arm -avd phone-api-15 -gpu on
emulator: ERROR: Could not load OpenGLES emulation library: libOpenglRender.so: cannot open shared object file: No such file or directory
emulator: WARNING: Could not initialize OpenglES emulation, using software renderer.

On the other hand #9 fails as before but with additional information:

../emulator -avd phone-api-15 -gpu on
libGL error: failed to load driver: swrast
libGL error: Try again with LIBGL_DEBUG=verbose for more details.
WARNING: Application calling GLX 1.3 function "glXCreatePbuffer" when GLX 1.3 is not supported! This is an application bug!
X Error of failed request: GLXUnsupportedPrivateRequest
  Major opcode of failed request: 147 (GLX)
  Minor opcode of failed request: 16 (X_GLXVendorPrivate)
  Serial number of failed request: 20
  Current serial number in output stream: 22

Is there an issue using emulator-arm vs emulator?

-Kevin

Launchpad Janitor (janitor) said : #11

This question was expired because it remained in the 'Open' state without activity for the last 15 days.