-
-
Notifications
You must be signed in to change notification settings - Fork 79
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Latest FreeRDP Dependency Behavior and Documentation #147
Comments
What version of freerdp should i run for the workaround? |
I haven't tested all versions but |
Hi @Ahmedsaed Do you mind sharing the .flatpak file for 2.6.1? |
I haven't used any Flatpaks in my setup. I also believe that freerdp is not available through FlatHub. As I have mentioned above. You can workaround this issue by using distrobox and export the program to the host.
|
Thank you. I installed CentOS on distrobox and used wget http://mirror.centos.org/centos/7/os/x86_64/Packages/freerdp-2.1.1-2.el7.x86_64.rpm Then sudo yum install freerdp-2.1.1-2.el7.x86_64.rpm It is now working! Thank you 😄 |
Describe the bug
The behavior of the FreeRDP dependency differs from user expectations due to the discrepancy between the version packaged in certain Linux distributions and the version marked as latest by the developer. Updating the documentation or providing a warning within the application may help guide users encountering this issue.
Steps to Reproduce:
/app
argument.Expected Behavior:
FreeRDP should properly handle the
/app
argument and perform the intended operation without issues.Actual Behavior:
In the latest couple of released versions of FreeRDP (e.g., version 3.4.0), using the
/app
argument causes FreeRDP to print the help message and exit instead of executing the desired operation.System information:
Impact:
This issue affects users relying on FreeRDP distro packages, particularly those needing to use the /app argument.
Workaround:
distrobox-export
to export the binary to host system. Ex:distrobox-export --bin /usr/bin/xfreerdp ~/.local/bin
The text was updated successfully, but these errors were encountered: