Is there an existing issue for this?
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
- Run container
- Connect to the exposed port, you will see that connection is successful but the Plasma interface does not show
Environment
- OS: Ubuntu 24.04
- How docker service was installed: Installed following the instructions at the official Docker website
CPU architecture
x86-64
Docker creation
docker run --rm -it --shm-size=1gb -p 3001:3001 -e DISABLE_SUDO=true linuxserver/webtop:ubuntu-kde-version-010e48ad bash
Container logs
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).
Is there an existing issue for this?
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
Environment
CPU architecture
x86-64
Docker creation
Container logs
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).