I'd like to set up Chrome in headless mode and the ChromeDriver for Selenium testing on my PythonAnywhere instance. I can't find any instructions on how to sort this out. Does anyone have any advice/pointers to docs please?
Meanwhile it works: you simply have to write an email to the PythonAnywhere support and they will enable it for your account (here are some details).
PythonAnywhere dev here -- unfortunately Chrome (headless or otherwise) doesn't work in our virtualization environment right now, so it won't work :-(
[edit] ...but now it does! See #Ralf Zosel's answer for more details.
Related
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 having trouble debugging my web project using the Chrome Browser. I can only use IE to do my debugging. I did some "googling" to resolve this problem, and came across a few Microsoft threads that said to update to the latest version of VS2017, which I did. I use version 15.9.13 and Visual Studio 2017 tells me I am "up to date" when I check for further updates.
When I first updated VS 2017, it started working, and I could debug using Chrome (finally!). But now it has stopped working again.
I saw in other threads where people suggested deleting the .vs folder, which I did, but had no luck with that.
Google Chrome is up to date at Version 75.0.3770.100
I debug and run my application as "Administrator" so that shouldn't be the problem either. I also close all browsers before running the debugger, so Chrome isn't running elsewhere when I try to debug.
Is there any explanation why Chrome cannot launch when using debugger? I would really like to use Chrome because of it's superior "dev tools" and inspection tools. Any suggestions? Was sad to have it working only one day.
Having configured the same environment like yours(VS version and Chrome version) but can't reproduce the issue.I would think if something is broken in VS or maybe third-party extension is the causes this issue.
Please try:
VS repair and a reinstall of Chrome(don't forget to backup the bookmarks)
Uninstall or disable third-party vs extensions, this won't take effect until restart vs
Navigate to %LocalAppData%\Microsoft\VisualStudio\15.xxx directory, delete all ComponentModelCache folders in all 15.xxx folders.
Open your project in vs, changed the target browser from Chrome to IE. Then F5 and wait until it is finish. Stop it and change the browser back to Chrome. After that the error disappeared.
Also, create a new asp.net web app and debug it with Chrome browser to check if the issue persists. Hope it helps.
We have few local sites with unsafe ports i.e. 100,101,102,103. Those were working fine on google chrome with explicitly-allowed-ports in the shortcut target. Suddenly they have stopped working for new update version of chrome v. 72.0.3626.109.
I am not able to find any solution to it. Even if I install the old version of chrome it gets updated to the new one. Can you please guide me what to do. I cant change the mapping of websites as there are limitations. Please guide.
This bug was already found in the Canary branch:
https://bugs.chromium.org/p/chromium/issues/detail?id=916025
Temporary solution is to disable the "Enable Network Service" option in the chrome://flags settings
I installed Tikiwiki LTS version 16 on Ubuntu 14.04.
I have a problem with Google Chrome when I try to login to the wiki.
It is a problem of dealing with cookies, I think. It passed in Firefox.
Any solutions?
Please give more details so you can be helped.
You are using 16.0 or 16.2 ? (last stable)
Do you see http://yourdomain/tiki-login.php on Chrome ?
When you fill the 2 fields and submit what happen ?
If you can log in with Firefox check the cookie settings on the login control panel, maybe the path or something got set wrong.
Try switching remember me off completely maybe?
Also check if sefurl is enabled, and if so try disabling that too.
The tiki.org sites all run on tiki 16.x latest and we haven't heard of any problems like this.
I found the solution, Tikiwiki need to be runned using a virtual host.
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.