GNOME Shell integration extension is running, native host connector is not detected? - chromium

I have followed these steps while installing the gnome extension of chromium in Ubuntu 20.04.
Installed the GNOME Shell integration extension on chromium.
As per their documentation ran a command to install chrome-gnome-shell
sudo apt-get install chrome-gnome-shell
Still while loading the gnome-extensions page, it is showing error that "Although GNOME Shell integration extension is running, native host connector is not detected. Refer documentation for instructions about installing connector."
Can anyone tell me how to resolve this issue in steps?

FYI: starting from Ubuntu 21.10 Firefox comes as a default browser and as a snap, as well as Chromium. And has the same problem: GNOME Shell integration shows the same error.
Other ways to install the extensions are:
gnome-extensions install --force your_downloaded_extension.zip
unzip your_downloaded_extension.zip ~/.local/share/gnome-shell/extensions/

Probably this is because you are running Chromium as a Snap. There is an open bug in Launchpad about this, that appears to still be happening in Ubuntu 20.04 (still happening in Ubuntu 22.04):
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1741074
The easiest solution would probably be to use another web browser, not in a Snap.

I experienced this issue when upgrading from Ubuntu 21.04 to Ubuntu 22.04 (Jammy Jellyfish), where Firefox was installed via snap - supposedly the sandboxing made it unable to detect.
My resolution (which brought back gnome extensions connector being seen) was to install firefox manually by debian package via the directions in https://balintreczey.hu/blog/firefox-on-ubuntu-22-04-from-deb-not-from-snap/ . You may also be able to install the direct tarball following directions in https://fostips.com/install-latest-firefox-non-esr-debian/
Another option is to use a native extension manager as suggested in https://haydenjames.io/ubuntu-22-04-install-gnome-extensions-manager-workaround/

I solved using Chrome and not more Firefox for extensions.gnome.
(I use Chrome just for manage this extension)

If you still got problems, you could simply do this:
sudo apt-get reinstall chrome-gnome-shell

For me it did work after all, but just by using another browser - Firefox

I'm using Ubuntu 20.10 and I also had this issue. I was using Chromium but I found that Chromium dropped support for this, therefore I installed Firefox from the software. This did not work either.
The fix was to uninstall Firefox from software and install Firefox from ubuntu software with the source: ubuntu-groovy-updates-main
I installed the browser extension on there and it worked perfectly.

Aevin J He gave the answer if you're on ubuntu 21.10. it really matters whom you install it from. don't use the default one, use the one with most reviews

Related

Install Phalcon on RHEL 7

I'm trying to install Phalcon on my RHEL 7 VM. I downloaded files and folders from GitHub and place them on my VM via WinSCP in /opt/ (using remi repo or git clone from VM is blocked)
When I move into /opt/phalcon/build/ and try to sudo ./install, I got a notice that PHP 5 is no longer supported, currently on my Red Hat, I have PHP 7.3.11 version running (checked using php -v and config page).
I installed things like php-devel or gcc.
I have rh-php73-php installed and running on my VM
Maybe someone can help me, because I have no idea how to fix it.
I have rh-php73-php installed and running on my VM
Sorry, but phalcon extension package doesn't exist for this PHP stack.
Using the full php stack from "remi-php73" repository or php73 SCL from "remi-safe" will give you "php-phalcon4" package with latest version of this extension.
using remi repo or git clone from VM is blocked
Use a proxy, or download packages and install them manually.
Tips: test installation from another computer, connected to internet, to get the full package list. You can even retrieve them later from /var/cache/yum (using keepcache=1 in yum.conf)
For memory, for a proper installation, follow the Wizard instructions

Redhawk IDE will not display Components

When I launch the REDHAWK IDE via Eclipse, I cannot see the installed components (SigGen, fastFilter, etc). I can see the components just fine if I use the command line to create a project. I'm convinced it has to be a path or variable issues, but I just don't know what to reconfigure.
I'm using REDHAWK Version 2.1.0 and on CentOS7
OSSIEHOME is set to the /usr/local/redhawk/core
SDRROOT is set to /var/redhawk/sdr
Any suggestions?
I found a solution by reinstalling and including every Redhawk package that I could find using "yum list redhawk*"
I have the same problem and it turns out I was using a Java version higher than 8 which is not supported by RedHawk. Make sure you use Java 8 to launch the IDE otherwise it does not work. Submitted a DR but because JDK8 still supported they do not feel the need to fix it.
I followed the official installation instructions for RedHawk 2.3.0 on Centos 7.9 and had this same issue, I fixed it by opening a terminal in the Redhawk installation directory and running
sudo yum install redhawk-basic-components-2.3.0-5.el7.x86_64.rpm
After which the components appeared in the IDE without a restart

How to download and install Code Rocket for Eclipse in Ubuntu 14.04

I'm using this link: http://www.rapidqualitysystems.com/updates/CodeRocketForEclipse/
But I can download an .exe installation and I'm using Ubuntu 14.04!
How or where can I download and install the package for Code Rocket in Eclipse for linux ?
The System Requirements listed for CodeRocket for Eclipse see here (near the bottom of the page) say it is for Windows only.

Install SQL Server ODBC Driver for Ubuntu 15.10

To install the ODBC Driver, I followed this tutorial: https://msdn.microsoft.com/en-us/library/hh568454(v=sql.110).aspx
But when I run "sudo bash ./install.sh install --force" I get this message
Then I launched this:
What have I to do to avoid the "not found" message for "libodbcinst.so.2" and for "libgss.so.3" ?
The tutorial states:
Before you can begin to use the driver, install the unixODBC driver manager
Do you have unixODBC installed?
It means that the right version of unixODBC (read: the one required by MS ODBC driver for Linux) was not installed in you system or not found by the MS ODBC driver installer.
Check your unixODBC version using odbc_config.
Edit:
Alright, I jumped through some hoops here.
The library libodbcinst.so.2 can be installed by installing the driver manager, as plhyhc suggested (basically running ./build_dm.sh from the same directory). Follow the instructions here: https://msdn.microsoft.com/en-us/library/hh568449(v=sql.110).aspx
I found an alternative way to install de odbc driver manager here: http://onefinepub.com/2014/03/installing-unixodbc-2-3-2-higher-ubuntu-12-04-lts/ in case microsoft's script fails (which it didn't for me).
Running odbc_config --version should tell you if the install failed (the command odbc_config will not be found if that is the case).
The missing libgss3 (A library for Generic Security Services) can be installed using apt:
sudo apt-get install libgss3
After that running ./install.sh verify didn't show any dependency errors for me anymore. And installed fine.
When I ran isql however (isql WebDB MyID MyPWD) it had another error for me: Can't open lib '/opt/microsoft/msodbcsql/lib64/libmsodbcsql-13.0.so.0.0, that library did exist, however when running ldd /opt/microsoft/msodbcsql/lib64/libmsodbcsql-13.0.so.0.0 I saw it still "misses" libodbcinst.so.2. Creating a symlink solved that problem for me:
sudo ln -s /usr/lib64/libodbcinst.so.2 /lib/x86_64-linux-gnu/libodbcinst.so.2
Original post:
I found this page: http://www.codesynthesis.com/~boris/blog/2011/12/02/microsoft-sql-server-odbc-driver-linux/
A little ways down he talks about what to do when libcrypto.so.6 and libssl.so.6 is not found. Apparently the versioning schemes for these libraries in RedHat EL are different then those for Ubuntu. He used symlinks to the equivalent libraries.
I realize these are not the libraries you found missing. But maybe you have equivalents? Maybe in /usr/lib?
I'm actually trying to get the odbc driver running myself too, if I find anything useful, I'll update this post.

How to install OpenNI 1.x on a Mac?

I have a Kinect for Windows and I would like to connect it to my Mac laptop with OSX 10.7.5.
I would like to use openNI as the driver.
OpenNI's website lists "OpenNI 2.1 Beta (OS X)" however the source-code page does not list install instructions. Are they found someplace else?
There are install instructions on the OpenNI 1.x github page and on OpenNI 1.x Unstable branch page. The instructions for the two branches are slightly different, however neither have worked for me.
I originally had XCode 4.6 installed. Both instructions state they want XCode 4.3.2, which I installed, renamed XCode 4.6 and used "sudo xcode-select -switch" to switch between them.
Both instructions ask for "libusb-devel +universal" and in both cases I get:
Error: Please do not install this port since it has been replaced by 'libusb'.
Error: org.macports.configure for port libusb-devel returned:
Please see the log file for port libusb-devel for details:
/opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_release_tarballs_ports_devel_libusb-devel/libusb-devel/main.log
Error: Processing of port libusb-devel failed
If I continue with the installation of "libusb +universal" instead, then the rest of the dependencies install fine (though I had to install GraphViz before Doxygen).
But then when I run: "./RedistMaker" I get a lot of warnings, though it does create a Final file. "sudo ./install.sh" runs fine and I'm guessing OpenNI is installed, but then I get a bunch more errors when trying to install Sensor.
Can anyone help tell where along the way should I have started to worry? Do I need to manually install libusb (which I have tried to do)?
Any help appreciated!
I fixed the installation of OpenNI by running these instructions:
> sudo rm -f /opt/local/lib/libusb-1.0.0.dylib
> sudo port clean libusb
> sudo port install libusb +universal
Basically the Mac install instructions need to be updated and should include a warning that the short install may leave files around that will need to be deleted before installing with port.