I have a problem with chromium when I run my tests through the puppeteer.
What happens is that my tests require the microphone to be enabled the moment I log in to the application, even after adding:
'--use-fake-ui-for-media-stream', '--no-sandbox', '--disable-setuid-sandbox'] : ['--use-fake-ui-for-media-stream'
Before working normally, after changing the machine it stopped working and I don't know if it is related to the version of the chromium that is started:
This is the version of chromium when testing starts:
Version 77.0.3844.0
And my version of the puppeteer is:
```"puppeteer": "^1.19.0"````
Has anyone ever experienced this? If so, how do I update the chromium?
Thanks,
I am attempting to use Chrome v60.0.3093.0 (Canary) with Selenium. I would like to also trying using it as a headless implementation. I was wondering if there is a version of the ChromeDriver that supports v60.x for use with selenium-webdriver v2.53.1
(I am doing this with MAC OS X)
You can found chrome and chromedriver versions compatibility information on official chromedriver download page: https://sites.google.com/a/chromium.org/chromedriver/downloads
There is also version selection guide for future updates. Note that this algorithm can be easily automated like in this answer.
selenium standalone server version 2.47.1
Google Chrome driver version - 2.21
Unable to invoke Chrome browser of version greater than 34 with Selenium Web driver.
Can anyone help me how to resolve this.
Downloaded and replaced latest chromedriver.exe and the issue got solved.
Thanks Krishnan Mahadevan.
I am using Ubuntu 12.10. When I try to install themes, extensions for Google Chrome browser from Chrome Web Store it shows the following error:
Could not install package:
'UTILITY_PROCESS_CRASHED_WHILE_TRYING_TO_INSTALL'.
Could not install package because a utility process crashed.
Try restarting Chrome and trying again.
I don't know what to do. And I can't find a proper solution.
This is an unidentified bug in Chrome that made a lot of noise.
Since Chrome developers could not obtain feedback about this bug in time, they marked it as WontFix. So simply waiting for a new version will most probably not help.
Closing for lack of actionable input on the bug.
If someone runs into this, please open a new bug!
You (yes, you, 007!) can actually help everyone running into this bug. Create an issue at crbug.com, mentioning the old issue #401655 and following the debug steps outlined in that issue report, esp. this comment.
That said, the bug is correlated with the kernel version used. Ubuntu 12.10 is no longer supported since 2014-05-16. You probably should move to 14.04 LTS release where this bug is not present.
But if you can't do that for whatever reason, and/or are willing to help Chrome development team, please investigate and make a bug report! And add a comment afterwards pointing to the bug you make.
Thank you for helping us help you help us all.
-- GLaDOS, Portal
version 46.0.2490.80
Fixed utility_process_crashed_while_trying_to_install issue as below:
modify the crx suffix to zip, e.g foo.crx->foo.zip
unzip the foo.zip to one folder, c:\chrome\foo
open chrome://extensions/
enable Developer Mode
"load unzipped extensions" and open c:\chrome\foo
foo.crx loaded successfully.
As crx is zip file and only htm, json, js files included, it's chrome bug and
hope this workaround will help you to avoid uninstall/install/upgrade pain :)
It is a bug in chrome, please downgrade your chrome browser or please wait for new version.
I am trying to run tests in Chrome browser 32.0.1700.76 (latest) using Selenium 2 Webdriver with chromedriver version 2.4
Chrome starts but the string "data;" is displayed in the url bar.
Those test worked fine with a previous Chrome version (28.xxxxx) but I can't downgrade Chrome.
Can anyone suggest me how can I solve the problem?
You need to either upgrade the ChromeDriver you are using or find a way to downgrade Chrome.
The basic principle of the issue is that the ChromeDriver v2.4's support of the most recent versions of Chrome is non-existent.
You get similar issues with Firefox, an upgrade will sometimes break the tests.