Getting Google repositories to work with apt-get on Ubuntu Hardy - google-chrome

I've installed Google Chrome on Hardy via the .deb file and would like to configure apt-get for automatic updates.
[I have another machine running Ubuntu Karmic where this works fine; apt-get knows the package as 'google-chrome'; I'm now using a Dell Mini 10 with Ubuntu 8.04 LTS installed]
As part of the .deb install, two entries have been added to the third- party software sources tab:
http://dl.google.com/linux/deb stable main
http://dl.google.com/linux/deb stable non-free main
However if I check for updates with either of these clicked, I get the following error:
Failed to fetch http://dl.google.com/linux/deb/dists/stable/Release Unable to find expected entry main/binary-lpia/Packages in Meta-index file (malformed Release file?)
There is a thread here which indicates others have had the same problem:
http://www.google.co.uk/support/forum/p/Chrome/thread?tid=097d103f87b49abe&hl=en
This references a further thread:
http://code.google.com/p/chromium/issues/detail?id=38608
which suggests the problem has been fixed.
Despite this I remain unable to get it to work, and none of the suggested workarounds seem to work either.
Ideas ? Thanks.

I think the issue here is that the Ubuntu installaion on your Dell Mini uses LPIA (Low Power Intel Architecture) and the Google Software Repository doesn't provide the "google-chrome" package for this architecture. Hence apt-get is giving you an error. You will have to do the updates manually using the "google-chrome" package for the i386 architecture.
On another note, the following thread provides details about repackaging an i386 package for LPIA. I hope this helps.
http://ubuntuforums.org/showthread.php?t=962835

Related

Where does cuda-repo-cross-<identifier>-all.deb come from?

I am trying to set up a cross-compile environment on an AWS EC2 Ubuntu box targeting Nvida Xavier devices on Cuda 10.2. I tried following the "instructions" at https://docs.nvidia.com/cuda/archive/10.2/cuda-installation-guide-linux/index.html#cross-platform which say to install
sudo dpkg -i cuda-repo-cross-<identifier>_all.deb
but no clue as to where I might get hold of that .deb file, or what <identifier> should be replaced with. I have installed the native package cuda-repo-ubuntu1804-10-2-local-10.2.89-440.33.01_1.0-1_amd64.deb and there are a load of .deb files in /var/cuda-repo-10-2-local-10.2.89-440.33.01, but none of them are that one.
So it turns out that the instructions that can be found by googling for, for instance, "cuda install cross compile" are wrong, or at least so incomplete as makes no difference.
Instead, use the SDK manager https://developer.nvidia.com/nvidia-sdk-manager to install just the host tools. It does run without a GUI.

Error in initiating astro after choosing a framework

I'm trying to initiate astro. When i don't choose a framework i get this error although i have git installed and fully working. Any help will be highly appreciated.
√ Which frameworks would you like to use? »
> Copying project files...
could not find commit hash for latest
This seems to be an issue with degit. Please check if you have 'git' installed on your system, and install it if you don't have (https://git-scm.com).
If you do have 'git' installed, please file a new issue here: https://github.com/withastro/astro/issues
It depends on your OS and environment.
For instance, withastro/astro issue 2144 reports the exact same error message, but on Windows, using Linux on WSL2 (Ubuntu 20.04.3 LTS).
Double-check your %PATH%/$PATH in your execution environment.
Update Oct. 2022, ten month later: withastro/astro issue 2144 is reported closed with the workaround by Matej Bunček:
As I was researching this seems to be a general issue with NPM for those who uses SSH.
There's an open issue here: npm/cli#2610 which is still far from being resolved and it's a huge thread.
Some folks might be interested in these workarounds to get it working.
git config --global url."https://github.com/".insteadOf git#github.com:
git config --global url."https://".insteadOf git://
Also I've tried yarn, npm and pnpm, all of them seems to have same problem so I believe it's core problem of node.
Also both npm 6 and 7 are not working.
Not a direct solution to your error message, but a general solution for those kinds of errors:
I would recommend doing the development inside docker containers, so called devcontainers.
Since you will develop in separate and isolated environments containing only the project's minimum dependencies and tools, it is a lot less likely to face OS specific issues in general.
Here are some resources to get started:
https://code.visualstudio.com/docs/remote/containers
https://microsoft.github.io/code-with-engineering-playbook/developer-experience/devcontainers/
https://github.com/microsoft/vscode-dev-containers

Installing Chrome on Red hat

We have failed trying to install Chrome version google-chrome-stable-70.0.3538.77-1.x86_64 on Redhat linux environment version 7.2.
We have created a yum repository and had done yum install google-chrome-stable but it fails at a step looking up for liberation-fonts stating requires liberation-fonts.
All the fonts with latest version are installed on it. I am attaching the installation logs and list of fonts installed on server.
I also tried install with .rpm link still had the same issue, and just to filter it out installed on different server of same os- still had same error.
Link to Logs:
Link to List of fonts:
Just to add we had no trouble with version 69.0.3497.92 and Google doesn't allow us to download previous versions of Chrome - at least for Redhat OS.
For what it's worth, I resolved this by installing it via rpm a package from a CentOS mirror on my laptop running redhat. In particular I installed this package: liberation-fonts-1.07.2-16.el7.noarch.rpm. Being a noarch file concerning fonts I wasn't concerned too much where it came from. I have doubts even the Chrome really needs this package since my installation had already several packages for liberation-fonts, including libertation-fonts-common but it allowed the chrome package to be installed.

Install GreenPAK Designer RPM

I am attempting to install closed source software from Silego, GreenPAK Designer, on a machine running Fedora 19. The supported installation packages on Silego's Website only target Ubuntu and Debian. I downloaded the .deb package and used Alien to convert to an RPM. So far so good, but a dry run of yum install showed dependency errors, which I solved by installing the necessary packages with yum:
qt5-qbase
qt5-qbase-gui
qt5-qtdeclarative
qt5-qtlocation
qwt
Now, yum installed the above libraries in /usr/lib/ but the GreenPAK RPM defaults to /usr/local/bin as the output dir. I figured I could run
sudo yum localinstall --nodeps --noscripts greenpak-designer-x.x.x.rpm
and get a successful install but I received conflict errors relating to dirs such as '/', '/usr', '/usr/bin' etc. I worked around this issue with:
rpmrebuild -pe --notest-install --replacefiles --noscripts greenpak-designer.x.x.x.rpm
and removing the offending lines in the script. It allowed me to install rpm but the software is broken because of dependency issues (not surprisingly). From the system log:
Jan 4 16:06:49 pelican gnome-session[1729]: /usr/local/greenpak-designer/bin/GP5: error while loading shared libraries: libicui18n.so.52: cannot open shared object file: No such file or directory
The machine has a /usr/lib/libicui18n.so.50
One thing I did not try is rebuilding my shared object cache with ldconfig, which sometimes solves problems with missing .so links when building from source but I don't see how that would apply in this instance (I'm not trying to link object files to libraries, rather simply trying to drop binaries in default install locations, no?)
Of course, I contacted the vendor and begged for an RPM. The contact was helpful but informed me the software folks are on a well deserved break. I thought I'd continue puttering with this in the meantime while I have time.
Any ideas? It seems the solution to this problem would be helpful when trying to install almost any closed source software targeting Debian on a Fedora box.

HeadlessException when trying to launch/run jProfiler 9 on Fedora 24 Workstation?

I just installed a fresh copy of Fedora 24 Workstation and did a full dnf update on the entire system.
Then I installed the jProfiler rpm from the jProfiler site.
However, when I try to launch jProfiler (either from the /opt/jprofiler9/jProfiler.desktop icon or from /opt/jprofiler9/bin/jprofiler shell script), I get the following error message:
java.awt.HeadlessException
at java.awt.SplashScreen.getSplashScreen(SplashScreen.java:117)
at com.exe4j.runtime.splash.AwtSplashScreen.<init>(AwtSplashScreen.java:17)
at com.exe4j.runtime.splash.SplashEngine.setJavaSplashScreenConfig(SplashEngine.java:17)
at com.install4j.runtime.launcher.UnixLauncher.main(UnixLauncher.java:50)
I've tried setting my display using DISPLAY=0.0 or even DISPLAY=:0, but neither seem to make any difference/impact.
Any suggestions how to get this to work? I suspect it is something obvious that I am overlooking.
After a bunch of trial and error, I finally tried to install the Oracle Hotspot JRE instead of the OpenJDK JRE. I downloaded Oracle's JDK, installed it, and then configured it as the system default using:
sudo alternatives --config java
Now everything works properly with Oracle JRE.