Printing in 64-Bit Google-Chrome fails
mike cloaked
mike.cloaked at gmail.com
Wed Feb 2 17:43:23 UTC 2011
On Wed, Feb 2, 2011 at 2:22 AM, Richard Shaw <hobbes1069 at gmail.com> 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!
--
mike c
More information about the users
mailing list