-
-
Notifications
You must be signed in to change notification settings - Fork 283
Closed
Labels
Description
Is there an existing issue for this?
- I have searched the existing issuesTo pick up a draggable item, press the space bar. While dragging, use the arrow keys to move the item. Press space again to drop the item in its new position, or press escape to cancel.
Current Behavior
I just get a black screen when accessing the webtop when I use any distro with KDE. I can't control anything or make anything happen on screen.
Expected Behavior
I should see a desktop.
Steps To Reproduce
docker compose up
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: all
capabilities:
- compute
- video
- graphics
- utility
environment:
- PUID=3000
- PGID=3000
- TZ=America/Los_Angeles
- TITLE=Ashkaan's Fedora
image: lscr.io/linuxserver/webtop:ubuntu-kde
network_mode: bridge
ports:
- 3000:3000
restart: unless-stopped
security_opt:
- seccomp:unconfined
shm_size: 1gb
volumes:
- /mnt/pool/docker/webtop:/config
- /etc/resolv.conf:/etc/resolv.conf:ro
networks:
bridge: {}
### Container logs
```bash
_XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created.
Metadata
Metadata
Assignees
Labels
Type
Projects
Status
Done
Milestone
Relationships
Development
Select code repository
Activity
github-actions commentedon Nov 16, 2024
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
dfldylan commentedon Nov 21, 2024
I have the same issue. After cancel nvidia setup, this issue disappear.
Or downgrade webtop to ubuntu-jammy (before 22.04.24)
I guess my host is ubuntu-jammy(instead of noble), so maybe run high-version ubuntu will cause this?
dfldylan commentedon Nov 23, 2024
#243 same here
thelamer commentedon Nov 23, 2024
Does debian-kde work with the same settings?
Ashkaan commentedon Dec 6, 2024
No, it doesn't. In fact, neither does ubuntu-xfce anymore, which did work on a previous version.
LinuxServer-CI commentedon Jan 6, 2025
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.
Ashkaan commentedon Jan 6, 2025
Hey team, this container is still not working for me. What can we do to fix the issue?
LinuxServer-CI commentedon Feb 7, 2025
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.
real-limitless commentedon Mar 6, 2025
I was able to work around this issue by doing a
podman exec -it <container_name> bash
and manually executing the startwm.shscript inside
/defaults
Another way I was able to work around this issue was by starting the desktop wm manually as well.
LinuxServer-CI commentedon Apr 7, 2025
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.
Xitee1 commentedon May 1, 2025
I'm new to webtop and having the same issue. It worked flawlessly and worked instantly without much configuration on pretty much all hosts but not so on a machine running Kubuntu KDE.
While writing this, suddenly the desktop just appeard and seems to be working. I did an test by restarting the container - turns out it just takes really really long (about 5 minutes) to come up while on all other hosts (even ones with less performance) it's nearly instant.
mg-dev25 commentedon May 1, 2025
The black screen is not a bug, it is a normal behavior implement by kasmvnc to indicate the GPU driver is not correct. Often this is because, when using KDE, the host for nvidia card, don't use the open source driver.
Xitee1 commentedon May 2, 2025
Oh I think I'm not having the exact same issue, this here is related to GPU. I do not even try to use a GPU. It just takes really long to start displaying a picture on this specific host and I can't figure out what is wrong. There's nothing in the logs that differs from the other hosts. Super annoying having to wait 5+ minutes after doing a restart of the container.
mg-dev25 commentedon May 3, 2025
@Xitee1 You need to share the yml docker compose file, for us to help you.
LinuxServer-CI commentedon Jun 2, 2025
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.
thelamer commentedon Jun 17, 2025
Images have been completely overhauled, if you still have an issue open a new one.
LinuxServer-CI commentedon Jul 18, 2025
This issue is locked due to inactivity