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

google-chrome: add new dep on at_spi2_atk #33062

Merged
merged 1 commit into from Dec 31, 2017
Merged

google-chrome: add new dep on at_spi2_atk #33062

merged 1 commit into from Dec 31, 2017

Conversation

andrewjss
Copy link

Fixes #32978

Motivation for this change

Current google-chrome beta and fail to run because of a failure to open libatk-bridge-2.0.so.0.

Things done
  • Build on NixOS
  • Tested execution of google-chrome{stable,beta,unstable}
  • Fits CONTRIBUTING.md

@FRidh
Copy link
Member

FRidh commented Dec 27, 2017

cc @msteen

@msteen
Copy link
Contributor

msteen commented Dec 27, 2017

Seems good to me.

BTW, I was just the one who packaged Google Chrome first. I would not consider myself an actual maintainer of it. I do not test new releases or have any rights to merge, so maybe someone else should become the maintainer?

@joachifm joachifm merged commit 8d2b39f into NixOS:master Dec 31, 2017
@joachifm
Copy link
Contributor

@msteen as long as you care somewhat about the package & can answer questions about it, I think it makes sense for you to be a maintainer. For something like this we should have an "active" maintainer as well, though ...

@YorikSar
Copy link
Contributor

Please backport this to stable, otherwise today's update to 64 will break Google Crhome there entirely.

cc @bendlas @vcunat

@andrewjss
Copy link
Author

What needs to happen? Just make a new pull request to release-17.09? The patch cherry-picks cleanly onto that branch.

@joachifm
Copy link
Contributor

You can create a patch with cherry-pick -x and submit a PR against the release branch

@andrewjss
Copy link
Author

Like this?

#34283

@shospodarets
Copy link

shospodarets commented Jan 26, 2018

Installed the Chrome on Cent OS using:

$ curl https://intoli.com/install-google-chrome.sh | bash
# from https://intoli.com/blog/installing-google-chrome-on-centos/

The version:

$ google-chrome-stable --version
Google Chrome 64.0.3282.119

The issue:

> Cannot start ChromeHeadless
> .../node_modules/puppeteer/.local-chromium/linux-526987/chrome-linux/chrome: error while loading shared libraries: libatk-bridge-2.0.so.0: cannot open shared object file: No such file or directory

Not fully sure, the issue is expected to be fixed soon (next version of google-chrome-stable), or the dependency should be added?
Discussed in puppeteer/puppeteer#765 @sangaline

@andrewjss
Copy link
Author

Is that a centos issue, a nix issue, a node issue, or a puppeteer issue?
If your 'google-chrome-stable --version' works, you have all the dependencies it needs.

@sangaline
Copy link

The google-chrome-stable is setting LD_LIBRARY_PATH=/opt/google/chrome/lib and using the /opt/google/chrome/chrome executable (which has been patched to use a relocated linker in /opt/google/chrome/lib/). If the Chromium binary that Puppeteer downloaded is being used then it won't know where to find these dependencies. You'll likely need to set LD_LIBRARY_PATH and use the /opt/google/chrome/chrome executable with Puppeteer in order to get it to work.

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

Successfully merging this pull request may close these issues.

None yet

9 participants