I have been using Selenium 3.0.0 beta2 with the Firefox 48.0.2 and geckodriverv10.0 for win 64.
The problem is that the browser crashes without closing.
> [Child 10232] ###!!! ABORT: Aborting on channel error.: file c:/builds/moz2_slave/m-rel-w32-00000000000000000000/build/src/ipc/glue/MessageChannel.cpp,
> line 2046
And it passes the test case.
I tried with FF 46.0.9 as well still gives the same error.
According to the geckodriver issue #210, this was caused by mozilla bug 1051567 and will not be resolved in FF48. FF49 is recommended.
I was getting this error with FF48.0.2 on OS X 10.11.6 and geckodriver 0.10.0 with Selenium 3.0.0-beta3. I tested with 49.0b9 and still see the error, but only intermittently. The line number has changed from 2046 to 2052.
I got it to work by using these versions:
Firefox Setup 48.0.2 (32bit)
geckodriver-v0.15.0-win32
JavaSetup8u121 (32bit)
selenium-server-standalone-3.3.1
Related
I'm having issues with vscode on Ubuntu running particular Python code (that seemingly relies on porting or connecting to an external application). The same code will run fine if I execute it directly from an Ubuntu terminal with the same env on the same machine.
Here's a couple of examples.
When I try to initiate vedo.plotter.Plotter() when running from vscode, I get this error:
ERROR: In /work/standalone-x64-build/VTK-source/Rendering/OpenGL2/vtkXOpenGLRenderWindow.cxx, line 1223
vtkXOpenGLRenderWindow (0x5587f7b42cf0): bad X server connection. DISPLAY=Aborted (core dumped)
If I run the same code directly in terminal, it runs fine, so this is an issue with the way vscode is configured, but I can't find any answers online. I've played with a few settings in vscode but with no success.
This seems to be an issue on all vscode installations I have running on Ubuntu (in this case 20.04). Here's the vscode info:
Version: 1.51.0
Commit: fcac248b077b55bae4ba5bab613fd6e9156c2f0c
Date: 2020-11-05T18:16:10.374Z
Electron: 9.3.3
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: 8.3.110.13-electron.0
OS: Linux x64 5.4.0-52-generic snap
Similarly, I'm unable to open up browser windows from vscode (for example plotly fig.show() and selenium driver = webdriver.Chrome(chromedriver) won't open browser windows. I get the following error with selenium:
selenium.common.exceptions.WebDriverException: Message: unknown error: Chrome failed to start: exited abnormally.
(unknown error: DevToolsActivePort file doesn't exist)
Again, this works fine direct from the terminal and everything works fine if run from a Windows or Mac installed vscode, so this is specific to this Ubuntu install.
I'd really appreciate any help!
Jonny
Running TestNG scripts through docker container with standlone-chrome image, at the container level chrome fails to start in Linux machine.
capablities also includes : --disable-dev-shm-usage",--no-sandbox,--headless.
I tried updating the chrome driver but still didn't worked.
org.openqa.selenium.WebDriverException: unknown error: Chrome failed to start: exited abnormally.
(unknown error: DevToolsActivePort file doesn't exist)
(The process started from chrome location /opt/google/chrome/chrome is no longer running, so ChromeDriver is assuming that Chrome has crashed.)
StackOverflow newbie here. Sharing the version of Chrome/ChromeDriver under discussion would help. In any case, we back-leveled to Chrome 78 (+ Driver), and this problem went away. It appears this error "DevToolsActivePort file doesn't exist" was introduced in late builds.
A few gotchas:
Finding an older release may be problematic; we found them here the version that worked for us is Linux_x64_693954_chrome-linux.zip
The chrome-wrapper script should be renamed to google-chrome
The chrome_sandbox executable must be renamed chrome-sandbox and chmodded 4755
Install the matching Chromedriver version 78 (chromedriver_78.0.3904.105)
The problem in omnetpp-5.4.1 installation.
I have successfully done the entire process of downloading OMNeT++. While writing OMNeT++ to enter into the IDE I am getting this error:
An error has occurred. See the log file
/home/abc/MySoftwares/omnetpp-5.4.1/samples/.metadata/.log.
Use OMNeT++ 5.5.1. Recent versions of debian updated java to version 11 which is not compatible with the Eclipse version in omnet 5.4.1.
I am trying to run protractor tests with jenkins, but I couldn't get it working.
The tests are started but all fails with one of the following exceptions:
from unknown error: page could not be found: chrome-extension://aapnijgdinlhnhlmodcfapnahmbfebeb/_generated_background_page.html
(Session info: content shell=)
(Driver info: chromedriver=2.28.455506 (18f6627e265f442aeec9b6661a49fe819aeeea1f),platform=Linux 4.4.0-22-generic x86_64)
or
Failed: Error while waiting for Protractor to sync with the page: "window.angular is undefined. This could be either because this is a non-angular page or because your test involves client-side navigation, which can interfere with Protractor's bootstrapping. See http://git.io/v4gXM for details"
The mentioned git issue doesn't help me.
All of them are running well local on a windows 10 machine.
The used versions local and on with jenkins are:
protractor: 5.1.1
chrome: 57.*
chromedriver: 2.28
I have found some issues that chrome should be downgraded to version 55.* but the all didn't solve my problem.
Thank you in advance
It says window.angular is undefined.
I assume it is not an angular site.
Have you tried entering
Browser.ignoreSynchronization = true
Before you get the browser.
I have tried all solution suggested by Google. But still struggling to below issue. I have setup of PHPUnit-Selenium based automation framework using headless Firefox on RedHat Linux
Selenium Log Error :
Caused by: org.openqa.selenium.WebDriverException: Failed to connect
to binary FirefoxBinary(/usr/bin/firefox) on port 7055; process output
follows: Error: no display specified Error: no display specified
So far I tried:
updated version of selenium driver
updated version of firefox
various selenium-firefox combinations using older versions
Xvfb working fine
Please also let me know :
How i can verify firefox on port 7055 ?
Is etc/hosts file can have cause of this issue ?