From unknown Thu Mar 28 21:10:32 2024 X-Loop: owner@bugs.x2go.org Subject: Bug#1167: [X2Go-Dev] Bug#1167: More details Reply-To: uli42@gmx.de, 1167@bugs.x2go.org Resent-From: Ulrich Sibiller Resent-To: x2go-dev@lists.x2go.org Resent-CC: X2Go Developers X-Loop: owner@bugs.x2go.org Resent-Date: Sat, 20 May 2017 10:10:01 +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.149527484512403 (code B ref 1167); Sat, 20 May 2017 10:10:01 +0000 Received: (at 1167) by bugs.x2go.org; 20 May 2017 10:07:25 +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=2.4 required=3.0 tests=BAYES_50,DKIM_SIGNED, DKIM_VALID,DKIM_VALID_AU,FREEMAIL_FROM,FREEMAIL_REPLYTO, FREEMAIL_REPLYTO_END_DIGIT,RCVD_IN_MSPIKE_H3,RCVD_IN_MSPIKE_WL, RCVD_IN_SORBS_SPAM,URIBL_BLOCKED autolearn=no autolearn_force=no version=3.4.1 Received: from localhost (localhost [127.0.0.1]) by ymir.das-netzwerkteam.de (Postfix) with ESMTP id 47BCB5DAD3 for <1167@bugs.x2go.org>; Sat, 20 May 2017 12:07:24 +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 SC8NNvqdDS6G for <1167@bugs.x2go.org>; Sat, 20 May 2017 12:07:17 +0200 (CEST) Received: from mail-vk0-f52.google.com (mail-vk0-f52.google.com [209.85.213.52]) by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id F190E5DAD2 for <1167@bugs.x2go.org>; Sat, 20 May 2017 12:07:16 +0200 (CEST) Received: by mail-vk0-f52.google.com with SMTP id h16so22638370vkd.2 for <1167@bugs.x2go.org>; Sat, 20 May 2017 03:07:16 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:reply-to:in-reply-to:references:from:date:message-id :subject:to; bh=E3Xr9rbGDGxcvA3WKXOYi8vVlO5tGPgx1SRH7X/bhKk=; b=vfREKhWsLlsGl1qd/i05I+5BqL2DkiBCnfV2C9EunAMZ3QT/rPszTUMHRz3/dD4oxF M263d3wP0nQyiQw8yg3uYXNV/Q3xpvRv7IOZ3QpTQX2HC9TYdrt9L8DUyI7+Saknbqyi tqhadCit9bZWGkyajWU84m5mVS42jZJupARjoCF81qL0t3/8TlFdLcfI5sgOFWx5GO3w CTyOZagortGW8wuYdNxWJ7rl2UT7gsAHW/sspLPX/DtIqqN/N7fNFYGwpMcSzkhslcCy aVYtMn1X/OIExZhjF0vbF9W1z3QH1GRMA/x3ilEYjptT1lqiap1CKA0hjOCV9K8ilzf2 33hg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:reply-to:in-reply-to:references :from:date:message-id:subject:to; bh=E3Xr9rbGDGxcvA3WKXOYi8vVlO5tGPgx1SRH7X/bhKk=; b=Mt3SzR5AFvpxZV95/XBJY3NxouooNwbz/ro6Hqjq8M7NcuIuVM/Ondwvzwt6Qy/F4H tTvn9jg/9VrvtgbQfgkim65KGNhfQ5WO+NFPQKR1E9YDMsvEXNA+nKJlQBLQjrm/3wmf M+LAkRZqVLlxRxRBZATa7U21EVgxKk4x8pimgFnjLmfTAHmfT+3voz7dZLFngk8o0Pi4 btK6Sa33x5QF1rEjDD8aH3ErwNU4W1X8WcJJMcg6qRMSQ8xaLrlV1Rdbx99d4X/Sh8Rv U3+VqFSvM0NDoqaBn8UZ7bezXE7G8rbHgrKxlebG5uB2zukUHiixJ8ufeAXs1NfoJ7B4 tiFQ== X-Gm-Message-State: AODbwcBlehIlLnxn4Byx4sF79ZqWorY6SKnd0EEYAOQ1kvHnXrvRXCCi Fj+HE7hllq+wRcj9wRX90QNbW/nqEQ== X-Received: by 10.31.155.74 with SMTP id d71mr3626095vke.147.1495274835706; Sat, 20 May 2017 03:07:15 -0700 (PDT) MIME-Version: 1.0 Received: by 10.176.4.99 with HTTP; Sat, 20 May 2017 03:06:55 -0700 (PDT) In-Reply-To: References: From: Ulrich Sibiller Date: Sat, 20 May 2017 12:06:55 +0200 Message-ID: To: "Petronic, Mark" , 1167@bugs.x2go.org Content-Type: text/plain; charset="UTF-8" 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