hello nick The term "prompt" refers to the screen displayed when SSH connecting to the target Linux system through Guacamole. In version 1.5.5, Korean input displays correctly as shown below, ---------------------------------------------------------------------------------------- Last Login: Thu Nov 7 17:20:25 2024 trom 192.168.0.65 ［centos@test-cent ~］ㅈㅈㄹㄷㅋㄹㅈㄷ <= Visible when typing in Korean -bash: ㅈㅈㄹㄷㅋㄹㅈㄷ: command not found [centos@test-cent ~]$ ---------------------------------------------------------------------------------------- but in the latest patch branch, there is no output for Korean input. ---------------------------------------------------------------------------------------- Last Login: Thu Nov 7 17:25:25 2024 trom 192.168.0.65 ［centos@test-cent ~］ <= When typing in Korean, it just appears as a blank space. -bash: ㅈㅈㄹㄷㅋㄹㅈㄷ: command not found. <= but command working [centos@test-cent ~]$ ---------------------------------------------------------------------------------------- Since this issue occurs when changing the guacd server version, it does not appear to be related to cache or style sheet issues.
On Sat, 9 Nov 2024 at 05:28, Nick Couchman <vn...@apache.org> wrote: > On Thu, Nov 7, 2024 at 4:18 AM YG HONG <epikhigh...@gmail.com> wrote: > >> Hello, >> In the guacamole-server patch, staging/1.6.0 branch, when typing Korean >> as shown in the image, nothing appears in the prompt. >> [image: Inline-image-2024-11-07 17.08.19.683.png] >> In the 1.5.5 tag, it works correctly as shown below. >> >> I analyzed the WebSocket messages for the working and non-working >> versions, and there is no blob message as shown below. >> >> # patch branch >> 3.key,8.16789812,1.1; >> 3.key,8.16789812,1.0; >> >> 4.rect,1.1,3.416,2.36,2.16,2.36;5.cfill,2.14,1.1,1.0,1.0,1.0,3.255;4.rect,1.1,3.448,2.36,2.16,2.36;5.cfill,2.14,1.1,3.153,3.153,3.153,3.255;4.sync,7.6858340,1.0; >> >> # 1.5.5 tag >> >> 3.key,8.16789812,1.1; >> 3.key,8.16789812,1.0; >> >> 4.rect,1.1,3.704,3.180,2.16,2.36;5.cfill,2.14,1.1,3.153,3.153,3.153,3.255;3.img,1.1,2.14,1.1,9.image/png,3.672,3.180;4.blob,1.1,204.iVBORw0KGgoAAAANSUhEUgAAABoAAAAkBAMAAABlFDcgAAAAKlBMVEUAAAAICAhubm5NTU0MDAyZmZlsbGyXl5eSkpJeXl5iYmIFBQVDQ0MrKyt6/vhGAAAAKElEQVQYlWNgGFxASBmZ5xo2RHjhHRDQCeaFQkEUiLfnDBScZRhEAAC+sReHXViHSwAAAABJRU5ErkJggg==;3.end,1.1;4.sync,7.6550327; >> >> 3.key,8.16789812,1.1; >> 3.key,8.16789812,1.0; >> >> 4.rect,1.1,3.736,3.180,2.16,2.36;5.cfill,2.14,1.1,3.153,3.153,3.153,3.255;3.img,1.1,2.14,1.1,9.image/png,3.704,3.180;4.blob,1.1,204.iVBORw0KGgoAAAANSUhEUgAAABoAAAAkBAMAAABlFDcgAAAAKlBMVEUAAAAICAhubm5NTU0MDAyZmZlsbGyXl5eSkpJeXl5iYmIFBQVDQ0MrKyt6/vhGAAAAKElEQVQYlWNgGFxASBmZ5xo2RHjhHRDQCeaFQkEUiLfnDBScZRhEAAC+sReHXViHSwAAAABJRU5ErkJggg==;3.end,1.1;4.sync,7.6550625; >> >> Is it a bug or a configuration mistake? >> > > I'm unable to see the images that you provided, so I'm not sure which > prompt you're talking about? To my knowledge, there's no reason why a > version upgrade would impact the ability to enter any particular language. > One thing to verify that you're doing when moving between versions is to > clear the browser cache to make sure all of the JavaScript and Stylesheet > information is being updated. > > -Nick >
