Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Description of problem:

Xfreerdp version check returns non-zero exit status

Version-Release number of selected component (if applicable):
RHEL
FreeRDP

How reproducible:

Try to check installed version of xfreerdp on the system

Steps to Reproduce:
1. Run 'xfreerdp --version ;echo $?'
2. Check the exit status of the command
3.

Actual results:

This returns non-zero value

This is FreeRDP version 2.1.1 (n/a)
45

Expected results:

It should return a zero exit value

Additional info:

Hmm, yes, xfreerdp actually returns -2003 in this case, however, UNIX limits this to 255, so the result is 45 (= 256 - 2003 % 256). Given the fact that exit codes overflow the range, it may also happen that some errors overflow to 0, which is also unexpected. The xfreerdp man page doesn't provide info about return codes, so this is not necessarily a bug. But there is a convention, that programs should return 0 in the case of success and non-zero otherwise, so it would be nice to honor it. However, I am not sure what would be the right fix here as the error codes are defined in winpr library, which makes me think that the same codes are returned from mstsc client. So I've opened an upstream issue for discussion.

[test@localhost ~]$ xfreerdp --version ;echo $?
This is FreeRDP version 2.2.0 (n/a)
0
[test@localhost ~]$ rpm -q freerdp
freerdp-2.2.0-2.el8.x86_64

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (freerdp bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2021:4186