[BUG] Just blank screen with 8687ac3a-ls43

[ishtangli]

Is there an existing issue for this?

• [X] I have searched the existing issues

Current Behavior

Black screen

Expected Behavior

No response

Steps To Reproduce

Just run the webui

Environment

- OS: Unraid
- How docker service was installed:

CPU architecture

x86-64

Docker creation

Via unraid app store

Container logs

No logs created

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

[j0nnymoe]

I don't believe there are no logs created. There will be -something- there.

[ishtangli]

Linux 6.1.63-Unraid. root@MyNAS:~# docker logs chromium [migrations] started [migrations] no migrations found ───────────────────────────────────────

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

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

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

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

User UID: 99 User GID: 100 ───────────────────────────────────────

[custom-init] No custom files found, skipping... [ls.io-init] done. _XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created.

Xvnc KasmVNC 1.2.0 - built Nov 25 2023 18:39:17 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

Obt-Message: Xinerama extension is not present on the server 2023-12-01 05:22:01,337 [INFO] websocket 0: got client connection from 127.0.0.1 2023-12-01 05:22:01,345 [PRIO] Connections: accepted: @192.168.2.226_1701379321.337262::websocket 2023-12-01 05:22:14,347 [PRIO] Connections: closed: @192.168.2.226_1701379321.337262::websocket (Clean disconnection)

[danielb7390]

Same problem, logs look the same as the user above. tried to right click and open chromium there, nothing. Tried opening xterm and running chromium, no errors, just goes back to the shell.

[ishtangli]

Forced a downgrade to previous version for now.

On Fri, Dec 1, 2023, 7:00 PM Daniel Sousa @.***> wrote:

Same problem, logs look the same as the user above. tried to right click and open chromium there, nothing. Tried opening xterm and running chromium, no errors, just goes back to the shell.

— Reply to this email directly, view it on GitHub https://github.com/linuxserver/docker-chromium/issues/19#issuecomment-1835892301, or unsubscribe https://github.com/notifications/unsubscribe-auth/AEHY5Z5PZ6SQANNPTWZ476LYHG2F5AVCNFSM6AAAAABABY7JOWVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMZVHA4TEMZQGE . You are receiving this because you authored the thread.Message ID: @.***>

[derp90]

Same issue Here is my log

2023-12-05 11:06:58.652100+00:00[migrations] started 2023-12-05 11:06:58.652151+00:00[migrations] no migrations found 2023-12-05 11:06:58.819176+00:00usermod: no changes 2023-12-05 11:06:58.819872+00:00─────────────────────────────────────── 2023-12-05 11:06:58.819900+00:002023-12-05T11:06:58.819900004Z 2023-12-05 11:06:58.819923+00:00██╗ ███████╗██╗ ██████╗ 2023-12-05 11:06:58.819936+00:00██║ ██╔════╝██║██╔═══██╗ 2023-12-05 11:06:58.819948+00:00██║ ███████╗██║██║ ██║ 2023-12-05 11:06:58.819960+00:00██║ ╚════██║██║██║ ██║ 2023-12-05 11:06:58.819978+00:00███████╗███████║██║╚██████╔╝ 2023-12-05 11:06:58.819991+00:00╚══════╝╚══════╝╚═╝ ╚═════╝ 2023-12-05 11:06:58.820004+00:002023-12-05T11:06:58.820004204Z 2023-12-05 11:06:58.820015+00:00Brought to you by linuxserver.io 2023-12-05 11:06:58.820038+00:00─────────────────────────────────────── 2023-12-05 11:06:58.820053+00:002023-12-05T11:06:58.820053779Z 2023-12-05 11:06:58.820065+00:00To support LSIO projects visit: 2023-12-05 11:06:58.820077+00:00https://www.linuxserver.io/donate/ 2023-12-05 11:06:58.820095+00:002023-12-05T11:06:58.820095004Z 2023-12-05 11:06:58.820107+00:00─────────────────────────────────────── 2023-12-05 11:06:58.820118+00:00GID/UID 2023-12-05 11:06:58.820130+00:00─────────────────────────────────────── 2023-12-05 11:06:58.821718+00:002023-12-05T11:06:58.821718418Z 2023-12-05 11:06:58.821737+00:00User UID: 911 2023-12-05 11:06:58.821745+00:00User GID: 911 2023-12-05 11:06:58.821752+00:00─────────────────────────────────────── 2023-12-05 11:06:58.821759+00:002023-12-05T11:06:58.821759586Z 2023-12-05 11:06:59.158984+00:00[custom-init] No custom files found, skipping... 2023-12-05 11:06:59.174867+00:00_XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created. 2023-12-05 11:06:59.175248+00:002023-12-05T11:06:59.175248180Z 2023-12-05 11:06:59.175274+00:00Xvnc KasmVNC 1.2.0 - built Nov 25 2023 18:39:17 2023-12-05 11:06:59.175288+00:00Copyright (C) 1999-2018 KasmVNC Team and many others (see README.me) 2023-12-05 11:06:59.175315+00:00See http://kasmweb.com for information on KasmVNC. 2023-12-05 11:06:59.175329+00:00Underlying X server release 12014000, The X.Org Foundation 2023-12-05 11:06:59.175342+00:002023-12-05T11:06:59.175342050Z 2023-12-05 11:06:59.177779+00:00[ls.io-init] done. 2023-12-05 11:06:59.234336+00:00Obt-Message: Xinerama extension is not present on the server 2023-12-05 11:07:46.443040+00:002023-12-05 11:07:46,442 [INFO] websocket 0: got client connection from 127.0.0.1 2023-12-05 11:07:46.461081+00:002023-12-05 11:07:46,460 [PRIO] Connections: accepted: @50.220.114.186_1701774466.443289::websocket

[ishtangli]

Latest release still shows just black.

[Kamusksn]

I have the same issue, just black screen after restart the image!

[dowonim323]

Same problem, I got log like this

[mod-init] Attempting to run Docker Modification Logic [mod-init] Adding linuxserver/mods:universal-internationalization to container [mod-init] Downloading linuxserver/mods:universal-internationalization from lscr.io [mod-init] Installing linuxserver/mods:universal-internationalization [mod-init] linuxserver/mods:universal-internationalization applied to container [migrations] started [migrations] no migrations found ───────────────────────────────────────

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

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

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

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

User UID: 1000 User GID: 1000 ───────────────────────────────────────

creating video group video24ic with id 109 adding /dev/dri/renderD129 to video group video24ic with id 109 permissions for /dev/dri/renderD128 are good creating video group videobd0d with id 44 adding /dev/dri/card1 to video group videobd0d with id 44 permissions for /dev/dri/card0 are good International Fonts/Locales installed skipping [custom-init] No custom files found, skipping... [ls.io-init] done. _XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created.

Xvnc KasmVNC 1.2.0 - built Oct 21 2023 22:22:14 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

Obt-Message: Xinerama extension is not present on the server Error: Connection refused at PulseAudioContext. (/kclient/node_modules/pulseaudio2/lib/pulse.js:120:36) at /kclient/node_modules/pulseaudio2/lib/pulse.js:133:21 at process.processTicksAndRejections (node:internal/process/task_queues:77:11) Kclient was unable to init audio, it is possible your host lacks support!!!! Error: Access denied at /kclient/node_modules/pulseaudio2/lib/pulse.js:133:21 at process.processTicksAndRejections (node:internal/process/task_queues:77:11) Kclient was unable to init audio, it is possible your host lacks support!!!! Connection failure: Connection refused pa_context_connect() failed: Connection refused xvnc_get_formats time="2023-12-12T18:46:55.184756605+09:00" level=error msg="failed to mount overlay: invalid argument" storage-driver=overlay2 2023-12-12 18:47:02,427 [INFO] websocket 0: got client connection from 127.0.0.1 2023-12-12 18:47:02,434 [PRIO] Connections: accepted: @..._1702374422.427596::websocket xvnc_get_formats

[fate8383]

I have exact the ama issue last two maybe more versions. Also right click xterm opens but right click chromium selection does nothing...tested on amd and arm instances the same result.

[drizuid]

can someone provide a docker run or compose? we can't reproduce this because

is completely useless

[github-actions[bot]]

A human has marked this issue as invalid, this likely happened because the issue template was not used in the creation of the issue.

[danielb7390]

The docker run command that unraid creates from the template is:

docker run
  -d
  --name='chromium'
  --net='bridge'
  -e TZ="Europe/London"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="vault"
  -e HOST_CONTAINERNAME="chromium"
  -e 'PUID'='99'
  -e 'PGID'='100'
  -e 'UMASK'='022'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:3000]'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/chromium-logo.png'
  -p '3100:3000/tcp'
  -v '/mnt/user/appdata/chromium':'/config':'rw'
  --device='/dev/dri'
  --shm-size=1gb 'lscr.io/linuxserver/chromium' 

EDIT: I got it to work.. just created a new empty config directory and it starts, so the problem seems to happen only when there's existing settings?

[drizuid]

The docker run command that unraid creates from the template is:

docker run
  -d
  --name='chromium'
  --net='bridge'
  -e TZ="Europe/London"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="vault"
  -e HOST_CONTAINERNAME="chromium"
  -e 'PUID'='99'
  -e 'PGID'='100'
  -e 'UMASK'='022'
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.webui='http://[IP]:[PORT:3000]'
  -l net.unraid.docker.icon='https://raw.githubusercontent.com/linuxserver/docker-templates/master/linuxserver.io/img/chromium-logo.png'
  -p '3100:3000/tcp'
  -v '/mnt/user/appdata/chromium':'/config':'rw'
  --device='/dev/dri'
  --shm-size=1gb 'lscr.io/linuxserver/chromium' 

EDIT: I got it to work.. just created a new empty config directory and it starts, so the problem seems to happen only when there's existing settings?

as you guys are the only ones reporting this, i can't definitively say. i know the --device line is wrong as it should be --device='/dev/dri:/dev/dri (as shown in the readme) but i dont think this would cause any problem. I suspect you had something configured that caused a problem and using a clean /config path took that out of play, but again, im guessing due to lack of info

[danielb7390]

With --device if it's only specified one, it's the host/container path will be the same, afaik Either way, i tried without /dev/dri, the problem remained.

There's no way to debug the chromium process? Like a verbose mode or something?

[drizuid]

There's no way to debug the chromium process? Like a verbose mode or something?

I'm sure chromium has debugging options, but as always, we support the container, not the application within. It is clear that some config in your prior /config path was the issue, assuming you still have that, you could swap it back and check chromium's documentation for debugging to see what caused it

ninjaedit, you could potentially right click on the desktop and open a terminal, then launch chromium in the foreground there and see some output. unless the "blank screen" is truly blank.. you could also try setting privileged (should only be needed for DinD)or seccomp unconfined as mentioned in the readme

[danielb7390]

I understand that this is not the container fault, so any help given is an extra 😅 I will probably choose the easy way out and just reset the entire chromium...

Meanwhile i saw your edit to open chromium in the terminal, already tried that, it gave no output, it just returns back to the shell

[drizuid]

I understand that this is not the container fault, so any help given is an extra 😅 I will probably choose the easy way out and just reset the entire chromium...

Meanwhile i saw your edit to open chromium in the terminal, already tried that, it gave no output, it just returns back to the shell

can you try the seccomp unconfined option?

[danielb7390]

I understand that this is not the container fault, so any help given is an extra 😅 I will probably choose the easy way out and just reset the entire chromium... Meanwhile i saw your edit to open chromium in the terminal, already tried that, it gave no output, it just returns back to the shell

can you try the seccomp unconfined option?

Tried with --security-opt seccomp=unconfined, same result. Also tried to remove the --shm-size=1gb, same result.

Quick google search, told me that if i call chromium with --enable-logging=stderr --v=1 # Output will be printed to standard error (eg. printed in the console) and to the debugger, yet i get nothing still, process just ends and returns to the shell.

[drizuid]

are you using unraid or using that docker run directly?

[danielb7390]

I'm editing the unraid template, then checking the generated docker run command.

For the debug line for chromium i used it inside the container in xterm.

[drizuid]

when you added in the --security-opt and confirmed it with the docker run, how does it look? can you share it?

[thelamer]

The latest version of chromium on alpine 3.18 and 3.19 segfaults, seems like all the time, but on this one container it launches the first time perfectly fine.

I might need to rebase to Debian as there is not a lot of info to go on but give me some time and sorry for the late response here I have been busy. Need to also open up an issue with Alpine.

Edit: the easy way to replicate is to close the window and try to launch it from terminal will result in

/usr/bin/chromium: line 26:   689 Segmentation fault      (core dumped) ${BIN} --ignore-gpu-blocklist --no-first-run --no-sandbox --password-store=basic --simulate-outdated-no-au='Tue, 31 Dec 2099 23:59:59 GMT' --start-maximized --test-type --user-data-dir "$@" > /dev/null 2>&1

[thelamer]

I'll keep working in the background, but in the mean time I rebased this image to debian.

[danielb7390]

Should that change fix the issue? Just tried with latest and same behavior.

[jessewritescode]

I also tried latest with the same result. In the meantime I was able to get things working by using 98239515-ls42--I.e.,

  chromium:
    # image: lscr.io/linuxserver/chromium:latest
    image: lscr.io/linuxserver/chromium:98239515-ls42

if anyone needs a temporary solution until this is resolved

[AndreiArdelean1]

With the latest image, now I get an error (with previous images I didn’t have an error)

Failed to execute child process "/usr/bin/chromium-browser" (No such file or directory)

I’ve checked and in the container there is /usr/bin/chromium but no /usr/bin/chromium-browser

And here are the container logs:

─────────────────────────────────────── GID/UID ─────────────────────────────────────── User UID: 1000 User GID: 1001 ─────────────────────────────────────── [custom-init] No custom files found, skipping... [ls.io-init] done. _XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created. Xvnc KasmVNC 1.2.0 - built Dec 16 2023 18:48:56 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 Obt-Message: Xinerama extension is not present on the server /config/.config/openbox/autostart: 2: chromium-browser: not found

[thelamer]

Didn't really think about the upgrade scenario that's my fault. Just run rm /config/.config/openbox/autostart in the container and restart it in the mean time, ill put a pointer in shortly.

[thelamer]

I added a symlink in the latest version. @AndreiArdelean1

[AndreiArdelean1]

With the latest inage the error doesn’t show but the browser still doesn’t open.

User UID: 1000 User GID: 1001 ───────────────────────────────────────

[custom-init] No custom files found, skipping... [ls.io-init] done. _XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created.

Xvnc KasmVNC 1.2.0 - built Dec 16 2023 18:48:56 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

Obt-Message: Xinerama extension is not present on the server

ERROR: openbox-xdg-autostart requires PyXDG to be installed 2024-01-01 10:19:42,036 [INFO] websocket 0: got client connection from 127.0.0.1 2024-01-01 10:19:42,077 [PRIO] Connections: accepted: @10.0.0.2_1704097182.42580::websocket

[fate8383]

With the latest inage the error doesn’t show but the browser still doesn’t open.

User UID: 1000

User GID: 1001

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

[custom-init] No custom files found, skipping...

[ls.io-init] done.

_XSERVTransmkdir: ERROR: euid != 0,directory /tmp/.X11-unix will not be created.

Xvnc KasmVNC 1.2.0 - built Dec 16 2023 18:48:56

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

Obt-Message: Xinerama extension is not present on the server

ERROR: openbox-xdg-autostart requires PyXDG to be installed

2024-01-01 10:19:42,036 [INFO] websocket 0: got client connection from 127.0.0.1

2024-01-01 10:19:42,077 [PRIO] Connections: accepted: @10.0.0.2_1704097182.42580::websocket

The same here

[thelamer]

did you try rm /config/.config/openbox/autostart and restart. I cannot reproduce on my end the debian base works.

[derp90]

did you try rm /config/.config/openbox/autostart and restart. I cannot reproduce on my end the debian base works.

I tried that and just a blank screen for me as well

[thelamer]

What is the output if you right click the desktop and run xterm from there run chromium-brpwser or wrapped-chromium? Also try seccomp unconfined

[derp90]

seccomp unconfined

[AndreiArdelean1]

Removing /config/.config/openbox/autostart has no effect Removing the /config/.config/chromium solves the problem but resets the settings Removing all from /config/.config/chromium except the Default directory solves the problem and keeps the settings

I already had seccomp:unconfined set.

Running:

• chromium-browser has no effect
• wrapped-chromium has no effect

[drizuid]

seccomp unconfined

it's not a command, look at the readme and put the seccomp:unconfined in your docker run/compose.

[drizuid]

Removing /config/.config/openbox/autostart has no effect Removing the /config/.config/chromium solves the problem but resets the settings Removing all from /config/.config/chromium except the Default directory solves the problem and keeps the settings

I already had seccomp:unconfined set.

Running:

• chromium-browser has no effect
• wrapped-chromium has no effect

if tells you in the error that it was left locked to avoid corruption. poss an unclean shutdown/restart. if you google that error, it tells you how to unlock it. that is what is preventing chromium from starting.

[fate8383]

rm -rf ~/.config/chromium/Singleton*

Running this command fixed it for me, thanks.

[derp90]

Running rm -rf ~/.config/chromium/SingletonLock Will fix the issue until the container is restarted

[derp90]

seccomp unconfined

it's not a command, look at the readme and put the seccomp:unconfined in your docker run/compose.

Whoops, misunderstood that.

I'm actually running it in kubernetes (truenas Scale) so all the docker options are not fully available to me. If you would like I can link you an instance of a chromium for debugging purposes

[thelamer]

Inside the web interface you can right click the desktop to open xterm, running the bin manually might show is where it is faulting

[AndreiArdelean1]

Running:

• chromium-browser has no effect
• wrapped-chromium has no effect

if tells you in the error that it was left locked to avoid corruption. poss an unclean shutdown/restart. if you google that error, it tells you how to unlock it. that is what is preventing chromium from starting.

When I run the commands, nothing shows up in either the console or the logs

And same as @derp90, running rm -rf ~/.config/chromium/SingletonLock will fix the issue until the container is restarted

[AndreiArdelean1]

Is the SingletonLock symlink broken? The file to which it points doesn't exist. The same for SingletonCookie

root@004f37ee3c32:~/.config/chromium# readlink -f /config/.config/chromium/SingletonLock
/config/.config/chromium/004f37ee3c32-349
root@004f37ee3c32:~/.config/chromium# ls /config/.config/chromium/
 AutofillStates             extensions_crx_cache         'Last Version'                        'Safe Browsing'         'Subresource Filter'
 BrowserMetrics-spare.pma   FileTypePolicies             'Local State'                          SafetyTips              TpcdMetadata
 CertificateRevocation      first_party_sets.db           MEIPreload                            segmentation_platform   TrustTokenKeyCommitments
 component_crx_cache        first_party_sets.db-journal   OnDeviceHeadSuggestModel              ShaderCache             Variations
'Crash Reports'             FirstPartySetsPreloaded       OptimizationHints                     SingletonCookie         ZxcvbnData
'Crowd Deny'                GraphiteDawnCache             OriginTrials                          SingletonLock
 Default                    GrShaderCache                 PKIMetadata                           SingletonSocket
 Dictionaries               hyphen-data                   PrivacySandboxAttestationsPreloaded   SSLErrorAssistant

lrwxrwxrwx  1 abc abc       18 Jan  8 10:14  SingletonCookie -> 840014527782887287
lrwxrwxrwx  1 abc abc       16 Jan  8 10:14  SingletonLock -> 004f37ee3c32-349
lrwxrwxrwx  1 abc abc       50 Jan  8 10:14  SingletonSocket -> /tmp/.org.chromium.Chromium.Z45301/SingletonSocket

[thelamer]

This container got rebased you probably need to purge your home directory or at least /config/.config/chromium

[derp90]

This container got rebased you probably need to purge your home directory or at least /config/.config/chromium

Wiping the config directory works for the first boot, but any reboots and blank screen issue returns.

[thelamer]

I added a hook to clear out these singleton files if chromium is not running, please test this tag and let me know:

lsiodev/chromium:amd64-4fed82c2-pkg-4fed82c2-dev-38e474cb898ef1652d55a867d3c18245f8a12d1b

[derp90]

I added a hook to clear out these singleton files if chromium is not running, please test this tag and let me know:

lsiodev/chromium:amd64-4fed82c2-pkg-4fed82c2-dev-38e474cb898ef1652d55a867d3c18245f8a12d1b

This seems to be working for me, multiple restarts with no issues

[danielb7390]

I added a hook to clear out these singleton files if chromium is not running, please test this tag and let me know:

lsiodev/chromium:amd64-4fed82c2-pkg-4fed82c2-dev-38e474cb898ef1652d55a867d3c18245f8a12d1b

Working for me too.

[Truth1984]

same issue, i'm running as root, so I have to add --no-sandbox to args to launch.