Firefox-ESR 60.6 not working

[myhrmans]

When trying to use Arsenic with the new firefox-esr build for raspberry pi 3b I get the following error.

2019-03-27 15:24.32 request                        body={"desiredCapabilities": {"browserName": "firefox", "marionette": true, "acceptInsecureCerts": true, "moz:firefoxOptions": {"args": ["-headless"]}}} method=POST url=http://localhost:43867/session
1553696672076   webdriver::command      WARN    You are using deprecated legacy session negotiation patterns (desiredCapabilities/requiredCapabilities), see https://developer.mozilla.org/en-US/docs/Web/WebDriver/Capabilities#Legacy
1553696672085   mozrunner::runner       INFO    Running command: "/usr/bin/firefox" "-marionette" "-headless" "-foreground" "-no-remote" "-profile" "/tmp/rust_mozprofile.vmvW1LqG2Uh7"
*** You are running in headless mode.
JavaScript error: resource://gre/modules/XPCOMUtils.jsm, line 187: TypeError: undefined has no properties
JavaScript error: resource://gre/modules/XPCOMUtils.jsm, line 187: TypeError: undefined has no properties
JavaScript error: resource://gre/modules/XPCOMUtils.jsm, line 187: TypeError: undefined has no properties
JavaScript error: resource://gre/modules/XPCOMUtils.jsm, line 187: TypeError: undefined has no properties
JavaScript error: resource://gre/modules/XPCOMUtils.jsm, line 187: TypeError: undefined has no properties
JavaScript error: resource://gre/modules/XPCOMUtils.jsm, line 187: TypeError: undefined has no properties
JavaScript error: resource://gre/modules/XPCOMUtils.jsm, line 187: TypeError: undefined has no properties
ExceptionHandler::GenerateDump cloned child 9542
ExceptionHandler::SendContinueSignalToChild sent continue signal to child
ExceptionHandler::WaitForContinueSignal waiting for continue signal...

Anyone have successfully used this library on a raspberry pi?

[myhrmans]

Im using the geckodriver 0.23.0 for this

[ghost]

I don't know if it helps but I succesfully used selenium on raspberry pi 3B by using the following chart : https://firefox-source-docs.mozilla.org/testing/geckodriver/geckodriver/Support.html Unsure if this applies to Arsenic as well though.

[myhrmans]

I don't know if it helps but I succesfully used selenium on raspberry pi 3B by using the following chart : https://firefox-source-docs.mozilla.org/testing/geckodriver/geckodriver/Support.html Unsure if this applies to Arsenic as well though. I would fall under this category right? And since Im running 0.23 with 60.6 I would be fine. I've used ChromeDriver for Selenium. What versions did you use for selenium?

[ghost]

I don't have my pi available right now, but I'll be able to answer this weekend if you wish.

It's interesting, I never succeeded running chromedriver on pi because of similar compatibility issues between driver and browser. (And rpi builds are a pain to find, too)

Anyway the table probably does not apply to Arsenic then.

[myhrmans]

That would be awesome!

[myhrmans]

We're you using firefox-esr if I may ask?

[ghost]

Oh right I forgot you mentioned firefox-esr. I think I had managed to find a classical firefox (not the esr package), but i'll tell you more later when I boot up my pi back.

[ghost]

Okay here is the configuration that made it work for me :

• firefox-esr 60.5.1esr-1~de armhf
• python 3.6.8
• selenium 3.141.0 (According to "selenium.__version__" in python)
• geckodriver 0.23.0 (2018-10-04) But once again this made selenium work. i'm not sure about arsenic, though i'm about to test it very soon

[myhrmans]

I actually never succeed with Firefox with similar drivers as you. I after a while switched to pyppeteer instead of arsenic with chromedriver 72.0xx. That worked like a charm. Thanks for the reply anyway!

[ghost]

If arsenic doesn't work i'll try your solution as well, thanks !

[ghost]

It works perfectly fine, although slow. Don't know why your setup was flawed ¯_(ツ)_/¯

[myhrmans]

Yeah that's wierd. I might have missed a package or similar during installation. Glad we both got it working anyhow!