• Bug#1099792: chromium 134.0.6998.35-1~deb12u1 into stable-security has

    From Francesco Ballarin@21:1/5 to All on Sat Mar 8 10:10:02 2025
    Source: chromium
    Severity: important
    X-Debbugs-Cc: c.schoenert@t-online.de, dilinger@debian.org, tpearson@raptorengineering.com
    Control: affects -1 python3-selenium
    Control: tags -1 bookworm

    Hi,
    there was a recent upload

    [2025-03-06] Accepted chromium 134.0.6998.35-1~deb12u1 (source amd64 all) into stable-security (Debian FTP Masters) (signed by: Andres Salomon)

    to stable-security which upgraded chromium from 133 to 134. Unfortunately, it seems that such an upgrade has broken python3-selenium, which hasn't been upgraded in stable since 4.8.3+dfsg-1, March 2023.

    Now when using python3-selenium I get
    ========
    Traceback (most recent call last):
    File "", line , in setUp
    self.selenium = webdriver.Chrome(options=chrome_options)
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/usr/lib/python3/dist-packages/selenium/webdriver/chrome/webdriver.py", line 80, in __init__
    super().__init__(
    File "/usr/lib/python3/dist-packages/selenium/webdriver/chromium/webdriver.py", line 104, in __init__
    super().__init__(
    File "/usr/lib/python3/dist-packages/selenium/webdriver/remote/webdriver.py", line 286, in __init__
    self.start_session(capabilities, browser_profile)
    File "/usr/lib/python3/dist-packages/selenium/webdriver/remote/webdriver.py", line 378, in start_session
    response = self.execute(Command.NEW_SESSION, parameters)
    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
    File "/usr/lib/python3/dist-packages/selenium/webdriver/remote/webdriver.py", line 440, in execute
    self.error_handler.check_response(response)
    File "/usr/lib/python3/dist-packages/selenium/webdriver/remote/errorhandler.py", line 245, in check_response
    raise exception_class(message, screen, stacktrace) selenium.common.exceptions.SessionNotCreatedException: Message: session not created
    from unknown error: cannot find Chrome binary
    =========
    while, on the same set up, on March 3 I wasn't getting any error, which to me suggests that the issue is caused by the upgrade from 133 to 134.

    While the bug is due to an upload to stable-security, this isn't reporting a security
    issue per se, rather a usability one.

    How can a working python3-selenium be restored for bookworm users?

    Thanks,
    Francesco

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Francesco Ballarin@21:1/5 to All on Sat Mar 8 11:40:01 2025
    Source: python-selenium
    Followup-For: Bug #1099792
    X-Debbugs-Cc: c.schoenert@t-online.de, dilinger@debian.org, tpearson@raptorengineering.com

    Hi Carsten,

    I'd say it's more the other way around.

    Indeed I was unsure whether to file this under selenium or under chromium.

    I am happy with whatever solution you come up with, including removing python3-selenium from the archive if no better solution is available.

    Thanks,
    Francesco

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)