question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

[BUG] Protocol error when test runner attempts to open new page on juggler - Ubuntu 22.04

See original GitHub issue

Context:

  • Playwright Version: @latest
  • Operating System: Kubernetes, Jenkins agent, Ubuntu 22.04
  • Node.js version: LTS
  • Browser: Firefox
  • Extra: cannot provide details, or snippets of actual code, since it is proprietary

Code Snippet

Help us help you! Put down a short code snippet that illustrates your bug and that we can run and debug locally. For example:

Describe the bug

When running Jenkins pipeline job, on Firefox the test will not run, since there is an error when test runner will attempt to open new page. Log:

> npx playwright test -g "XXX" --config=configs/test.pwConfig.ts
15:40:29  
15:40:30  
15:40:30  Running 3 tests using 1 worker
15:40:52  ·×F·
15:40:52  
15:40:52    1) [desktop firefox] › XXX:32:3 › login › XXX 
15:40:52  
15:40:52      browserContext.newPage: Protocol error (Browser.newPage): receiver.addEventListener is not a function awaitEvent/<@chrome://juggler/content/Helper.js:27:16
15:40:52      awaitEvent@chrome://juggler/content/Helper.js:26:12
15:40:52      newPage@chrome://juggler/content/TargetRegistry.js:329:20

Add any other details about the problem here.

Issue Analytics

  • State:closed
  • Created a year ago
  • Comments:15 (7 by maintainers)

github_iconTop GitHub Comments

1reaction
dgozmancommented, Oct 20, 2022

@radekBednarik Good news! I found an issue in Firefox instrumentation and landed a fix. So, this should be fixed with the next v1.28.0 release. Meanwhile, you can try @playwright/test@next tomorrow to check it out on the canary release.

0reactions
dgozmancommented, Nov 7, 2022

@radekBednarik This looks like a different issue, unfortunately. The logs are not really helpful. Could you please file a new issue, run with DEBUG=pw:protocol and attach the logs? That said, the chances to fix it without a local repro are slim.

Read more comments on GitHub >

github_iconTop Results From Across the Web

Call for Testing: Ubuntu 22.04 LTS and Ubuntu Flavours
Hi everyone were about 3 weeks away from the Ubuntu 22.04 LTS release. As a community we need to test and find bugs...
Read more >
Disk by UUID not detected (initramfs), boot failure - Ask Ubuntu
My issue occurred while juggling with a virtual installation based on a copied disk image. This resulted in a changed uuid and the...
Read more >
I am not able to open katalon . i am having error
I am not able to open katalon in Ubuntu 22.04 . on first time login. i have entered my login credentials . it...
Read more >
An X11 apologist tries Wayland - Hacker News
Today, with Wayland now default, I can't change it at all when running Ubuntu or ElementaryOS. You can say this is a GNOME...
Read more >
glibcxx_3.4.30 install | The AI Search Engine You Control
Strict. Open links in a new tab ... Running: conda install -c conda-forge gcc=12.1.0. Fixed the error for me. Open side ... Then...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found