This is more serious than looks from your case, naoliv. In my case in Ubuntu it 
installs an MTA.

The following NEW packages will be installed:
  alien{a} heirloom-mailx{a} libqt4-gui{a} libqt4-sql-sqlite{a} librpm0{a}
  librpmbuild0{a} librpmio0{a} lsb{a} lsb-core{a} lsb-cxx{a} lsb-desktop{a}
  lsb-graphics{a} ncurses-term{a} pax{a} postfix{a} rpm{a}
The following packages will be upgraded:
  google-chrome-unstable
1 packages upgraded, 16 newly installed, 0 to remove and 0 not upgraded.
Need to get 18.6MB of archives. After unpacking 16.2MB will be used.

I'm seeing this too.

 Issue 35685  has been merged into this issue.

This seems like a simple oversight.

 Issue 35824  has been merged into this issue.

mdm also complained. He said, "chrome now depends on CVS and also alien and rpm and 
qt4 and m4". Not sure what Debian-based distro he's on though.

I run Ubuntu, and I had to install alien, rpm, various qt4 packages and a mail client.  
That's the updates for my Debian-based distro at least.

thestig: the machine I was talking about is Ubuntu 8.04, but it's the same in 9.10 and 
presumably most or all other Debian derivatives.

 Issue 36001  has been merged into this issue.

Issue chromium-os:1594 has been merged into this issue.

This was an attempt to consolidate our DEB deps on the more generic 'lsb' package 
(similar to what the RPM packages use). Unfortunately, that pulls in a lot of stuff 
that isn't installed by default on some DEB distros, so I'm reverting to the 'lsb-
base' dependency we had before.

This fix should appear in something after r39250.

 Issue 36045  has been merged into this issue.

 Issue 36076  has been merged into this issue.

If it's possible, can we cherry-pick this onto the beta branch?

The same issue exists on the beta branch where Chrome wants me to install 44 extra 
packages.

Ubuntu 9.10
Google Chrome 5.0.307.7 beta

It is cherry-picked for beta, but it missed the current build.

To get around it for now, download the deb file and use dpkg to install with the 
following. This will ignore the dependency issues and configure the browser. I 
wouldn't make this practice going forward. Ubuntu/Debian is pretty forgiving and a 
browser is far from a core library/package on your system.

dpkg -i --force depends google-chrome-unstable_current_i386.deb

 Issue 36139  has been merged into this issue.

I'm glad to see that this is fixed -- but does that mean that it will uninstall all 
these unneeded packages that it installed for me as well on Ubuntu?  Or do I have to 
try and remember the 44 some-odd packages that it "depended" on and uninstall each one 
by myself?

After installing the next version, 'apt-get' should prompt you that there are packages 
which are no longer needed, and 'apt-get autoremove' should clean them up.

I uninstalled Chrome after it installed all these packages, but 'sudo apt-get 
autoremove' didn't clean it.

I'm still getting the dependency issue in channel deb http://dl.google.com/linux/deb/ 
stable main

Should I be using a different one?

nolotari: I don't know what channel you're referring to, but as noted above, the fix 
will be in builds after r39250, which means neither the current dev channel 
(5.0.307.9-r39052) nor the current beta channel (5.0.322.2-r38810) have it. Updates 
for both should go out within a few days.

That's what I was asking, thanks.

have same problem in karmic, i had google-chrome-unstable, but it asked me to install 
all this stuff like two weeks ago... I'm on an EEEPC 4G, and I have little disk... so 
I canceled, uninstalled and reinstalled but: google-chrome-beta, which didn't asked 
me those dependencies... till next week... Now I want to figure out this. So, I was 
using always sudo apt-get update && sudo aptitude full-upgrade to update my system, 
this is faster and less resource-demanding than synaptic/update manager. But I turned 
again to synaptic, so as to unmark in a clarifying menu all the unwanted updates 
(rpm, alien, etc)... I was able to do it yesterday, tried to block version on google-
chrome-beta until they repair this, that I think must be a mistake on dependencies, 
but I have had done sthg wrong, because today i repeated sudo apt-get update && sudo 
aptitude full-upgrade, but it still wants to update google-chrome-beta with all that 
enormous unwanted staff... I will have to stuck with synaptic and "GUI manual 
unmarking"... until this matter stops

@Gabriel: please see the postings in this bug report, this is a packaging issue and
it will be fixed. In the meantime, your best bets are either to uninstall Chrome for
now and use something else until it is fixed, or upgrade selectively with 
Synaptic/KPackageKit, which is what I am doing: just ignore the Chrome upgrade for
now. 

What I'm horrified by is that 5.0.307.9 hasn't been taken off the repo.

Verified as fixed on  linux (Ubuntu 8.04 -debian unstable and Open Suse 11.1(rpm -
unstable builds):
Google Chrome	5.0.322.2 (Official Build 38810) dev
WebKit	533.1
V8	2.1.0.1
User Agent	Mozilla/5.0 (X11; U; Linux x86_64; en-US) AppleWebKit/533.1 (KHTML, 
like Gecko) Chrome/5.0.322.2 Safari/533.1

"Verified as fixed on  linux (Ubuntu 8.04 -debian unstable and Open Suse 11.1(rpm -
unstable builds):
Google Chrome	5.0.322.2 (Official Build 38810) dev"

Actually 5.0.322.2-r38810 is the _problematic_ version.

Not fixed at all...

$ apt-cache policy google-chrome-unstable
google-chrome-unstable:
  Installed: (none)
  Candidate: 5.0.322.2-r38810
  Version table:
     5.0.322.2-r38810 0
        500 http://dl.google.com stable/main Packages

$ apt-get install google-chrome-unstable
Reading package lists... Done
Building dependency tree       
Reading state information... Done
The following extra packages will be installed:
  alien at libelf1 libqt3-mt libqt4-assistant libqt4-gui libqt4-sql-sqlite librpm0
librpmbuild0 librpmio0 lsb lsb-core lsb-cxx lsb-desktop lsb-graphics m4 ncurses-term
pax rpm rpm-common rpm2cpio time
Suggested packages:
  lsb-rpm libqt3-mt-psql libqt3-mt-mysql libqt3-mt-odbc libqt4-dev lsb-printing
lsb-multimedia lsb-languages elfutils rpm-i18n
The following NEW packages will be installed
  alien at google-chrome-unstable libelf1 libqt3-mt libqt4-assistant libqt4-gui
libqt4-sql-sqlite librpm0 librpmbuild0 librpmio0 lsb lsb-core lsb-cxx lsb-desktop
lsb-graphics m4 ncurses-term pax rpm rpm-common
  rpm2cpio time
0 upgraded, 23 newly installed, 0 to remove and 0 not upgraded.
Need to get 22.4MB of archives.
After this operation, 73.8MB of additional disk space will be used.
Do you want to continue [Y/n]? n
Abort.

rekhas: OpenSuse was never a problem (RPM distros bring in all these extra LSB 
packages already). The problem on DEB-based distros will be fixed with a build after 
r39250.

Back to normal with 5.0.335.0 (Official Build 39561) dev
under Debian Lenny
Many thanks for fixing this issue!

@Comment 24 by henkjan.sleijster:

Same here: google-chrome-beta 5.0.307.11-r39572 does not depend on all these extra 
packages, which is good, but "apt-get autoremove" doesn't clean up the mess. This is 
in Kubuntu-lucid. I am lucky I installed the bad package from the command line and 
saved the output, so I was able to remove them by hand. But this really depends on 
your local installation. For me, the clean up was a matter of

sudo apt-get remove alien bsd-mailx libqt4-gui lsb lsb-core lsb-cxx lsb-desktop lsb-
graphics mailx ncurses-term pax postfix

I actually tried, for the benefit of others, to just remove lsb and then run apt-get 
autoremove, but that didn't work, either.

About the removal of no longer needed automatically installed packages, 'aptitude' 
does a much better job of that than apt-get.

It seems first update after installing fresh 9.10 and Chrome
triggers a postfix update failure warning dialog on some systems;
see https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/526785
So there's even more harm than just the extra downloads.

About https://bugs.launchpad.net/ubuntu/+source/postfix/+bug/526785, no. It's not 
related with Chrome.

I could be wrong, but I thought installing lsb pulled in postfix.

I believe it pulls in mail-transfer-agent which the virtual package resolution process decides is best satisfied by 
postfix.

I've read comments up thru #42, and see no recent activity, so this might not be the place to post a comment. A few minutes ago, I went the "popular" path and tried to install Chrome for 64-bit openSUSE. All went well for a few seconds, and then (yet again*) I got a dependency failure -- a list of maybe 15 missing libraries. That has been the history ever since Chrome was offered for Linux; I'm sadly disappointed that such a savvy org. as Google doesn't offer packages.

nbodley: This bug is very unlikely to be related to your issue. But do open a new issue for it, and provide as much information as you can about the problem so we can help to figure out why it's not working for you. Thanks.

For [mdm]:
First, I must apologize; I think I was overtired, and failed to notice that I had downloaded a .rpm file.
Second, I'll probably be busy for a few days, and hope I won't forget!

Typically, what happens is as I described -- install seems to run fine, until it's stopped dead by dependency failures -- missing libraries. 
openSUSE 11.1 has some corrupted executable code, which could conceivably cause the problem. Although very likely unrelated, selecting "Num Lock" does not enable keypad numerial input; that's one example of corrupted executable code.

I hope to reinstall Linux (perhaps several distros.; am having a bitchy time getting sound to work).
If I can't install Chrome into (perhaps more than one) distro., I'll do my best to provide details.

Regards,
[nb]

I added a comment to the thread on this bug. Hope to be able to help more,  
in a few days.

This issue has been closed for some time. No one will pay attention to new comments.
If you are seeing this bug or have new data, please click New Issue to start a new bug.