New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 795759 link

Starred by 2 users

Issue metadata

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



Sign in to add a comment

Discrepancy between dependencies required by google-chrome-unstable and google-chrome-stable

Reported by globinos...@gmail.com, Dec 18 2017

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3270.0 Safari/537.36

Steps to reproduce the problem:
1. set `deb [arch=amd64] http://dl.google.com/linux/chrome/deb/ stable main` as a repo
2. run `apt update`
3. install `google-chrome-unstable`
4. run `google-chrome-unstable`

What is the expected behavior?
chrome unstable run without error.

What went wrong?
The dependencies for Unstable are not met making chrome not running (libgconf-2-4 is required by unstable but absent from the dependencies).

Here the message:
`
error while loading shared libraries: libgconf-2.so.4: cannot open shared object file: No such file or directory
`

The dependencies for google-chrome-stable contain `libgconf-2-4 (>= 3.2.5)` that is also required by google-chrome-unstable.

To check the dependencies for google-chrome-stable and google-chrome-unstable, run `apt show google-chrome-stable` and `apt show google-chrome-unstable`

Did this work before? N/A 

Chrome version: 65.0.3294.5-1  Channel: n/a
OS Version: ubuntu 17.10
Flash Version: 

Here are the dependencies diff between the 2 packages: 

Stable have gconf-service, libgconf-2-4 (>= 3.2.5) that Unstable do not have.
Unstable do not run without : libgconf-2-4

Unstable have libatk-bridge2.0-0 that Stable do not have (but seems not required to run)
 
FWIW, we're seeing Puppeteer devs running into this as well trying to run headless in Docker:

https://github.com/GoogleChrome/puppeteer/issues/1627

Cc: dvallet@chromium.org
dvallet@ is there someone on the headless team that can take a look at this?
Could we confirm if this is something that was added by headless? 
I see several references of Chrome neading libgconf-2-4 and I don't remember adding this dependency directly in headless
Cc: skyos...@chromium.org
FWIW, Unbuntu has google-chrome-unstable 66 now and I no longer see this error when running in a Docker container.

https://www.ubuntuupdates.org/package/google_chrome/stable/main/base/google-chrome-unstable

Hmm, weird, if anything headless should have removed the dependency on libgconf.

> FWIW, Unbuntu has google-chrome-unstable 66 now and I no longer see this error when running in a Docker container

Ah, should we close this then?
Status: WontFix (was: Unconfirmed)
Closing this as it no longer appears to be necessary with the latest google-chrome-unstable build for ubuntu. Please reopen/comment if someone still sees issues.

Sign in to add a comment