You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
It seems like with the recent update to 2.3.1 on the F-Droid build, my connection to a Windows Server 2012 R2 machine is having a display issue. When Performance -> GFX is checked, I see a very washed out display of the screen. I can barely see objects in it. If I disable the GFX option, then it seems to work normally. If I try connecting to a Windows 10 machine with it enabled, I'll see white artifacts on the screen but most of it is still visible.
To Reproduce
Edit settings for a connection (in this case, Windows Server 2012?)
Enable the GFX performance option
Save and connect to machine
See error
Expected behavior
The desktop would be drawn normally.
Screenshots
You can just make out some objects on my desktop when I adjust the brightness and contrast.
Application details
FreeRDP version: 2.3.1
OS version connecting to (server side): Windows Server 2012 R2
If available the log output from a run with /log-level:trace 2>&1 | tee log.txt (see below)
Environment (please complete the following information):
Describe the bug
It seems like with the recent update to 2.3.1 on the F-Droid build, my connection to a Windows Server 2012 R2 machine is having a display issue. When Performance -> GFX is checked, I see a very washed out display of the screen. I can barely see objects in it. If I disable the GFX option, then it seems to work normally. If I try connecting to a Windows 10 machine with it enabled, I'll see white artifacts on the screen but most of it is still visible.
To Reproduce
Expected behavior
The desktop would be drawn normally.
Screenshots
You can just make out some objects on my desktop when I adjust the brightness and contrast.
Application details
/log-level:trace 2>&1 | tee log.txt
(see below)Environment (please complete the following information):
ADB:
The text was updated successfully, but these errors were encountered: