Please read this before reporting a bug:
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
https://wiki.archlinux.org/title/Bug_reporting_guidelines
Do NOT report bugs when a package is just outdated, or it is in the AUR. Use the 'flag out of date' link on the package page, or the Mailing List.
REPEAT: Do NOT report bugs for outdated packages!
FS#69797 - [freerdp] 2.3.0 causing display issues in Remmina
Attached to Project:
Arch Linux
Opened by D (snowstorm) - Friday, 26 February 2021, 16:14 GMT
Last edited by David Runge (dvzrv) - Wednesday, 05 May 2021, 10:11 GMT
Opened by D (snowstorm) - Friday, 26 February 2021, 16:14 GMT
Last edited by David Runge (dvzrv) - Wednesday, 05 May 2021, 10:11 GMT
|
DetailsDescription:
After updating to FreeRDP 2.3.0, I am no longer able to use Remmina to access Windows (Server, 10) computers as the display becomes white or otherwise unreadable. Additional info: * FreeRDP version 2.3.0-1 * Reported upstream here: https://github.com/FreeRDP/FreeRDP/issues/6840 * Upstream suggests it's a packaging issue, and to compile with -DWITH_VAAPI=OFF Steps to reproduce: * On an up to date (as of 2020-Feb-26) Arch installation with GNOME, open Remmina * Connect to a device running Windows Server or Windows 10 * Watch the remote display window and note the artifacts and white screen Workaround: Reverting to 2.2.0-2 resolved the issue |
This task depends upon
Closed by David Runge (dvzrv)
Wednesday, 05 May 2021, 10:11 GMT
Reason for closing: Not a bug
Additional comments about closing: Unrelated upstream issue
Wednesday, 05 May 2021, 10:11 GMT
Reason for closing: Not a bug
Additional comments about closing: Unrelated upstream issue
It would be nice if you could comment on your hardware in the upstream ticket.
Meanwhile I will rebuild the package and remove the feature. Looking at https://bugs.archlinux.org/task/67219 I see that more people are experiencing issues with it.
So the removal of VAAPI broke it for me.