[🐛 Bug]: Error using user-data-dir= in Chrome 103.0.5060.53

[cjdduarte]

What happened?

When using chrome_options.add_argument('user-data-dir=' in Chrome 103 the error occurs:

Selenium.common.exceptions.WebDriverException: Message: unknown error: unexpected command response
(Session info: chrome=103.0.5060.53)

if I remove this parameter, it works.

How can we reproduce the issue?

from selenium import webdriver
from selenium.webdriver.chrome.service import Service

chrome_options = webdriver.ChromeOptions()
chrome_options.add_argument('user-data-dir=C:\\Perfil')

driver_path = 'chromedriver.exe'
service = Service(driver_path)
driver = webdriver.Chrome(service=service,options=chrome_options)

driver.get("https://google.com")

Relevant log output

elenium.common.exceptions.WebDriverException: Message: unknown error: unexpected command response
  (Session info: chrome=103.0.5060.53)
Stacktrace:
Backtrace:
	Ordinal0 [0x007E6463+2188387]
	Ordinal0 [0x0077E461+1762401]
	Ordinal0 [0x00693D78+802168]
	Ordinal0 [0x00687210+750096]
	Ordinal0 [0x0068675A+747354]
	Ordinal0 [0x00685D3F+744767]
	Ordinal0 [0x0068557C+742780]
	Ordinal0 [0x00699BF3+826355]
	Ordinal0 [0x006ECF6D+1167213]
	Ordinal0 [0x006DC5F6+1099254]
	Ordinal0 [0x006B6BE0+945120]
	Ordinal0 [0x006B7AD6+948950]
	GetHandleVerifier [0x00A871F2+2712546]
	GetHandleVerifier [0x00A7886D+2652765]
	GetHandleVerifier [0x0087002A+520730]
	GetHandleVerifier [0x0086EE06+516086]
	Ordinal0 [0x0078468B+1787531]
	Ordinal0 [0x00788E88+1805960]
	Ordinal0 [0x00788F75+1806197]
	Ordinal0 [0x00791DF1+1842673]
	BaseThreadInitThunk [0x75F7FA29+25]
	RtlGetAppContainerNamedObjectPath [0x77987A9E+286]
	RtlGetAppContainerNamedObjectPath [0x77987A6E+238]

Operating System

Windows 10 and Manjaro

Selenium version

Python (Selenium 4)

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

Chrome 103

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

ChromeDriver 103.0.5060.53

Are you using Selenium Grid?

No response

[github-actions]

@cjdduarte, thank you for creating this issue. We will troubleshoot it as soon as we can.

---

Info for maintainers

Triage this issue by using labels.

If information is missing, add a helpful comment and then I-issue-template label.

If the issue is a question, add the I-question label.

If the issue is valid but there is no time to troubleshoot it, consider adding the help wanted label.

If the issue requires changes or fixes from an external project (e.g., ChromeDriver, GeckoDriver, MSEdgeDriver, W3C), add the applicable G-* label, and it will provide the correct link and auto-close the issue.

After troubleshooting the issue, please add the R-awaiting answer label.

Thank you!

[amark720]

Me too facing this same issue!

OS- Windows 10, Language- Python
Here is the Traceback of my device:

File "C:/Users/gs-2764/PycharmProjects/TestProject/StudyBullet/StudyBullet_Rss_Post.py", line 320, in <module>
   driver.close()
 File "C:\Users\gs-2764\PycharmProjects\TestProject\venv\lib\site-packages\selenium\webdriver\remote\webdriver.py", line 688, in close
   self.execute(Command.CLOSE)
 File "C:\Users\gs-2764\PycharmProjects\TestProject\venv\lib\site-packages\selenium\webdriver\remote\webdriver.py", line 321, in execute
   self.error_handler.check_response(response)
 File "C:\Users\gs-2764\PycharmProjects\TestProject\venv\lib\site-packages\selenium\webdriver\remote\errorhandler.py", line 242, in check_response
   raise exception_class(message, screen, stacktrace)
selenium.common.exceptions.WebDriverException: Message: unknown error: unexpected command response
 (Session info: chrome=103.0.5060.53)

[diemol]

Is this happening only with Chrome 103? Did it happen with Chrome 102?

[dianis55]

+
Having a same problem now

[amark720]

Is this happening only with Chrome 103? Did it happen with Chrome 102?

Not faced this issue in Chrome 102 version. I'm seeing this issue after updating to chrome 103.

[cjdduarte]

Only on 103.
On 102 it works.

[cjdduarte]

I found this:
https://bugs.chromium.org/p/chromedriver/issues/detail?id=4121

[diemol]

Nice, there is already a Chromium issue. I will close this and then you can all follow that one.