Greetings, I am now favoring Google Chrome over Firefox and Galeon; I use both on my i386 Dell Laptop and 64Bit Desktop. From either Galeon or Firefox on both machines printing functions correctly. Using Google-Chrome, printing functions correctly on the i386 laptop, but fails on the 64Bit desktop (it prints multiple pages of occasional gibberish). Any suggestions?

On Tue, 1 Feb 2011, Richard Shaw wrote: > On Tue, Feb 1, 2011 at 10:20 AM, Max Pyziur <pyz(a)brama.com&gt; wrote: >> >> Greetings, >> >> I am now favoring Google Chrome over Firefox and Galeon; I use both on my >> i386 Dell Laptop and 64Bit Desktop. From either Galeon or Firefox on both >> machines printing functions correctly. >> >> Using Google-Chrome, printing functions correctly on the i386 laptop, but >> fails on the 64Bit desktop (it prints multiple pages of occasional >> gibberish). >> >> Any suggestions? > > What version are you running? stable? beta? unstable? > > I run the beta right from their yum repo and have very few issues. My only issue is printing in the 64bit version; otherwise, I'm a quiet cheerleader. On both 64bit and i386 machines I've installed the latest stable release by way of yum/rpm: google-chrome-stable-8.0.552.237-70801.x86_64

google-chrome-unstable-10.0.648.6-72589.x86_64

On Tue, Feb 1, 2011 at 6:40 PM, Genes MailLists <lists(a)sapience.com&gt; wrote: > On 02/01/2011 12:14 PM, Richard Shaw wrote: > Interesting. I don't have 8.0 stable available for some reason... >> >> # yum list google-chrome\* >> Loaded plugins: changelog, presto, refresh-packagekit, remove-with-leaves, rpm- >> : warm-cache >> Installed Packages >> google-chrome-beta.x86_64 8.0.552.200-65749 @google64 >> Available Packages >> google-chrome-beta.i386 8.0.552.200-65749 google >> google-chrome-stable.i386 7.0.517.44-64615 google >> google-chrome-stable.x86_64 7.0.517.44-64615 google64 >> google-chrome-unstable.i386 9.0.576.0-65344 google >> google-chrome-unstable.x86_64 9.0.576.0-65344 google64 >> >> Where do you get yours from? >> >> Thanks, >> Richard > > All of yours are not updated (they look way behind .. i mean way way > behind) ..this is the current unstable I have - just letting yum update > from the google repo: > > google-chrome-unstable-10.0.648.6-72589.x86_64 Yeah, after seeing your previous email I did some researching but didn't find anything wrong with my repo... I just did a "yum clean all" and I still see the same versions. My /etc/yum.repos.d/google.repo: [google] name=Google - i386 baseurl=http://dl.google.com/linux/rpm/stable/i386 enabled=1 gpgcheck=1 gpgkey=https://dl-ssl.google.com/linux/linux_signing_key.pub [google-testing] name=Google Testing - i386 baseurl=http://dl.google.com/linux/rpm/testing/i386 enabled=1 gpgcheck=1 [google64] name=Google - x86_64 baseurl=http://dl.google.com/linux/rpm/stable/x86_64 enabled=1 gpgcheck=1 gpgkey=https://dl-ssl.google.com/linux/linux_signing_key.pub > I'd force install fresh if I were you. Also I did not realized they > could be installed on top of each other interesting .. I only have > unstable. I thought they all ended up in same place (/opt/google/chrome). I've only got the one installed, the rest are just available packages. Richard

I downloaded directly from the google website the latest google-chrome and opened the RPM archive and found the shell script that adds the chrome specific repo. Now I'm showing the newer software packages. # yum list google-chrome* Loaded plugins: changelog, presto, refresh-packagekit, remove-with-leaves, rpm-              : warm-cache Installed Packages google-chrome-beta.x86_64             8.0.552.200-65749          @google64 Available Packages google-chrome-beta.i386               8.0.552.200-65749          google google-chrome-beta.x86_64             9.0.597.84-72991           google-chrome64 google-chrome-stable.i386             7.0.517.44-64615           google google-chrome-stable.x86_64           8.0.552.237-70801          google-chrome64 google-chrome-unstable.i386           9.0.576.0-65344            google google-chrome-unstable.x86_64         10.0.648.11-73099          google-chrome64 I wonder if Google knows about this discrepancy?