[BUG] Cannot Open Settings Manager

[Ashkaan]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

When I click on Settings Manager, nothing happens.

When I right-click the Desktop and hit Desktop Settings..., I get the following error:

Expected Behavior

I should be able to open Settings Manager

Steps To Reproduce

run the docker
go to the site
click "Applications" and then "Settings Manager"

Environment

- OS: TrueNAS 24.10
- How docker service was installed: built-in

CPU architecture

x86-64

Docker creation

name: webtop
services:
  webtop:
    container_name: webtop
    deploy:
      resources:
        reservations:
          devices:
            - driver: nvidia
              count: "1"
              capabilities:
                - compute
                - video
                - graphics
                - utility
    environment:
      - PUID=3000
      - PGID=3000
      - TZ=America/Los_Angeles
      - TITLE=Webtop
      - CUSTOM_USER=ashkaan
      - DOCKER_MODS=linuxserver/mods:universal-package-install
      - INSTALL_PACKAGES=git|nano|vlc|thunar-archive-plugin
    image: lscr.io/linuxserver/webtop:ubuntu-xfce
    network_mode: bridge
    ports:
      - 3000:3000
    privileged: true
    restart: unless-stopped
    shm_size: 4gb
    volumes:
      - /mnt/pool/docker/webtop:/config
      - /etc/resolv.conf:/etc/resolv.conf:ro
networks:
  bridge: {}

Container logs

───────────────────────────────────────

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

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

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

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

User UID:    3000
User GID:    3000
───────────────────────────────────────
**** permissions for /dev/dri/card0 are good ****
**** permissions for /dev/dri/card1 are good ****
**** permissions for /dev/dri/renderD128 are good ****
**** Adding git to OS package install list ****
**** Adding nano to OS package install list ****
**** Adding vlc to OS package install list ****
**** Adding thunar-archive-plugin to OS package install list ****
[pkg-install-init] **** Installing all mod packages ****
Hit:1 https://download.docker.com/linux/ubuntu noble InRelease
Hit:2 http://archive.ubuntu.com/ubuntu noble InRelease
Hit:3 http://archive.ubuntu.com/ubuntu noble-updates InRelease
Hit:4 http://archive.ubuntu.com/ubuntu noble-security InRelease
Hit:5 https://ppa.launchpadcontent.net/mozillateam/ppa/ubuntu noble InRelease
Reading package lists...
Reading package lists...
Building dependency tree...
Reading state information...
git is already the newest version (1:2.43.0-1ubuntu7.1).
nano is already the newest version (7.2-2ubuntu0.1).
vlc is already the newest version (3.0.20-3build6).
thunar-archive-plugin is already the newest version (0.5.2-1build2).
0 upgraded, 0 newly installed, 0 to remove and 23 not upgraded.
[custom-init] No custom files found, skipping...
/usr/bin/nvidia-smi
/usr/bin/nvidia-smi
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root

Xvnc KasmVNC 1.3.3 - built Nov  9 2024 19:26:20
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
 2024-11-18 11:29:29,155 [INFO] websocket 0: got client connection from 127.0.0.1
 2024-11-18 11:29:29,182 [PRIO] Connections: accepted: @10.1.0.161_1731958169.156343::websocket

[hgw77]

Could it be that docker DIND is activated in your container? It is automatically activated if you start your container in privileged mode. Try --env START_DOCKER=false maybe that will help. I had a similar issue in KDE with the settings and the reason was that /tmp was emptied by DIND.

Here is the issue that I opened for reference

[Ashkaan]

Sadly, with the environment, KASM won't connect to the instance.