Closed monteslu closed 3 months ago
Hello Luis, I followed the same process on a PI 4B and got the same results. Any help from the developer would be appreciated.
temporary workaround until this gets fixed
in app.py
comment out:
# from selenium import webdriver
# from selenium.webdriver.chrome.options import Options
# from selenium.webdriver.chrome.service import Service
# from selenium.webdriver.common.by import By
# from selenium.webdriver.common.keys import Keys
# from selenium.webdriver.support import expected_conditions as EC
# from selenium.webdriver.support.ui import WebDriverWait
and this:
# if not args.hide_splash_screen:
# if platform == "raspberry_pi":
# service = Service(executable_path='/usr/bin/chromedriver')
# else:
# service = None
# options = Options()
# if args.window_size:
# options.add_argument("--window-size=%s" % (args.window_size))
# options.add_argument("--window-position=0,0")
# options.add_argument("--kiosk")
# options.add_argument("--start-maximized")
# options.add_experimental_option("excludeSwitches", ['enable-automation'])
# driver = webdriver.Chrome(service=service, options=options)
# driver.get(f"{k.url}/splash" )
# driver.add_cookie({'name': 'user', 'value': 'PiKaraoke-Host'})
# # Clicking this counts as an interaction, which will allow the browser to autoplay audio
# wait = WebDriverWait(driver, 60)
# elem = wait.until(EC.element_to_be_clickable((By.ID, "permissions-button")))
# elem.click()
It will let you launch the server, then you can open the browser to the URL it shows you on the command line.
This was fixed a couple of days ago. It's a selenium release incompatibility. A git pull
and rerun of ./setup.sh
of the latest master branch should address the issue.
To check, ensure requirements.txt contains selenium==4.21.0
if not, you need to pull the update and rerun setup
Perhaps there can be an option to start headless and we can just fire up the browser ourselves?
There is: ./pikaraoke.sh --headless
See ./pikaraoke.sh --help
for all options
dup of #346
Describe the bug
Error running on rpi 400 latest raspberry pi OS fully updated
To Reproduce Steps to reproduce the behavior:
Expected behavior Should load server and fire up browser
Screenshots If applicable, add screenshots to help explain your problem.
Platform (please complete the following information):
Additional context
Perhaps there can be an option to start headless and we can just fire up the browser ourselves?