Hello everybody We have an installation base of about 100 users for a web application based on Gears. First internal distribution of the Gears MSI package was in December 2009. Since it is an enterprise setup the rights of the individual Windows users are very restrictive.
As new versions were available after December 2009, Gears seems to be able (in the described restrictive environment) to install some new components, but not all (we assume). Consequently it fails with the following popup message when a web application tries to use Gears: "A Gears update has been downloaded. Please close all browser windows to complete the upgrade process." Closing the browser does not help, neither does a reboot of the system. The message just re-appears the next time an application tries to use Gears. Gears cannot be used anymore. The version collision detection and subsequent error message is IMHO located in the function OneTimeDetectVersionCollision() in base/common/ detect_version_collision_win32.cc. The string of the message itself seems only to be produced in the function GetVersionCollisionErrorString() in base/common/ detect_version_collision_win32.cc and has the StringID "IDS_VERSION_COLLISION_TEXT". Can anybody explain this behavior and suggest steps to take to prevent this deadlock situation? How can we disable the auto update mechanism of Gears? Thank you very much for any valuable feedback! Regards Nicola
