X2Go Bug report logs - #503
Can't start X Server, please check your installation

Full log

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

Received: (at 503) by bugs.x2go.org; 27 May 2014 13:43:06 +0000
From mikedep333@gmail.com  Tue May 27 15:43:05 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,FREEMAIL_FROM,
	T_DKIM_INVALID,URIBL_BLOCKED autolearn=ham version=3.3.2
Received: from mail-we0-f182.google.com (mail-we0-f182.google.com [74.125.82.182])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id 99C203D166
	for <503@bugs.x2go.org>; Tue, 27 May 2014 15:43:05 +0200 (CEST)
Received: by mail-we0-f182.google.com with SMTP id t60so9411467wes.41
        for <503@bugs.x2go.org>; Tue, 27 May 2014 06:43:05 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:in-reply-to:references:date:message-id:subject:from:to
         :cc:content-type;
        bh=rBBm1Ok9lLhYL7wrNPhlTGdfanXde8RCyuoKw1Xu2kc=;
        b=tOUoBmKNdkCmx6bDLsbovkpRGr4TT2kfR1vGk2WuF2P6AYqhuMzfs96x+HcyOzXi/3
         8KhUHNyiZ+pz/PzU9yuTG1brhg0llONW1o3MIrckxsvK4bCZhxWGJUvbDNzN3NAbX+9x
         zvy1iKGlhDwcKKJZovyClCjIOXgtWtcopBNW/dH0I78V57ZAThRWQyGQpIlCsXg31ZyG
         rp2lzsYQBIaqY4DMqZ79fzB4gvVKAZIK2ryC91iT8j2E1pH0yLrh1tf8pMQosVgXvpkJ
         WwEh2TsrD3/r32MsMf3GGADzAhYES5s0fxvCfnrg6WZ8kcRqImLpZRDHtKI/zmJr1cBQ
         lTPw==
MIME-Version: 1.0
X-Received: by 10.180.96.225 with SMTP id dv1mr38554973wib.37.1401198184985;
 Tue, 27 May 2014 06:43:04 -0700 (PDT)
Received: by 10.180.107.132 with HTTP; Tue, 27 May 2014 06:43:04 -0700 (PDT)
In-Reply-To: <53848F36.5080501@stefanbaur.de>
References: <5384864E.2080708@lostcantina.com>
	<53848F36.5080501@stefanbaur.de>
Date: Tue, 27 May 2014 09:43:04 -0400
Message-ID: <CAMKht8g_dodhhtBimTY_hYJrM_ux54Kf2kZ5cmiyzVaz9Q_SFg@mail.gmail.com>
Subject: Re: [X2Go-Dev] Bug#503: Bug#503: Can't start X Server, please check
 your installation
From: Michael DePaulo <mikedep333@gmail.com>
To: 503@bugs.x2go.org, postmaster <postmaster@lostcantina.com>
Cc: Stefan Baur <newsgroups.mail2@stefanbaur.de>
Content-Type: text/plain; charset=UTF-8

Hi, I am the Windows maintainer for X2Go Client.

1st of all, I am sorry you ran into this bug. It is on my to-fix list.

2nd, this is a duplicate of bug 109. I am still learning the debian
bug tracking system, I will mark this as a duplicate when I get home
from work.

On Tue, May 27, 2014 at 9:12 AM, Stefan Baur
<newsgroups.mail2@stefanbaur.de> wrote:
> Am 27.05.2014 14:34, schrieb postmaster:
>
>> so i try to desinstall and reinstall but, OMG, X2GO REMEMBER THE OLD
>> PARAMETERS.
>> (the baby seal with My session / root@123.45.67.89 / gnome / 800x600 /
>> enabled)
>
> That's not OMG, that's desired behavior.  Just imagine what would happen
> if uninstalling Microsoft Office would mean all your Word and Excel
> documents would get deleted as well.  Same here.  Uninstall purges the
> program files, but not the data.
>

As stefan mentioned, the settings are stored per-user. This is why we
do not delete them.

Deleting settings vs deleting session profiles may be another discussion.

>> so the desinstallation is not clean !
>
> To purge the data from the particular user profile, you either have to
> remove the registry keys under HKEY_CURRENT_USER\Software\Obviously
> Nice\x2goclient (in case of a standard x2goclient Windows installation),
> or delete the ".x2goclient" folder from the user's home directory (if
> you were using x2goclient in portable mode).
> This is something you have to do *per user*, so if you logged in as
> Administrator to (un)install x2goclient, you need to log off, and log
> back on again as the user you were running x2goclient under, *then* run
> regedit *as the user* and remove the above-specified tree.

As Stefan mentioned, you have to do this per user.

To avoid deleting your session profiles, just follow these per-user
instructions instead to fix this specific bug/setting. They assume you
are not in portable mode. They are mentioned in bug 109 now.

1. Open regedit (you do not need admin rights.)
2. Browse to the registry key HKEY_CURRENT_USER\Software\Obviously
Nice\x2goclient\settings
3.Then set "useintx" to "true"

> [...]
>
>> so i return to 3.99.2.2
>> goodbye 4.X
>> :-/
>
> Also, you were using an outdated 4.x release.  Please try 4.0.2.0
> instead of 4.0.1.3.
>
> -Stefan

The bug is still present in 4.0.2.0. However, we still advise
upgrading to 4.0.2.0, largely because of the vulnerabilities in VcXsrv
which have been patched.
http://wiki.x2go.org/doku.php/doc:release-notes-mswin:x2goclient-4.0.2.0

-Mike#2

Send a report that this bug log contains spam.