From newsgroups.mail2@stefanbaur.de Wed Dec 11 15:25:32 2013 Received: (at submit) by bugs.x2go.org; 11 Dec 2013 14:25:32 +0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on ymir.das-netzwerkteam.de X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,SPF_HELO_PASS autolearn=ham version=3.3.2 Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.10]) by ymir (Postfix) with ESMTP id 30ABA5DB17 for ; Wed, 11 Dec 2013 15:25:32 +0100 (CET) Received: from [192.168.0.3] (dslb-188-105-138-093.pools.arcor-ip.net [188.105.138.93]) by mrelayeu.kundenserver.de (node=mreu3) with ESMTP (Nemesis) id 0M4P8q-1VcVap3HRc-00yZwF; Wed, 11 Dec 2013 15:25:31 +0100 Message-ID: <52A875E6.7070603@stefanbaur.de> Date: Wed, 11 Dec 2013 15:25:42 +0100 From: Stefan Baur User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:24.0) Gecko/20100101 Thunderbird/24.2.0 MIME-Version: 1.0 To: submit@bugs.x2go.org Subject: Chromium/chrome still crash VcXsrv when used with X2Go (VcXsrv doesn't crash with Chromium/Chrome and plain X via SSH) Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:69kzZ3f9ptAlpcvqqJcuT1tb5NcF2Sbfi1TPcMH6Lg1 bIBnc/5HICyKvV/gxY+ItsULmFbwmy6U101l56+LnNgZP9HT32 5gp2eh70YyTZ5GeWXiNrECZDKB7HH8LmqAk/KQxu8jNb7MI47f xgr9eZU1Bo8WRPkf/h81SxqhtiOysy2i06Q+Vy+kvcTy4fTXar 1Gf8pRKMH3ZH0eYraqQTwwqs5PrTWtNJpq/81Bn2lYqDxw7o/8 blummPKy29fXKJzKWq4eSD65haHQ3eFYZuje6n7qXy0aiidloM 4KJ2TbjpKNCqfzAY8TIy5Ing8hNLwvHVzK2NyKczr1LGH2EPRh TO/jCO1mK2O0uiPpYR+2w/zhJQqW/nqxxi3Ip36UQ Package: x2goclient Severity: wishlist Version: 4.0.1.2 Even with the newer Xserver that is included in x2goclient-4.0.1.2-pre02-setup, Chromium and Chrome still crash at random intervals. To be exact, they're not crashing themselves, they're crashing the Xserver. Pausing and resuming a session lets you continue where you stopped, yet, this is an instability that users won't put up with since they quit Windows 98/Millennium for good. It's only when X2Go is involved that these crashes occur - if you export the display with ssh (from PuTTY) instead of using x2goclient.exe, Chromium and Chrome behave well. This is not a showstopper for me (my customers are using Iceweasel so far), but it is an issue where I had hoped to see some improvement with the new Xserver. From newsgroups.mail2@stefanbaur.de Fri Jun 6 19:15:43 2014 Received: (at 362) by bugs.x2go.org; 6 Jun 2014 17:15:44 +0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on ymir.das-netzwerkteam.de X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00 autolearn=ham version=3.3.2 X-Greylist: delayed 301 seconds by postgrey-1.34 at ymir.das-netzwertkeam.de; Fri, 06 Jun 2014 19:15:43 CEST Received: from mout.kundenserver.de (mout.kundenserver.de [212.227.17.13]) by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 668315DB24 for <362@bugs.x2go.org>; Fri, 6 Jun 2014 19:15:43 +0200 (CEST) Received: from [192.168.0.3] (dslb-088-067-156-041.pools.arcor-ip.net [88.67.156.41]) by mrelayeu.kundenserver.de (node=mreue104) with ESMTP (Nemesis) id 0MD8ge-1X0c6o08js-00Ga2M; Fri, 06 Jun 2014 19:10:42 +0200 Message-ID: <5391F632.1040503@stefanbaur.de> Date: Fri, 06 Jun 2014 19:11:14 +0200 From: Stefan Baur User-Agent: Mozilla/5.0 (Windows NT 6.1; WOW64; rv:24.0) Gecko/20100101 Thunderbird/24.5.0 MIME-Version: 1.0 To: x2go-dev@lists.x2go.org, 362@bugs.x2go.org Subject: Re: [X2Go-Dev] Bug#362: Chromium/chrome still crash VcXsrv when used with X2Go (VcXsrv doesn't crash with Chromium/Chrome and plain X via SSH) References: <52A875E6.7070603@stefanbaur.de> In-Reply-To: <52A875E6.7070603@stefanbaur.de> X-Enigmail-Version: 1.6 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Provags-ID: V02:K0:nweTTmPsvNFTONsv0KEGGSED8gQ9b0qgts3G15Audsf JmZvvgDoDusECaLVzJQpl4VA2rFK0NLDrEZyGCW9eDD7p7sneE dpbgyBqEnjOR6ZoQ9MYgKD6bP3zCKF3F2HSLoC9IHQ+BbicwsF hmZNd+6OdlHS97qqexxpE6BpVYa+HCqrnGIBm4LFLCvVH/DMKq 9FTZUwZiaX/V91WCCmMc8TI7uNJIpdKqIgC2TDFWsr5AL+R4HI TeIGIWHDx/0yXANAVy4JGVwPzHchqwqz8lGm8KmAAhX3frUBqo I4Q1M7ma8wUg15xFyBjmx64SXcTsxWvAAnXcni+5U37keu1ipm P247ruSsZ/M5JZZ5tU3uBowH4dwt/wIFbfK+xA+Gf Am 11.12.2013 15:25, schrieb Stefan Baur: > Package: x2goclient > Severity: wishlist > Version: 4.0.1.2 > > Even with the newer Xserver that is included in > x2goclient-4.0.1.2-pre02-setup, Chromium and Chrome still crash at > random intervals. > To be exact, they're not crashing themselves, they're crashing the Xserver. > Pausing and resuming a session lets you continue where you stopped, yet, > this is an instability that users won't put up with since they quit > Windows 98/Millennium for good. > It's only when X2Go is involved that these crashes occur - if you export > the display with ssh (from PuTTY) instead of using x2goclient.exe, > Chromium and Chrome behave well. I'm not seeing this bug any more with Chromium 35.0.1916.114-1~deb7u2 on Debian Wheezy with X2Go Server 4.0.1.15-0x2go1+git20140403.847+wheezy.main.1 and X2Go Client 4.0.2.0+build2 on Windows 7. Of course, this may just be because I haven't tested it long enough. It would be cool if someone else could try to run it in this particular combination, and try Chrome as well, so we can get a second opinion on whether to close the bug or not. -Stefan