[BUG] Multiple dependencies missing (PyXDG, Xinerama etc)

[privacyadmin]

Is there an existing issue for this?

• [X] I have searched the existing issues

Current Behavior

Fresh install on a newly formatted system with Docker on Fedora 40 Server. Running the image resulted in on first run resulted in "openbox-xdg-autostart requires PyXDG". Installing python3-xdg resolves this issue but returns this error "Xinerama extension is not present on the server" this time

Expected Behavior

Chromium browser should be shown

Steps To Reproduce

1. Run container
2. Install python3-xdg to resolve openbox-xdg-autostart requires PyXDG
3. Restart container
4. New error "Xinerama extension is not present on the server"

Environment

- OS: Fedora 40
- How docker service was installed:
dnf install dnf-plugins-core
dnf config-manager --add-repo https://download.docker.com/linux/fedora/docker-ce.repo
dnf install docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin

CPU architecture

x86-64

Docker creation

services:
  chromium:
    image: lscr.io/linuxserver/chromium:latest
    container_name: chromium
    security_opt:
      - seccomp:unconfined #optional
    environment:
      - PUID=1000
      - PGID=1000
      - CHROME_CLI=https://www.linuxserver.io/ #optional
    volumes:
      - /example/Docker/chromium/config:/config
    ports:
      - 8855:8855
    shm_size: "1gb"
    restart: unless-stopped

Container logs

───────────────────────────────────────
[custom-init] No custom files found, skipping...
Xvnc KasmVNC 1.2.0 - built Jun 26 2024 18:56:36
Copyright (C) 1999-2018 KasmVNC Team and many others (see README.me)
See http://kasmweb.com for information on KasmVNC.
Underlying X server release 12014000, The X.Org Foundation
[ls.io-init] done.
Obt-Message: Xinerama extension is not present on the server
19

[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.

[thelamer]

If you want to see something fun go ahead and change this line to not pipe to null: https://github.com/linuxserver/docker-chromium/blob/master/root/usr/bin/wrapped-chromium#L30

It is just Openbox warnings and they have no effect on the functionality of the container. We are running Desktop apps and DEs inside a Docker container with the minimal set of software needed to run the underlying application. There will be all kinds of Nag messages depending on the app/DE.

[privacyadmin]

I thought those errors might have been causing this blank screen.

Any clue on what might have cause this problem?

[thelamer]

right click the desktop, open a terminal and run chromium see what it spits out. Use chromium --no-sandbox if you are running without seccomp unconfined.