[BUG] Bug in IME Input Mode
Is there an existing issue for this?
- [x] I have searched the existing issues
Current Behavior
After entering a certain number of different Chinese characters, new characters cannot be inputted correctly. As shown in the image, after I have entered some characters, only previously entered characters can be inputted correctly when I try to enter new ones. Characters that have not appeared before are ignored and cannot be inputted.
I tested both the linuxserver/webtop:ubuntu-kde and linuxserver/webtop:ubuntu-xfce images and found that they both have this issue. However, I don't think it's a bug in Kasm, because I tested the kasmweb/core-ubuntu-jammy image and did not encounter the problem.
Expected Behavior
No response
Steps To Reproduce
1.Enable IME Input Mode 2.Use the Chinese input method to type some different characters 3.After entering a certain amount, notice that some new characters are being ignored
Environment
- OS:unraid 6.12.10
- How docker service was installed:
CPU architecture
x86-64
Docker creation
services:
webtop-dev:
image: linuxserver/webtop:ubuntu-xfce
container_name: webtop-dev
security_opt:
- seccomp:unconfined #optional
environment:
- TZ=Asia/Shanghai
- HOST_OS=Unraid
- HOST_HOSTNAME=Tower
- HOST_CONTAINERNAME=webtop-dev
- PUID=1000
- PGID=1000
- SUBFOLDER=/ #optional
- TITLE=Webtop-dev #optional
#- DOCKER_MODS=linuxserver/mods:universal-package-install
- INSTALL_PACKAGES=fonts-noto-cjk
- LC_ALL=zh_CN.UTF-8
- TITLE=dev-webtop
labels:
- net.unraid.docker.managed=dockerman
- net.unraid.docker.webui=https://192.168.2.2:3001
- net.unraid.docker.icon=https://cn.ubuntu.com/static/img/favicon.ico
volumes:
- /mnt/cache/appdata/webtop_dev:/config
- /mnt:/mnt
#- /var/run/docker.sock:/var/run/docker.sock #optional
ports:
- 3001:3001
devices:
- /dev/dri:/dev/dri #optional
shm_size: "1gb" #optional
restart: unless-stopped
privileged: true
Container logs
o support LSIO projects visit:
https://www.linuxserver.io/donate/
───────────────────────────────────────
GID/UID
───────────────────────────────────────
User UID: 1000
User GID: 1000
───────────────────────────────────────
**** permissions for /dev/dri/renderD128 are good ****
**** permissions for /dev/dri/card0 are good ****
[custom-init] No custom files found, skipping...
[ls.io-init] done.
2024-06-17 13:54:25,572 [PRIO] Connections: accepted: @192.168.0.10_1718603665.562547::websocket
2024-06-17 13:54:50,053 [PRIO] Input: Failure adding new keysym 0x1005426
2024-06-17 13:54:50,053 [PRIO] Input: Failure adding new keysym 0x1005065
2024-06-17 13:54:50,053 [PRIO] Input: Failure adding new keysym 0x1005eb7
2024-06-17 13:54:50,053 [PRIO] Input: Failure adding new keysym 0x1007825
2024-06-17 13:54:50,053 [PRIO] Input: Failure adding new keysym 0x100783a
2024-06-17 13:54:50,053 [PRIO] Input: Failure adding new keysym 0x100594b
2024-06-17 13:54:50,054 [PRIO] Input: Failure adding new keysym 0x1008fdb
2024-06-17 13:54:51,209 [PRIO] Input: Failure adding new keysym 0x1008bf4
2024-06-17 13:54:54,802 [PRIO] Input: Failure adding new keysym 0x1006740
2024-06-17 13:54:54,803 [PRIO] Input: Failure adding new keysym 0x1006740
2024-06-17 13:54:54,803 [PRIO] Input: Failure adding new keysym 0x1006740
2024-06-17 13:54:56,124 [PRIO] Input: Failure adding new keysym 0x1005723
2024-06-17 13:54:56,125 [PRIO] Input: Failure adding new keysym 0x1008bde
2024-06-17 13:54:56,125 [PRIO] Input: Failure adding new keysym 0x1008282
2024-06-17 13:54:56,125 [PRIO] Input: Failure adding new keysym 0x1005feb
2024-06-17 13:54:56,125 [PRIO] Input: Failure adding new keysym 0x1005230
2024-06-17 13:55:00,461 [PRIO] Input: Failure adding new keysym 0x100554a
2024-06-17 13:55:00,462 [PRIO] Input: Failure adding new keysym 0x1005723
2024-06-17 13:55:00,462 [PRIO] Input: Failure adding new keysym 0x1008bde
2024-06-17 13:55:00,462 [PRIO] Input: Failure adding new keysym 0x1008282
2024-06-17 13:55:02,508 [PRIO] Input: Failure adding new keysym 0x1004e3a
2024-06-17 13:55:03,902 [PRIO] Input: Failure adding new keysym 0x1008bb0
2024-06-17 13:55:03,902 [PRIO] Input: Failure adding new keysym 0x1005f97
2024-06-17 13:55:03,902 [PRIO] Input: Failure adding new keysym 0x1004ed8
2024-06-17 13:55:03,902 [PRIO] Input: Failure adding new keysym 0x1006b3e
2024-06-17 13:55:04,359 [PRIO] Input: Failure adding new keysym 0xfc
2024-06-17 13:55:04,935 [PRIO] Input: Failure adding new keysym 0x1005973
2024-06-17 13:55:04,935 [PRIO] Input: Failure adding new keysym 0x100540d
2024-06-17 13:55:04,935 [PRIO] Input: Failure adding new keysym 0x10079f0
2024-06-17 13:55:06,286 [PRIO] Input: Failure adding new keysym 0x1006211
2024-06-17 13:55:06,286 [PRIO] Input: Failure adding new keysym 0x1004e14
2024-06-17 13:55:07,348 [PRIO] Input: Failure adding new keysym 0x1005065
2024-06-17 13:55:07,348 [PRIO] Input: Failure adding new keysym 0x1005eb7
2024-06-17 13:55:07,348 [PRIO] Input: Failure adding new keysym 0x10051b7
2024-06-17 13:55:07,348 [PRIO] Input: Failure adding new keysym 0x10070ed
2024-06-17 13:57:07,273 [PRIO] Connections: closed: @192.168.0.10_1718603665.562547::websocket (Clean disconnection)
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
Can you let me know what tag of kasmweb/core-ubuntu-jammy you tested with ?
Can you let me know what tag of
kasmweb/core-ubuntu-jammyyou tested with ?
kasmweb/core-ubuntu-jammy:develop
kasmweb/core-ubuntu-jammy develop be078449058a 3 months ago 2.41GB
Many updates have been made to webtop since this issue was opened including bumping the KasmVNC and NoVNC combo to head. Can you pull the latest and confirm this still persists (use a private browsing mode to ensure browser cache is not used)
Many updates have been made to webtop since this issue was opened including bumping the KasmVNC and NoVNC combo to head. Can you pull the latest and confirm this still persists (use a private browsing mode to ensure browser cache is not used)
I just tested the latest linuxserver/webtop:ubuntu-xfce image, and the issue still persists.
REPOSITORY TAG IMAGE ID CREATED SIZE linuxserver/webtop ubuntu-xfce 4f16da12d4dd 4 days ago 2.5GB
Can you let me know your run command for kasmweb/core-ubuntu-jammy:develop also the underlying browser you are using to test and base operating system on the client. (this all happens clientside trying to determine if there are any differences in the client)
Can you let me know your run command for
kasmweb/core-ubuntu-jammy:developalso the underlying browser you are using to test and base operating system on the client. (this all happens clientside trying to determine if there are any differences in the client)
browser: edge
operating system on the client: windows10 and windows11
command:
services:
ubuntu-test:
image: kasmweb/core-ubuntu-jammy:develop
container_name: ubuntu-test
restart: unless-stopped
ports:
- "6903:6901"
volumes:
- "/mnt:/mnt"
environment:
- TZ=Asia/Shanghai
- VNC_PW=a123456789
- LANG=zh_CN.UTF-8
- LANGUAGE=zh_CN.UTF-8
- kasm_ime_mode_default_on=true
- locale=zh_CN.UTF-8
- timezone=Asia/Shanghai
shm_size: 512M
network_mode: bridge
privileged: true
Linking this issue and closing, looks like we differ somehow for xkbcomp, do not have a solution yet: https://github.com/linuxserver/docker-baseimage-kasmvnc/issues/79
https://github.com/linuxserver/docker-baseimage-kasmvnc/issues/79#issuecomment-2644442244
This temporarily solved it.