[REGRESSION]: getting "Protocol error (Target.setDiscoverTargets): Target closed" after upgrading from v0.10 on CentOS7
See original GitHub issueTook awhile to figure out why this is. Seems that in one of the newer chromium releases upgrade cups which doesn’t play nice with CentOS7. Ultimately the solution is to build cups from source:
wget https://github.com/apple/cups/releases/download/release-1.7.5/cups-1.7.5-source.tar.gz
yum install -y rpm-build rpmdevtools gcc gcc-c++ libgcrypt-devel gnutls-devel pam-devel dbus-devel avahi-devel
yum erase cups-libs # if you're upgrading, this will remove gtk
rpmdev-setuptree
rpmbuild -ta --without libusb1 cups-1.7.5-source.tar.gz
yum install -y ~/rpmbuild/RPMS/x86_64/cups-libs-1.7.5-1.x86_64.rpm gtk3
Making an issue for future readers and since I’m not entirely sure how you’d like to go about updating the CentOS guide
Issue Analytics
- State:
- Created 4 years ago
- Reactions:2
- Comments:6 (2 by maintainers)
Top Results From Across the Web
(Puppeteer) Protocol error (Target.setDiscoverTargets)
The tab is visible but the page hasn't been loaded yet, or is going to be replaced due to the initial load of...
Read more >Puppeteer - Protocol error (Page.navigate): Target closed
The Target closed exception is thrown when you are trying to run a function, but the target (tab) was already closed.
Read more >[7.5.0] Problem with reporting feature (dependencies most likely)
Now, it fails with main error. Error spawning Chromium browser: [Error: Protocol error (Target.setDiscoverTargets): Target closed.].
Read more >Playwright v1.2.0 release notes (2020-07-07) | LibHunt
#1140 - [REGRESSION]: getting "Protocol error (Target.setDiscoverTargets): Target closed" after upgrading from v0.10 on CentOS7
Read more >Protocol error (Page.printToPDF): Target closed. - jsreport forum
I Seem to be getting this error quite a lot after updating to version 2.5.0: Protocol error (Page.printToPDF): Target closed.
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Apparently a newer revision fixes the issue https://support.google.com/chrome/thread/29660240?hl=en&msgid=33421825
I am getting this on
Ubuntu 16.04.5 LTS
. The chromium version downloaded isChromium 82.0.4057.0
.Gives
EDIT: This fault happened to me because I had
headless: false,
when running playwright on a remote ssh host. I assume in this case it is expected to not work, but the actual error message shown could be much better?