Google cloud sdk version 370.0.0-0 won't install on raspberry pi - google-cloud-sdk

I ran a routine apt upgrade on my RPi running Raspbian (Debian) version 10.11. This upgraded google-cloud-sdk from version 369 to version 370. The upgrade failed with
/usr/bin/gcloud: 190: exec: /usr/bin/../lib/google-cloud-sdk/platform/bundledpythonunix/bin/python3: Exec format error
I uninstalled google-cloud-sdk and reinstalled, same error.
I explicitly installed version 369 and I'm back up.
I'm mostly posting this so that perhaps someone at Google will see and fix this. Or not. I'm happy staying on version 369 for now.

Looks like a broken installer by google. A workaround is use CLOUDSDK_PYTHON environment variable to point installed python3 such as
export CLOUDSDK_PYTHON=/usr/local/bin/python3.9

Related

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

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

Running Big Commerce's Stencil CLI on Windows 10

I can not get Stencil to run for the life of me. I am using NVM to mange my version of node - I tried both 10.16 and 10.19.
I have reinstalled Stencil 2 or 3 times now and ever time I get the same error:
WTF? Has anyone got this to successfully run on a Windows 10 machine? We originally had node 13.9 installed but I was getting the same errors so I figured it was because it was outside their "approved" versions. I spoke to their customer support and they told me that it should work with newer version but that they can't give it proper approval until it's goes through some process.
So I can't get this to work on any version......
Any help would be very much appreciated!
Before installing nvm was a previous version of node installed? You'll need to uninstall nvm and node before installing nvm which can cause this. You can confirm which version of node is installed using node --version

Scales pkg do not install in my 2009 32 bit Mac mini (El Capitan) Rstudio

I recently upgrade my 2009 Mac mini adding 2gb of ram and installing "El Capitan". For some reason when I try to install "ggplot2" the package Scales ask me for compile it, when I hit yes to continue the process a message appears saying that is unable to compile the dependency. When I check my installed packages the installed Scales version installed is the 0.4.0 and don't allow me to update it to the 0.4.1 version. I try selecting another mirror and installing manually the newer version but it dosen't work. I also install gfortran 4.2.3 and tcltk 8.5.5x11 trying to solve the compiling problem.
The messages that appears are the following:
-"ERROR: compilation failed for package ‘scales’"
-"ERROR: lazy loading failed for package ‘ggplot2’"
I will appreciate any help.
Thanks!

Error when installing tideSDK developer 1.4.2 on fedora 13

i have installed tideSDK 1.3.1-beta on my machine
File path is "user/.tidesdk"..
then tried to install tideSDK developer 1.4.2 i got following error message.
Couldn't load file:/home/mareeswari/TideSDK-Developer-1.4.2-linux-x86/runtime/1.3.1-beta/libtide.so, error: /usr/lib/libstdc++.so.6: version `GLIBCXX_3.4.15' not found (required by /home/mareeswari/TideSDK-Developer-1.4.2-linux-x86/runtime/1.3.1-beta/libtide.so)
This is a valid crash. Its because TideSDK does not support fedora / redhat family yet. The underlying binaries are compiled for Ubuntu.
I've successfully got Tide Developer working on Fedora 18.
I had a similar issue to you, however it was complaining about libpng12, so installed the libpng12 and libpng12-devel and it worked fine.
Hope this helps someone

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.