[BUG] <title>Unable to Input Chinese After a While When "Enable Local Input Method" Is Enabled

[randydl]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

After enabling the "Enable Local Input Method" option in the settings, I was initially able to input Chinese characters without issues. However, after typing for a while, the input stops working. The Chinese characters I type no longer appear in the container, as if they are disappearing without being registered.

Expected Behavior

No response

Steps To Reproduce

As mentioned above

Environment

CPU architecture

x86-64

Docker creation

docker run -d \
  --name=firefox \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Etc/UTC \
  -p 3000:3000 \
  -p 3001:3001 \
  -v /path/to/config:/config \
  --restart unless-stopped \
  lscr.io/linuxserver/firefox:latest

Container logs

[migrations] started
[migrations] no migrations found
usermod: no changes
───────────────────────────────────────

      ██╗     ███████╗██╗ ██████╗
      ██║     ██╔════╝██║██╔═══██╗
      ██║     ███████╗██║██║   ██║
      ██║     ╚════██║██║██║   ██║
      ███████╗███████║██║╚██████╔╝
      ╚══════╝╚══════╝╚═╝ ╚═════╝

   Brought to you by linuxserver.io
───────────────────────────────────────

To support LSIO projects visit:
https://www.linuxserver.io/donate/

───────────────────────────────────────
GID/UID
───────────────────────────────────────

User UID:    911
User GID:    911
───────────────────────────────────────
...+.......+.........+...+......+..+..........+...+..+.........+...+......+.........+...+...+......+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++*.+.....+......+.+..+...+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++*.+.+...+............+.....+..........+........+....+...+...............+..+..........+..+.........+.+...+......+.........+..+..........+.....+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
.......+..+...+.+.....+.......+..+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++*.....+.+..+.......+..+...+.+.....+..........+......+.....+.+...........................+...+.....+.........+...+..........+...+...+......+...+.....+......+.+.....+....+.....+......+.+.....+.......+......+..+.......+..+......+....+.........+..+..........+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++*..+..+...................+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
-----
[custom-init] No custom files found, skipping...
[ls.io-init] done.
Openbox-Message: Failed to open the display from the DISPLAY environment variable.
_XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created.

Xvnc KasmVNC 1.3.3 - built Feb 22 2025 19:05:16
Copyright (C) 1999-2018 KasmVNC Team and many others (see README.me)
See http://kasmweb.com for information on KasmVNC.
Underlying X server release 12101012

The XKEYBOARD keymap compiler (xkbcomp) reports:
> Warning:          Could not resolve keysym XF86CameraAccessEnable
> Warning:          Could not resolve keysym XF86CameraAccessDisable
> Warning:          Could not resolve keysym XF86CameraAccessToggle
> Warning:          Could not resolve keysym XF86NextElement
> Warning:          Could not resolve keysym XF86PreviousElement
> Warning:          Could not resolve keysym XF86AutopilotEngageToggle
> Warning:          Could not resolve keysym XF86MarkWaypoint
> Warning:          Could not resolve keysym XF86Sos
> Warning:          Could not resolve keysym XF86NavChart
> Warning:          Could not resolve keysym XF86FishingChart
> Warning:          Could not resolve keysym XF86SingleRangeRadar
> Warning:          Could not resolve keysym XF86DualRangeRadar
> Warning:          Could not resolve keysym XF86RadarOverlay
> Warning:          Could not resolve keysym XF86TraditionalSonar
> Warning:          Could not resolve keysym XF86ClearvuSonar
> Warning:          Could not resolve keysym XF86SidevuSonar
> Warning:          Could not resolve keysym XF86NavInfo
Errors from xkbcomp are not fatal to the X server
[mi] mieq: warning: overriding existing handler (nil) with 0x55ea239e0930 for event 2
[mi] mieq: warning: overriding existing handler (nil) with 0x55ea239e0930 for event 3
19
Obt-Message: Xinerama extension is not present on the server
 2025-02-27 16:24:10,975 [INFO] websocket 0: got client connection from 127.0.0.1
 2025-02-27 16:24:10,981 [PRIO] Connections: accepted: @172.17.0.1_1740673450.975523::websocket
 2025-02-27 16:25:03,848 [PRIO] Input: Failure adding new keysym 0x1005361
 2025-02-27 16:25:17,678 [PRIO] Input: Failure adding new keysym 0x1006211
 2025-02-27 16:25:17,678 [PRIO] Input: Failure adding new keysym 0x1006765
 2025-02-27 16:25:17,678 [PRIO] Input: Failure adding new keysym 0x10090a3
 2025-02-27 16:25:17,678 [PRIO] Input: Failure adding new keysym 0x10056f0
 2025-02-27 16:25:17,678 [PRIO] Input: Failure adding new keysym 0x10096be
 2025-02-27 16:25:22,405 [PRIO] Input: Failure adding new keysym 0x1006211
 2025-02-27 16:25:22,405 [PRIO] Input: Failure adding new keysym 0x1006765
 2025-02-27 16:25:26,492 [PRIO] Input: Failure adding new keysym 0x1006211
 2025-02-27 16:25:26,492 [PRIO] Input: Failure adding new keysym 0x1006765
 2025-02-27 16:25:30,937 [PRIO] Input: Failure adding new keysym 0x1006211
 2025-02-27 16:25:30,937 [PRIO] Input: Failure adding new keysym 0x1006765

[github-actions]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[LinuxServer-CI]

This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.

[LinuxServer-CI]

This issue is locked due to inactivity