Attempting to update extensions through browser using chrome-gnome-shell fails and messes everything up
Bug #1687288 reported by
Wise Melon
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Chrome GNOME Shell |
Expired
|
High
|
|||
| Ubuntu GNOME |
Confirmed
|
Undecided
|
Unassigned | ||
| chrome-gnome-shell (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
I have found the same issue with Firefox (though I have not yet been able to test in any other browser not using the NPAPI plugin) as I have with Epiphany in Bug #1686796. The only real difference between the Firefox and Epiphany experience is that with Firefox I don't get the "ERROR" message on the site and the extensions do actually seem to update properly, but it turns them all on and doesn't allow me to disable them until I restart the system. It also messed the AO up and made the extensions not function properly.
Further information including screenshots can be found at the bug I mentioned as I basically get all the same stuff. I am running Ubuntu GNOME 17.04 with GNOME 3.24.1.
| Changed in chrome-gnome-shell: | |
| importance: | Unknown → High |
| status: | Unknown → Confirmed |
| Changed in ubuntu-gnome: | |
| status: | New → Confirmed |
| Changed in chrome-gnome-shell (Ubuntu): | |
| status: | New → Confirmed |
| Changed in chrome-gnome-shell: | |
| status: | Confirmed → Incomplete |
| Changed in chrome-gnome-shell: | |
| status: | Incomplete → Expired |
Revision history for this message
| Wise Melon (wise-melon-deactivatedaccount) wrote | #1 |
To post a comment you must log in.
The upstream bug (along with most others) has been moved to their new bug reporting system here: https:/