Why I dumped Debian Squeeze's Chromium for the Chrome browser from Google's repository

| | Comments (11) |

google-chrome-logo-300px.jpgI've always been an advocate for using the packages supplied by the distribution/project you happen to be running as an OS. Rarely do I go outside the "official" repositories for something shinier and newer. That's changing, and swapping the Chromium browser in Debian Squeeze for the Google Chrome browser directly from Google is my latest shift in this direction.

Why did I do it? Well, I've had more than a few incompatibility problems with the Version 6.0.472.63 of Chromium that is in the Debian Squeeze repositories, which won't be updated for anything but bug fixes for the life of Debian's stable release.

Chromium is still super fast, just like Chrome. But now with Google Chrome 11.0.696.68, all the trouble I've been having with complicated web forms has vanished.

And since Chrome/Chromium is pretty much a moving target development-wise, I'm not worried about the browser suddenly "breaking" on me, especially if the version shipping with Squeeze is old enough to be somewhat broken already.

chromium_logo.pngThe only problem with the Google package is that Chrome didn't automatically get into the "Internet" section of the GNOME menu. Instead, it's buried deep within the "Debian" menu. Since I wanted to launch it from the upper panel, I just dropped the icon right there, and load it that way every time. That's a small "fail," that is more than made up by the fact that v.11.x works so much better than v.6.x.

Note: I realize that I could find a more up-to-date source of Chromium, but while I'm not 100 percent comfortable with Google's handling of the data they receive via Chrome and other products, I'm willing to accept that for the moment (but reserve the right to change my mind at any time).

I've come to see the wisdom of a stable operating-system base -- such as Debian Squeeze, the Ubuntu LTS, Slackware, or anything that works well in your particular situation -- combined with newer (or even "rolling") versions of key applications such as web browsers, still-alpha-quality video editors, or other fast-developing software that doesn't benefit so much from standing completely still.

Hence I've used the Debian Mozilla team APT archive for newer versions of Firefox/Iceweasel and Thunderbird/Icedove, Liquorix for newer kernels (though now that new kernels are moving through Debian Backports, I should give them a try), and Dropbox.

I have all of these accounted for in separate .list files in /etc/apt/sources.list.d/, which means that if/when the packages are updated by their respective maintainers, they will flow into my Squeeze box at those intervals.

But there are pitfalls. There's something to be said for sticking with what Debian brought, but any longtime user of Linux/BSD knows that there are packages that become "problematic" in a particular release and are either slightly or completely broken. However, today I'm trying to at the Mozilla Debian team's site, and it appears to be offline. Maybe I need to go straight to Mozilla and try their packages?

I haven't made the leap from OpenOffice to LibreOffice, from OpenShot 1.1.x to 1.3.x, or even for a newer gPodder. If (and as) I stick with Debian Squeeze, all of this will be on the table. Having the latest Mozilla and Google web browsers, a kernel that works with my hardware (I stalled at 2.6.37) and Dropbox, with the rest of Debian Squeeze chugging along nicely, is keeping me quite happy for the time being.


11 Comments

Zman said:

Google Chrome is a piece of junk.
The number of bug fixes it has rivals Microsoft's IE.

Gladys said:

Why not use SRWare Iron so as to have the Google Chrome code but stripped of privacy concerns? BTW there is a Chrome extension that acts as an update button bringing in the latest version (download) and installing it so that too would be a good option.

HxJ said:

@Zman

That doesn't make any sense. Are you saying fixing bugs is a bad thing?

I've done the same thing, Steven. I was having issues with Chromium from Squeeze's repository and couldn't work the bugs out. When switching to Google Chrome, the issues went away. Like you, I try not to stray from the distribution's repository but sometimes, when you can't get an issue resolved, you have to.

Great article.

BobK54 said:

This is a great reason for the rolling release model. I'm using Chromium 11.0.696.65, FROM THE PCLinuxOS REPOSITIRY. This rev of Chromium was added almost immediately and I am confident it was after dev testing.

Randy said:

Chromium is up to 13 now, also it has no tracking, just like SRWare Iron it`s built from the original Chromium Project. Chrome was also, but then Google added all the tracking crap.

Where can I find a rolling repository for the "stable" Chromium for Debian/Ubuntu? I'd be very interested in installing it.

overvolting said:

I’m using wheezy and consequently the official google chrome repo won’t work.

Check this out as another option, source build off an ubuntu daily chromium repo:

https://launchpad.net/~chromium-daily/+archive/ppa

I chose maverick because it seemed to have similar package requirements to what wheezy has available.

I added the following line to my sources.list.d/chromium.list
deb-src http://ppa.launchpad.net/chromium-daily/ppa/ubuntu maverick main

and added the key as described at the link.

Then with:
apt-get source chromium-browser
dpkg-buildpackage
and using dpkg –force-depends to force install the produced debs chromium-browser and chromium-codecs-extra
I ended up with a brilliant daily build of chromium v13

No problems whatsoever. All extensions work as well.

homebrew said:

chromium stable channel for ubuntu:

https://launchpad.net/~chromium-daily/+archive/stable

might work for debian as well.

gabriel said:

Only problem with sticking with debian's version is that google will not play nice.

They simply can't stand people building the software themselves.

try to install anything from the extension store, and it will simply not work as of a few months from now.

Google is becoming the new microsoft, faster than apple.

the dsc said:

What's the apt line for chrome's debian repositories?

On some official google page it says that each app somehow adds its respective repository to the list or something to that effect (thus not finding necessary to show the apt lines), which does not seem to be really the case.

I do have some google apt lines but they seem to be fairly old, the google chromium I had was something like 13 or 15, whereas the one I've just downloaded (albeit beta) is 17.

Leave a comment

Tech Talk column

Steven Rosenberg's weekly Tech Talk column, which appeared Saturdays in the Los Angeles Daily News through about October 2009, is available on the Daily News Technology page.

About this blog






Steven Rosenberg aims to learn what he does not know. He writes about it here.



About this Entry

This page contains a single entry by Steven Rosenberg published on May 20, 2011 2:02 PM.

The Ubuntu GNOME Remix -- an ISO is imminent was the previous entry in this blog.

Blogging with DokuWiki (and thinking in progress about the philosophy of blog software) is the next entry in this blog.

Find recent content on the main index or look in the archives to find all content.

Recent Comments

the dsc on Why I dumped Debian Squeeze's Chromium for the Chrome browser from Google's repository: What's the apt line for chrome's debian repositories? On some officia ...

gabriel on Why I dumped Debian Squeeze's Chromium for the Chrome browser from Google's repository: Only problem with sticking with debian's version is that google will n ...

homebrew on Why I dumped Debian Squeeze's Chromium for the Chrome browser from Google's repository: chromium stable channel for ubuntu: https://launchpad.net/~chromium-d ...

overvolting on Why I dumped Debian Squeeze's Chromium for the Chrome browser from Google's repository: I’m using wheezy and consequently the official google chrome repo won’ ...

Steven Rosenberg on Why I dumped Debian Squeeze's Chromium for the Chrome browser from Google's repository: Where can I find a rolling repository for the "stable" Chromium for De ...

Randy on Why I dumped Debian Squeeze's Chromium for the Chrome browser from Google's repository: Chromium is up to 13 now, also it has no tracking, just like SRWare Ir ...

BobK54 on Why I dumped Debian Squeeze's Chromium for the Chrome browser from Google's repository: This is a great reason for the rolling release model. I'm using Chrom ...

chadmccullough.myopenid.com on Why I dumped Debian Squeeze's Chromium for the Chrome browser from Google's repository: I've done the same thing, Steven. I was having issues with Chromium fr ...

HxJ on Why I dumped Debian Squeeze's Chromium for the Chrome browser from Google's repository: @Zman That doesn't make any sense. Are you saying fixing bugs is a ba ...

Gladys on Why I dumped Debian Squeeze's Chromium for the Chrome browser from Google's repository: Why not use SRWare Iron so as to have the Google Chrome code but strip ...

Powered by Movable Type 4.25

Search this blog

Loading

LXer

Links

Life, the Universe and Debian
Simplify
Daily News technology
LXer
Distrowatch
Linus' Blog
David Pogue
BoingBoing
Linux Today
TuxRadar
Linux.com
Linux Planet
The Open Road
Linux Outlaws podcast
Dan Lynch
Fabian Scherschel
The VAR Guy
Larry the Free Software Guy
Chess Griffin
Linux Reality podcast
Desktop Linux
Practical Technology
Linux Devices
ZDNet
ZDNet's Storage Bits
ZDNet U.K.
iTWire
CNet News
Webware
Beyond Binary
TechCrunch
The Register
Ars Technica
Reg Developer
Computerworld
Computerworld blogs
Steven J. Vaughan-Nichols at Computerworld
Debian
Planet Debian
Debian Forums
Debian News
debianHELP
debiantutorials.org
The Debian User
Wolfgang Lonien
Debian-News.net
Debian Administration
Debian Admin
Debian Weather
Aaron Toponce
Ubuntu
Xubuntu
Kubuntu
Edubuntu
Planet Ubuntu
Ubuntu Forums
Ubuntu Geek
Works With U
OMG! Ubuntu!
I' Been to Ubuntu
Tanner Helland
Dustin Kirkland
Ubuntu UK Podcast
Ubuntu Linux Help
Popey
Linux Mint
CrunchBang Linux
OpenBSD
OpenBSD Journal
OpenBSD Ports
OpenBSD 101
Planet.OpenBSD.nu
jggimi's OpenBSD live CD
DaemonForums
BSDanywhere
Marc Balmer
Denny's OpenBSD blog
Polarwave's OpenBSD Tips and Tricks
Binary Updates for OpenBSD
Puppy Linux
Damn Small Linux
Tiny Core Linux
Lucky 13's Linux blog (lots of Tiny Core)
Lucky 13's BSD blog
PCLinuxOS
Mandriva
Red Hat
Red Hat News
Red Hat Blogs
Red Hat: Truth Happens
Red Hat Magazine
CentOS
Planet CentOS
Fedora
Planet Fedora
Fedora Forums
Fedora Docs
Join Fedora
Paul Frields
Slackware
Slackbuilds
Robby's Slackware Packages
Slackblogs
dropline GNOME for Slackware
GNOME Slackbuild
GWARE - GNOME for Slackware
Wolvix
Zenwalk Linux
Vector Linux
Slax
Splack Linux — Slackware for Sparc
Nonux
How to Forge
marc.info BSD and Linux mailing list archive
FreeBSD
FreeBSD, the Unknown Giant
A Year in the Life of a BSD Guru
NetBSD
hubertf's NetBSD Blog
PC-BSD
Daemon Forums
FreeBSD Forums
Planet FreeBSD
Evilcoder.org
miwi's Privat Blog
DragonFlyBSD
DragonFlyBSD Digest
DesktopBSD
BSD Talk podcast
BSD Magazine
Rhyous
OpenSolaris
MilaX
BeleniX
DeLi Linux
Linux Loop
Electronista
The Tech Report
Engadget
Gizmodo
Phoronix
xkcd – A webcomic of romance, sarcasm, math and language
Nixie Pixel
Technology for Mortals
Thoughts on Technology
ZaReason
System 76
Tiger Direct
NewEgg
DealExtreme

Advertisement

Other blogs

Estimated stats from spring game in Inside UCLA with Jon Gold
Missing Person in Inside USC with Scott Wolf
Mohammad House opens in The Sausage Factory
How royally screwed are Kings fans without Miller and Fox narrating this playoff fun run? in Farther Off the Wall
SOFTBALL: Oaks Christian's Ackermann reaches milestone in Daily News High School Spotlight