Bug 2050350 - x2goversion is not producing the correct output
Summary: x2goversion is not producing the correct output
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: x2goserver
Version: 35
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Orion Poplawski
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-03 18:15 UTC by John Radley
Modified: 2022-03-17 10:44 UTC (History)
2 users (show)

Fixed In Version: x2goserver-4.1.0.3-17.el8 x2goserver-4.1.0.3-17.fc34 x2goserver-4.1.0.3-17.fc35
Doc Type: ---
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-02-13 00:39:41 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)

Description John Radley 2022-02-03 18:15:15 UTC
Description of problem:

On Fedora Workstation and SilverBlue 35, a Remmina client cannot connect to X2goServer as the utility x2goversion is outputting incomplete data.

Version-Release number of selected component (if applicable):
Fedora Workstation and SilverBlue 35
x2goserver: 4.1.0.3

How reproducible:

Steps to Reproduce:
1.Using Fedora Workstation 35, install x2goserver and associated packages
Ensure that SSHD is working. 

Using Remmina, with the X2go plugin, which you can install using the Snap version, attempt to make a connection and you'll be met with a dialog stating that pyhoca-cli has stopped unexpectedly.

(Note: That with X2go's own Client, a connection is made satisfactorily, but with SELINUX AVC errors!)

2.You can also reproduce with pyhoca-cli as well.
Install this on your Fedora Workstation 35 and issue a request to localhost.
pyhoca-cli -d --libdebug -u john --password secret --list-desktops --server 127.0.0.1
The output incorrectly states the server is not installed.


Actual results:
pyhoca-cli[2660] (x2gocontrolsession-pylib) DEBUG: server-side X2Go components and their versions are: {'': '4.1.0.3'}
pyhoca-cli: error: the remote server does not have the X2Go Server software installed
<NOTICE the incomplete JSON>

<This is the cause>
$x2goversion

: 3.2.0.0
: 4.1.0.3
: 4.1.0.3
: 3.2.0.0
: 4.1.0.3
: 4.1.0.3
: 4.1.0.3
: 3.5.99.26
: 4.1.0.3

Expected results:

pyhoca-cli[3335] (x2gocontrolsession-pylib) DEBUG: server-side X2Go components and their versions are: {'x2gomatebindings': '0.0.1.6', 'x2goserver': '4.1.0.3', 'x2goserver-common': '4.1.0.3', 'x2goserver-extensions': '4.1.0.3', 'x2goserver-fmbindings': '4.1.0.3', 'x2goserver-printing': '4.1.0.3', 'x2goserver-x2goagent': '3.5.99.26', 'x2goserver-xsession': '4.1.0.3'}
pyhoca-cli[3335] (PyHocaCLI) NOTICE: authentication has been successful

X2Go desktops available for sharing
===================================
Host: 192.168.14.20 - [192.168.14.20]:22
Username: john

<NOTICE the correct JSON>

x2godesktopsharing: 3.2.0.0
x2gomatebindings: 0.0.1.6
x2goserver: 4.1.0.3
x2goserver-common: 4.1.0.3
x2goserver-desktopsharing: 4.1.0.3
x2goserver-extensions: 4.1.0.3
x2goserver-fmbindings: 4.1.0.3
x2goserver-printing: 4.1.0.3
x2goserver-x2goagent: 3.5.99.23
x2goserver-xsession: 4.1.0.3


Additional info:

/usr/bin/x2goversion
The cause is LINE 45
X2GO_COMPONENT="$(echo "$(basename ${compfile})" | cut -d '.' -f '2')"
For Fedora 35, this should be
X2GO_COMPONENT="$(echo "$(basename ${compfile})" | cut -d '.' -f '4')"

On Fedora you can make a quick edit.
But I'm defeated on Silverblue!
Fortunately Xrdp works!


I'll be amazed if this ever gets fixed.
X2go having not issued any Fedora versions since 30, and the fix is needed in Fedora not Ubuntu.
OR, I'll cross post to Remmina to see if they can work round this issue in their client code.

Comment 1 Fedora Update System 2022-02-04 03:05:38 UTC
FEDORA-2022-5e73dd3d2e has been submitted as an update to Fedora 35. https://bodhi.fedoraproject.org/updates/FEDORA-2022-5e73dd3d2e

Comment 2 Fedora Update System 2022-02-04 03:05:39 UTC
FEDORA-2022-35ba0a92c9 has been submitted as an update to Fedora 34. https://bodhi.fedoraproject.org/updates/FEDORA-2022-35ba0a92c9

Comment 3 Fedora Update System 2022-02-04 03:05:39 UTC
FEDORA-EPEL-2022-fbfc5b5ced has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-fbfc5b5ced

Comment 4 Fedora Update System 2022-02-05 00:33:30 UTC
FEDORA-EPEL-2022-fbfc5b5ced has been pushed to the Fedora EPEL 8 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2022-fbfc5b5ced

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 5 Fedora Update System 2022-02-05 01:31:18 UTC
FEDORA-2022-35ba0a92c9 has been pushed to the Fedora 34 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-35ba0a92c9`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-35ba0a92c9

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2022-02-05 02:11:40 UTC
FEDORA-2022-5e73dd3d2e has been pushed to the Fedora 35 testing repository.
Soon you'll be able to install the update with the following command:
`sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2022-5e73dd3d2e`
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2022-5e73dd3d2e

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 7 Fedora Update System 2022-02-13 00:39:41 UTC
FEDORA-EPEL-2022-fbfc5b5ced has been pushed to the Fedora EPEL 8 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 8 Fedora Update System 2022-02-13 01:06:11 UTC
FEDORA-2022-35ba0a92c9 has been pushed to the Fedora 34 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 9 Fedora Update System 2022-02-13 01:14:37 UTC
FEDORA-2022-5e73dd3d2e has been pushed to the Fedora 35 stable repository.
If problem still persists, please make note of it in this bug report.

Comment 10 David Gardner 2022-03-17 10:44:29 UTC
This also affects the EPEL 7 release of x2goserver in package x2goserver-4.1.0.3-9.el7.x86_64.

Is EPEL 7 still supported and so should get this fix as well?


Note You need to log in before you can comment on or make changes to this bug.