X2Go Bug report logs - #1593
X2Go Windows Client fails to connect to hostname resolving to both IPv4 and IPv6

Package: x2goclient; Maintainer for x2goclient is X2Go Developers <x2go-dev@lists.x2go.org>; Source for x2goclient is src:x2goclient.

Reported by: me@jcn50.com

Date: Thu, 24 Nov 2022 16:20:01 UTC

Severity: normal

Merged with 1592, 1594

Reply or subscribe to this bug.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to x2go-dev@lists.x2go.org, owner@bugs.x2go.org:
Bug#1593; Package x2go windows client. (Thu, 24 Nov 2022 16:20:01 GMT) (full text, mbox, link).

Acknowledgement sent to me@jcn50.com:
New Bug report received and forwarded. Copy sent to owner@bugs.x2go.org. (Thu, 24 Nov 2022 16:20:02 GMT) (full text, mbox, link).

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

Package: X2Go Windows Client
Version: 4.1.2.2

I have a hostname that has both 1x IPv4 address (A records) and 1x IPv6 
address (AAAA records). The client fails to connect (connection timeout 
error) if I use the hostname. However if I enter the IPv4 or the IPv6 
instead of the hostname: it works!

Proposed solution: it should try to connect/resolve to the IPv6 first, 
then the IPv4.

Regards,
Chris.

PS: I have re-sent this message because I was not a member of the 
mailing list, and I cancelled the previously sent one.

Information forwarded to x2go-dev@lists.x2go.org, owner@bugs.x2go.org:
Bug#1593; Package x2go windows client. (Thu, 24 Nov 2022 16:40:02 GMT) (full text, mbox, link).

Acknowledgement sent to me@jcn50.com:
Extra info received and forwarded to list. Copy sent to owner@bugs.x2go.org. (Thu, 24 Nov 2022 16:40:03 GMT) (full text, mbox, link).

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

Please see Bug #1594 for the exact message (if you can delete this 
thread that will be even better).
Sorry I am not very familiar with all the lists~.

Merged 1592 1593 Request was from x2go@jugra.de to control@bugs.x2go.org. (Wed, 14 Dec 2022 20:50:02 GMT) (full text, mbox, link).

Merged 1592 1593 1594 Request was from x2go@jugra.de to control@bugs.x2go.org. (Wed, 14 Dec 2022 20:50:02 GMT) (full text, mbox, link).

Bug reassigned from package 'x2go windows client' to 'x2goclient'. Request was from x2go@jugra.de to control@bugs.x2go.org. (Wed, 14 Dec 2022 20:50:03 GMT) (full text, mbox, link).

No longer marked as found in versions 4.1.2.2. Request was from x2go@jugra.de to control@bugs.x2go.org. (Wed, 14 Dec 2022 20:50:03 GMT) (full text, mbox, link).

Information forwarded to x2go-dev@lists.x2go.org, X2Go Developers <x2go-dev@lists.x2go.org>:
Bug#1593; Package x2goclient. (Sun, 01 Nov 2026 05:50:16 GMT) (full text, mbox, link).

Acknowledgement sent to info@blavatfamilyfoundation.com:
Extra info received and forwarded to list. Copy sent to X2Go Developers <x2go-dev@lists.x2go.org>. (Sun, 01 Nov 2026 05:50:17 GMT) (full text, mbox, link).

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

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

Send a report that this bug log contains spam.

X2Go Developers <owner@bugs.x2go.org>. Last modified: Mon Nov 9 05:30:40 2026; Machine Name: ymir.das-netzwerkteam.de

X2Go Bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

X2Go Bug report logs - #1593 X2Go Windows Client fails to connect to hostname resolving to both IPv4 and IPv6

X2Go Bug report logs - #1593
X2Go Windows Client fails to connect to hostname resolving to both IPv4 and IPv6