Update chrome-gnome-shell to version 9 in all supported releases

Bug #1688551 reported by Ken VanDine
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
chrome-gnome-shell (Ubuntu)
Fix Released
Undecided
Ken VanDine
Xenial
Fix Released
Undecided
Ken VanDine
Yakkety
Fix Released
Undecided
Ken VanDine
Zesty
Fix Released
Undecided
Ken VanDine
Artful
Fix Released
Undecided
Ken VanDine

Bug Description

Impact
======
gnome-shell provides a browser plugin so that users can manage GNOME Shell extensions by visiting https:/extensions.gnome.org/ in Firefox, Chrome and compatible browsers.

This extension will stop working in Firefox once users upgrade to Firefox 54. Firefox 54 is scheduled for upstream release June 13, 2017 and 54 Beta has been available since April 19th.

Test Case
=========
- In Ubuntu GNOME, install the updated chrome-gnome-shell
- Open Firefox and browse to https://extensions.gnome.org/local/
- In the list of extensions, turn on the "Applications Menu". The Activities button in the top left of the screen should now read Applications and show a menu of installed apps when clicked.
- Turn off the "Applications Menu". The Applications button should revert to being a simple Activities button.

* Repeat the above test with chromium-browser

* Repeat the above test with Firefox 54 Beta
https://launchpad.net/~mozillateam/+archive/ubuntu/firefox-next

Regression Potential
===================
If there is a problem with this update, users might not be able to easily install new extensions. A workaround is to install extensions with GNOME Software (click the Addons button on the main page) but that only works in Ubuntu 17.04+.

Users can also activate/deactivate and remove extensions with Tweak Tool, installed by default in Ubuntu GNOME.

Other Info
==========
chrome-gnome-shell 9 is available in artful. We want to make version 9 available in -updates for 16.10, 16.04 and 17.04 to ensure no regressions when updating to Firefox 54.

https://wiki.mozilla.org/RapidRelease/Calendar

There are actually two parts to chrome-gnome-shell: a system helper and a browser addon. The chrome-gnome-shell package provides the system helper. You should be promoted to install the browser add on yoru first visit to https://extensions.gnome.org

Changed in chrome-gnome-shell (Ubuntu Artful):
status: New → Fix Released
Changed in chrome-gnome-shell (Ubuntu Xenial):
assignee: nobody → Ken VanDine (ken-vandine)
Changed in chrome-gnome-shell (Ubuntu Yakkety):
assignee: nobody → Ken VanDine (ken-vandine)
Changed in chrome-gnome-shell (Ubuntu Zesty):
assignee: nobody → Ken VanDine (ken-vandine)
Changed in chrome-gnome-shell (Ubuntu Artful):
assignee: nobody → Ken VanDine (ken-vandine)
Jeremy Bícha (jbicha)
description: updated
Revision history for this message
Steve Langasek (vorlon) wrote : Please test proposed package

Hello Ken, or anyone else affected,

Accepted chrome-gnome-shell into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/chrome-gnome-shell/9-0ubuntu1~ubuntu16.10 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in chrome-gnome-shell (Ubuntu Yakkety):
status: New → Fix Committed
tags: added: verification-needed
Changed in chrome-gnome-shell (Ubuntu Zesty):
status: New → Fix Committed
Revision history for this message
Steve Langasek (vorlon) wrote :

Hello Ken, or anyone else affected,

Accepted chrome-gnome-shell into zesty-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/chrome-gnome-shell/9-0ubuntu1~ubuntu17.04 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Revision history for this message
Steve Langasek (vorlon) wrote :

Hello Ken, or anyone else affected,

Accepted chrome-gnome-shell into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/chrome-gnome-shell/9-0ubuntu1~ubuntu16.04.2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Changed in chrome-gnome-shell (Ubuntu Xenial):
status: New → Fix Committed
Jeremy Bícha (jbicha)
tags: added: verification-done-zesty verification-failed-xenial verification-failed-yakkety
removed: verification-needed
Revision history for this message
Jeremy Bícha (jbicha) wrote :

I verified chrome-gnome-shell 9.0ubuntu1~ubuntu17.04 on Ubuntu GNOME 17.04. After installing the update, I restarted my computer to ensure that there wasn't an old version of the chrome-gnome-shell background service running in the background. I verified that I was able to activate and deactivate the Applications Menu extension in Firefox 53, Firefox 54 Beta and chromium-browser.

For 16.04 and 16.10, a packaging regression was accidentally introduced so a fix for that has been uploaded to the SRU queues. The regression breaks chrome-gnome-shell integration in Firefox, but Chrome & Chromium were not affected.

Revision history for this message
Adam Conrad (adconrad) wrote :

Hello Ken, or anyone else affected,

Accepted chrome-gnome-shell into xenial-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/chrome-gnome-shell/9-0ubuntu1~ubuntu16.04.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

tags: added: verification-needed
Revision history for this message
Adam Conrad (adconrad) wrote :

Hello Ken, or anyone else affected,

Accepted chrome-gnome-shell into yakkety-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/chrome-gnome-shell/9-0ubuntu1~ubuntu16.10.1 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed.Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, and change the tag from verification-needed to verification-done. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed. In either case, details of your testing will help us make a better decision.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance!

Revision history for this message
Jeremy Bícha (jbicha) wrote :

I verified chrome-gnome-shell 9.0ubuntu1~ubuntu16.10.1 on Ubuntu GNOME 16.10 and chrome-gnome-shell 9-0ubuntu1~ubuntu16.04.3 on Ubuntu GNOME 16.04 LTS.

After installing the update, I restarted my computer to ensure that there wasn't an old version of the chrome-gnome-shell background service running in the background. I verified that I was able to activate and deactivate the Applications Menu extension in Firefox 53, Firefox 54 Beta and chromium-browser.

tags: added: verification-done xenial yakkety zesty
removed: verification-done-zesty verification-failed-xenial verification-failed-yakkety verification-needed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package chrome-gnome-shell - 9-0ubuntu1~ubuntu17.04

---------------
chrome-gnome-shell (9-0ubuntu1~ubuntu17.04) zesty-proposed; urgency=medium

  * Backport to zesty (LP: #1688551)
  * debian/watch
  * -debian/patches/git_handle-gnome-shell-not-running.patch merged upstream

 -- Ken VanDine <email address hidden> Thu, 04 May 2017 11:11:47 -0400

Changed in chrome-gnome-shell (Ubuntu Zesty):
status: Fix Committed → Fix Released
Revision history for this message
Brian Murray (brian-murray) wrote : Update Released

The verification of the Stable Release Update for chrome-gnome-shell has completed successfully and the package has now been released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

tags: added: verification-done-xenial verification-done-yakkety
removed: verification-done
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package chrome-gnome-shell - 9-0ubuntu1~ubuntu16.04.3

---------------
chrome-gnome-shell (9-0ubuntu1~ubuntu16.04.3) xenial; urgency=medium

  * Revert accidental dropping of this change:
  * debian/rules: Force Firefox helper to use non-multiarch directory
    (not needed with zesty's cmake)

chrome-gnome-shell (9-0ubuntu1~ubuntu16.04.2) xenial-proposed; urgency=medium

  * Backport to xenial (LP: #1688551)
  * debian/watch
  * -debian/patches/git_handle-gnome-shell-not-running.patch merged upstream

 -- Jeremy Bicha <email address hidden> Wed, 31 May 2017 15:42:52 -0400

Changed in chrome-gnome-shell (Ubuntu Xenial):
status: Fix Committed → Fix Released
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package chrome-gnome-shell - 9-0ubuntu1~ubuntu16.10.1

---------------
chrome-gnome-shell (9-0ubuntu1~ubuntu16.10.1) yakkety; urgency=medium

  * Revert accidental dropping of this change:
  * debian/rules: Force Firefox helper to use non-multiarch directory
    (not needed with zesty's cmake)

chrome-gnome-shell (9-0ubuntu1~ubuntu16.10) yakkety-proposed; urgency=medium

  * Backport to yakkety (LP: #1688551)
  * debian/watch
  * -debian/patches/git_handle-gnome-shell-not-running.patch merged upstream

 -- Jeremy Bicha <email address hidden> Wed, 31 May 2017 15:53:11 -0400

Changed in chrome-gnome-shell (Ubuntu Yakkety):
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.