<html>
  <head>
    <meta content="text/html; charset=ISO-8859-1"
      http-equiv="Content-Type">
  </head>
  <body bgcolor="#FFFFFF" text="#000000">
    <div class="moz-cite-prefix">On 29/07/2013 08:42, Kjell Otto wrote:<br>
    </div>
    <blockquote
cite="mid:CAHeJaP+OMx+fT--LawVVp3R2T5eu4VL79oh0CZ_9HDnVd_dSSA@mail.gmail.com"
      type="cite">
      <div dir="ltr">Hi Roland,
        <div><br>
        </div>
        <div>sorry to let you down on this, I'm still busy doing other
          stuff all the time.</div>
      </div>
    </blockquote>
    <br>
    No problem! We all have to pay the bills somehow, right? :-)<br>
    <br>
    <blockquote
cite="mid:CAHeJaP+OMx+fT--LawVVp3R2T5eu4VL79oh0CZ_9HDnVd_dSSA@mail.gmail.com"
      type="cite">
      <div dir="ltr">
        <div>The error you're getting seems to be related to your
          X-Server installation.</div>
        <div>The KDE part of the agent starting is completely normal,
          it's just about setting your </div>
        <div>color depth AFAIK.</div>
        <div><br>
        </div>
        <div>
          <div>Sorry about messing arround with Master and Shadow
            stuff... What I ment was</div>
          <div>this: When you're starting a GNOME session. You can just
            close the window when</div>
          <div>you're leaving the desktop. Then just start the GNOME
            session again once you want</div>
          <div>to come back. And you'll see the old one is still running
            and resumable. </div>
          <div><br>
          </div>
          <div>There is another way to connect to an opened session, via
            the desktopsharing feature</div>
          <div>of x2go. But that seems unrelated...</div>
        </div>
        <div><br>
        </div>
        <div>It seems that you've messed up a part of your X or X
          configuration. This is acutally</div>
        <div>what stops your x2go client from really doing something:</div>
        <div><big style="font-family:arial,sans-serif"><font
              face="monospace"><br>
            </font></big></div>
        <div><big style="font-family:arial,sans-serif"><font
              face="monospace">check command message </font></big><br
            style="font-family:arial,sans-serif;font-size:13px">
          <br style="font-family:arial,sans-serif;font-size:13px">
          <big style="font-family:arial,sans-serif"><font
              face="monospace">X Error: BadWindow (invalid Window
              parameter) 3</font></big><br
            style="font-family:arial,sans-serif;font-size:13px">
          <big style="font-family:arial,sans-serif"><font
              face="monospace">  Major opcode: 20 (X_GetProperty)</font></big><br
            style="font-family:arial,sans-serif;font-size:13px">
          <big style="font-family:arial,sans-serif"><font
              face="monospace">  Resource id:  0x4004bbc</font></big><br
            style="font-family:arial,sans-serif;font-size:13px">
          <big style="font-family:arial,sans-serif"><font
              face="monospace">X Error: BadWindow (invalid Window
              parameter) 3</font></big><br
            style="font-family:arial,sans-serif;font-size:13px">
          <big style="font-family:arial,sans-serif"><font
              face="monospace">  Major opcode: 15 (X_QueryTree)</font></big><br
            style="font-family:arial,sans-serif;font-size:13px">
          <big style="font-family:arial,sans-serif"><font
              face="monospace">  Resource id:  0x4004bbc</font></big><br>
        </div>
        <div><br>
        </div>
        <div>Try to find the problem related to this. It seems that your
          problem is not about</div>
        <div>
          x2go...</div>
      </div>
    </blockquote>
    I consider this good news!  Let me see what I can do about this. 
    You're right, the Xserver setup was having trouble at some stage, so
    I'll go through that in detail to see what's wrong there.<br>
    <br>
    I have had a detailed analysis with Mike Gabriel over on IRC as
    well, and it also lead to x2go not being able to connect to
    screen:50 for some reason.<br>
    <br>
    regards<br>
    <br>
    Roland<br>
    <br>
  </body>
</html>