Headless build GLXBadFBConfig error

[anoopsonar30]

Steps to reproduce

1. Use habitat-docker on remote AWS server and set up X11 forwarding. Directly using the source github repo on an AWS server results in the same error.
2. (habitat) root@ip-172-31-77-104:/habitat-sim# python examples/example.py --scene ../habitat-api/data/scene_datasets/habitat-test-scenes/skokloster-castle.glb

Observed Results

==== Initialized Sensor Spec: ===== Sensor uuid: color_sensor Sensor type: SensorType.COLOR Sensor position: [0. 1.5 0. ]

debug1: client_input_channel_open: ctype x11 rchan 3 win 65536 max 16384 debug1: client_request_x11: request from 172.31.77.104 57626 debug1: channel 1: new [x11] debug1: confirm x11 X Error of failed request: GLXBadFBConfig Major opcode of failed request: 149 (GLX) Minor opcode of failed request: 34 () Serial number of failed request: 21 Current serial number in output stream: 22 debug1: channel 1: FORCE input drain

Expected Results

Something like - 640 x 480, total time: 3.208 sec. FPS: 311.7

Relevant Code

I have received the expected output in the past. However I'm suddenly getting this error. I don't think this is an X forwarding error since other applications like xclock and xeyes seem to be working just fine. Running glxinfo gives a similar error -

ubuntu@ip-172-31-77-104:~$ glxinfo debug1: client_input_channel_open: ctype x11 rchan 3 win 65536 max 16384 debug1: client_request_x11: request from 172.31.77.104 35806 debug1: channel 1: new [x11] debug1: confirm x11 name of display: ip-172-31-77-104:10.0 X Error of failed request: BadValue (integer parameter out of range for operation) Major opcode of failed request: 149 (GLX) Minor opcode of failed request: 24 (X_GLXCreateNewContext) Value in failed request: 0x0 Serial number of failed request: 19 Current serial number in output stream: 20 debug1: channel 1: FORCE input drain

[anoopsonar30]

@erikwijmans

[erikwijmans]

How X11 forwarding works is quite strange and it seems like the OpenGL specs after OpenGL 2 didn't bother implementing it, so it may never work as we rely in features from these versions. If glxinfo isn't working, there is definitely nothing we can do to fix that on our end.

[anoopsonar30]

I see. That's unfortunate. I guess I'll try using VNC and see if that works.

[aclegg3]

Seems like limitations were identified and the issue can be closed.