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

Latest chromium incompatibility #2

Open
mlagoma opened this issue Sep 26, 2024 · 3 comments
Open

Latest chromium incompatibility #2

mlagoma opened this issue Sep 26, 2024 · 3 comments

Comments

@mlagoma
Copy link

mlagoma commented Sep 26, 2024

I'm hitting errors similar to those in the following issue:
mattsse/chromiumoxide#229

I'm wondering if there's some incompatibility with the current chromium release and the version of chromiumoxide used in this package?

Works locally:
Chromium 127.0.6533.99 Arch Linux

Hitting problems in different remote env:
Chromium 129.0.6668.58 built on Debian GNU/Linux 12 (bookworm)
(was previously working on this env, dont know if chromium version changed)

@Havunen
Copy link

Havunen commented Oct 1, 2024

Those errors appear when the locally installed chromium contains newer code than the version used to compile chromiumoxide

@Massimiliano-solutiontech
Copy link
Owner

The main issue is in how the WS protocol is implemented on Chromium, so there's nothing that we can do besides downgrade to a working version mattsse/chromiumoxide#167

If you are using Debian/Ubuntu you can follow those steps:

wget https://freeshell.de/phd/chromium/jammy/pool/chromium_116.0.5845.179~linuxmint1+victoria/chromium_116.0.5845.179~linuxmint1+victoria_amd64.deb
sudo dpkg -i chromium_116.0.5845.179~linuxmint1+victoria_amd64.deb
sudo apt --fix-broken install
sudo dpkg -i chromium_116.0.5845.179~linuxmint1+victoria_amd64.deb

the chromium version in the above example is, in fact, an example so feel free to download which ever version you prefer and from whatever source you prefer (I know for sure that version is working because I'm using that on a project).
If you have node installed you can use @puppeteer/browsers to download and install Chromium

@Havunen
Copy link

Havunen commented Nov 10, 2024

What do you think if chromiumoxide would change its versioning to be based on chromium cdp protocol revision, it could be probably automated using github flows. Then each user can pick the revision they need

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

3 participants