-
-
Notifications
You must be signed in to change notification settings - Fork 8.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[🐛 Bug]: NoSuchDriverException under Windows if user home contains special characters #13653
Comments
@ivy-lmu, thank you for creating this issue. We will troubleshoot it as soon as we can. Info for maintainersTriage this issue by using labels.
If information is missing, add a helpful comment and then
If the issue is a question, add the
If the issue is valid but there is no time to troubleshoot it, consider adding the
If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C),
add the applicable
After troubleshooting the issue, please add the Thank you! |
@bonigarcia I thought this was fixed a while ago, do you know? |
The same change has been done for the java bindings. |
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. |
@diemol Do we need to check Ruby/Python/JS for this as well? |
I am not aware of that. |
What happened?
Under Windows, it is possible that the user's home directory contains special characters such as ü, ä and ö etc..
With the user home
C:\Users\DieLücke
the following line of code in Java leads to NoSuchDriverException:WebDriver driver = new ChromeDriver();
With
C:\Users\hello
the same code works fine.How can we reproduce the issue?
Relevant log output
Operating System
Windows
Selenium version
Java 4.18.1
What are the browser(s) and version(s) where you see this issue?
Chrome, Firefox
What are the browser driver(s) and version(s) where you see this issue?
ChromeDriver, GeckoDriver
Are you using Selenium Grid?
No response
The text was updated successfully, but these errors were encountered: