AuthorTopic: google chrome linux... (Read 53823 times)

Ok, something about links and uploads and stuff with google sites makes it impossible (at least, I haven't found a solution yet) for wget to get stuff from a google site. You will have to get the pieces by downloading from these links:

if [ $check = "1d4c6c58d1b831772c375ae4a9f51c35" ];thenecho google-chrome-unstable-current-1vl60.tlz has been put back together and is the same as the original.elseecho google-chrome-unstable-current-1vl60.tlz has been put back together but is not the same as the original. The pieces may be corrupted.fi

exit 0

That should put the pieces back together into the package and check to make sure that the md5sum is the same as the original.

Since Google released an official beta version for linux, I decided to take a look at it. It's a .deb or .rpm package ( and 32 or 64 bit) so I cracked open the .deb, and repackaged it as a .tlz (as I did before). I installed the package and I think it would work except for this error message that I get when I execute "google-chrome":

[7376:7376:18159943326:FATAL:/usr/local/google/home/chrome-eng/b/slave/chrome-official-linux/build/src/chrome/browser/zygote_host_linux.cc(117)] The SUID sandbox helper binary was found, but is not configured correctly. Rather than run without sandboxing I'm aborting now. You need to make sure that /opt/google/chrome/chrome-sandbox is mode 4755 and owned by root.Trace/breakpoint trap

I'm not sure about how to check the "mode 4755" but I did confirm that chrome-sandbox is owned by root. Any ideas about how to fix this?

I installed google-chrome-beta_current_i386.rpm and all seems to be working fine.No hang-ups or hick-ups sofar. Flash is excellent. Installed as rpm -i --nodeps.

That will work if you already have the dependencies installed, but for someone adding to a freshly installed Vector system, it just wouldn't work. I've noticed brokndodges script isn't working for me anymore since Google come out with this official release.

I've been busy with work and other stuff. I just now check the forums and found that the installer is broken. Google now has two entries in the Packages.gz file. My script assumes only one entry. I'm going to have to find a way to parse the data into the two seperate entries. There is one entry for the Beta version and one for the Unstable version.

Ok, I have updated the scripts to handle the new multi-package release of google chrome. Right now both the update script and the install script default to the first package listed, at the moment that is the beta release. I'll implement package selection in a few days. Working on a method of determining the installed package and keeping to that for the update script. Have the basic variables already in place to select which release you want for the install script. i just haven't built the menu, that will rely on the method I use to determine which package is installed for the update script.

I did a lil work today on the crash issue, still can't figure it out. Both scripts will crash xfce!!! You must reboot after running the scripts. Once rebooted, everything will return to normal. You can type "reboot" in the terminal that you ran the script in to reboot the system.

#! /bin/bash# Title: install-chrome# Author: BroknDodge# License: BSD# Version: 0.0.5## Special thanks to the following Vectorians for their help and suggestions:# Daniel stretchedthin uelsk8ts# hata_ph rbistolfi MOE-lnx## Very Special thanks to the folks at Chromium.org and Google# without whom there wouldn't be anything to install#

#------------------------------------------## Setting up the Environment

nssInstalled=`slapt-get --search nss-3.12.3` # I really need to check the versionnssInstalled=${nssInstalled#*=} # as well, but this build seems tonssInstalled=${nssInstalled%]*} # work best with 3.12.3

Tested my install script today. Still works, ran it from tty2 cause of the swap space issue I posted bout in the Lounge. Installed Chrome without any issues, I issued a reboot from tty2 without checking to see if xfce had crashed, just assumed it would. Once rebooted, Chrome was working flawlessly. Except for the swap issue previously mentioned.

Followed the Light tutorial. A few glitches when tried with a light that's in use and has had packages installed:

Tried mc to install mozilla-nss. "Install" is not in the menu of my later version of mc installation. Not knowing how to change the menu or manually install the package, I located a VL 6 package of mozilla-nss (now in the testing repo) and installed.

Tried alien for chrome itself, but I'm not willing to learn how to use it properly right now, so it failed. Chrooted to my fresh light jail, did mc -V, and d/l'd that version from the "old" repo to my working light, installing it with upgradepkg. Installed chrome using mc. Didn't get the xdg-desktop warning, but was warned that atd wasn't running. Something for me to look at later, as the install did complete, and I'm posting from Chrome right now.

The hard part, of course, was remembering my forum password.

Speed is improved, flash is better though still not practical on this machine (ALSA needs tweaks for VIA). FYI, this version of chrome-linux has been "upgraded" from beta to stable.

In terms of Google Chrome speed, on this computer, it is not dissimilar to Opera's latest, among others.Right now, out of the popular Web Browsers, Opera and Seamonkey are one of the few web browsers I trust. Okay, Seamonkey, not as popular, but I find it much more stable than Firefox.

To me, mainstream means trouble. I prefer browsers more away from mainstream such as Konqueror, Midori, Netsurf, and Dillo. You might find them faster, too. More of an essence, you should find them much more safer, because feeble-minded virus programmers invest on a big catch, predominately - the mainstream web browsers. Plus these Open Source browsers intentions are more clear than Google's.

In terms of security, I find some of Google's practices questionable. By the way, I notice on a MS Windows machines Google Chrome chooses to install on administrators account, strictly. Which is unsafe, the least, let alone, suspect.

Also, the Youtube Downloader is another suspect program (as identified by Eset Smart Security for Windows). You would figure Youtube would provide that feature by default. As to: why not?, It would appear as another questionable practice.

No disrespect, I could be wrong about people running machines as testers, but in my neighborhood people put out testers curbside from time to time. I had grabbed one myself, only to test software with it, but ultimately, don't make it your main computer. Invest, you deserve much better than that. Above all, don't frustrate yourself or waste time.

Futhermore, I would question any company that releases a watered down versions of their product (like Picasa) for Unix and Linux. I don't see Unix and Linux as an afterthought, neither should they.

Followed the Light tutorial. A few glitches when tried with a light that's in use and has had packages installed:

Tried mc to install mozilla-nss. "Install" is not in the menu of my later version of mc installation. Not knowing how to change the menu or manually install the package, I located a VL 6 package of mozilla-nss (now in the testing repo) and installed.

Tried alien for chrome itself, but I'm not willing to learn how to use it properly right now, so it failed. Chrooted to my fresh light jail, did mc -V, and d/l'd that version from the "old" repo to my working light, installing it with upgradepkg. Installed chrome using mc. Didn't get the xdg-desktop warning, but was warned that atd wasn't running. Something for me to look at later, as the install did complete, and I'm posting from Chrome right now.

The hard part, of course, was remembering my forum password.

Speed is improved, flash is better though still not practical on this machine (ALSA needs tweaks for VIA). FYI, this version of chrome-linux has been "upgraded" from beta to stable.

Good tutorial, thank you. Hope the feedback helps.

For Chrome you need to download the .rpm package and also you'll need to install rpm in light from the repository as it was not installed by default.but it's in the repro. Then the install in mc will show in the menu.works great here.