Public bug reported:
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.
** Affects: chrome-gnome-shell
Importance: High
Status: Confirmed
** Affects: ubuntu-gnome
Importance: Undecided
Status: New
** Affects: chrome-gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Also affects: chrome-gnome-shell (Ubuntu)
Importance: Undecided
Status: New
** Bug watch added: GNOME Bug Tracker #781969
https://bugzilla.gnome.org/show_bug.cgi?id=781969
** Also affects: chrome-gnome-shell via
https://bugzilla.gnome.org/show_bug.cgi?id=781969
Importance: Unknown
Status: Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1687288
Title:
Attempting to update extensions through browser using chrome-gnome-
shell fails and messes everything up
To manage notifications about this bug go to:
https://bugs.launchpad.net/chrome-gnome-shell/+bug/1687288/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
