New issue
Advanced search Search tips

Issue 719220 link

Starred by 4 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Jul 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

Chromium with --headless still requires GUI packages.

Reported by lem...@gmail.com, May 7 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 6.1; WOW64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/58.0.3029.82 Safari/537.36 Vivaldi/1.9.818.44

Steps to reproduce the problem:
1. Install headless chromium on Ubuntu. In this case, using https://launchpad.net/~saiarcot895/+archive/ubuntu/chromium-dev, because there is no official dev channel I can find.
2. Realize that this seems to try to drag in an entire desktop environment, despite the fact that when I build headless_shell, it just requires libfontconfig
3. Manually download the chromium install package.
4. Force dpkg to ignore the unneeded desktop cruft by forcing it to install with broken dependencies.
5. Try to run  chromium-browser --headless --remote-debugging-port=9222 --disable-gpu

What is the expected behavior?
The whole point of the headless browser, at least for me, is the fact I can run it on a headless system, e.g. no X or display components whatsoever. If the --headless parameter doesn't allow this, it's kind of pointless, you might as well just use xvfb.

What went wrong?
I'd guess that it's hard to make an application that conditionally depends on certain shared libraries. 

IIRC, there was a long-term goal to replace headless_shell with a flag option for the normal chromium binary. However, a critical part of the value of headless_shell is the lack of requirement for graphics components.

Did this work before? N/A 

Chrome version: N/A  Channel: dev
OS Version: N/A
Flash Version: N/A
 

Comment 1 by lem...@gmail.com, May 7 2017

Whoops, the error is:


test@worker-4:~# chromium-browser --headless --remote-debugging-port=9222  --disable-gpu
/usr/lib/chromium-browser/chromium-browser: error while loading shared libraries: libXcomposite.so.1: cannot open shared object file: No such file or directory.

I can't resolve /just/ that issue, as the workaround for getting chromium installed resulted in a broken package system. I manually installed things until I hit a dependency for libcups, at which point I gave up (this computer does not, and never will have a printer. Why is cups *required*?

Labels: Needs-Milestone

Comment 3 by grt@chromium.org, May 29 2017

Labels: -OS-Windows OS-Linux
OS->Linux

Comment 4 by ajha@chromium.org, May 30 2017

Labels: Proj-Headless

Comment 5 by ajha@chromium.org, Jun 14 2017

Labels: TE-NeedsTriageHelp
Cc: skyos...@chromium.org
Components: Internals>Headless
Status: WontFix (was: Unconfirmed)
That .deb binary is just the regular Chrome browser, so it requires the same GUI packages normal Chrome does. Note that a desktop environment doesn't actually have to be present -- just the shared libraries need to be there.

If you want a binary with fewer dependencies, you can build the Headless Shell application manually following these instructions:

https://chromium.googlesource.com/chromium/src/+/lkgr/headless/README.md#Usage-as-a-C_library

Sign in to add a comment