X2Go Bug report logs - #1524
X2go Windows client path bug

Received: (at 1524) by bugs.x2go.org; 16 Jul 2024 21:44:06 +0000
From celi@dieese.org.br  Tue Jul 16 23:44:05 2024
X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on
	ymir.das-netzwerkteam.de
X-Spam-Level: *
X-Spam-Status: No, score=1.8 required=3.0 tests=BAYES_50,DKIM_SIGNED,
	DKIM_VALID,DKIM_VALID_AU,FORGED_SPF_HELO,HTML_MESSAGE,MIME_HTML_ONLY,
	RCVD_IN_VALIDITY_RPBL_BLOCKED,RCVD_IN_VALIDITY_SAFE_BLOCKED,
	SPF_HELO_PASS,URIBL_BLOCKED autolearn=no autolearn_force=no
	version=3.4.4
Received: from pagliacci.dieese.org.br (serpina.dieese.org.br [201.28.107.202])
	by ymir.das-netzwerkteam.de (Postfix) with ESMTPS id E0CB85E140
	for <1524@bugs.x2go.org>; Tue, 16 Jul 2024 23:44:04 +0200 (CEST)
Received: from localhost (localhost.localdomain [127.0.0.1])
	by pagliacci.dieese.org.br (listas.dieese.org.br) with ESMTP id 5AC03121865
	for <1524@bugs.x2go.org>; Tue, 16 Jul 2024 18:44:02 -0300 (-03)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dieese.org.br;
	s=202102; t=1721166242;
	bh=FNiXOtRM99VVeh5U/IhFLB4TdEwIZRIH1BUcMLkm4jA=;
	h=Date:To:From:Subject:From;
	b=lLrEoyZRQ2aeEWudLV8FlqDikeC7nYHM/FL+/ZYBkDRgJMPkLBGPidkXcrmEiQiAi
	 8ZSXDJkKCS7vPMSLraJ27waastsCRFbYTvlIyQzGIPzqebxaHPJ20BZZXpD6q0nCA6
	 2RGCQsqTM6ficwB4YpJV8yzoGhP23/lfajLZbrNqKbsY57FpmtAi8D/2y/HoAWUHoR
	 Qw/+Y6OWhTyJ/33SeeBndAFcePG8odbLe2JedyXlChiNMfRzfSEUCrSAOFm3oV3Dvl
	 DdwVVJIvqjqCBkJUtYRQvJar6EIRSTnVvdb6UwQkArEE2L8JaXe5T+sfEw1nfi57zn
	 +yhQzD9ZRhBtA==
X-Virus-Scanned: Debian amavisd-new at dieese.org.br
Received: from pagliacci.dieese.org.br ([127.0.0.1])
	by localhost (mail1.dieese.org.br [127.0.0.1]) (amavisd-new, port 10024)
	with ESMTP id 6Vdw_dJyCkhU for <1524@bugs.x2go.org>;
	Tue, 16 Jul 2024 18:44:01 -0300 (-03)
Received: from [192.168.0.89] (unknown [189.62.45.142])
	by pagliacci.dieese.org.br (listas.dieese.org.br) with ESMTPSA id 9301F121861
	for <1524@bugs.x2go.org>; Tue, 16 Jul 2024 18:44:01 -0300 (-03)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/simple; d=dieese.org.br;
	s=202102; t=1721166241;
	bh=FNiXOtRM99VVeh5U/IhFLB4TdEwIZRIH1BUcMLkm4jA=;
	h=Date:To:From:Subject:From;
	b=LQC0xVWhC9iWFfPbeZrGQuk1oYnw1RZ7snIz2KVfb1FSwLTkgSqA/TUrIyigTzm5g
	 9ffGsl8tyOCOdjDWsyaXAc+DAKzEyY0M/OFSDNbDe/K0NhbAmovI89na5eKDhnQ5rm
	 I1AIbanmrtM3v36Dw7hD/MuN1RuERwT4NXp/eQnczxOZjyrV5yVtvJpkuCwIpQjRY6
	 a39jVWipugaSKKIxe8mJoQYIy+RMjPLekBO8/1BnxTYyIx6OTxkvjJu0CrQIq1svKo
	 rxqESlj7g5tXlZeuMe5CdMgRrzAUiy6k4gPjRnLSzrJtSXB7xEKdSs/lE8kBTfK3A8
	 510Ugaj4lnqYA==
Message-ID: <0ca8498d-f489-4158-8c3a-cfba3f1db26b@dieese.org.br>
Date: Tue, 16 Jul 2024 18:44:01 -0300
MIME-Version: 1.0
User-Agent: Mozilla Thunderbird
Content-Language: pt-BR
To: 1524@bugs.x2go.org
From: Celi <celi@dieese.org.br>
Subject: Is there a way to workaround this?
Content-Type: multipart/related;
 boundary="------------CzqZ8RlMEmrsJRzKdwILleSX"