From unknown Tue May 05 13:11:31 2026 X-Loop: owner@bugs.x2go.org Subject: Bug#1167: [X2Go-Dev] Bug#1167: More details Reply-To: "Petronic, Mark" , 1167@bugs.x2go.org Resent-From: "Petronic, Mark" Resent-To: x2go-dev@lists.x2go.org Resent-CC: X2Go Developers X-Loop: owner@bugs.x2go.org Resent-Date: Sat, 20 May 2017 20:55:02 +0000 Resent-Message-ID: Resent-Sender: owner@bugs.x2go.org X-X2Go-PR-Message: followup 1167 X-X2Go-PR-Package: x2goclient X-X2Go-PR-Keywords: Received: via spool by 1167-submit@bugs.x2go.org id=B1167.14953135855596 (code B ref 1167); Sat, 20 May 2017 20:55:02 +0000 Received: (at 1167) by bugs.x2go.org; 20 May 2017 20:53:05 +0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on ymir.das-netzwerkteam.de X-Spam-Level: X-Spam-Status: No, score=-1.9 required=3.0 tests=BAYES_00,DKIM_SIGNED, DKIM_VALID,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,RCVD_IN_MSPIKE_H3, RCVD_IN_MSPIKE_WL,SPF_HELO_PASS,URIBL_BLOCKED autolearn=ham autolearn_force=no version=3.4.1 Received: from localhost (localhost [127.0.0.1]) by ymir.das-netzwerkteam.de (Postfix) with ESMTP id 7FA725DAD3 for <1167@bugs.x2go.org>; Sat, 20 May 2017 22:53:03 +0200 (CEST) X-Virus-Scanned: Debian amavisd-new at ymir.das-netzwerkteam.de Received: from ymir.das-netzwerkteam.de ([127.0.0.1]) by localhost (ymir.das-netzwerkteam.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id wZn_RwXVTKB9 for <1167@bugs.x2go.org>; Sat, 20 May 2017 22:52:55 +0200 (CEST) X-Greylist: delayed 106491 seconds by postgrey-1.35 at ymir.das-netzwerkteam.de; Sat, 20 May 2017 22:52:55 CEST Received: from NAM02-SN1-obe.outbound.protection.outlook.com (mail-sn1nam02on0116.outbound.protection.outlook.com [104.47.36.116]) by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 3E2045DAD2 for <1167@bugs.x2go.org>; Sat, 20 May 2017 22:52:54 +0200 (CEST) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=echostar.onmicrosoft.com; s=selector1-hughes-com; h=From:Date:Subject:Message-ID:Content-Type:MIME-Version; bh=glls9Pc0MFUYBkOLZAMAfxVHxdvvdnRkB+AElFVaN2w=; b=GMqa6qLsHxP9QhD5o08aT98tTwN7I2xTS9IItX+ma88M+TvRk/WUUJd+XUrFuaVO7Iqwvjyf+bSRSWh4MFHMQHFh6rcB9t7Fm8yx3AYF0rmFRvkWdknLdXI35UD1bRC4L6w539mjVUiAexYoIN5BOzLe1NzuVC7ntiPZ3F7Edas= Received: from BN6PR1101MB2260.namprd11.prod.outlook.com (10.174.113.135) by BN6PR1101MB2260.namprd11.prod.outlook.com (10.174.113.135) with Microsoft SMTP Server (version=TLS1_2, cipher=TLS_ECDHE_RSA_WITH_AES_128_CBC_SHA256_P256) id 15.1.1101.14; Sat, 20 May 2017 20:52:51 +0000 Received: from BN6PR1101MB2260.namprd11.prod.outlook.com ([10.174.113.135]) by BN6PR1101MB2260.namprd11.prod.outlook.com ([10.174.113.135]) with mapi id 15.01.1101.017; Sat, 20 May 2017 20:52:51 +0000 From: "Petronic, Mark" To: "1167@bugs.x2go.org" <1167@bugs.x2go.org>, "uli42@gmx.de" Thread-Topic: [X2Go-Dev] Bug#1167: More details Thread-Index: AdLQq/746d+rgjgnSPirbME61j5F+AApNAuAABY6bCo= Date: Sat, 20 May 2017 20:52:51 +0000 Message-ID: References: , In-Reply-To: Accept-Language: en-US Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: authentication-results: bugs.x2go.org; dkim=none (message not signed) header.d=none;bugs.x2go.org; dmarc=none action=none header.from=hughes.com; x-originating-ip: [25.167.1.132] x-ms-publictraffictype: Email x-microsoft-exchange-diagnostics: 1;BN6PR1101MB2260;7:+FPYoArWlSpQtxazwNY2Rrx/7H6c0WP2GRd81PXKLApt4BHazf9zSuPiUS3kVacGrzCwfL0POMpAytI+1qv3UQhC1nkLHLua7iuENl2oHydwp/Io/tGkxWhTD8rUpy5zLTyEQJzN7juVSVvvtxO4BVRu9rwq9TqIrl3a+Lo8DIJ73uNmAWSOCO0vHNMrSt5LHe1rII6wTl2CYVzpaBlcbjCiUS6UREsponD4cpVycU1Q7t8L72Vb1sOpoaTlizXVzyOQ+VTtYe8Z1r9y5mWvqJ1lkj+U8haE/Voe1sM15Wqq6JLgpDrBcXnm/oCbHsEN3quC2ms9II0MXNIwejklRg== x-ms-traffictypediagnostic: BN6PR1101MB2260: x-ms-office365-filtering-correlation-id: 1b0efed0-310c-47ba-5eee-08d49fc22e5c x-microsoft-antispam: UriScan:;BCL:0;PCL:0;RULEID:(22001)(2017030254075)(201703131423075)(201703031133081);SRVR:BN6PR1101MB2260; x-microsoft-antispam-prvs: x-exchange-antispam-report-test: UriScan:(158342451672863); x-exchange-antispam-report-cfa-test: BCL:0;PCL:0;RULEID:(6040450)(601004)(2401047)(5005006)(8121501046)(3002001)(10201501046)(93006095)(93001095)(6041248)(20161123555025)(20161123560025)(20161123558100)(20161123564025)(201703131423075)(201702281528075)(201703061421075)(201703061406153)(20161123562025)(6072148);SRVR:BN6PR1101MB2260;BCL:0;PCL:0;RULEID:;SRVR:BN6PR1101MB2260; x-forefront-prvs: 03137AC81E x-forefront-antispam-report: SFV:NSPM;SFS:(10019020)(6009001)(39450400003)(39860400002)(39840400002)(39400400002)(39410400002)(39850400002)(377454003)(24454002)(9686003)(2906002)(33656002)(7736002)(478600001)(54896002)(38730400002)(122556002)(2900100001)(76176999)(50986999)(54356999)(8676002)(77096006)(3660700001)(8936002)(66066001)(6506006)(6436002)(81166006)(5660300001)(74316002)(8666007)(6116002)(102836003)(3846002)(3280700002)(2501003)(99286003)(55016002)(189998001)(53936002)(25786009)(72206003)(86362001)(53546009)(2950100002)(7696004)(229853002);DIR:OUT;SFP:1102;SCL:1;SRVR:BN6PR1101MB2260;H:BN6PR1101MB2260.namprd11.prod.outlook.com;FPR:;SPF:None;MLV:sfv;LANG:en; spamdiagnosticoutput: 1:99 spamdiagnosticmetadata: NSPM Content-Type: multipart/alternative; boundary="_000_BN6PR1101MB2260E070C64962EC353C56F592FA0BN6PR1101MB2260_" MIME-Version: 1.0 X-OriginatorOrg: hughes.com X-MS-Exchange-CrossTenant-originalarrivaltime: 20 May 2017 20:52:51.3547 (UTC) X-MS-Exchange-CrossTenant-fromentityheader: Hosted X-MS-Exchange-CrossTenant-id: 0e1f3187-4610-4ce2-bad1-b92f4ba36ab3 X-MS-Exchange-Transport-CrossTenantHeadersStamped: BN6PR1101MB2260 --_000_BN6PR1101MB2260E070C64962EC353C56F592FA0BN6PR1101MB2260_ Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Yes, I noticed the same thing when I was googling around for clues. We are = running the latest version of vmware-tools and I believe, when we moved to = vmware version 6 this started happening around that time but we were not ab= le to correlate it then and a number of updates have been applied since the= n. I had the VM admins build me an image with the older version of the tool= s last week but I still experienced the crash. IMO, given the popup error r= efers to a crash related to a pure virtual function, it would seem that thi= s very well might be breakage in some vmware DLL API that is not acting in = a backwards compatible manner. Just a guess. Also, this only occurs when I= configure the vcxsrv in rootless mode. I might try your suggestion by tryi= ng to run the image on a player. I already know it happens on different hos= ts as we have a number of hosts supporting the VDI instances and we float a= round day to day. I've confirmed it happens on different hosts in that way.= Thanks for you suggestions and input! Mark ________________________________ From: Ulrich Sibiller Sent: Saturday, May 20, 2017 6:06:55 AM To: Petronic, Mark; 1167@bugs.x2go.org Subject: Re: [X2Go-Dev] Bug#1167: More details On Fri, May 19, 2017 at 4:44 PM, Petronic, Mark wrote: > vm3dum.dll Googling for vm3dum.dll reveals a lot of crashes related to that vmware dll. So I suppose it has nothing to do with x2go but with your vmware. Some post suggest upgrading vmware-tools so please try that and see if the crashes go away. Also you could try moving the virtual machine to another host (or maybe a vmware player or workstation) and check if the crashes persist. Uli --_000_BN6PR1101MB2260E070C64962EC353C56F592FA0BN6PR1101MB2260_ Content-Type: text/html; charset="us-ascii" Content-Transfer-Encoding: quoted-printable

Yes, I noticed the same thing when I was googling around for clues. We a= re running the latest version of vmware-tools and I believe, when we moved = to vmware version 6 this started happening around that time but we were not= able to correlate it then and a number of updates have been applied since then. I had the VM admins build = me an image with the older version of the tools last week but I still experienced the crash. IMO, given the pop= up error refers to a crash related to a pure virtual function, it= would seem that this very well might be breakage in some vmware DLL API th= at is not acting in a backwards compatible manner.  Just a guess. Also, this only occurs when I configure the vcxsrv in = rootless mode. I might try your suggestion by trying to run the image on a = player. I already know it happens on different hosts as we have a number of= hosts supporting the VDI instances and we float around day to day. I've confirmed it happens on different hosts i= n that way. Thanks for you suggestions and input!


Mark

From: Ulrich Sibiller <= ;ulrich.sibiller@gmail.com>
Sent: Saturday, May 20, 2017 6:06:55 AM
To: Petronic, Mark; 1167@bugs.x2go.org
Subject: Re: [X2Go-Dev] Bug#1167: More details
 
On Fri, May 19, 2017 at 4:44 PM, Petronic, Mark <Mark.Petronic@hughes.com> wrote:
> vm3dum.dll

Googling for vm3dum.dll reveals a lot of crashes related to that
vmware dll. So I suppose it has nothing to do with x2go but with your
vmware. Some post suggest upgrading vmware-tools so please try that
and see if the crashes go away.

Also you could try moving the virtual machine to another host (or
maybe a vmware player or workstation) and check if the crashes
persist.

Uli

 --_000_BN6PR1101MB2260E070C64962EC353C56F592FA0BN6PR1101MB2260_--