New issue
Advanced search Search tips
Note: Color blocks (like or ) mean that a user may not be available. Tooltip shows the reason.

Issue 777658 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 3
Type: Bug



Sign in to add a comment

Extensions not working on Ubuntu for build 62.0.3202.62

Reported by mich...@theguestbook.com, Oct 24 2017

Issue description

Chrome Version       : 62.0.3202.62 (Official Build) (64-bit)


What steps will reproduce the problem?

All my Chrome extensions are corrupted on my machine:
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04.3 LTS
Release:	16.04
Codename:	xenial 

What is the expected result?
Working extensions

What happens instead?
Extensions don't work, some say, "This extension may have been corrupted."

Please provide any additional information below. Attach a screenshot if
possible.

 
chrome-bug.png
91.0 KB View Download
Labels: Needs-Triage-M62
Cc: sc00335...@techmahindra.com
Components: Platform>Extensions
Labels: Needs-Feedback Triaged-ET OS-Linux
Unable to reproduce the issue on the reported chrome version 62.0.3202.62 and on the latest canary 64.0.3248.0 using Windows 10, Ububtu 14.04 and Mac 10.12.6 
Attaching the screen cast of the same.

@Reporter: Could you please check the issue by creating fresh profile. And aslo please check by uninstalling and re-installing chrome. Any further inputs from your end in triaging the issue is very helpful.

Thanks!
777658.ogv
2.6 MB View Download
@Reporter here. It breaks current installed extensions when Chrome updated from a prior version. Installing / re-installing the extension works.
Project Member

Comment 5 by sheriffbot@chromium.org, Oct 24 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "sc00335628@techmahindra.com" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Status: WontFix (was: Unconfirmed)
As per c#4, the issue seems to be resolved. Hence closing the issue as won't fix
@Reporter: Please feel free to file a new issue if you still encounter any such issues.

Sign in to add a comment