I've been trying to run a Native Messaging on Debian Linux, but when I click the connect button, I only get the message "Connecting to native messaging host com.google.chrome.example.echo" and nothing else.
Everything is similar to the default example, I only changed the path at the manifest file. What is wrong?
It does work in Chrome 35, Chromium 34 (from default depository) and Opera Developer on Ubuntu 14.04.
Though I couldn't get it working in Opera Developer 24 (chromium 37).
Opera just fixed that. But broke it later again.
So take another look on your settings:
Location of home manifest file:
~/.config/chromium/NativeMessagingHosts/
~/.config/google-chrome/NativeMessagingHosts/
~/.config/opera-developer/NativeMessagingHosts
How to Debug
Start Chromium like:
chromium-browser --enable-logging --v=1
You will get an error message like this if the path is wrong:
ERROR:native_process_launcher.cc(131)] Can't find manifest for native messaging host com.google.chrome.example.echo
Support
For any version of Chromium-version under 34 the userspace isn't supported, you need a CLI switch:
--native-messaging-hosts="com.google.chrome.example.echo=~/.config/chromium/NativeMessagingHosts/com.google.chrome.example.echo.json"
Also it didn't work in Opera-Developer 24 for me at the moment.
Related
Netbeans 15 can't open firefox or node.js on Linux Mint 21 (Ubuntu 22).
It all boils down that it cannot see some apps located in /bin
If I go to Tools->General->Webrowser->Edit->Browse...
I cannot see firefox or node at the path /bin with the internal Netbeans file browser, while if I use the system file explorer they are shown normally.
So it seems that somehow Netbeans has no access to these applications? Strangely other apps like /bin/gpg or /bin/cp for example are shown correctly within the Netbeans file browser window (started with the browse button)
UPDATE:
It is working without problem on Netbeans 12 which I just have installed on the same system. So only Netbeans 15 has the problem.
UPDATE 2
Netbeans 15 was installed via flatpak and and I suppose that the flatpak rights management does restrict access to firefox.
Flatpak's right management / sand-boxing does restrict access to Firefox and other apps like node. If I build Netbeans 15 from source, everything is working. Flatpak can be a real mess here. :(
I am looking to install Chrome Driver (For my selenium project) on an Amazon Linux 2 (Arm 64).
I have done this on Ubuntu and seems pretty straight, it also seems straight on AL2 x86, like this script from Intoli but it 404 when looking for Chrome on ARM :(. So far I see Chrome is not available for ARM so I see the alternative is to use Chromium.
I tried installing it manually but it seems there is no compiled on Chromium downloads page for ARM.
Finally i found the Electron's unofficial webdrivers, which seem to be the answer, and after downloading, installing dependencies (libXcursor, libXfixes, libXdamage) and running it:
[ec2-user#scraping1 current]$ chromedriver
Starting ChromeDriver 100.0.4896.143 (6bf1afe83487405ea0aff37182f05e3db45559c2-refs/branch-heads/4951#{#831}) on port 9515
Only local connections are allowed.
Please see https://chromedriver.chromium.org/security-considerations for suggestions on keeping ChromeDriver safe.
ChromeDriver was started successfully.
And run my project I get:
2.7.3 :004 > Selenium::WebDriver::Service.driver_path = "/usr/bin/chromedriver"
=> "/usr/bin/chromedriver"
session = Capybara::Session.new
Webdrivers::BrowserNotFound: Failed to find Chrome binary.
Which means i don't have Chrome installed, but then how to install it? I have seen this question which seems to be my same problem but it is unclear to me how to install Chromium; I see it is needed to download and use the chromedriver compiled for ARM64 which I have done already.
I cannot open Appium inspector on Linux Ubuntu.
In the same folder I have 3 files:
Appium-Inspector-linux-2022.2.1.AppImage /
Appium-Server-GUI-linux-1.22.2.AppImage /
latest-linux.yml
When I open the Appium-Server-GUI-linux-1.22.2.AppImage file, start the server e click on the button to open Appium Ispector, it open a web page.
to fix this, it was necessary:
1: Start Appium Server
I did this, executing Appium-Server-GUI-linux-1.22.2.AppImage file.
2: Start Appium Inspector through of file Appium-Inspector-linux-2022.2.1.AppImage
3: Create the capabilities
After that, the Appium Inspector still don't open throught on Appium Server button, but it make it open and you can use.
Since the release of Appium v1.22 they have changed how the Appium Inspector works. I refer you to their official documentation on GitHub https://github.com/appium/appium-inspector, citing:
Appium Inspector is released in two formats:
As a desktop app for macOS, Windows, and Linux. You can get the most
recent published version of this app at the Releases section of this
repo. Simply grab the appropriate version for your OS and follow
standard installation procedures (but see the note below for macOS).
As a web application, hosted by Appium Pro. (It's currently a known
issue that the web version does not work on Safari). Please make sure
to read the note below on CORS as well.
If you like to work the old way, download Appium Desktop v1.21 or below.
install latest appium-inspector
open appium-inspector and insert "/wd/hub" in Remote Path
I have a sample app in GWT. When I run it and open in my Firefox - the browser still displays this:
Even if GWTP Developer plugin is sucessfully installed
My Firefox version is 25.0 (on Fedora 20), I know that the new versions of Firefox have problem with GWT plugin, but this version should be probably ok. What is the problem?
It's a known problem. Check this out: http://code.google.com/p/google-web-toolkit/issues/detail?id=8423
The solutions proposed there are to either:
download a special plugin that they've made for this bug
yum removing firefox and xulrunner and installing Firefox 25 from
ftp://ftp.mozilla.org/pub/firefox/releases/25.0/linux-x86_64/en-US/
You can also try upgrading to firefox 26, as the support was removed
in 27 and 26 should work fine with the normal plugin.
I followed the instruction at:
https://developer.blackberry.com/html5/documentation/use_the_ripple_emulator_chrome_extension_2007542_11.html
to run remote site app project, it works.
But when I tested sample (bbui.js sample) on local disk
BB10 document said:
https://developer.blackberry.com/html5/documentation/accessing_a_local_project_in_ripple_1948645_11.html
So I copied the bbuijs samples project to
Mac OS: /Users//RippleSites.samples
But when I pointed chrome to
localhost:9910/samples/index.htm (Ripple emulator extension)
Chrome said
could not connect to localhost:9910
Is there anything wrong?
Do I need to run web server sharing?
Welcome any comment
Easiest thing to do here it got to enable "web sharing" (your last pic). create a symbolic link from the Web Server's home dir to your samples. So:
cd /Library/WebServer/Documents/
ln -s <path to your samples> <name of dir>
Note: you might have to use "sudo" ahead of that last command.
You should then be able to go to 127.0.0.1/(name of dir) and it should work for you.
Hope this helps.
I have the same problem ("could not connect to localhost:9910") on Windows 7 in Chrome with Ripple emulator version 0.9.10 (beta)
The documentation at https://developer.blackberry.com/html5/documentation/accessing_a_local_project_in_ripple_1948645_11.html
does mention how to install the Chrome extention. But it does not mention that the Ripple button in Chrome has a popup where you can start the local service running on port 9910.
My steps taken were:
Open the kitchensink example by following https://developer.blackberry.com/html5/documentation/enabling_the_ripple_emulator.html
This allows you to see the Ripple emulator working.
Create the local directory as described in https://developer.blackberry.com/html5/documentation/accessing_a_local_project_in_ripple_1948645_11.html
Then you will be able to see the services button and start the service.
Open your local project via loaclhost:9910/
Image of the option menu:
(source: escay.nl)