omurozlu opened a new issue, #12095:
URL: https://github.com/apache/cloudstack/issues/12095

   ### problem
   
   When using CloudStack 4.22 noVNC console, clipboard text containing Turkish 
characters is not transmitted correctly to Windows virtual machines.
   
   "asdasdç"
   Inside the Windows VM it appears corrupted:
   "asdasd."
   
   The issue only occurs with noVNC → Windows clipboard operations.
   It does not occur on Linux VMs.
   Typing manually sometimes works, but clipboard “Send” is consistently broken.
   
   This suggests a missing or incorrect UTF-8 → Windows codepage conversion in 
the noVNC version included with the CloudStack 4.22 SystemVM.
   
   ### versions
   
   CloudStack version: 4.22.0
   System VM Template: systemvm64template 4.22 (fresh download)
   Hypervisor: VMware ESXi 8.x
   vCenter: 8.x
   Browsers tested: Chrome, Firefox (same result)
   Guest OS: Windows Server 2016 / 2019 / 2022 (all affected)
   
   ### The steps to reproduce the bug
   
   1.   Deploy a Windows VM in CloudStack 4.22
   2.   Open noVNC console → Clipboard
   3.   Paste the following UTF-8 text: "asdasdç"
   4.   Click Send Clipboard
   5.   Paste the text inside the Windows VM 
   
   Expected: Unicode characters should be transmitted correctly
   Actual: Turkish characters appear corrupted or replaced with “?”
   
   ### What to do about it?
   
        The noVNC version embedded in SystemVM may not properly handle UTF-8 
clipboard transmission for Windows guests.
        •       CloudStack may need:
        •       An updated noVNC version inside the SystemVM
        •       A fix to clipboard handling for non-ASCII characters
        •       Unicode normalization before sending text to the RFB server
   
   This issue appears similar to:
   https://github.com/apache/cloudstack/issues/7335
   
   Please investigate whether the current SystemVM noVNC build processes 
clipboard text incorrectly or lacks UTF-8 handling required for Windows VMs.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to