[BUG] Black screen in KASM

[tuxpeople]

Is there an existing issue for this?

• [X] I have searched the existing issues

Current Behavior

I added the linuxserver.io Registry to my KASM Installation. When I start Obsidian, all I get is a black screen. It looks like this black screen is coming from the window manager, as I can change between 4 desktops using swipe gestures and I get a little context menu to start terminal and chromium if I do a right-click into the black screen:

Expected Behavior

I see Obsidian and can user it.

Steps To Reproduce

1. I Installed KASM 1.15.0.577587 on Ubuntu 24.04 (x86_64) with Docker version 26.1.3, build b72abbb
2. I added https://kasmregistry.linuxserver.io/ as KASM registry
3. I installed the Obsidian Workspace from said Registry. It's using lscr.io/linuxserver/obsidian:latest, docker image inspect says build_version is Linuxserver.io version:- v1.5.12-ls9 Build-date:- 2024-05-26T11:51:21+00:00
4. I started the installed Obsidian Workspace

Step 1 has been done using this script:

sudo /bin/dd if=/dev/zero of=/var/swap.1 bs=1M count=2048
sudo /sbin/mkswap /var/swap.1
sudo chmod 600 /var/swap.1
sudo /sbin/swapon /var/swap.1
echo '/var/swap.1 swap swap defaults 0 0' | sudo tee -a /etc/fstab
curl -fsSL https://get.docker.com | sudo sh
wget $(curl -s https://api.github.com/repos/kasmtech/kasm-install-wizard/releases/latest | jq -r .assets[0].browser_download_url) -O /tmp/kasm_workspaces.tar.gz
cd /tmp
tar -xf kasm_workspaces.tar.gz
sudo bash /tmp/kasm_release/install.sh noninteractive -e -p $(hostname -I | cut -d' ' -f1 | tr -d '\\n') -m $(hostname -I | cut -d' ' -f1 | tr -d '\\n') | grep 'Login Credentials' -A 50 | grep -v DataSourceVMware | sudo tee /root/kasm-passwords.txt >/dev/null 2>&1

Environment

KASM: 1.15.0.577587
OS: Ubuntu 24.04 (x86_64)
Docker: 26.1.3, build b72abbb

CPU architecture

x86-64

Docker creation

Container logs

kasm-obsidian-log.json

[github-actions[bot]]

Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.

[turkievicz]

I have the same issue, but I "fixed" opening xterm and sudo /opt/obsidian/obsidian --no-sandbox

[OJ7]

I have the same issue, but I "fixed" opening xterm and sudo /opt/obsidian/obsidian --no-sandbox

@turkievicz I tried that out, but got this error:

[DuelistRag3]

This is duo to permision errors, obsidian can´t interact with /opt/obsidian/ current workaround is du open xterm and use

sudo su and afterwards chmod -R 777 /opt/obsidian

each time u run the workspace, currently im working to get it executed on start !docker exec config does not work!

[DuelistRag3]

ok nevermind, got it with docker exec config working: { "first_launch": { "user": "root", "cmd": "bash -c 'chmod -R 777 /opt/obsidian/'" } }

[OJ7]

ok nevermind, got it with docker exec config working: { "first_launch": { "user": "root", "cmd": "bash -c 'chmod -R 777 /opt/obsidian/'" } }

This fixed the issue for me, thanks!

[tuxpeople]

ok nevermind, got it with docker exec config working: { "first_launch": { "user": "root", "cmd": "bash -c 'chmod -R 777 /opt/obsidian/'" } }

This fixed the issue for me, thanks!

Can also confirm the fix. I think that fix schould go into the image or at least into the KASM registry of linuxserver.

[saberxt]

I have same problem but a little difference.

I can use obsidian for a minute or two then it becomes black.

[thelamer]

Does anyone know the directories that need to be symlinked into the users $HOME, this would be the best approach.

[DuelistRag3]

Does anyone know the directories that need to be symlinked into the users $HOME, this would be the best approach.

same directorys as mentioned in my comment

[thelamer]

Does anyone know the directories that need to be symlinked into the users $HOME, this would be the best approach.

same directorys as mentioned in my comment

Yeah I get that, was more reaching if people had drilled into what actual directories need read/write. The reason it is not working in Kasm is we run a chown outside of their init here: https://github.com/linuxserver/docker-obsidian/blob/main/root/etc/s6-overlay/s6-rc.d/init-obsidian-config/run

Give me a bit to see if chowning like this with sudo is the best approach, or if it can be done more surgically for specific folders inside of /opt/obsidian.

[thelamer]

This has been resolved with the latest image, if there is any persistence linked to your existing container the /home/kasm-user/.openbox/autostart file will need to be deleted.