Printing in 64-Bit Google-Chrome fails

[Max Pyziur]

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?

Much thanks,

Max Pyziur
[e-mail]

[Richard Shaw]

On Tue, Feb 1, 2011 at 10:20 AM, Max Pyziur  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.

Richard

[Max Pyziur]

On Tue, 1 Feb 2011, Richard Shaw wrote:
> On Tue, Feb 1, 2011 at 10:20 AM, Max Pyziur  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

fyi,

Max Pyziur
[e-mail]
> Richard
>
> users mailing list
> [e-mail]
> To unsubscribe or change subscription options:
> https://admin.fedoraproject.org/mailman/listinfo/users
> Guidelines: http://fedoraproject.org/wiki/Mailing_list_guidelines

[Richard Shaw]

On Tue, Feb 1, 2011 at 11:03 AM, Max Pyziur  wrote:
> On Tue, 1 Feb 2011, Richard Shaw wrote:
> > On Tue, Feb 1, 2011 at 10:20 AM, Max Pyziur  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

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

[Genes MailLists]

On 02/01/2011 12:14 PM, Richard Shaw wrote:
nteresting. 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

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).

[Genes MailLists]

On 02/01/2011 07:40 PM, Genes MailLists wrote:
> google-chrome-unstable-10.0.648.6-72589.x86_64

Sorry - make that

google-chrome-unstable-10.0.648.11-73099.x86_64
>

As for printing - there is a bug I know about in which any pull down
menu buttons on websites - print black instead of whatever is
written/selected for that item.  This is for all versions - its being
fixed (may have been already I haven't checked in a while).

This is with unstable - which I find the best choice for me at the
moment - including full support for cert management (which was
introduced in 10.0).

gene

[Richard Shaw]

On Tue, Feb 1, 2011 at 6:40 PM, Genes MailLists  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

[David]

On 2/1/2011 9:00 PM, Richard Shaw wrote:
> On Tue, Feb 1, 2011 at 6:40 PM, Genes MailLists  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

Go to the three links. Those repos are empty.

[Richard Shaw]

On Tue, Feb 1, 2011 at 8:15 PM, David  wrote:
> On 2/1/2011 9:00 PM, Richard Shaw wrote:
> > On Tue, Feb 1, 2011 at 6:40 PM, Genes MailLists  wrote:
> > > 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
>
> Go to the three links. Those repos are empty.

No, not empty, just not directly browse-able.
Output from "yum repolist"
google                     Google - i386                                       5
google-chrome64            Google Chrome                                       3
google-testing             Google Testing - i386                               1
google64                   Google - x86_64                                     4

The numbers on the end are the number of packages in the repo.

I do get updated packages from time to time, but they seem to lag
horribly. Anyway I found the problem.

My links go to the general google repo, not the chrome specific one.
What's strange is if you do a google search on "google yum repo", the
links you find tell you to use the information just like I have.

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?

Thanks,
Richard

[mike cloaked]

On Wed, Feb 2, 2011 at 2:22 AM, Richard Shaw  wrote:
> 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?

Normally if you prepare the general google repo and then do yum
install google-chrome-stable then the install process will also
install the chrome repo for you and then automatically give you yum
updates.  It is possible that if you did your install another way then
the chrome repo may not have been part of the deal!