Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't open chrome and firefox #209

Open
Akira46 opened this issue Sep 11, 2024 · 4 comments
Open

Can't open chrome and firefox #209

Akira46 opened this issue Sep 11, 2024 · 4 comments

Comments

@Akira46
Copy link

Akira46 commented Sep 11, 2024

Image
vnc

Detailed error description
i want to run chromium browser but why when i open it nothing happens. chromium doesn't open and i don't get any notification. please tell me how to fix it because i really need chromium.

Additional content

I used docker hub to download console/debian-xfce-vnc:latest

@thordin9
Copy link

Same issue

@yozh
Copy link

yozh commented Dec 4, 2024

Having same problem. Chromium only opens from terminal with sandbox

@ph-jake
Copy link

ph-jake commented Dec 5, 2024

With a somewhat recent change to the script launching Chromium, the ability to insert CHROMIUM_FLAGS from the environment has been blocked. CHROMIUM_FLAGS is simply cleared out at the start of the script.

This used to be a feature, where the launcher would read $HOME/.chromium-browser.init into CHROMIUM_FLAS, and later use the CHROMIUM_FLAGS from the environment. Both situation are covered by the container startup scripts.

/dockerstartup/chrome-init.sh writes the current settings to $HOME/.chromium-browser.init

/dockerstartup/vnc_startup.sh both calls this script and sources the generated output to set the environment.

Now that this no longer works perhaps having /dockerstartup/chrome-init.sh writing a file to /etc/chromium.d/ instead could be a solution.

@DeltaWhy
Copy link

DeltaWhy commented Dec 9, 2024

I'm seeing the same or similar issue. Firefox works but Chromium won't start. From the terminal, the process appears to hang with no output. From ps ax I see both a chromium and chrome_crashpad_handler process, but there's nothing in the 'Crash Reports' folder. Running with strace shows it's hanging on a socket recv. I've tried with and without --no-sandbox (in args or in env), with --privileged on the Docker container, etc. but it behaves the same regardless. This is occurring on both the Debian and Rocky images.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants