I think it's unlikely that we will ship separate packages for headless and desktop Chrome.

I am not looking or a separate package. I am looking for the provided .rpm (and possibly .deb) to install all dependencies.

Ok I see.  Which libraries and fonts were missing?

Can you be more specific about what command you used to install the RPM package, and what's missing?

I was already worrying about this when I filed  bug 750947  ...

Our admin installed this on (I think CentOS-latest-stable). He reported that libosmesa.so and "some fonts" were missing when he tried to start `google-chrome --headless` from command line. Note that some websites state you need to use `--disble-gpu` as well; I am not sure if this is still necessary.
Various blogs report having to installing various fonts in order to get this to work. I was hoping that one of the Chrome developers would know what the definitive list is.

FWIW, libosmesa.so is no longer needed now that we have switched to SwiftShader (no need for --disable-gpu either)

Unable to test this issue because of non-availability of linux server machines, hence adding TE-Hardware-Dependency label

An open-source project does not have Linux servers? That is a sad!

The most common use-case for running Chrome-headless is on a build machine. The most common is probably Jenkins, and I do not know anybody who runs Jenkins on bare metal; it is almost always in some sort of virtual environment. The most stripped down virtual environment is a Docker container.
If you can get chrome to install and run in a Docker container, then I am almost certain you have all the other possibilities covered.

Are you using the Google-provided Chrome rpms here? Note that CentOS isn't really officially supported -- see https://groups.google.com/a/chromium.org/d/msg/chromium-dev/E0BJplS2v1w/q8HS6nrXAwAJ

Yes, using the Google-provided .rpm and .deb.

I tested CentOS 7.4.1708 with Chrome 61.0.3163.91. I don't remember when I did this install, but there are about 700 packages on the system. From a VT (not in X), I ran:

google-chrome-stable --headless --remote-debugging-port=9222 https://www.google.com

and it worked.

I realized this was not a pure server image, so I trimmed it down to ~580 packages. I tried removing all the mesa packages that google-chrome-stable didn't depend on, for instance. Still works.

If you still can't get it to work, it may be helpful to attach a text file with the list of packages installed on the CentOS server. I can then try that exact setup.

The install was performed by our admin on a CentOS 7.3.1611. I am not sure if I can reproduce the exact scenario. However, searching the web for "chrome install headless server" (which is what our admin did), you can find multiple blogs / tutorials / whatever that talk about installing several different fonts packages. One such article suggested you need: xfonts-100dpi xfonts-75dpi xfonts-scalable xfonts-cyrillic. Our admin just blasted that in, and after that Chrome worked, so we did not investigate further.

bug 695212 seems very similar
https://bugs.chromium.org/p/chromium/issues/detail?id=695212#c18 says that installing gnu-free-sans-fonts fixed a similar (the same?) issue on CentOS 7.

I have:

ghostscript-fonts
liberation-fonts-common
liberation-sans-fonts
urw-fonts

I don't have any of the suggested fonts.

Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot