playwright
playwright copied to clipboard
[Bug]: old fallback selected during install-deps when not using Ubuntu
Version
1.42.1
Steps to reproduce
No minimal repro, as it's a bug in install-deps
- Try running
npx playwright install-deps
on a Linux distro based on Ubuntu 22.04, I used Zorin OS 17.1
Expected behavior
Ubuntu 22.04 should be selected as fallback instead of 20.04. Expected:
BEWARE: your OS is not officially supported by Playwright; installing dependencies for ubuntu22.04-x64 as a fallback.
Actual behavior
BEWARE: your OS is not officially supported by Playwright; installing dependencies for ubuntu20.04-x64 as a fallback.
Installing dependencies...
Switching to root user to install dependencies...
Hit:2 https://brave-browser-apt-release.s3.brave.com stable InRelease
Hit:1 https://packages.microsoft.com/repos/code stable InRelease
Hit:3 http://in.archive.ubuntu.com/ubuntu jammy InRelease
Hit:4 https://pkg.cloudflare.com/cloudflared jammy InRelease
Get:5 http://security.ubuntu.com/ubuntu jammy-security InRelease [110 kB]
Hit:6 http://archive.ubuntu.com/ubuntu jammy InRelease
Get:7 http://in.archive.ubuntu.com/ubuntu jammy-updates InRelease [119 kB]
Hit:8 https://ppa.launchpadcontent.net/obsproject/obs-studio/ubuntu jammy InRelease
Hit:9 https://ppa.launchpadcontent.net/zorinos/apps/ubuntu jammy InRelease
Hit:10 https://packages.zorinos.com/stable jammy InRelease
Hit:11 https://ppa.launchpadcontent.net/zorinos/drivers/ubuntu jammy InRelease
Hit:12 https://ppa.launchpadcontent.net/zorinos/patches/ubuntu jammy InRelease
Hit:13 https://packages.zorinos.com/patches jammy InRelease
Hit:14 https://ppa.launchpadcontent.net/zorinos/stable/ubuntu jammy InRelease
Hit:15 http://in.archive.ubuntu.com/ubuntu jammy-backports InRelease
Hit:16 https://packages.zorinos.com/apps jammy InRelease
Hit:17 https://packages.zorinos.com/drivers jammy InRelease
Fetched 229 kB in 3s (67.6 kB/s)
Reading package lists... Done
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
Note, selecting 'libfontconfig1' instead of 'libfontconfig'
Package ttf-ubuntu-font-family is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
Package ttf-unifont is not available, but is referred to by another package.
This may mean that the package is missing, has been obsoleted, or
is only available from another source
However the following packages replace it:
fonts-unifont
E: Package 'ttf-unifont' has no installation candidate
E: Package 'ttf-ubuntu-font-family' has no installation candidate
E: Unable to locate package libx264-155
E: Unable to locate package libenchant1c2a
E: Unable to locate package libicu66
E: Unable to locate package libvpx6
E: Unable to locate package libwebp6
Failed to install browser dependencies
Error: Installation process exited with code: 100
Additional context
Maybe add an option in the install-deps command for manual fallback version selection?
Environment
System:
OS: Linux 6.5 Zorin OS 17.1 17.1
CPU: (6) x64 AMD Ryzen 5 4500U with Radeon Graphics
Memory: 2.65 GB / 7.14 GB
Container: Yes
Binaries:
Node: 20.11.0 - ~/.nvm/versions/node/v20.11.0/bin/node
npm: 10.4.0 - ~/.nvm/versions/node/v20.11.0/bin/npm
IDEs:
VSCode: 1.87.2 - /usr/bin/code
Languages:
Bash: 5.1.16 - /usr/bin/bash
npmPackages:
@playwright/test: ^1.42.1 => 1.42.1
+1
+1
Is this resolved?
Looks like this requires a similar hack to https://github.com/microsoft/playwright/blob/a28f51a0f31b9499849c481b3658d0985b223c06/packages/playwright-core/src/utils/hostPlatform.ts#L69
We are open to a contribution but don't plan to work on it. I'll close it for now, since this is not a priority for us. Feel free to create a PR and linking to this issue.
Why was this issue closed?
Thank you for your contribution to our project. This issue has been closed due to its limited upvotes and recent activity, and insufficient feedback for us to effectively act upon. Our priority is to focus on bugs that reflect higher user engagement and have actionable feedback, to ensure our bug database stays manageable.
Should you feel this closure was in error, please create a new issue and reference this one. We're open to revisiting it given increased support or additional clarity. Your understanding and cooperation are greatly appreciated.