You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Been using this image/container for a while, but after the last 2-3 updates has suddenly become very unstable and unusable.
Getting lots of VNC errors like in the image attached:
Expected Behavior
Should not freeze and crash
Steps To Reproduce
Open calibre via port 8080 (mapped to 8082 in my case) and calibre is very sluggish (far more sluggish than usual) then within 10-15 seconds get a blue screen with VNC error
Environment
- OS: Arch LTS Kernel
- How docker service was installed: from Arch repo
[migrations] started
[migrations] no migrations found
───────────────────────────────────────
██╗ ███████╗██╗ ██████╗
██║ ██╔════╝██║██╔═══██╗
██║ ███████╗██║██║ ██║
██║ ╚════██║██║██║ ██║
███████╗███████║██║╚██████╔╝
╚══════╝╚══════╝╚═╝ ╚═════╝
Brought to you by linuxserver.io
───────────────────────────────────────
To support LSIO projects visit:
https://www.linuxserver.io/donate/
───────────────────────────────────────
GID/UID
───────────────────────────────────────
User UID: 1000
User GID: 1000
───────────────────────────────────────
Linuxserver.io version: v7.20.0-ls308
Build-date: 2024-10-23T06:42:34+00:00
───────────────────────────────────────
**** creating video group videopjlb with id 985 ******** adding /dev/dri/card1 to video group videopjlb with id 985 ******** creating video group video5uuk with id 989 ******** adding /dev/dri/renderD128 to video group video5uuk with id 989 ****
[custom-init] No custom files found, skipping...
_XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created.
Xvnc KasmVNC 1.3.2 - built Oct 19 2024 19:06:02
Copyright (C) 1999-2018 KasmVNC Team and many others (see README.me)
See http://kasmweb.com for information on KasmVNC.
Underlying X server release 12014000, The X.Org Foundation
[ls.io-init] done.
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
19
Obt-Message: Xinerama extension is not present on the server
xvnc_get_formats
WARNING: Kernel has no file descriptor comparison support: Operation not permitted
2024-10-23 16:00:52,457 [INFO] websocket 0: got client connection from 127.0.0.1
2024-10-23 16:00:52,469 [PRIO] Connections: accepted: @192.168.1.107_1729695652.458301::websocket
The text was updated successfully, but these errors were encountered:
Try with seccomp unconfined WARNING: Kernel has no file descriptor comparison support: Operation not permitted this makes me think it is a kernel syscall.
Is there an existing issue for this?
Current Behavior
Been using this image/container for a while, but after the last 2-3 updates has suddenly become very unstable and unusable.
Getting lots of VNC errors like in the image attached:
Expected Behavior
Should not freeze and crash
Steps To Reproduce
Open calibre via port 8080 (mapped to 8082 in my case) and calibre is very sluggish (far more sluggish than usual) then within 10-15 seconds get a blue screen with VNC error
Environment
CPU architecture
x86-64
Docker creation
Container logs
The text was updated successfully, but these errors were encountered: