Skip to content

Subject: ❗ WebDriver Manager selects incorrect file (THIRD_PARTY_NOTICES.chromedriver) as ChromeDriver executable — Fails with Exec Format Error #699

@iamsudheerkabeer

Description

@iamsudheerkabeer

Description:

I’m encountering a critical error when using WebDriver Manager to launch ChromeDriver on my Linux system. The issue appears to be that the WebDriver Manager selects an incorrect file (THIRD_PARTY_NOTICES.chromedriver) as the executable, leading to the following failure:

💥 [2025-08-14 23:33:20] ERROR: Failed to launch Chrome Driver: [Errno 8] Exec format error: '/home/allan/.wdm/drivers/chromedriver/linux64/138.0.7204.183/chromedriver-linux64/THIRD_PARTY_NOTICES.chromedriver'
💥 [2025-08-14 23:33:20] CRITICAL: Re-login failed. Shutting down.

This file is not an executable, but rather a documentation file included with the driver. Somehow, WebDriver Manager is mistakenly identifying it as the driver binary.


System Details:

  • OS: Linux (64-bit)
  • ChromeDriver version: 138.0.7204.183
  • WebDriver Manager location:
    /home/allan/.wdm/drivers/chromedriver/linux64/138.0.7204.183/chromedriver-linux64/
  • Incorrect file used: THIRD_PARTY_NOTICES.chromedriver
  • Expected file: chromedriver (the actual binary)

Steps to Reproduce:

  1. Use WebDriver Manager to auto-download the ChromeDriver on a Linux machine.
  2. Run a Selenium script that attempts to launch the browser.
  3. Observe that the manager selects the wrong file (THIRD_PARTY_NOTICES.chromedriver).
  4. The process fails with an Exec format error.

Expected Behavior:

WebDriver Manager should correctly identify and use the chromedriver binary, not any other file in the driver directory.


Suggested Fix:

Please implement stricter logic to filter non-executable files and ensure that the selected file is:

  • Named chromedriver (on Linux/macOS) or chromedriver.exe (on Windows).
  • Actually an executable binary.

Also, a check for valid ELF (or PE on Windows) headers could prevent these errors.


This issue is blocking automation workflows and causing full shutdowns on failure, so a fix would be greatly appreciated.

Please let me know if additional logs or testing help is needed.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions