ISIS q-applications no longer work with Xming (ISIS versions 8.2.0 and higher)

[mtbland]

ISIS version(s) affected: x.y.z
8.3.0 and 8.2.0 (ISIS 8.1.0 is fine)

Description
This may be particular to my system, but something changed in ISIS versions > 8.1.0 that are preventing me from using q-applications (qview, qmos, qnet, etc) with Xming. I work from a Windows machine and use Putty to access a linux system with ISIS installed. This has worked just fine (and still does) for all versions of ISIS <= 8.1.0. However, if I'm running 8.2.0 or 8.3.0 the application fails immediately and I get the following error:

qt.qpa.gl: QXcbConnection: Failed to initialize GLX
qt.qpa.xcb: QXcbConnection: XCB error: 1 (BadRequest), sequence: 165, resource id: 90, major code: 130 (Unknown), minor code: 47
qt.qpa.xcb: QXcbConnection: XCB error: 170 (Unknown), sequence: 180, resource id: 90, major code: 146 (Unknown), minor code: 20
The X11 connection broke (error 1). Did the X11 server die?

As soon as I switch back to 8.1.0 everything works fine, so this appears to be a change in the latest versions. The fix may be a change to Xming or Putty's X forwarding but that's not obvious to me.

How to reproduce
This may be specific to my setup but...

1. From a Window machine SSH onto a remote Linux system that has ISIS installed. Make sure Xming is running
2. Conda activate ISIS8.3.0
3. qview foo.cub (should fail)
4. Conda deactivate. Then conda activate ISIS8.1.0 and qview foo.cub to confirm it works.

Possible Solution
I can do most things I need using ISIS8.1.0, but I'll want updates in the latest version of ISIS soon.

Additional context

[mtbland]

In case it's helpful - I am running Putty 0.81 and Xming 6.9.0.31.

[amystamile-usgs]

I looked into this today and here’s what I’ve found so far. I used PuTTY to connect to a Linux EC2 instance with an Anaconda installation (version 8.3.0) and was able to successfully run qview. (Versions: Xming 7.7.0, PuTTY 0.83). This suggests that the issue may be related to our preinstalled conda environments on our virtual machines. However, I’m currently encountering different errors with Xming, preventing me from verifying this further. I’ll keep you posted.