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

[Bug]: webkit launch ends in failure on Ubuntu 24.04 #31615

Closed
radekBednarik opened this issue Jul 9, 2024 · 4 comments
Closed

[Bug]: webkit launch ends in failure on Ubuntu 24.04 #31615

radekBednarik opened this issue Jul 9, 2024 · 4 comments

Comments

@radekBednarik
Copy link

radekBednarik commented Jul 9, 2024

Version

1.45.1

Steps to reproduce

  1. clone repo [email protected]:radekBednarik/pw-repro-webkit-fail.git
  2. npm install
  3. npx playwright install --with-deps
  4. npx playwright test

Expected behavior

Example tests are expected to PASS.

Actual behavior

  1) [webkit] › example.spec.ts:3:5 › has title ────────────────────────────────────────────────────

    Error: browserType.launch: Target page, context or browser has been closed
    Browser logs:

    <launching> /home/radek/.cache/ms-playwright/webkit-2035/pw_run.sh --inspector-pipe --headless --no-startup-window
    <launched> pid=34434
    [pid=34434][err] /home/radek/.cache/ms-playwright/webkit-2035/minibrowser-wpe/bin/MiniBrowser: error while loading shared libraries: libvpx.so.7: cannot open shared object file: No such file or directory
    [pid=34434] <process did exit: exitCode=127, signal=null>
    [pid=34434] starting temporary directories cleanup
    Call log:
      - <launching> /home/radek/.cache/ms-playwright/webkit-2035/pw_run.sh --inspector-pipe --headless --no-startup-window
      - <launched> pid=34434
      - [pid=34434][err] /home/radek/.cache/ms-playwright/webkit-2035/minibrowser-wpe/bin/MiniBrowser: error while loading shared libraries: libvpx.so.7: cannot open shared object file: No such file or directory
      - [pid=34434] <process did exit: exitCode=127, signal=null>
      - [pid=34434] starting temporary directories cleanup

Additional context

  • Running on WSL under Win11

Environment

System:
    OS: Linux 5.15 Ubuntu 24.04 LTS 24.04 LTS (Noble Numbat)
    CPU: (32) x64 AMD Ryzen 9 7950X 16-Core Processor
    Memory: 28.97 GB / 30.90 GB
    Container: Yes
  Binaries:
    Node: 20.15.0 - ~/.nvm/versions/node/v20.15.0/bin/node
    npm: 10.7.0 - ~/.nvm/versions/node/v20.15.0/bin/npm
    pnpm: 9.3.0 - /mnt/c/Program Files/nodejs/pnpm
    bun: 1.1.4 - ~/.bun/bin/bun
  IDEs:
    VSCode: 1.90.2 - /mnt/c/Users/bedna/AppData/Local/Programs/Microsoft VS Code/bin/code
  Languages:
    Bash: 5.2.21 - /usr/bin/bash
  npmPackages:
    @playwright/test: ^1.45.1 => 1.45.1
@mxschmitt
Copy link
Member

I tried to reproduce doing the following, but was not able to:

wsl --install --distribution Ubuntu-24.04
sudo su
curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.39.7/install.sh | bash
source /root/.bashrc
nvm install 20
cd
git clone https://github.com/radekBednarik/pw-repro-webkit-fail
cd pw-repro-webkit-fail
npm install
npx playwright install --with-deps
npx playwright test

What am I doing different? Did you update your Ubuntu to 24?

Could you try

npx playwright uninstall
npx playwright install --with-deps

@radekBednarik
Copy link
Author

@mxschmitt hello, yes, that worked! looks like update from 22.04 to 24.04 broke something. Thanks and this can be closed.

@mxschmitt
Copy link
Member

(probably you still had our 22.04 version of WebKit installed, so re-installing the browser will download the 24.04 version of it).

@juliaogris
Copy link

I too have misbehaving webkit tests on Ubuntu noble (24.04) after upgrade, however

npx playwright uninstall
npx playwright install --with-deps

did not fix it for me.

The same tests work fine when run via mcr.microsoft.com/playwright:v1.48.0-noble docker image.

I cannot create a minimal reproduce of my system setup and I'm completely in the dark how to best debug this. Here's one thing I've tried:

$ DEBUG=pw:browser npx playwright test
...

w:browser [pid=24665][err] ** (MiniBrowser:24685): CRITICAL **: 15:25:02.402: WebKitWebView is-controlled-by-automation set but automation is not allowed in the context, falling back to default session. +0ms
  pw:browser [pid=24665][err] MESA: error: zink: could not create swapchain +116ms
  pw:browser [pid=24665] <gracefully close start> +30s
  pw:browser [pid=24665] <process did exit: exitCode=0, signal=null> +11ms

Any pointers much appreciated.

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