From antoine.tran@thales-services.fr Fri Oct 9 10:39:49 2020 Received: (at submit) by bugs.x2go.org; 9 Oct 2020 08:39:51 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on ymir.das-netzwerkteam.de X-Spam-Level: X-Spam-Status: No, score=0.3 required=3.0 tests=BAYES_40,HTML_MESSAGE, KHOP_HELO_FCRDNS,SPF_HELO_NONE,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.2 Received: from smtp.thales-services.fr (mx.thales-services.fr [37.35.5.91]) by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 186FF5DAE9 for ; Fri, 9 Oct 2020 10:39:48 +0200 (CEST) Received: from [10.254.131.37] (94-88-190-213.static.intermediasud.com [213.190.88.94]) (Authenticated sender: antoine.tran@thales-services.fr) by smtp.thales-services.fr (Postfix) with ESMTPSA id F0690BD5B4 for ; Fri, 9 Oct 2020 10:39:17 +0200 (CEST) From: Antoine Tran Subject: Recent Firefox 68 and chromium crash in X2go To: "submit@bugs.x2go.org" Message-ID: Date: Fri, 9 Oct 2020 10:39:15 +0200 User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:60.0) Gecko/20100101 Thunderbird/60.9.1 MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="------------E9FAAFED51B006F41D48DCDA" Content-Language: en-US X-Bm-Milter-Handled: 13859c35-bb26-4a9b-af70-45c11bcf932b X-Bm-Transport-Timestamp: 1602232758136 This is a multi-part message in MIME format. --------------E9FAAFED51B006F41D48DCDA Content-Type: text/plain; charset=utf-8; format=flowed Content-Transfer-Encoding: 8bit Package: x2goserver Version:x2goserver-4.1.0.3-3.el7.x86_64.rpm Tag: firefox chromium glx Dear all, We use in our project X2go from Windows 10 with x2goclient latest 4.1.2.2 and that connects to docker image containing CentOs 7.8, x2goserver latest 4.1.0.3. We used Firefox 60.9.0 and it works quite well if we disable the hardware acceleration via about:config pref("browser.tabs.remote.autostart", false); pref("browser.tabs.remote.autostart.2", false); But we upgraded to Firefox 68 with package from CentOs. I also tried Firefox 68 ESR and 78 ESR directly from firefox website. All of that crashed after some time, with symptoms like "Gah. Your tab just crashed." and some "ipc_channel_posix.cc, line 358" in console. Or sometime it just disappear. It happens when we resize the windows  of Firefox or after browsing a few seconds. I also tried disabling hardware acceleration and setting number of process for tab management CSP to 1. What is the relationship between X2go and this error? If I launch chromium, it is a bit more stable but right at the beginning, it complains the minimal version for glx required is 1.3, while we have 1.2 in x2go environment. And it crashes too after a few browsing. I have a big suspicion Firefox behave badly for the same reason. I know x2go provides a workaround: https://wiki.x2go.org/doku.php/wiki:development:glx-xlib-workaround . Which I haven't time to test yet. My questions: 1. Does anyone reproduce the same error? It is not normal to have two recent browser that crashes in an updated OS. 2. Is-there an already built RPM containing the glx lib, so that we just do yum install something to have glx set to 1.4? I did not find one. Antoine --------------E9FAAFED51B006F41D48DCDA Content-Type: text/html; charset=utf-8 Content-Transfer-Encoding: 8bit 
Package: x2goserver
Version: x2goserver-4.1.0.3-3.el7.x86_64.rpm
Tag: firefox chromium glx

Dear all,

We use in our project X2go from Windows 10 with x2goclient latest 4.1.2.2 and that connects to docker image containing CentOs 7.8, x2goserver latest 4.1.0.3. We used Firefox 60.9.0 and it works quite well if we disable the hardware acceleration via about:config

pref("browser.tabs.remote.autostart", false);
pref("browser.tabs.remote.autostart.2", false);

But we upgraded to Firefox 68 with package from CentOs. I also tried Firefox 68 ESR and 78 ESR directly from firefox website. All of that crashed after some time, with symptoms like "Gah. Your tab just crashed." and some "ipc_channel_posix.cc, line 358" in console. Or sometime it just disappear. It happens when we resize the windows  of Firefox or after browsing a few seconds.

I also tried disabling hardware acceleration and setting number of process for tab management CSP to 1.

What is the relationship between X2go and this error? If I launch chromium, it is a bit more stable but right at the beginning, it complains the minimal version for glx required is 1.3, while we have 1.2 in x2go environment. And it crashes too after a few browsing.

I have a big suspicion Firefox behave badly for the same reason. I know x2go provides a workaround: https://wiki.x2go.org/doku.php/wiki:development:glx-xlib-workaround . Which I haven't time to test yet.

My questions:

  1. Does anyone reproduce the same error? It is not normal to have two recent browser that crashes in an updated OS.
  2. Is-there an already built RPM containing the glx lib, so that we just do yum install something to have glx set to 1.4? I did not find one.

Antoine

--------------E9FAAFED51B006F41D48DCDA--