[BUG] Using libsoup2 and libsoup3 in the same process is not supported.

[lunika]

System info

• Playwright Version: [v1.38.0]
• Operating System: Docker image mcr.microsoft.com/playwright:v1.38.0-jammy
• Browser: [WebKit]
• Other info: The image is ran on circle-ci. The same image as no problem with firefox and chrome browser. We don't have any issue running the same code locally.

A similar issue exists and is closed : #26653
This issue should be fixed with Playwright 1.38.0 but we still have it but only with the safari browser.

If you clone the repo, you should not have any error locally, you can test by running the following command :

$ make bootstrap
$ make e2e

You can also check the result on circle-ci with the following link : https://app.circleci.com/pipelines/github/openfun/marsha/14253/workflows/28f88761-d423-43c1-b4c1-4702c879a09f/jobs/421630

Both libsoup 2 and 3 are indeed installed in this image:

$ docker run --rm -it mcr.microsoft.com/playwright:v1.38.0-jammy /bin/bash -c "dpkg -l | grep libsoup"
ii  libsoup-3.0-0:amd64                  3.0.7-0ubuntu1                          amd64        HTTP library implementation in C -- Shared library
ii  libsoup-3.0-common                   3.0.7-0ubuntu1                          all          HTTP library implementation in C -- Common files
ii  libsoup2.4-1:amd64                   2.74.2-3                                amd64        HTTP library implementation in C -- Shared library
ii  libsoup2.4-common                    2.74.2-3                                all          HTTP library implementation in C -- Common files

If libsoup2 is removed (just for testing), it also deletes gstreamer plugins that seems used by webkit.

Source code

Link to the GitHub repository with the repro

https://github.com/openfun/marsha/blob/804a873683fa650623e0c48e92313b072d31f3bf/.circleci/config.yml#L620-L747

This commit is part of this PR: openfun/marsha#2433

Expected

The test suite should run without issue with libsoup. Libsoup compatibility issue is fixed with version 1.38.0 and we don't have this issue with firefox and chrome browsers.

[yury-s]

Yeah, this issue is supposed to have been fixed in #26653 but looks like it is not. Does it reproduce inside mcr.microsoft.com/playwright:v1.38.0-jammy outside of circle ci?

[lunika]

No we reproduce it only on circleci.

[tobbsel]

We have the same issue in a Jenkins pipeline. We use mcr.microsoft.com/playwright:v1.38.1-jammy as a base image.
Using
FROM mcr.microsoft.com/playwright:v1.38.1-jammy
RUN apt-get remove -y libsoup2.4
in our docker image fixes our problem for now. Not sure if the mentioned gstreamer plugins are actually no problem or if they just aren't necessary in our concrete use-case. (We also use webkit.)

[yury-s]

Yeah, gstreamer plugins are needed in some scenarios that involve videos.

[lunika]

And this is our case indeed

[tolu]

I've been seeing this same issue in GitLab CI.
Our tests do not include video (even though our app does) but was resolved via this before_script: (thanks to @tobbsel comment 🙇 )

playwright_tests:
  stage: e2e-test
  image: mcr.microsoft.com/playwright:v1.38.1-jammy
  before_script:
    - apt-get remove -y libsoup2.4
  script:
    - npm ci
    - npm run test:e2e

[americos]

FWIW I have the same issue in Semaphore CI. Also using mcr.microsoft.com/playwright:v1.38.1-jammy

[oleksii-fedorenko-94]

Same on Buildkite CI using mcr.microsoft.com/playwright:latest. So it seems the issue exists even in 1.39 version.

[mxschmitt]

Steps to reproduce:

1. Create a Ubuntu 20.04 VM
2. Install Docker & run 22.04 PW Docker container with WebKit:

   curl -L get.docker.com | sh
   docker run --rm -it mcr.microsoft.com/playwright:v1.39.0-jammy /bin/bash
   cd
   npm init playwright -y testpw
   # Press Enter a few times
   cd testpw
   npx playwright test --project=webkit

Expected: It works
Actual: It does not

    Error: browserType.launch: Browser closed.
    ==================== Browser output: ====================
    <launching> /ms-playwright/webkit-1921/pw_run.sh --inspector-pipe --headless --no-startup-window
    <launched> pid=963
    [pid=963][err] 
    [pid=963][err] (MiniBrowser:985): GStreamer-WARNING **: 13:40:22.894: External plugin loader failed. This most likely means that the plugin loader helper binary was not found or could not be run. You might need to set the GST_PLUGIN_SCANNER environment variable if your setup is unusual. This should normally not be required though.
    [pid=963][err] 
    [pid=963][err] (MiniBrowser:985): libsoup-ERROR **: 13:40:23.080: libsoup3 symbols detected. Using libsoup2 and libsoup3 in the same process is not supported.
    [pid=963][err] /ms-playwright/webkit-1921/pw_run.sh: line 24:   985 Trace/breakpoint trap   (core dumped) WEBKIT_FORCE_COMPLEX_TEXT="1" "$MINIBROWSER" "$@"
    [pid=963] <process did exit: exitCode=133, signal=null>
    [pid=963] starting temporary directories cleanup
    =========================== logs ===========================
    <launching> /ms-playwright/webkit-1921/pw_run.sh --inspector-pipe --headless --no-startup-window
    <launched> pid=963
    [pid=963][err] 
    [pid=963][err] (MiniBrowser:985): GStreamer-WARNING **: 13:40:22.894: External plugin loader failed. This most likely means that the plugin loader helper binary was not found or could not be run. You might need to set the GST_PLUGIN_SCANNER environment variable if your setup is unusual. This should normally not be required though.
    [pid=963][err] 
    [pid=963][err] (MiniBrowser:985): libsoup-ERROR **: 13:40:23.080: libsoup3 symbols detected. Using libsoup2 and libsoup3 in the same process is not supported.
    [pid=963][err] /ms-playwright/webkit-1921/pw_run.sh: line 24:   985 Trace/breakpoint trap   (core dumped) WEBKIT_FORCE_COMPLEX_TEXT="1" "$MINIBROWSER" "$@"
    [pid=963] <process did exit: exitCode=133, signal=null>
    [pid=963] starting temporary directories cleanup
    ============================================================

Main issue to investigate: Why does it work when Docker Host Ubuntu version matches and does not if its Ubuntu 20.04?

Note: If a user runs the Docker container with --privileged it works as expected.