From unknown Fri Mar 29 13:06:32 2024 X-Loop: owner@bugs.x2go.org Subject: Bug#215: Fwd: [X2Go-Dev] Google Chrome and chromium-browser both crash when their advanced settings menu is accessed (Windows X2GoClient) Reply-To: Stefan Baur , 215@bugs.x2go.org Resent-From: Stefan Baur Resent-To: x2go-dev@lists.berlios.de Resent-CC: X2Go Developers X-Loop: owner@bugs.x2go.org Resent-Date: Tue, 21 May 2013 10:18:02 +0000 Resent-Message-ID: Resent-Sender: owner@bugs.x2go.org X-X2Go-PR-Message: report 215 X-X2Go-PR-Package: x2goclient X-X2Go-PR-Keywords: Received: via spool by submit@bugs.x2go.org id=B.136913094731706 (code B); Tue, 21 May 2013 10:18:02 +0000 Received: (at submit) by bugs.x2go.org; 21 May 2013 10:09:07 +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=0.0 required=5.0 tests=RCVD_IN_DNSWL_NONE, SPF_HELO_PASS,URIBL_BLOCKED autolearn=ham version=3.3.2 X-Greylist: delayed 451 seconds by postgrey-1.34 at ymir; Tue, 21 May 2013 12:09:07 CEST Received: from moutng.kundenserver.de (moutng.kundenserver.de [212.227.17.9]) by ymir (Postfix) with ESMTP id 1393E5DB13 for ; Tue, 21 May 2013 12:09:07 +0200 (CEST) Received: from [192.168.0.3] (dslb-188-105-142-114.pools.arcor-ip.net [188.105.142.114]) by mrelayeu.kundenserver.de (node=mrbap4) with ESMTP (Nemesis) id 0LeM29-1U8kc21KUn-00q9KA; Tue, 21 May 2013 11:56:35 +0200 Message-ID: <519B44EC.3030507@stefanbaur.de> Date: Tue, 21 May 2013 11:57:00 +0200 From: Stefan Baur User-Agent: Mozilla/5.0 (Windows NT 6.1; rv:17.0) Gecko/20130509 Thunderbird/17.0.6 MIME-Version: 1.0 To: submit@bugs.x2go.org References: <5194C92C.8010004@stefanbaur.de> In-Reply-To: <5194C92C.8010004@stefanbaur.de> X-Forwarded-Message-Id: <5194C92C.8010004@stefanbaur.de> Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 8bit X-Provags-ID: V02:K0:rvUj1ogoY9boaxmpNtQH8UbxMn+k5Bhejttomj+A9wA 4WgjMhrE9SXZuUZwvIKojRI0r5zbQPQlpwpU68gHm7IGvsZXEG AAazkd70t8kjfOgNfkh+DBeolI3zJ/vAP/8bg/8TfTxd1Mc/0b J3yyFO3vul77PuDZZXC9cN6qnDi9Ry/5/3OYCoonehiJKoFkNX 2IF8h5ekuRmV5V3mv/dMHqag2Ypf1xJPF37Hh0hcwiwHEFsi0E zvEXInlJPspy019Xyzcrhf1++kuyMIz2YN04KzPWF3IHwejHPd lSapK4LmB/sVCCxA+Vx9wx00MJXDkWgMF4nH8wjrITWRMrMhEZ 276yUzP3mIlHrpSvdtEG22TzolsGY1ts4yj5Vkkwc Package: x2goclient Version: 4.0.0.3 Severity: important -------- Original-Nachricht -------- Betreff: [X2Go-Dev] Google Chrome and chromium-browser both crash when their advanced settings menu is accessed (Windows X2GoClient) Datum: Thu, 16 May 2013 13:55:24 +0200 Von: Stefan Baur Antwort an: x2go-dev@lists.berlios.de An: x2go-dev@lists.berlios.de Hi, this is basically a repeat of Message-ID: <4FB3F9DA.1020602@stefanbaur.de>, as the problem still hasn't been fixed. I'm not copying it to the bugtracker directly as I am not sure whether it is a client- or server-side issue, or both. @DEVs: Please advise how it should be tagged, or forward and tag it yourself. What's new is that I've now also tried it on Debian Wheezy with the following packages installed on the server: dpkg -l | grep x2go ii cups-x2go 3.0.0.4-0~x2go1+wheezy~main~62~build1 all Virtual X2Go printer for CUPS ii x2go-keyring 2012.07.23+wheezy~main~17~build1 all GnuPG keys of all X2Go developers and the X2Go archive ii x2goagent 2:3.5.0.20-0+wheezy~main~405~build1 all X2Go agent ii x2goserver 4.0.0.1-0~x2go1+wheezy~main~648~build1 i386 X2Go server daemon scripts ii x2goserver-extensions 4.0.0.1-0~x2go1+wheezy~main~648~build1 all X2Go server daemon scripts (extensions) ii x2goserver-printing 4.0.0.1-0~x2go1+wheezy~main~648~build1 all X2Go server daemon scripts (printing) dpkg -l | grep nx ii libnx-x11 2:3.5.0.20-0+wheezy~main~405~build1 i386 nx-X11 ii nxagent 2:3.5.0.20-0+wheezy~main~405~build1 i386 NX agent On the client side, I am now using X2GoClient V. 4.0.0.3 on Windows 7 (32-bit, German) Note: The problem is *independent* of the compression *settings* (it occurs with WAN/nopack as well), but it does *not* occur when bypassing X2Go and running an unaccelerated, regular X session via SSH - with the X Server "stolen" from the X2GoClient package. Also, it doesn't matter which version of the X2GoClient you use, both the interim client and the new one show this behavior in their 4.0.0.3 versions. What happens: Whenever you try to access the advanced settings/proxy settings in chromium-browser or Google Chrome, vcxsrv.exe crashes. The following problem details are given: Problemsignatur: Problemereignisname: APPCRASH Anwendungsname: vcxsrv.exe Anwendungsversion: 0.0.0.0 Anwendungszeitstempel: 4f852997 Fehlermodulname: vcxsrv.exe Fehlermodulversion: 0.0.0.0 Fehlermodulzeitstempel: 4f852997 Ausnahmecode: c0000005 Ausnahmeoffset: 00160860 Betriebsystemversion: 6.1.7601.2.1.0.768.3 Gebietsschema-ID: 1031 Zusatzinformation 1: 0a9e Zusatzinformation 2: 0a9e372d3b4ad19135b953a78882e789 Zusatzinformation 3: 0a9e Zusatzinformation 4: 0a9e372d3b4ad19135b953a78882e789 Lesen Sie unsere Datenschutzbestimmungen online: http://go.microsoft.com/fwlink/?linkid=104288&clcid=0x0407 Wenn die Onlinedatenschutzbestimmungen nicht verfügbar sind, lesen Sie unsere Datenschutzbestimmungen offline: C:\windows\system32\de-DE\erofflps.txt It would be really cool if you see to getting this fixed soon, some of my users really want to use Chrome these days. Kind Regards, Stefan _______________________________________________ X2Go-Dev mailing list X2Go-Dev@lists.berlios.de https://lists.berlios.de/mailman/listinfo/x2go-dev