-
-
Notifications
You must be signed in to change notification settings - Fork 1.7k
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
GFX: graphic glitches when a monitor is more than 4096 pixels wide or high #3083
Comments
@jsorg71 Does librfxcodec encoder support more than 4096 pixels per screen/encoder? |
Oh no, the history only had 64x64 64x64 tiles so that is 4096x4096 pixels. I don't think it's a codec limitation, just an implementation limit. We can improve that. |
@jsorg71 Could extend librfxcoec to support screens larger than 4096x4096 pixcels? |
Is this limit set by the various |
I don't have a 4K monitor to test but I created neutrinolabs/librfxcodec#65 to possibly fix this. |
I was able to edit an rdp file to get a single monitor > 4K and it seems to work ok. |
@jsorg71 please see the repro steps above; we can just pass |
thanks @rowlap I am able to test now. I also went back to devel branch to make sure I can repro the issue(which I should have done first) and I can so I think it's fixed. |
Merged neutrinolabs/librfxcodec#65. |
I will close this after updaitng submodule. |
xrdp version
0.10.0-beta.3
Detailed xrdp version, build options
Operating system & version
FreeBSD 14 but actually not OS specific
Installation method
dnf / apt / zypper / pkg / etc
Which backend do you use?
xorgxrdp 0.10.1
What desktop environment do you use?
Xfce but any
Environment xrdp running on
any
What's your client?
Win 11 mstsc.exe
Area(s) with issue?
Graphic glitches
Steps to reproduce
Start an xrdp session at least one monitor has more than 4096 pixels wide or high.
We can start an RDP session larger than the physical monitor if specifying width/height via command line options.
mstsc /w:4160 /h:2160 /v:xrdp-server.example.com
to specify screen✔️ Expected Behavior
Works fine as well if the width or height is less than or equal to 4096 pixels.
❌ Actual Behavior
No response
Anything else?
This issue is similar to #2063 but there's no protocol error. #2063 happens if the total screen width is more than 8192. However, this issue happens when one of the monitors has a width of more than 4096.
Screenshot:
The text was updated successfully, but these errors were encountered: