X2Go Bug report logs - #362
Chromium/chrome still crash VcXsrv when used with X2Go (VcXsrv doesn't crash with Chromium/Chrome and plain X via SSH)

version graph

Package: x2goclient; Maintainer for x2goclient is X2Go Developers <x2go-dev@lists.x2go.org>; Source for x2goclient is src:x2goclient.

Reported by: Stefan Baur <newsgroups.mail2@stefanbaur.de>

Date: Wed, 11 Dec 2013 14:33:02 UTC

Severity: wishlist

Found in version 4.0.1.2

Full log


🔗 View this message in rfc822 format

X-Loop: owner@bugs.x2go.org
Subject: Bug#362: Chromium/chrome still crash VcXsrv when used with X2Go (VcXsrv doesn't crash with Chromium/Chrome and plain X via SSH)
Reply-To: Stefan Baur <newsgroups.mail2@stefanbaur.de>, 362@bugs.x2go.org
Resent-From: Stefan Baur <newsgroups.mail2@stefanbaur.de>
Resent-To: x2go-dev@lists.berlios.de
Resent-CC: X2Go Developers <x2go-dev@lists.berlios.de>
X-Loop: owner@bugs.x2go.org
Resent-Date: Wed, 11 Dec 2013 14:33:02 +0000
Resent-Message-ID: <handler.362.B.138677193210308@bugs.x2go.org>
Resent-Sender: owner@bugs.x2go.org
X-X2Go-PR-Message: report 362
X-X2Go-PR-Package: x2goclient
X-X2Go-PR-Keywords: 
Received: via spool by submit@bugs.x2go.org id=B.138677193210308
          (code B); Wed, 11 Dec 2013 14:33:02 +0000
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 <submit@bugs.x2go.org>; 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 <newsgroups.mail2@stefanbaur.de>
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
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.

Send a report that this bug log contains spam.


X2Go Developers <owner@bugs.x2go.org>. Last modified: Thu Nov 21 16:05:03 2024; Machine Name: ymir.das-netzwerkteam.de

X2Go Bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.