New issue
Advanced search Search tips

Issue 2362 link

Starred by 24 users

Issue metadata

Status: Fixed
Owner:
Closed: Sep 2008
EstimatedDays: ----
NextAction: ----
OS: All
Pri: 2
Type: Bug

Restricted
  • Only users with Commit permission may comment.



Sign in to add a comment

"Checking for updates..." stays forever

Reported by mahan...@gmail.com, Sep 16 2008

Issue description

Product Version      : 0.2.152.1 (Official Build 2164)

What steps will reproduce the problem?
1. go to "About"

What is the expected result?
"No updates found"

What happens instead?
"Checking for updates..." is taking forever.

Please provide any additional information below. Attach a screenshot if 
possible.
 
There were no problems with 149 version, the bug appeared only in 151.
I have Vista SP1.

another person experiencing the bug as well: http://news.cnet.com/8301-
1001_3-10042670-92.html?part=rss&subj=news&tag=2547-1_3-0-20
 

Comment 1 by finnur@chromium.org, Sep 16 2008

Status: Assigned
Thanks for filing the bug. I am looking at it now.

Comment 2 by Deleted ...@, Sep 17 2008

I have the same problem, and tt also creates multiple instance of Googleupdate.exe

Comment 3 by finnur@chromium.org, Sep 17 2008

A fix is in review. 

And by the way - Depending on what Google apps you have installed it can be normal to 
have more than one instance of GoogleUpdate running.

Comment 4 by finnur@chromium.org, Sep 17 2008

Labels: Mstone-0.3

Comment 5 by phistuck@gmail.com, Sep 17 2008

Seems like you cannot download any file with this version.

Comment 6 by Deleted ...@, Sep 17 2008

Tabs saved dissapeard when closing.
Configuration changes also tend to be erased.

I downloaded the regular chrome version and installed it over. But not effect, Build 
still show at 0.2.152.1 

Comment 7 by bgam...@gmail.com, Sep 17 2008

This bug is mentioned in CNet's article on the 152.1 update:
http://news.cnet.com/8301-1001_3-10042670-92.html?part=rss&subj=news&tag=2547-1_3-0-
20

Comment 8 by Deleted ...@, Sep 17 2008

instead of downloading a file this version also gives you about:blank (found that out 
when tried opening a downloadable link in new tab.)

Comment 9 by finnur@chromium.org, Sep 17 2008

Status: Fixed
Fixed in revision 2334.


Comment 10 by tbepo...@gmail.com, Sep 18 2008

Is r2334 on the "Dev channel" or is that happening in a day or so?
@finnur: Thanks for fixing it, but how to do we update to 2334 with our update 
checker not working? Is there a way that we can do it manually?

Comment 12 by dtfi...@gmail.com, Sep 22 2008

If anyone has the solution to the broken update paradox, we'd love to hear it. I 
can't find any direct links where I can manually download and install the next dev 
channel build of Chrome.
I reinstalled Chrome and updated it to the newest dev release. That is still 
0.2.152.1 which means I still have the downloading problem (and the "Checking for 
updates..." problem).

Two instances of GoogleUpdate.exe is running.

Comment 14 by seega...@gmail.com, Sep 24 2008

I don't think this bug should be closed yet. I'm still experiencing update-paradox, 
and there is no fix.

This bug doesn't seem to have been crunched yet - or at least the newer version in 
which it has been resolved has not yet been released. I'm looking forward to seeing 
it...

Henri
Now that the 0.2.153.1 release is out, how do we upgrade to it, with the 2362 bug in 
0.2.152.1
1: Uninstall the 0.2.152.1 (with Control Panel->Uninstall a program)
2: Download & Install the offical Chrome version here: http://www.google.com/chrome
3: Start the chromechannel-1.0.exe and you choice for Dev and Ok.
4: Start the Chrome Go to About Google Chrome.
5: Update and Restart

Done.
But, I cannot uninstall - it simply does not "take".  I remain at 0.2.152.1 and seem 
to be stuck there.
You only need to wait - Chrome gets autoupdated in the background. If you are having 
problem uninstalling, I suggest you kill all lingering Chrome instances in the 
background and wait until you get autoupdated (and refrain from using the About box 
until you've been upgraded). To check your version, type in about:version into the 
Omnibox after starting Chrome and if it doesn't say version 0.2.152.1 then it is safe 
to use the About box again.

Comment 20 Deleted

#16, #17. Thanks. Looks like this is working now.


finnur - I am on 0.2.152.1. I has not auto-updated to new version. How long does it 
take to autoupdate?
Well, it depends on when it ran last, I guess. I don't know the exact interval but I 
it probably runs every few hours. In your case, it might happen in the next few 
minutes (best case) or within a few hours (worst case), depending on when it ran 
last. If you don't feel like waiting, uninstall, reinstall and go back on the dev 
channel and update through the About box.
@atul.arora: 0.2.152.1 doesn't auto-update because of the bug. To update to the 
latest dev version, you will have to

1. Uninstall Chrome (go to Control Panel > Add/Remove Programs).

2. Download and install the latest beta version Chrome from 
http://www.google.com/chrome

3. Download the Chrome Channel Chooser from http://dev.chromium.org/getting-
involved/dev-channel/ and select the dev channel. If you already have the Chrome 
Channel Chooser, then there's no need to download it again — just run the program and 
switch channels to dev.

4. After changing to the dev channel, upgrade Chrome the usual way (go to wrench icon 
> About Google Chrome > Update Now), then restart when prompted.

That's it. If you also have multiple Chrome profiles, those profiles will remain 
intact even after uninstalling.
Oh, my bad. You said auto-update, not the manual update. :)
@finnur - thanks for your response. I will wait for the auto-update to happen today. 
If not I will re-install tomorrow.
My problem was three-fold: unable to un-install; unable to re-install; auto-update 
did not work.  

My solution (on Vista):  remove all physical evidence of Chrome (directory 
structure); remove all Chrome entries in registry (using RegEdit); re-boot; follow 
instructions 2 - 4 in Comment 24 (above).

Before removing the directory structure, I made a copy of the User Data directory and 
was able to copy that back in after getting 0.2.153.1 (Official Build 2519) 
successfully installed.

It worked for me ...

Comment 28 by phistuck@gmail.com, Dec 18 2008

Oh, no, the updates thing has manifested itself into a new version. :(
When I click on the "Update now" button, it says "Installing a new version" (or similar) 
but nothing really happens. No installation is done. I tried it a few times already and 
nothing happens, this message stalls and every time I try to open the About window, it 
shows that there is an update and I have the option to click "Update now" as if I never 
touched that button. :(

Comment 29 by phistuck@gmail.com, Dec 18 2008

It could be because my browser crashed due to  issue 5667  :(
I will try and restart my computer - but you should be aware of the problem.

Thank you.

Comment 30 by phistuck@gmail.com, Dec 18 2008

OK, the problem was - that I did not have enough space.
This also, should not happen.
It fills up my drive and it does not install and no error message is being displayed. 
Should I open another case for it?
Yes please.
Same problem with Google Chrome beta 3.0.195.21 attempting to update to 3.0.195.24

I have both Google Chrome and Chromium installed on the same PC (but Chromium not 
running when I check for updates). Chromium is renamed to chromium.exe; both Chrome 
and Chromium are installed into default directories. This configuration exists for 
several months now, and I've made several updates without any problems until 
yesterday.
By "same problem", I meant "Checking for updates" is rotating forever, and never ends.

Comment 34 Deleted

Comment 35 by Deleted ...@, Sep 16 2010

When is google gonna fix this, it just is stuck on cjecking for updates, windows 7

Comment 36 by iam...@gmail.com, Sep 16 2010

@35 - brandonpeters400 - This issue was fixed a year ago. So, if you're having this problem, it's a new problem and I would recommend you submit a new issue instead of commenting on an issue that was entered two years ago.

In the meantime, try uninstalling Chrome, then installing it again.

Project Member

Comment 37 by bugdroid1@chromium.org, Oct 12 2012

Labels: Restrict-AddIssueComment-Commit
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.

Sign in to add a comment