-
-
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
xrdp-0.10.1 After VNC connection is successful, it cannot be used(RealVNC on windows) #3288
Comments
Thanks for using the form @baryaor. It's not only important for us - it's important for other users who may have similar issues.
|
@baryaor - did you get any further with this? |
After deleting the 'error=1' in the "resize_server_to_client_layout" function in the "vnc. c" , it works normal, but I'm not sure if there are any other effects |
I tested xrdp-0.9. x and did not find this issue |
Thanks. What seems to be happening is the VNC server is being asked to resize, even though it doesn't support that feature. I've submitted a request to RealVNC for a download of 6.2.1 so I can try to reproduce this (it's not a free product). In the meantime, can you try adding this line to the
that might be sufficient. Please let me know either way. |
I've had a reply from RealVNC also. They ask if you are in a position to try with the latest version 7.13.0. Is this something you can do? |
xrdp version
0.10.1
Detailed xrdp version, build options
Operating system & version
Debian 3.2.57
Installation method
git clone & make install
Which backend do you use?
No response
What desktop environment do you use?
No response
Environment xrdp running on
No response
What's your client?
windws 11
Area(s) with issue?
Other
Steps to reproduce
When vncserver is on windows, its version is RealVNC 6.2.1,I can successfully connect to VNC,but i cannot be operated and the mouse cannot click
✔️ Expected Behavior
No response
❌ Actual Behavior
xrdp-0.10.1 After VNC connection is successful, it cannot be used(RealVNC on windows)
logs:
[2024-10-24T17:15:54.651+0800] [INFO ] [xrdp_mm_setup_mod1(xrdp_mm.c:356)] loaded module 'libvnc.so' ok, interface size 4832, version 4
[2024-10-24T17:15:54.880+0800] [INFO ] [vnc_clip_open_clip_channel(vnc_clip.c:1082)] VNC: Clipboard supports ISO-8859-1 text only
[2024-10-24T17:15:54.884+0800] [INFO ] [find_preferred_text_format(vnc_clip.c:287)] VNC: Format id CF_UNICODETEXT available from RDP client
[2024-10-24T17:15:54.884+0800] [INFO ] [find_preferred_text_format(vnc_clip.c:287)] VNC: Format id CF_<0x0000c3f6> available from RDP client
[2024-10-24T17:15:54.885+0800] [INFO ] [find_preferred_text_format(vnc_clip.c:287)] VNC: Format id CF_LOCALE available from RDP client
[2024-10-24T17:15:54.885+0800] [INFO ] [find_preferred_text_format(vnc_clip.c:287)] VNC: Format id CF_TEXT available from RDP client
[2024-10-24T17:15:54.885+0800] [INFO ] [find_preferred_text_format(vnc_clip.c:287)] VNC: Format id CF_OEMTEXT available from RDP client
[2024-10-24T17:15:54.886+0800] [INFO ] [handle_cb_format_list(vnc_clip.c:338)] Asking RDP client for clip data format=CF_UNICODETEXT
[2024-10-24T17:15:55.829+0800] [INFO ] [advance_resize_state_machine(xrdp_mm.c:1191)] advance_resize_state_machine: Processing resize to: 1280 x 768. Advancing state from WMRZ_ENCODER_DELETE to WMRZ_ENCODER_DELETE. Previous state took 0 MS.
[2024-10-24T17:15:55.835+0800] [INFO ] [advance_resize_state_machine(xrdp_mm.c:1191)] advance_resize_state_machine: Processing resize to: 1280 x 768. Advancing state from WMRZ_ENCODER_DELETE to WMRZ_SERVER_MONITOR_RESIZE. Previous state took 0 MS.
[2024-10-24T17:15:55.840+0800] [ERROR] [resize_server_to_client_layout(vnc.c:409)] resize_server_to_client_layout: Asked to resize server, but not possible
[2024-10-24T17:15:55.845+0800] [INFO ] [process_display_control_monitor_layout_data(xrdp_mm.c:1751)] process_display_control_monitor_layout_data: mod_server_monitor_resize failed 1
[2024-10-24T17:15:55.849+0800] [INFO ] [advance_resize_state_machine(xrdp_mm.c:1191)] advance_resize_state_machine: Processing resize to: 1280 x 768. Advancing state from WMRZ_SERVER_MONITOR_RESIZE to WMRZ_ERROR. Previous state took 1 MS.
[2024-10-24T17:15:55.122+0800] [INFO ] [dynamic_monitor_process_queue(xrdp_mm.c:1977)] dynamic_monitor_process_queue: Clearing failed request to resize to: (w: 1280 x h: 768)
[2024-10-24T17:16:12.637+0800] [INFO ] [find_preferred_text_format(vnc_clip.c:287)] VNC: Format id CF_UNICODETEXT available from RDP client
[2024-10-24T17:16:12.637+0800] [INFO ] [find_preferred_text_format(vnc_clip.c:287)] VNC: Format id CF_TEXT available from RDP client
[2024-10-24T17:16:12.638+0800] [INFO ] [find_preferred_text_format(vnc_clip.c:287)] VNC: Format id CF_LOCALE available from RDP client
[2024-10-24T17:16:12.638+0800] [INFO ] [find_preferred_text_format(vnc_clip.c:287)] VNC: Format id CF_OEMTEXT available from RDP client
[2024-10-24T17:16:12.639+0800] [INFO ] [handle_cb_format_list(vnc_clip.c:338)] Asking RDP client for clip data format=CF_UNICODETEX
remarks:
1.When vncserver is on Linux, its version is TigerVNC 1.8.0, and it works normally on xrdp 0.10.1
2.When vncserver is on windows, its version is RealVNC 6.2.1,I can successfully connect to VNC,but i cannot be operated and the mouse cannot click,The error log is as shown above
Anything else?
No response
The text was updated successfully, but these errors were encountered: