[🐛 Bug]: Selenium Manager should support Edge management using RPM in Linux

[bonigarcia]

What happened?

Currently, Selenium Manager uses the DEB package in Linux for Edge management. Nevertheless, this package is not compatible with the Red Hat Linux distros (e.g., Fedora). That should be improved in the Selenium Manager logic since Edge is also shipped as RPM: https://www.microsoft.com/en-us/edge/download?form=MA13FJ

How can we reproduce the issue?

Run this command in a RPM-based Linux system:

./selenium-manager --trace --browser edge --force-browser-download

Relevant log output

[2024-02-27T10:56:10.769Z TRACE] Artifacts: [Artifact { artifact_name: "deb", location: "https://packages.microsoft.com/repos/edge/pool/main/m/microsoft-edge-stable/microsoft-edge-stable_122.0.2365.52-1_amd64.deb", hash: "8542F251416132389AADE5EBD734F29F29275727ABB78E4DD07E2247CC28191C", hash_algorithm: "SHA256", size_in_bytes: 165968574 }]
[2024-02-27T10:56:10.769Z DEBUG] Downloading edge 122.0.2365.52 from https://packages.microsoft.com/repos/edge/pool/main/m/microsoft-edge-stable/microsoft-edge-stable_122.0.2365.52-1_amd64.deb
[2024-02-27T10:56:10.769Z TRACE] Downloading https://packages.microsoft.com/repos/edge/pool/main/m/microsoft-edge-stable/microsoft-edge-stable_122.0.2365.52-1_amd64.deb to temporal folder "/tmp/selenium-manager9CpqoP"
[2024-02-27T10:56:10.962Z TRACE] File to be downloaded: microsoft-edge-stable_122.0.2365.52-1_amd64.deb
[2024-02-27T10:56:10.962Z TRACE] File downloaded to temporal folder: /tmp/selenium-manager9CpqoP/microsoft-edge-stable_122.0.2365.52-1_amd64.deb
[2024-02-27T10:56:49.706Z TRACE] The detected extension of the compressed file is deb
[2024-02-27T10:56:49.706Z TRACE] Extracting from /tmp/selenium-manager9CpqoP/microsoft-edge-stable_122.0.2365.52-1_amd64.deb to /tmp/selenium-manager9CpqoP
[2024-02-27T10:56:59.294Z TRACE] Moving extracted files and folders from /tmp/selenium-manager9CpqoP/opt/microsoft/msedge to /home/vagrant/.cache/selenium/edge/linux64/122.0.2365.52
[2024-02-27T10:57:00.419Z ERROR] Cross-device link (os error 18)

Operating System

Red Hat Linux (e.g., Fedora)

Selenium version

4.18+

What are the browser(s) and version(s) where you see this issue?

Edge

What are the browser driver(s) and version(s) where you see this issue?

NA

Are you using Selenium Grid?

No

[luisfcorreia]

Hints for fixing

You can read "/etc/os-release" (as regular user) to figure out which Linux Distro is present.

For reference:

Debian 11 (bullseye)

PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

Rocky Linux

NAME="Rocky Linux"
VERSION="9.3 (Blue Onyx)"
ID="rocky"
ID_LIKE="rhel centos fedora"
VERSION_ID="9.3"
PLATFORM_ID="platform:el9"
PRETTY_NAME="Rocky Linux 9.3 (Blue Onyx)"
ANSI_COLOR="0;32"
LOGO="fedora-logo-icon"
CPE_NAME="cpe:/o:rocky:rocky:9::baseos"
HOME_URL="https://rockylinux.org/"
BUG_REPORT_URL="https://bugs.rockylinux.org/"
SUPPORT_END="2032-05-31"
ROCKY_SUPPORT_PRODUCT="Rocky-Linux-9"
ROCKY_SUPPORT_PRODUCT_VERSION="9.3"
REDHAT_SUPPORT_PRODUCT="Rocky Linux"
REDHAT_SUPPORT_PRODUCT_VERSION="9.3"

Fedora Worstation 39

NAME="Fedora Linux"
VERSION="39 (Workstation Edition)"
ID=fedora
VERSION_ID=39
VERSION_CODENAME=""
PLATFORM_ID="platform:f39"
PRETTY_NAME="Fedora Linux 39 (Workstation Edition)"
ANSI_COLOR="0;38;2;60;110;180"
LOGO=fedora-logo-icon
CPE_NAME="cpe:/o:fedoraproject:fedora:39"
DEFAULT_HOSTNAME="fedora"
HOME_URL="https://fedoraproject.org/"
DOCUMENTATION_URL="https://docs.fedoraproject.org/en-US/fedora/f39/system-administrators-guide/"
SUPPORT_URL="https://ask.fedoraproject.org/"
BUG_REPORT_URL="https://bugzilla.redhat.com/"
REDHAT_BUGZILLA_PRODUCT="Fedora"
REDHAT_BUGZILLA_PRODUCT_VERSION=39
REDHAT_SUPPORT_PRODUCT="Fedora"
REDHAT_SUPPORT_PRODUCT_VERSION=39
SUPPORT_END=2024-11-12
VARIANT="Workstation Edition"
VARIANT_ID=workstation

[github-actions]

This issue has been automatically locked since there has not been any recent activity since it was closed. Please open a new issue for related bugs.