### Is there an existing issue for this? - [x] I have searched the existing issues ### Current Behavior KDE Wayland does not initialize when DISABLE_SUDO=true is used ### Expected Behavior KDE Wayland should work even with DISABLE_SUDO=true ### Steps To Reproduce 1. Run container 2. Connect to the exposed port, you will see that connection is successful but the Plasma interface does not show ### Environment ```markdown - OS: Ubuntu 24.04 - How docker service was installed: Installed following the instructions at the official Docker website ``` ### CPU architecture x86-64 ### Docker creation ```bash docker run --rm -it --shm-size=1gb -p 3001:3001 -e DISABLE_SUDO=true linuxserver/webtop:ubuntu-kde-version-010e48ad bash ``` ### Container logs ```bash INFO:printing:Print queue Selkies listening on /config/.XDG/selkies-cups/cups.sock, spooling to /config/.local/state/selkies/print [svc-de] /config/.XDG/wayland-1 found launching de Applying KWin clipboard rule... /defaults/startwm_wayland.sh: line 49: /usr/bin/sudo: Permission denied /defaults/startwm_wayland.sh: line 53: /usr/bin/sudo: Permission denied /defaults/startwm_wayland.sh: line 54: /usr/bin/sudo: Permission denied kbuildsycoca6 running... INFO:ws:Client ('127.0.0.1', 50264) connected (legacy, role controller, slot None). ```
Activity
thelamer commentedon Oct 5, 2026
Any of the hardening values are only for single application images and are tightly integrated with labwc and openbox.
You cannot harden a Webtop, it is a full desktop.
thelamer commentedon Oct 21, 2026
The sudo requirement has been dropped from ubuntu-kde e5843d4 It will come to the other branches in due time.
thelamer commentedon Oct 22, 2026
All kde distros complete sudo is no longer required and
-e DISABLE_SUDO=trueworks as expected.