[BUG] Black Screen

[alx-xlx]

Is there an existing issue for this?

• I have searched the existing issues

Current Behavior

The obsidan goes black and doesn't respond

Expected Behavior

Should not be black

Steps To Reproduce

1. docker compose up

Environment

- OS: RaspberryPI
- How docker service was installed:

CPU architecture

arm64

Docker creation

---
services:
  obsidian:
    image: lscr.io/linuxserver/obsidian:latest
    container_name: obsidian
    security_opt:
      - seccomp:unconfined #optional
    environment:
      - PUID=1000
      - PGID=1000
    volumes:
      - /home/pi/data/obsidian:/config
      - /home/pi/0x.PiCloud/Obsidian:/data
    ports:
      - 6010:3000
      - 6011:3001
    devices:
      - /dev/dri:/dev/dri #optional
    shm_size: "1gb"
    # restart: unless-stopped
    labels:
      - sablier.enable=true
      - sablier.group=obsidian
    healthcheck:
      test: ["CMD", "curl", "-f", "http://localhost:3000"]
      interval: 30s
      timeout: 5s
      retries: 3
      start_period: 10s

Container logs

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

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

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

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

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

User UID:    1000
User GID:    1000
───────────────────────────────────────
**** permissions for /dev/dri/renderD128 are good ****
**** permissions for /dev/dri/card1 are good ****
**** permissions for /dev/dri/card0 are good ****
[custom-init] No custom files found, skipping...
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root

Xvnc KasmVNC 1.3.4 - built Apr 12 2025 19:13:46
Copyright (C) 1999-2018 KasmVNC Team and many others (see README.me)
See http://kasmweb.com for information on KasmVNC.
Underlying X server release 12101007

V3D 7.1 not supported by this version of Mesa.
[ls.io-init] done.
V3D 7.1 not supported by this version of Mesa.
[mi] mieq: warning: overriding existing handler (nil) with 0x555636665700 for event 2
[mi] mieq: warning: overriding existing handler (nil) with 0x555636665700 for event 3
Obt-Message: Xinerama extension is not present on the server
17
 2025-05-04 18:22:45,573 [INFO] websocket 0: got client connection from 127.0.0.1
 2025-05-04 18:22:45,589 [PRIO] Connections: accepted: @192.168.0.101_1746363165.573990::websocket
 2025-05-04 18:23:31,314 [PRIO] Connections: closed: @192.168.0.101_1746363165.573990::websocket (Clean disconnection)
 2025-05-04 18:23:32,049 [INFO] websocket 1: got client connection from 127.0.0.1
 2025-05-04 18:23:32,066 [PRIO] Connections: accepted: @192.168.0.101_1746363212.49519::websocket
 2025-05-04 18:23:45,847 [PRIO] Connections: closed: @192.168.0.101_1746363212.49519::websocket (Clean disconnection)
 2025-05-04 18:23:46,386 [INFO] websocket 2: got client connection from 127.0.0.1
 2025-05-04 18:23:46,403 [PRIO] Connections: accepted: @192.168.0.101_1746363226.386297::websocket

[j0nnymoe]

Try without mapping your GPU.

[alx-xlx]

ok I comment the below and it works for like 1mins and then hangs and then it automatically turns into black screen

    # devices:
    #  - /dev/dri:/dev/dri #optional

I am running the v1.8.10-ls63 , but this issue has started way before this version.

From what I can tell the obsidian app in the docker probably is running well as my vault files are getting synced from the docker-obsidian to my other devices.
So imo the display on docker-obsidian is not working for some reason.

[ConsularParadi]

Having the same issue with latest as well as 1.8.7 images. Screen remains black irrespective of mapping the gpu.

[Tigo72]

Having the same issue with latest as well as 1.8.7 images. Screen remains black irrespective of mapping the gpu.

Same here still, similar logs as reported above that give little to go from. Docker 1.8.7 does work for me, from which I can update to 1.8.10 within the application. But then there's no connection between container and internet to update or sync, for instance.
DOCKER versions 1.8.9 and 10 have that connection restored, but with that black screen within half a minute.

This is a lasting issue, as also reported here: #19

[dspacks]

Having similar issue on :latest; found old issue: #7 that helped; executing sudo /opt/obsidian/obsidian --no-sandbox from xterm brought obsidian up.

[LinuxServer-CI]

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.

[Goelant]

Got the same issue and don't have any logs to help. Is it possible to enable the no-sandbox mode by default ?