user_manager.js error when reinstalling Chrome
Reported by
jocdelad...@gmail.com,
Jan 6 2017
|
|||||
Issue description
Chrome Version: Chrome 55 (it happens with new installations of Chrome)
Hi, I would like to inform of a bug which has been reported in the Spanish Chrome Forum several times.
All the users complaining about this issue explain the following:
1. A malicious extension is installed in Chrome.
2. They uninstall Chrome.
3. When Chrome is uninstalled, some users say that they "cleaned their computer". I have requested them to clarify what this means, and for the time being two of them have specified that they ran CCleaner.
4. They install Chrome again.
5. A window entitled "Google Chrome" with the Chrome logo in the lower-left corner and a gray background appears, but the user cannot do anything. (see the attached screenshot)
Another thing the users have in common is that they use Windows (versions 7 and 10).
Oh, and a user also said that the following error appears in that screen (probably he saw this in the dev tools):
Uncaught TypeError: Cannot set property 'hidden' of null
at UserManager.showScreen (user_manager.js:1477)
at Function.UserManager.showUserManagerScreen (user_manager.js:6167)
at <anonymous>:1:19
I was not able to reproduce this bug by myself in a Windows 10 virtual machine, but as it is a recurring topic in the forum I thought it would be worth looking into this to check if it is an actual Chromium bug.
BTW, I attach the threads in which users complain about this issue (it's all in Spanish hehe):
* https://productforums.google.com/forum/#!category-topic/chrome-es/BTqyMsXMmXI;noredirect=true (main thread where we're redirecting all users)
* https://productforums.google.com/forum/#!category-topic/chrome-es/4ONdr81T60Q;noredirect=true
* https://productforums.google.com/forum/#!category-topic/chrome-es/C7Oeh80eD9I;noredirect=true
* https://productforums.google.com/forum/#!category-topic/chrome-es/m2M7UKSBzHU;noredirect=true
And this is a link to a thread about this issue in the Spanish private forums:
* https://productforums.google.com/forum/#!private-topic/chrome-es+rs-mentor/CFs_9iyKsMA
If there's anything else I can help you with, or anything you want me to ask the users in the forum, please, let me know.
,
Jan 10 2017
jocdeladria@ please follow the below steps which may resolve the issue you are facing. 1. Uninstall google chrome. 2. Download the chrome cleanup tool from "https://bugs.chromium.org/p/chromium/issues/detail?id=678233" and run it. 3. In the machine go to "C:\Users\*****\AppData\Local\Google" and delete the chrome folder 4. Download & Install the latest stable version from "https://www.google.co.in/chrome/browser/desktop/" After the fresh installation, retry the scenario and let us know your observations.
,
Jan 10 2017
Sorry kkaluri@chromium.org In steep 2 i think that the correct link is https://www.google.es/chrome/cleanup-tool/ Is that correct? Regards, Nico.
,
Jan 10 2017
Hi again! Nico: I think you're right :P kkaluri@ I'm not facing this issue myself, but a lot of users in the Google Product Forums are actually facing it, that's why I reported it. Nico and I have asked them to carry out the steps in #2, so we'll let you know about the results. Thanks ;)
,
Jan 18 2017
Thank you for providing more feedback. Adding requester "kkaluri@chromium.org" for another review and adding "Needs-Review" label for tracking. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Mar 13 2017
Cleaning up "Needs-Review" label as we are not using this label for triage. Ref bug 684919
,
Mar 13 2017
,
Mar 7 2018
jocdeladria@, Nico@: Is it possible to confirm if the issue was resolved post reinstalling chrome as suggested? If not, kindly update with latest observations.
,
Mar 7 2018
Hi! As I stated in the original bug report and in #4: "I was not able to reproduce this bug by myself in a Windows 10 virtual machine", "but a lot of users in the Google Product Forums are actually facing it, that's why I reported it". I just saw in the private Forums that a year ago a Top Contributor reminded us that a user came to the Forum to tell us that the steps provided in this issue solved the issue: https://productforums.google.com/d/msg/chrome-es/yqrC3mNRNP8/_YyJYCxFEQAJ Nevertheless, we haven't seen in the Forum any further reports of this issue, so I guess this is not a problem anymore and we could close this issue as WontFix. Do you think this would be the best way to procede? Thanks for revisiting this issue and pinging us mailtoga@ ;)
,
May 30 2018
As per comment #9 closing this issue |
|||||
►
Sign in to add a comment |
|||||
Comment 1 by ajha@chromium.org
, Jan 9 2017