Comment #43 on issue 1565 by fam@live.nl: Don't make GoogleUpdate
always-resident
http://code.google.com/p/chromium/issues/detail?id=1565
It is running all the time.
My version is indeed 1.2.183.7
--
You received this message because you are listed in the owner
or CC fields of this
Comment #41 on issue 1565 by fam@live.nl: Don't make GoogleUpdate
always-resident
http://code.google.com/p/chromium/issues/detail?id=1565
It still keeps running every minute at my pc (vista)
--
You received this message because you are listed in the owner
or CC fields of this issue, or
Comment #42 on issue 1565 by ddor...@google.com: Don't make GoogleUpdate
always-resident
http://code.google.com/p/chromium/issues/detail?id=1565
Is GoogleUpdate.exe running all the time or does a new process get launched
once per
minute? If it is the former, please check that you have
Comment #39 on issue 1565 by divi...@hotmail.com: Don't make GoogleUpdate
always-resident
http://code.google.com/p/chromium/issues/detail?id=1565
http://google-opensource.blogspot.com/2009/07/google-update-regularly-scheduled.html
Add label: Fixed.
--
You received this message because you
Comment #34 on issue 1565 by fam@live.nl: Don't make GoogleUpdate
always-resident
http://code.google.com/p/chromium/issues/detail?id=1565
It has been reported in
http://code.google.com/p/omaha/issues/list. This is now an open-source
program just
like chromium...
--
You received this
Comment #33 on issue 1565 by leonard.iozzi: Don't make GoogleUpdate
always-resident
http://code.google.com/p/chromium/issues/detail?id=1565
This is just one more thread in which Google ignores this issue.
I uninstalled all Google apps and google update still runs. I consider that
not only
Comment #32 on issue 1565 by fam@live.nl: Don't make GoogleUpdate
always-resident
http://code.google.com/p/chromium/issues/detail?id=1565
You can disable it using Windows Defender -- Tools -- 4th icon -- Google
Update --
Disable.
But indeed it is very annoying. (Thats why I disabled
Comment #31 on issue 1565 by slautie: Don't make GoogleUpdate
always-resident
http://code.google.com/p/chromium/issues/detail?id=1565
I totally agree with all the comments. The worse with the updater is that
when I
start my vista system, every time I get a permission request to start it...
Comment #28 on issue 1565 by Tda7000: Don't make GoogleUpdate
always-resident
http://code.google.com/p/chromium/issues/detail?id=1565
I don't want your automatic updater either. At least Apple gives you the
option not
to install it. I'd rather use Safari than Chrome anyway.
Automatic
Comment #29 on issue 1565 by goo...@synetech.cjb.net: Don't make
GoogleUpdate always-resident
http://code.google.com/p/chromium/issues/detail?id=1565
Even better would be a portable version for users who know what “an any
key” is.
--
You received this message because you are listed in the
Comment #27 on issue 1565 by alf.p.steinbach: Don't make GoogleUpdate
always-resident
http://code.google.com/p/chromium/issues/detail?id=1565
I note that the team's arguments are of the sort We need to do it this way
because
we can imagine some silly ways that Won't Work.
That's usual
Comment #26 on issue 1565 by loyukfai: Don't make GoogleUpdate
always-resident
http://code.google.com/p/chromium/issues/detail?id=1565
I can't speak for everybody but I do think many of us don't mind Chrome
updating
itself when it's running. It's the usage of a separated and constantly
Comment #25 on issue 1565 by zastrowm: Don't make GoogleUpdate
always-resident
http://code.google.com/p/chromium/issues/detail?id=1565
Although I don't want the updater running 24x7, I do like the silent
updates. The
simplicity and non-clutter of chrome is what made me switch from firefox
Comment #23 on issue 1565 by cl...@positech.co.uk: Don't make GoogleUpdate
always-resident
http://code.google.com/p/chromium/issues/detail?id=1565
I agree that this is hacky and annoying. I don't need to use googles
browser badly
enough to tolerate it spamming my processes list
--
You
Comment #22 on issue 1565 by blackboxxx: Don't make GoogleUpdate
always-resident
http://code.google.com/p/chromium/issues/detail?id=1565
I think the current behavior of GoogleUpdate.exe is justifiable for the
sake of
security. However, it could be a little more transparent.
For example, I
Comment #20 on issue 1565 by t...@crowdersoftware.com: Don't make
GoogleUpdate always-resident
http://code.google.com/p/chromium/issues/detail?id=1565
On the update curfluffle:
I'm glad to hear the team are looking at fixing this problem. The keys to
keep in
mind for that are 1)
Comment #16 on issue 1565 by pesotra...@yahoo.com: Don't make GoogleUpdate
always-resident
http://code.google.com/p/chromium/issues/detail?id=1565
GoogleUpdate.exe is the WORST part of the browser and reason enough for
many to
refuse to use this otherwise fine browser. I simply HATE
Comment #13 on issue 1565 by [EMAIL PROTECTED]: Don't make GoogleUpdate
always-resident
http://code.google.com/p/chromium/issues/detail?id=1565
One of the reasons that doesn't work is that we'd like the update mechanism
to be
able to recover from a bad update being pushed out. If we push
Comment #14 on issue 1565 by omattos: Don't make GoogleUpdate
always-resident
http://code.google.com/p/chromium/issues/detail?id=1565
erikkay:
You could run the update app on program startup AND on a windows schedule
(say once per
week). That way if an update goes bad, it can be repaired
Comment #15 on issue 1565 by johnmee: Don't make GoogleUpdate
always-resident
http://code.google.com/p/chromium/issues/detail?id=1565
Thanks erikkay for explaining the pickle.
If the update occurs only when the browser is in use (eg: irritating prompt
for
restart during session) then the
Comment #12 on issue 1565 by [EMAIL PROTECTED]: Don't make GoogleUpdate
always-resident
http://code.google.com/p/chromium/issues/detail?id=1565
I'm not sure about the scheduled tasks alternative, but perhaps google
update could
kick off asynchronously when google software is started and
Issue 1565: Don't make GoogleUpdate always-resident
http://code.google.com/p/chromium/issues/detail?id=1565
Comment #6 by stasgold:
Agree,
I think no need to schedule it also: in my view it's enough to check for
update every
time Chrome is starting to run ( just the way it's done in FireFox )
Issue 1565: Don't make GoogleUpdate always-resident
http://code.google.com/p/chromium/issues/detail?id=1565
Comment #7 by stasgold:
It would be nice not to schedule it , but to check for update every
time Chrome is starting up ( just the way it's done in FireFox )
--
You received this
Issue 1565: Don't make GoogleUpdate always-resident
http://code.google.com/p/chromium/issues/detail?id=1565
Comment #8 by rustamabd:
I hate GoogleUpdate.exe! Why can't Google software check for updates on
startup?
--
You received this message because you are listed in the owner
or CC
Issue 1565: Don't make GoogleUpdate always-resident
http://code.google.com/p/chromium/issues/detail?id=1565
Comment #2 by [EMAIL PROTECTED]:
(No comment was entered for this change.)
Issue attribute updates:
Cc: [EMAIL PROTECTED]
--
You received this message because you are listed in
Issue 1565: Don't make GoogleUpdate always-resident
http://code.google.com/p/chromium/issues/detail?id=1565
Comment #3 by [EMAIL PROTECTED]:
(No comment was entered for this change.)
Issue attribute updates:
Labels: -Area-Unknown Area-Installer
--
You received this message because
Issue 1565: Don't make GoogleUpdate always-resident
http://code.google.com/p/chromium/issues/detail?id=1565
Comment #4 by [EMAIL PROTECTED]:
Nice idea, it looks very bad, that GoogleUpdate is watching all the time in
my processes.
--
You received this message because you are listed in the
Issue 1565: Don't make GoogleUpdate always-resident
http://code.google.com/p/chromium/issues/detail?id=1565
Comment #5 by gtucker:
GoogleUpdate.exe actually exists in the scheduler. And services. And
runs, at
startup, from the Windows registry. It's a real pain to remove
completely.
Issue 1565: Don't make GoogleUpdate always-resident
http://code.google.com/p/chromium/issues/detail?id=1565
Comment #1 by kingfinn:
I removed the entire Google update directory just to get rid of this.
--
You received this message because you are listed in the owner
or CC fields of this
29 matches
Mail list logo
