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

Message #10 received at 362@bugs.x2go.org (full text, mbox, reply):

Received: (at 362) by bugs.x2go.org; 6 Jun 2014 17:15:44 +0000
From newsgroups.mail2@stefanbaur.de  Fri Jun  6 19:15:43 2014
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 <newsgroups.mail2@stefanbaur.de>
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

Send a report that this bug log contains spam.

X2Go Developers <owner@bugs.x2go.org>. Last modified: Thu Nov 21 16:43:51 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.