X2Go Bug report logs - #218
x2gobroker: Hostname is used instead of FQDN

Full log

🔗 View this message in rfc822 format

MIME-Version: 1.0
X-Mailer: MIME-tools 5.502 (Entity 5.502)
X-Loop: owner@bugs.x2go.org
From: owner@bugs.x2go.org (X2Go Bug Tracking System)
Subject: Bug#218 closed by Mike Gabriel <mike.gabriel@das-netzwerkteam.de>
 (X2Go issue (in src:x2gobroker) has been marked as closed)
Message-ID: <handler.218.c.137064017110140.notifdone@bugs.x2go.org>
References: <20130607212219.6BBE15DB2C@ymir>
X-X2go-PR-Keywords: confirmed pending
X-X2go-PR-Message: they-closed 218
X-X2go-PR-Package: x2gobroker
X-X2go-PR-Source: x2gobroker
Date: Fri, 07 Jun 2013 21:32:56 +0000
Content-Type: multipart/mixed; boundary="----------=_1370640776-19907-0"

[Message part 1 (text/plain, inline)]

This is an automatic notification regarding your Bug report
which was filed against the x2gobroker package:

#218: x2gobroker: Hostname is used instead of FQDN

It has been closed by Mike Gabriel <mike.gabriel@das-netzwerkteam.de>.

Their explanation is attached below along with your original report.
If this explanation is unsatisfactory and you have not received a
better one in a separate message then please contact Mike Gabriel <mike.gabriel@das-netzwerkteam.de> by
replying to this email.


-- 
X2Go Bug Tracking System
Contact owner@bugs.x2go.org with problems

[Message part 2 (message/rfc822, inline)]

From: Mike Gabriel <mike.gabriel@das-netzwerkteam.de>

To: 218-submitter@bugs.x2go.org

Cc: control@bugs.x2go.org, 218@bugs.x2go.org

Subject: X2Go issue (in src:x2gobroker) has been marked as closed

Date: Fri, 7 Jun 2013 23:22:19 +0200 (CEST)

close #218
thanks

Hello,

we are very hopeful that X2Go issue #218 reported by you
has been resolved in the new release (0.0.2.3) of the
X2Go source project »src:x2gobroker«.

You can view the complete changelog entry of src:x2gobroker (0.0.2.3)
below, and you can use the following link to view all the code changes
between this and the last release of src:x2gobroker.

    http://code.x2go.org/gitweb?p=x2gobroker.git;a=commitdiff;h=5a969b79741be3d85dc82738361dfda4fc10c75d;hp=6a16a5739fc702c12d3cc8738837a8a29cae8c12

If you feel that the issue has not been resolved satisfyingly, feel
free to reopen this bug report or submit a follow-up report with
further observations described based on the new released version
of src:x2gobroker.

Thanks a lot for contributing to X2Go!!!

light+love
X2Go Git Admin (on behalf of the sender of this mail)

---
X2Go Component: src:x2gobroker
Version: 0.0.2.3
Status: RELEASE
Date: Fri, 07 Jun 2013 23:21:29 +0200
Fixes: 152 218
Changes: 
 x2gobroker (0.0.2.3) RELEASED; urgency=low
 .
   * New upstream version (0.0.2.3):
     - inifile broker: Allow explicit specification combinations of
       »<hostname> (<address>)« in host= session profile field. (Fixes: #218).
     - Add rootless=false to example session profiles for all Desktop sessions in
       x2gobroker-sessionprofiles.conf.
     - Handle the rootless property automatically for know-by-name desktop
       sessions.
     - Make enable-plain-output, enable-uccs-output functional.
     - Add agent-quer-mode »NONE«. Disable X2Go Broker Agent calls completely.
     - Add status={S,R} to session profile list items when returned through X2Go
       Session Broker. (Fixes: #152). Handle taking over of running sessions and
       resuming sessions more reliably. Provide mechanism to suspend/terminate
       sessions through X2Go Server's (>= 4.0.1.0) x2gocleansessions daemon.

[Message part 3 (message/rfc822, inline)]

From: Anders Bruun Olsen <abo@dsl.dk>

To: submit@bugs.x2go.org

Subject: x2gobroker: Hostname is used instead of FQDN

Date: Wed, 22 May 2013 15:30:29 +0200

[Message part 4 (text/plain, inline)]

Package: x2gobroker
Version: 0.0.2.2

I am setting up a loadbalanced cluster of x2go servers with a broker in
front. There are thinclients on the LAN accessing the broker/cluster and
there will be users logging on from outside. Users on the LAN are served
term1.example.lan and term2.example.lan, whereas users from outside get
term1.example.com and term2.example.com. So far everything has worked fine,
but now I have started testing outside access, which does not work.
x2gobroker (with autologin) tells x2goclient to access term1 or term2 - it
leaves out the rest of the domain name. This works fine on the LAN, because
the machines there have example.lan set as their searchdomain, but machines
from outside can't resolve "term1" to "term1.example.com" and need to be
given the FQDN. Please note that the FQDNs is specified in the
sessionprofiles, but x2goclient still tries to resolve the short version of
the name.

-- 
Anders Bruun Olsen
It-ansvarlig
Det Danske Sprog- og Litteraturselskab
(Society for Danish Language and Literature)

[Message part 5 (text/html, inline)]

Send a report that this bug log contains spam.