[X2Go-Dev] Firefox 45.0-2 and 46.0-2 on Archlinux crash when used with x2go

[Rett D. Walters]

Hello:

I reported this issue on the x2go-user list a couple of weeks ago and it 
was suggested that I report it here if I continue to have the issue.

Basically, I am running a VM on ESXi 5.1 with Archlinux installed and 
the following x2go packages (arch standard packages) as a server running 
xfce4.

extra/x2go-agent 3.5.0.32-2
extra/x2goserver 4.0.1.19-4
extra/nxagent 3.5.0.32-2

And I am running a client running archlinux using a KDE plasma 5 desktop 
and x2goclient using the latest x2goclient packages from the arch repo:

extra/x2goclient 4.0.5.1-2

After a little bit of mouse movement on the firefox window and a few 
second of usage, firefox will crash to the desktop - running from a 
terminal window reveals the following error:

[2257] ###!!! ABORT: Request 131.45: BadRequest (invalid request code or 
no such operation): file 
/build/firefox/src/firefox-46.0/toolkit/xre/nsX11ErrorHandler.cpp, line 157
[2257] ###!!! ABORT: Request 131.45: BadRequest (invalid request code or 
no such operation): file 
/build/firefox/src/firefox-46.0/toolkit/xre/nsX11ErrorHandler.cpp, line 157
Segmentation fault (core dumped)

I have tried the usual safe mode and new profile creation and it crashes 
no matter what I try.  Firefox will run properly on a VM console X 
session using the Vsphere client without issues on the same server. 
Mouse movement in the FIrefox window seems to cause the crash to happen 
faster.

I have tried a couple of other tests on another server this time a 
physical server running archlinux and the same packages as mentioned 
above with Openbox and the same thing happens.  Again FIrefox runs fine 
on the console of the server.

I have also tested twm and the same thing occurs, so it doesn't seem to 
be dependent on the desktop environment in use, only crashes when using 
x2go to deliver the application.

Also tried the published application mode of x2go, same thing happens 
albeit it takes a little longer to crash.

FIrefox 44 did not have this issue and ran fine on x2go.

Any ideas on how to fix this? I really enjoy x2go's functionality for a 
couple of years now, but this has become a serious usability problem.

Please let me know what other information or help I can provide to pin 
this down.

Thanks in advance,

Rett Walters